idnits 2.17.1 draft-chen-pwe3-mpls-tp-aii-icc-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 164 has weird spacing: '...ntifier thi...' -- The document date (August 12, 2012) is 4275 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-08) exists of draft-ietf-mpls-tp-itu-t-identifiers-03 -- Obsolete informational reference (is this intentional?): RFC 4447 (Obsoleted by RFC 8077) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Chen 3 Internet-Draft L. Zheng 4 Intended status: Standards Track Huawei Technologies Ltd. 5 Expires: February 13, 2013 August 12, 2012 7 ICC_Operator_ID Attachment Individual Identifier (AII) 8 draft-chen-pwe3-mpls-tp-aii-icc-02 10 Abstract 12 This document defines a new Attachment Individual Identifier (AII) 13 type which could be used to identify the pseudowire endpoint when 14 ICC_Operator_ID is used to uniquely identify an operator in MPLS-TP 15 networks. The new AII (ICC_Operator_ID AII) consists a 16 ICC_Operator_ID, a prefix and a AC ID field. 18 Requirements Language 20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 21 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 22 document are to be interpreted as described in RFC 2119 [RFC2119]. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on February 13, 2013. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. ICC_Operator_ID AII . . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 4 61 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 63 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 66 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 69 1. Introduction 71 RFC6370 [RFC6370] specifies an initial set of identifiers to be used 72 in the Multiprotocol Label Switching Transport Profile (MPLS-TP). 73 The Global_ID is defined in RFC6370 [RFC6370] to uniquely identify an 74 operator. [I.D.draft-ietf-mpls-tp-itu-t-identifiers] 75 [I-D.ietf-mpls-tp-itu-t-identifiers] specifies the ICC_Operator_ID, 76 an alternative way to uniquely identify an operator based on ITU-T 77 conventions. We call both Global_ID and ICC_Operator_ID as Operator 78 ID in this document. 80 RFC4447 [RFC4447] defines the signaling mechanisms for establishing 81 point- to-point pseudowires (PWs) between two provider edge (PE) 82 nodes. It defines the PWid FEC element and Generalized ID (GID) FEC 83 element. In GID FEC element, the attachment individual identifiers 84 (AIIs) in conjunction with an attachment group identifier (AGI), 85 serve as PW endpoint identifiers. 87 Six types of Attachment Individual Identifier (AII) have been 88 defined. AII Type 1 defined in RFC6074[RFC6074] has a fixed-length 89 32-bit value that is unique within the scope of the local Provider 90 Edge (PE). AII Type 2 defined in RFC5003 [RFC5003] consists a 91 4-octet length Global ID, a 32-bit prefix field and a 4-octet 92 attachment circuit identifier (AC ID) field. AII type 3-6 has been 93 defined by MFA Forum. Existing AIIs do not support ICC based 94 identifier. 96 This document defines a new AII type (ICC_Operator_ID AII). It use a 97 combination of a 8-octet length ICC_Operator_ID, a 4-octet length 98 prefix and a 4-octet length AC ID to create globally unique AII 99 values. The ICC_Operator_ID AII could be used to identify the 100 pseudowire endpoint when ICC_Operator_ID is used to uniquely identify 101 an operator in MPLS-TP networks. A typical use for this AII in 102 MPLS-TP enviroment is in Pseudowire Path Identifier. 104 2. ICC_Operator_ID AII 106 ICC_Operator_ID AII has the consistent structure with AII Type 2, 107 which permits varying levels of AII summarization to take place, thus 108 reducing the scaling burden on the AII distribution mechanisms and PE 109 memory as described in RFC5003[RFC5003]. ICC_Operator_ID AII use a 110 combination of a 8-octet length ICC_Operator_ID, a 4-octet length 111 prefix and a 4-octet length AC ID to create globally unique AII 112 values. The encoding of ICC_Operator_ID AII is as follows: 114 0 1 2 3 115 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 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | AII Type | Length | ICC_Operator_ID | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | ICC_Operator_ID(contd.) | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | ICC_Operator_ID(contd.) | Prefix | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Prefix(contd.) | AC ID | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | AC ID(contd.) | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 Figure 1. ICC_Operator_ID AII 129 AII Type: To be allocated by IANA. 131 Length: 1 octet in length, specifies the length of the value field in 132 octets. The length is set to 14. 134 ICC_Operator_ID: ICC_Operator_ID of the sender node. As defined in 135 [I-D.ietf-mpls-tp-itu-t-identifiers], the ICC_Operator_ID is formed 136 by Country Code (CC) and ICC(ITU Carrier Code ) as CC::ICC. The ICC 137 itself is a string of one to six characters, global uniqueness is 138 assured by concatenating the ICC with a CC. The Country Code 139 (alpha-2) is a string of two alphabetic characters represented with 140 upper case letters (i.e., A-Z). When the length of a ICC_Operator_ID 141 string is less than 8 octets, the higher-order unused octets of the 142 ICC_Operator_ID field MUST be set to zero. 144 Prefix: Same as [RFC5003]. 146 AC ID field: Same as [RFC5003]. 148 2.1. Procedures 150 Since the Operator ID MAY be either the Global_ID or ICC_Operator_ID, 151 the two ends of a PW may use the different AII type. During the 152 Label Mapping procedure, one end may not map the TAI to one of its 153 Forwarders. In this case, it MUST send a Label Release message to 154 the other end, with a Status Code of "Unassigned/Unrecognized TAI", 155 and the processing of the Label Mapping message is complete. 157 3. IANA Considerations 159 The IANA is requested to as assign a new AII type from the 160 "Attachment Individual Identifier (AII) Type" registry. 162 Value Meaning Reference 163 ----- -------------------------- ---------------------- 164 TBD ICC_Operator_ID identifier this document (sect 2) 166 4. Security Considerations 168 This draft does not introduce any new security issues, the security 169 mechanisms defined in [RFC5003] apply here. 171 5. Acknowledgements 173 6. References 175 6.1. Normative References 177 [I-D.ietf-mpls-tp-itu-t-identifiers] 178 Winter, R., Gray, E., Helvoort, H., and M. Betts, "MPLS-TP 179 Identifiers Following ITU-T Conventions", 180 draft-ietf-mpls-tp-itu-t-identifiers-03 (work in 181 progress), March 2012. 183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 184 Requirement Levels", BCP 14, RFC 2119, March 1997. 186 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 187 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 189 6.2. Informative References 191 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 192 Heron, "Pseudowire Setup and Maintenance Using the Label 193 Distribution Protocol (LDP)", RFC 4447, April 2006. 195 [RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto, 196 "Attachment Individual Identifier (AII) Types for 197 Aggregation", RFC 5003, September 2007. 199 [RFC6074] Rosen, E., Davie, B., Radoaca, V., and W. Luo, 200 "Provisioning, Auto-Discovery, and Signaling in Layer 2 201 Virtual Private Networks (L2VPNs)", RFC 6074, 202 January 2011. 204 Authors' Addresses 206 Mach Chen 207 Huawei Technologies Ltd. 208 China 210 Email: mach.chen@huawei.com 212 Lianshu Zheng 213 Huawei Technologies Ltd. 214 China 216 Email: vero.zheng@huawei.com