Network Working Group Kamran Raza Internet Draft Cisco Systems Intended Status: Standards Track Expiration Date: October 27, 2010 April 28, 2010 LDP Typed Wildcard PW FEC Elements draft-raza-l2vpn-pw-typed-wc-fec-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on October 27, 2010. Copyright Notice Copyright (c) 2010 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 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 BSD License. Raza Expires October 2010 [Page 1] Internet-Draft LDP Typed Wildcard PW FEC Elements April 2010 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. Conventions used in this document The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Table of Contents 1. Introduction .................................................. 2 2. Typed Wildcard for PWid FEC Element ........................... 3 3. Typed Wildcard for Generalized PWid FEC Element ............... 3 4. Security Considerations ....................................... 3 5. IANA Considerations ........................................... 4 6. Acknowledgments ............................................... 4 7. References .................................................... 4 7.1 Normative References ...................................... 4 7.2 Informative References .................................... 4 Author's Address.................................................. 4 1. Introduction An extension [TYPED-WC] to the Label Distribution Protocol (LDP) [RFC5036] 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. [RFC4447] defines the "PWid FEC Element" and "Generalized PWid FEC Element" but it does not specify Typed Wildcard format for these elements. This document specifies the format of the Typed Wildcard FEC for the "PWid FEC Element" and the "Generalized PWid FEC Element" defined in [RFC4447]. The procedures for Typed Wildcard processing for PWid and Generalized PWid FEC Elements are same as described in [TYPED-WC] for any typed wildcard FEC Element type. Raza Expires October 2010 [Page 2] Internet-Draft LDP Typed Wildcard PW FEC Elements April 2010 2. Typed Wildcard for PWid FEC Element The format of the PWid FEC Typed Wildcard FEC is: 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Typed Wcard | Type = PWid | Len = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Format of PWid Typed Wildcard FEC Element where: Typed Wcard (one octet): as specified in [TYPED-WC] FEC Element Type (one octet): PWid FEC Element (type 0x80 [RFC4447]) Len FEC Type Info (one octet): Zero. (There is no additional FEC info) 3. Typed Wildcard for Generalized PWid FEC Element The format of the Generalized PWid FEC Typed Wildcard FEC is: 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Typed Wcard | Type=Gen.PWid | Len = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: Format of Generalized PWid Typed Wildcard FEC Element where: Typed Wcard (one octet): as specified in [TYPED-WC] FEC Element Type (one octet): Generalized PWid FEC Element (type 0x81 [RFC4447]) Len FEC Type Info (one octet): Zero. (There is no additional FEC info) When Generalized PWid FEC Typed Wildcard is used, "PW Grouping ID TLV" [RFC4447] MUST NOT be present in the same message. 4. Security Considerations No new security considerations beyond that apply to the base LDP specification [RFC5036], [RFC4447] and [MPLS_SEC] apply to the use of the PW Typed Wildcard FEC Element types described in this document. Raza Expires October 2010 [Page 3] Internet-Draft LDP Typed Wildcard PW FEC Elements April 2010 5. IANA Considerations This document defines no new element for IANA Consideration. 6. Acknowledgments The author would like to thank Eric Rosen, M. Siva, and Zafar Ali for review of this document. This document was prepared using 2-Word-v2.0 template.dot. 7. References 7.1. Normative References [RFC5036] Andersson, L., Menei, I., and Thomas, B., Editors, "LDP Specification", RFC 5036, September 2007. [TYPED-WC] Thomas, B., Asati, R., and Minei, I., "LDP Typed Wildcard FEC", draft-ietf-mpls-ldp-typed-wildcard-07.txt, Work in Progress, March 2010. [RFC4447] L. Martini, Editor, E. Rosen, El-Aawar, T. Smith, G. Heron, "Pseudowire Setup and Maintenance using the Label Distribution Protocol", RFC 4447, April 2006. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC2119, March 1997. 7.2. Informative References [MPLS_SEC] Fang, L. et al., "Security Framework for MPLS and GMPLS Networks", draft-ietf-mpls-mpls-and-gmpls-security-framework- 05.txt, Work in Progress, March 2009. Author's Address: Syed Kamran Raza Cisco Systems, Inc., 2000 Innovation Drive, Kanata, ON K2K-3E8, Canada. E-mail: skraza@cisco.com Raza Expires October 2010 [Page 4]