Internet Engineering Task Force (IETF) K. Raza
Request for Comments: 6667 S. Boutros
Category: Standards Track C. Pignataro
ISSN: 2070-1721 Cisco Systems
July 2012
LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for
PWid and Generalized PWid FEC Elements
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6667.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Raza, et al. Standards Track [Page 1]RFC 6667 PWid and Gen. PWid Typed Wildcard FEC July 2012
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may not be modified, and derivative works of it may not
be created, except to format it for publication as an RFC or to
translate it into languages other than English.
Table of Contents
1. Introduction ....................................................2
2. Typed Wildcard for PW FEC Elements ..............................3
3. Applicability Statement .........................................4
4. Operation .......................................................4
4.1. PW Consistency Check .......................................5
4.2. PW Graceful Shutdown .......................................5
4.3. Wildcard PW Status .........................................5
4.4. Typed Wildcard MAC Withdrawal in VPLS ......................6
5. Security Considerations .........................................6
6. Acknowledgments .................................................7
7. References ......................................................7
7.1. Normative References .......................................7
7.2. Informative References .....................................7
1. Introduction
An extension to the Label Distribution Protocol (LDP) [RFC5036]
defines the general notion of a "Typed Wildcard Forwarding
Equivalence Class (FEC) Element" [RFC5918]. This can be used when
requesting, releasing, or withdrawing all label bindings for a given
type of FEC Element is desired. However, a Typed Wildcard FEC
Element must be individually defined for each type of FEC Element.
[RFC4447] defines the "PWid FEC Element" and "Generalized PWid FEC
Element", but does not specify the Typed Wildcard format for these
elements. This document specifies the format of the Typed Wildcard
FEC Element for the "PWid FEC Element" and "Generalized PWid FEC
Element". The procedures for Typed Wildcard processing for PWid and
Generalized PWid FEC Elements are the same as described in [RFC5918]
for any Typed Wildcard FEC Element type.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
datatracker.ietf.org