datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for PWid and Generalized PWid FEC Elements
draft-ietf-pwe3-pw-typed-wc-fec-03

RFC
Document Stream: IETF
Last updated: 2012-02-06
Replaces: draft-raza-pwe3-pw-typed-wc-fec
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html
IETF State: In WG Last Call (pwe3)
Document shepherd:Andrew Malis
Shepherd writeup
Consensus:Unknown
IESG State: RFC 6667
IANA Action State: No IC 
On agenda of 2012-04-12 IESG telechat
Responsible AD: Stewart Bryant
IESG Note: Andrew Malis (amalis@gmail.com) is the document shepherd.
Send notices to: pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-pw-typed-wc-fec@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-pwe3-pw-typed-wc-fec.

Abstract:
The "Typed Wildcard Forwarding Equivalence Class (FEC) Element" defines an extension to the Label Distribution Protocol (LDP) that can be used when requesting, withdrawing, or releasing all label bindings for a given FEC Element type is desired. However, a Typed Wildcard FEC Element must be individually defined for each FEC Element type. This specification defines the Typed Wildcard FEC Elements for the Pseudowire Identifier (PWid) (0x80) and Generalized PWid (0x81) FEC Element types. [STANDARDS-TRACK]

Authors:
Kamran Raza <skraza@cisco.com>
Sami Boutros <sboutros@cisco.com>
Carlos Pignataro <cpignata@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)