--- 1/draft-ietf-mpls-tp-itu-t-identifiers-06.txt 2013-01-09 18:16:12.947791420 +0100 +++ 2/draft-ietf-mpls-tp-itu-t-identifiers-07.txt 2013-01-09 18:16:12.967790556 +0100 @@ -1,53 +1,55 @@ Network Working Group R. Winter, Ed. Internet-Draft NEC Intended status: Standards Track E. Gray, Ed. -Expires: May 11, 2013 Ericsson +Expires: July 13, 2013 Ericsson H. van Helvoort Huawei Technologies Co., Ltd. M. Betts ZTE - November 7, 2012 + January 9, 2013 MPLS-TP Identifiers Following ITU-T Conventions - draft-ietf-mpls-tp-itu-t-identifiers-06 + draft-ietf-mpls-tp-itu-t-identifiers-07 Abstract This document specifies an extension to the identifiers to be used in the Transport Profile of Multiprotocol Label Switching (MPLS-TP). Identifiers that follow IP/MPLS conventions have already been defined. This memo augments that set of identifiers for MPLS-TP - management and OAM functions to include identifier information in a - format typically used by the ITU-T. + management and Operations, Administration, and Maintenance (OAM) + functions to include identifier information in a format typically + used by the International Telecommunication Union Telecommunication + Standardization Sector (ITU-T). 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 11, 2013. + This Internet-Draft will expire on July 13, 2013. Copyright Notice - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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 @@ -81,22 +83,22 @@ Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction This document augments the initial set of identifiers to be used in the Transport Profile of Multiprotocol Label Switching (MPLS-TP) defined in [RFC6370]. [RFC6370] defines a set of MPLS-TP transport and management entity identifiers to support bidirectional (co-routed and associated) - point-to-point MPLS-TP LSPs, including PWs and Sections which follow - the IP/MPLS conventions. + point-to-point MPLS-TP Label Switched Paths (LSPs), including + Pseudowire (PWs) and Sections which follow the IP/MPLS conventions. This document specifies an alternative way to uniquely identify an operator/service provider based on ITU-T conventions and specifies how this operator/service provider identifier can be used to make the existing set of MPLS-TP transport and management entity identifiers, defined by [RFC6370], globally unique. This document solely defines those identifiers. Their use and possible protocols extensions to carry them is out of scope in this document. @@ -196,21 +198,22 @@ traditionally identifies operators/service providers based on the ITU-T Carrier Code (ICC) as specified in [M1400]. The ITU-T Telecommunication Standardization Bureau (TSB) maintains a list of assigned ICCs [ICC-list]. Note that ICCs can be assigned to both, ITU-T members as well as non-members, all of which are referenced at [ICC-list]. The national regulatory authorities act as an intermediary between the ITU/TSB and operators/service providers. Amongst the things that the national authorities are responsible for in the process of assigning an ICC is to ensure that the Carrier - Codes are unique within their country. + Codes are unique within their country. This uniqueness assumption is + the basis for creating a globally unique ICC-based operator ID. The ICC itself is a string of one to six characters, each character being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9). Alphabetic characters in the ICC SHOULD be represented with upper case letters. Global uniqueness is assured by concatenating the ICC with a Country Code (CC). The Country Code (alpha-2) is a string of two alphabetic characters represented with upper case letters (i.e., A-Z). The Country Code format is defined in ISO 3166-1 [ISO3166-1]. Together, @@ -369,42 +372,38 @@ document the Attachment Individual Identifier (AII) is composed of three fields. These are the ICC_Operator_ID, the Node_ID and the AC_ID. The AC-ID is as defined in [RFC5003]. The complete globally unique PW_Path_ID is formulated as: A1-{ICC_Operator_ID::Node_ID::AC_ID}:: Z9-{ICC_Operator_ID::Node_ID::AC_ID} 7. Maintenance Identifiers - A Maintenance Entity Group (MEG) as defined by [RFC6371] is a - collection of one or more maintenance enties that belong to the same - transport path. These maintenance entities can be e.g. Maintenance - Entity Group End Points (MEPs) or Maintenance Entity Group - Intermediate Points (MIPs). The following sub-sections define the - identifiers for the various maintenance-related groups and entities. - In contrast to the IDs defined in [RFC6370], this document does not + The following sub-sections define the identifiers for the various + maintenance-related groups and entities as defined in [RFC6371]. In + contrast to the IDs defined in [RFC6370], this document does not define separate maintenance identifiers for sections, PWs and LSPs. 7.1. MEG Identifiers MEG_IDs for MPLS-TP Sections, LSPs and Pseudowires following ITU-T conventions are based on the globally unique ICC_Operator_ID. In this case, the MEG_ID is a string of up to 15 characters and consists of three subfields: the Country Code (as described in Section 3), the ICC (as described in Section 3) which together form the ICC_Operator_ID, followed by a Unique MEG ID Code (UMC) as defined in [Y.1731_cor1]. The resulting MEG_ID is: - CC:ICC:UMC + CC::ICC::UMC To avoid the potential for the concatenation of a short (i.e. less than 6 Character) ICC with a UMC not being unique the UMC MUST start with the "/" character which is not allowed in the ICC itself. This way, the MEG_ID can also be easily decomposed into its individual components by a receiver. The UMC MUST be unique within the organization identified by the combination of CC and ICC. @@ -433,35 +432,34 @@ prefixing the identifier of the interface the MIP resides with the ICC_Operator_ID as described in Section 3.1. This allows MIPs to be independently identified in nodes where a per-interface MIP model is used. If only a per-node MIP model is used, one MIP is configured. In this case, the MIP_ID is formed by using the Node_ID and an IF_Num of 0. 8. Security Considerations - This document extends an existing information model and does not + This document extends an existing naming scheme and does not introduce new security concerns. But, as mentioned in the security considerations section of [RFC6370] protocol specifications that - describe use of this information model may introduce security risks - and concerns about authentication of participants. For this reason, + describe use of this naming scheme may introduce security risks and + concerns about authentication of participants. For this reason, these protocol specifications need to describe security and authentication concerns that may be raised by the particular mechanisms defined and how those concerns may be addressed. 9. IANA Considerations There are no IANA actions resulting from this document. 10. References - 10.1. Normative References [ISO3166-1] "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes", ISO 3166-1. [M1400] "Designations for interconnections among operators' networks", ITU-T Recommendation M.1400, July 2006, .