LDP Typed Wildcard PW FEC Elements
draft-raza-l2vpn-pw-typed-wc-fec-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Syed Kamran Raza , Sami Boutros | ||
| Last updated | 2010-07-08 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
An extension to the Label Distribution Protocol (LDP) defines the general notion of a "Typed Wildcard Forwarding Equivalence Class (FEC) Element". This can be used when it is desired to request all label bindings for a given type of FEC Element, or to release or withdraw all label bindings for a given type of FEC element. However, a typed wildcard FEC element must be individually defined for each type of FEC element. This specification defines the typed wildcard FEC elements for the Pseudowire Identifier (PW Id) and Generalized Pseudowire Identifier (Gen. PW Id) FEC types.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)