Network Working Group M. Chen Internet-Draft L. Zheng Intended status: Standards Track Huawei Technologies Ltd. Expires: May 3, 2012 October 31, 2011 ICC_Operator_ID Attachment Individual Identifier (AII) draft-chen-pwe3-mpls-tp-aii-icc-01 Abstract This document defines a new Attachment Individual Identifier (AII) type which could be used when ICC_Operator_ID is used to uniquely identify an operator. The new AII (ICC_Operator_ID AII) consists a ICC_Operator_ID, a prefix and a AC ID field. Requirements Language 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]. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on May 3, 2012. Copyright Notice Copyright (c) 2011 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 Chen & Zheng Expires May 3, 2012 [Page 1] Internet-Draft ICC AII October 2011 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 Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. ICC_Operator_ID AII . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Chen & Zheng Expires May 3, 2012 [Page 2] Internet-Draft ICC AII October 2011 1. Introduction RFC6370 [RFC6370] specifies an initial set of identifiers to be used in the Multiprotocol Label Switching Transport Profile (MPLS-TP). The Global_ID is defined in RFC6370 [RFC6370] to uniquely identify an operator. [I.D.draft-ietf-mpls-tp-itu-t-identifiers] [I-D.ietf-mpls-tp-itu-t-identifiers] specifies the ICC_Operator_ID, an alternative way to uniquely identify an operator based on ITU-T conventions. RFC4447 [RFC4447] defines the signaling mechanisms for establishing point- to-point pseudowires (PWs) between two provider edge (PE) nodes. It defines the format of the GID FEC TLV and the use and semantics of the attachment group identifier (AGI). Two types of Attachment Individual Identifier (AII) have been defined. AII Type 1 defined in RFC6074[RFC6074] has a fixed-length 32-bit value that is unique within the scope of the local Provider Edge (PE). AII Type 2 defined in RFC5003 [RFC5003] consists a 4-octet length Global ID, a 32-bit prefix field and a 4-octet attachment circuit identifier (AC ID) field. Existing AIIs do not support ICC_Operator_ID based identifier. This document defines a new AII type (ICC_Operator_ID AII). It use a combination of a 8-octet length ICC_Operator_ID, a 4-octet length prefix and a 4-octet length AC ID to create globally unique AII values. 2. ICC_Operator_ID AII ICC_Operator_ID AII has the consistent structure with AII Type 2, which permits varying levels of AII summarization to take place, thus reducing the scaling burden on the AII distribution mechanisms and PE memory as described in RFC5003[RFC5003]. The encoding of ICC_Operator_ID AII is as follows: Chen & Zheng Expires May 3, 2012 [Page 3] Internet-Draft ICC AII October 2011 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AII Type=03 | Length | ICC_Operator_ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ICC_Operator_ID(contd.) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ICC_Operator_ID(contd.) | Prefix | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Prefix(contd.) | AC ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AC ID(contd.) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1. ICC_Operator_ID AII AII Type: To be allocated by IANA (0x03 is recommended). Length: 1 octet in length, specifies the length of the value field in octets. The length is set to 14. ICC_Operator_ID: ICC_Operator_ID of the sender node. As defined in [I-D.ietf-mpls-tp-itu-t-identifiers], the ICC_Operator_ID is formed by Country Code (CC) and ICC(ITU-T Carrier Code ) as CC::ICC. The ICC itself is a string of one to six characters, global uniqueness is assured by concatenating the ICC with a CC. The Country Code (alpha-2) is a string of two alphabetic characters represented with upper case letters (i.e., A-Z). When the length of a ICC_Operator_ID string is less than 8 octets, the higher-order unused octets of the ICC_Operator_ID field MUST be set to zero. Prefix: Same as [RFC5003]. AC ID field: Same as [RFC5003]. 2.1. Procedures Since the operator could be identified by either the Global_ID or ICC_Operator_ID, the two ends of a PW may use the different AII type. During the Label Mapping procedure, one end may not map the TAI to one of its Forwarders. In this case, it MUST send a Label Release message to the other end, with a Status Code of "Unassigned/ Unrecognized TAI", and the processing of the Label Mapping message is complete. 3. IANA Considerations IANA maintains a registry of "Attachment Individual Identifier (AII) Chen & Zheng Expires May 3, 2012 [Page 4] Internet-Draft ICC AII October 2011 Type". This document request IANA to assign a new AII Type as follows: AII Type ICC_Operator_ID 0x03(TBD) 4. Security Considerations This draft does not introduce any new security issues, the security mechanisms defined in [RFC5003] apply here. 5. Acknowledgements 6. References 6.1. Normative References [I-D.ietf-mpls-tp-itu-t-identifiers] Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP Identifiers Following ITU-T Conventions", draft-ietf-mpls-tp-itu-t-identifiers-01 (work in progress), October 2011. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 6.2. Informative References [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. Heron, "Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)", RFC 4447, April 2006. [RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto, "Attachment Individual Identifier (AII) Types for Aggregation", RFC 5003, September 2007. [RFC6074] Rosen, E., Davie, B., Radoaca, V., and W. Luo, "Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)", RFC 6074, January 2011. [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. Chen & Zheng Expires May 3, 2012 [Page 5] Internet-Draft ICC AII October 2011 Authors' Addresses Mach Chen Huawei Technologies Ltd. Q14 Huawei Campus, No. 156 Beiqing Road, Hai-dian District Beijing 100095 China Email: mach@huawei.com Lianshu Zheng Huawei Technologies Ltd. Q14 Huawei Campus, No. 156 Beiqing Road, Hai-dian District Beijing 100095 China Email: vero.zheng@huawei.com Chen & Zheng Expires May 3, 2012 [Page 6]