draft-ietf-mpls-tp-itu-t-identifiers-07.txt   draft-ietf-mpls-tp-itu-t-identifiers-08.txt 
Network Working Group R. Winter, Ed. Network Working Group R. Winter
Internet-Draft NEC Internet-Draft NEC
Intended status: Standards Track E. Gray, Ed. Intended status: Standards Track E. Gray
Expires: July 13, 2013 Ericsson Expires: August 29, 2013 Ericsson
H. van Helvoort H. van Helvoort
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
M. Betts M. Betts
ZTE ZTE
January 9, 2013 February 25, 2013
MPLS-TP Identifiers Following ITU-T Conventions MPLS-TP Identifiers Following ITU-T Conventions
draft-ietf-mpls-tp-itu-t-identifiers-07 draft-ietf-mpls-tp-itu-t-identifiers-08
Abstract Abstract
This document specifies an extension to the identifiers to be used in This document specifies an extension to the identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP). the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
Identifiers that follow IP/MPLS conventions have already been Identifiers that follow IP/MPLS conventions have already been
defined. This memo augments that set of identifiers for MPLS-TP defined. This memo augments that set of identifiers for MPLS-TP
management and Operations, Administration, and Maintenance (OAM) management and Operations, Administration, and Maintenance (OAM)
functions to include identifier information in a format typically functions to include identifier information in a format typically
used by the International Telecommunication Union Telecommunication used by the International Telecommunication Union Telecommunication
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 13, 2013. This Internet-Draft will expire on August 29, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Requirements notation . . . . . . . . . . . . . . . . . . 4 1.2. Requirements notation . . . . . . . . . . . . . . . . . . 4
1.3. Notational Conventions . . . . . . . . . . . . . . . . . . 4 1.3. Notational Conventions . . . . . . . . . . . . . . . . . . 4
2. Named Entities . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Named Entities . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Uniquely Identifying an Operator - the ICC_Operator_ID . . . . 5 3. Uniquely Identifying an Operator - the ICC_Operator_ID . . . . 5
3.1. Use of the ICC_Operator_ID . . . . . . . . . . . . . . . . 6 3.1. Use of the ICC_Operator_ID . . . . . . . . . . . . . . . . 6
4. Node and Interface Identifiers . . . . . . . . . . . . . . . . 6 4. Node and Interface Identifiers . . . . . . . . . . . . . . . . 6
5. MPLS-TP Tunnel and LSP Identifiers . . . . . . . . . . . . . . 7 5. MPLS-TP Tunnel and LSP Identifiers . . . . . . . . . . . . . . 7
5.1. MPLS-TP Point-to-Point Tunnel Identifiers . . . . . . . . 7 5.1. MPLS-TP Point-to-Point Tunnel Identifiers . . . . . . . . 7
5.2. MPLS-TP LSP Identifiers . . . . . . . . . . . . . . . . . 7 5.2. MPLS-TP LSP Identifiers . . . . . . . . . . . . . . . . . 8
5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers . . . 7 5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers . . . 8
5.2.2. MPLS-TP Associated Bidirectional LSP Identifiers . . 8 5.2.2. MPLS-TP Associated Bidirectional LSP Identifiers . . 8
6. Pseudowire Path Identifiers . . . . . . . . . . . . . . . . . 9 6. Pseudowire Path Identifiers . . . . . . . . . . . . . . . . . 9
7. Maintenance Identifiers . . . . . . . . . . . . . . . . . . . 9 7. Maintenance Identifiers . . . . . . . . . . . . . . . . . . . 9
7.1. MEG Identifiers . . . . . . . . . . . . . . . . . . . . . 9 7.1. MEG Identifiers . . . . . . . . . . . . . . . . . . . . . 9
7.2. MEP Identifiers . . . . . . . . . . . . . . . . . . . . . 10 7.2. MEP Identifiers . . . . . . . . . . . . . . . . . . . . . 10
7.3. MIP Identifiers . . . . . . . . . . . . . . . . . . . . . 10 7.3. MIP Identifiers . . . . . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . . 11 10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 11 10.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
This document augments the initial set of identifiers to be used in This document augments the initial set of identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP) the Transport Profile of Multiprotocol Label Switching (MPLS-TP)
defined in [RFC6370]. defined in [RFC6370] by adding new identifiers based on ITU-T
conventions. It is not intended that both types of identifier will
be used at the same time in the same domain.
[RFC6370] defines a set of MPLS-TP transport and management entity [RFC6370] defines a set of MPLS-TP transport and management entity
identifiers to support bidirectional (co-routed and associated) identifiers to support bidirectional (co-routed and associated)
point-to-point MPLS-TP Label Switched Paths (LSPs), including point-to-point MPLS-TP Label Switched Paths (LSPs), including
Pseudowire (PWs) and Sections which follow the IP/MPLS conventions. Pseudowire (PWs) and Sections which follow the IP/MPLS conventions.
This document specifies an alternative way to uniquely identify an This document specifies an alternative way to generate unambiguous
operator/service provider based on ITU-T conventions and specifies identifiers for operators/service providers based on ITU-T
how this operator/service provider identifier can be used to make the conventions and specifies how these operator/service provider
existing set of MPLS-TP transport and management entity identifiers, identifiers can be used to generate unambiguous identifiers for the
defined by [RFC6370], globally unique. existing set of identifiable MPLS-TP entities described in
[RFC6370]."
This document solely defines those identifiers. Their use and This document solely defines those identifiers. Their use and
possible protocols extensions to carry them is out of scope in this possible protocols extensions to carry them is out of scope in this
document. document.
In this document, we follow the notational convention laid out in In this document, we follow the notational convention laid out in
[RFC6370], which is included in this document for convenience in [RFC6370], which is included in this document for convenience in
Section 1.3. Section 1.3.
1.1. Terminology 1.1. Terminology
CC: Country Code CC: Country Code
ICC: ITU Carrier Code ICC: ITU Carrier Code
ISO: International Organization for Standardization
ITU-T: International Telecommunication Union Telecommunication ITU-T: International Telecommunication Union Telecommunication
Standardization Sector Standardization Sector
LSP: Label Switched Path LSP: Label Switched Path
MEG: Maintenance Entity Group MEG: Maintenance Entity Group
MEP: Maintenance Entity Group End Point MEP: Maintenance Entity Group End Point
MIP: Maintenance Entity Group Intermediate Point MIP: Maintenance Entity Group Intermediate Point
skipping to change at page 5, line 24 skipping to change at page 5, line 31
o MIP o MIP
The following sections go through this list of identifiers one by The following sections go through this list of identifiers one by
one. The structure of this document is loosely aligned with the one. The structure of this document is loosely aligned with the
structure of [RFC6370]. structure of [RFC6370].
3. Uniquely Identifying an Operator - the ICC_Operator_ID 3. Uniquely Identifying an Operator - the ICC_Operator_ID
In [RFC6370] an operator is uniquely identified by the Global_ID In [RFC6370] an operator is uniquely identified by the Global_ID
which is based on the AS number of the operator. The ITU-T however which is based on the AS number of the operator. The ITU-T however
traditionally identifies operators/service providers based on the traditionally identifies operators/service providers based on the ITU
ITU-T Carrier Code (ICC) as specified in [M1400]. Carrier Code (ICC) as specified in [M1400].
The ITU-T Telecommunication Standardization Bureau (TSB) maintains a The ITU-T Telecommunication Standardization Bureau (TSB) maintains a
list of assigned ICCs [ICC-list]. Note that ICCs can be assigned to 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 both, ITU-T members as well as non-members, all of which are
referenced at [ICC-list]. The national regulatory authorities act as referenced at [ICC-list]. The national regulatory authorities act as
an intermediary between the ITU/TSB and operators/service providers. an intermediary between the ITU/TSB and operators/service providers.
Amongst the things that the national authorities are responsible for Amongst the things that the national authorities are responsible for
in the process of assigning an ICC is to ensure that the Carrier in the process of assigning an ICC is to ensure that the Carrier
Codes are unique within their country. This uniqueness assumption is Codes are unique within their country. This uniqueness assumption is
the basis for creating a globally unique ICC-based operator ID. the basis for creating a globally unique ICC-based operator ID.
The ICC itself is a string of one to six characters, each character 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). being either alphabetic (i.e. A-Z) or numeric (i.e. 0-9).
Alphabetic characters in the ICC SHOULD be represented with upper Alphabetic characters in the ICC SHOULD be represented with upper
case letters. case letters.
Global uniqueness is assured by concatenating the ICC with a Country Global uniqueness is assured by concatenating the ICC with a Country
Code (CC). The Country Code (alpha-2) is a string of two alphabetic Code (CC). The Country Code (alpha-2) is a string of two alphabetic
characters represented with upper case letters (i.e., A-Z). The characters represented with upper case letters (i.e., A-Z).
Country Code format is defined in ISO 3166-1 [ISO3166-1]. Together,
the CC and the ICC form the ICC_Operator_ID as: The International Organization for Standardization (ISO) establishes
internationally recognised codes for the representation of names of
countries, territories or areas of geographical interest, and their
subdivisions, published as a list of CCs [CC-list] in standard ISO
3166-1 [ISO3166-1].
The ICC and CC characters are coded according to ITU-T Recommendation
T.50 [T.50].
Together, the CC and the ICC form the ICC_Operator_ID as:
CC::ICC CC::ICC
3.1. Use of the ICC_Operator_ID 3.1. Use of the ICC_Operator_ID
The ICC_Operator_ID is used as a replacement for the Global_ID as The ICC_Operator_ID is used as a replacement for the Global_ID as
specified in [RFC6370], i.e. its purpose is to provide a globally specified in [RFC6370], i.e. its purpose is to provide a globally
unique context for other MPLS-TP identifiers. unique context for other MPLS-TP identifiers.
As an example, an Interface Identifier (IF_ID) in [RFC6370] is As an example, an Interface Identifier (IF_ID) in [RFC6370] is
skipping to change at page 11, line 24 skipping to change at page 11, line 35
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto, [RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto,
"Attachment Individual Identifier (AII) Types for "Attachment Individual Identifier (AII) Types for
Aggregation", RFC 5003, September 2007. Aggregation", RFC 5003, September 2007.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
[T.50] "International Reference Alphabet- 7-bit coded character
set for information exchange", ITU-T Recommendation ITU-T
T.50 (1992).
[Y.1731_cor1] [Y.1731_cor1]
"OAM functions and mechanisms for Ethernet based networks "OAM functions and mechanisms for Ethernet based networks
- Corrigendum 1", ITU-T Recommendation ITU-T G.8013/Y.1731 - Corrigendum 1", ITU-T Recommendation ITU-T G.8013/Y.1731
(2011) Corrigendum 1. (2011) Corrigendum 1.
10.2. Informative References 10.2. Informative References
[CC-list] "List of Country Codes - ISO 3166 (CCs)",
<http://www.iso.org/iso/country_codes.htm>.
[ICC-list] [ICC-list]
"List of ITU Carrier Codes (ICCs)", "List of ITU Carrier Codes (ICCs)",
<http://www.itu.int/oth/T0201>. <http://www.itu.int/oth/T0201>.
[RFC6371] Busi, I. and D. Allan, "Operations, Administration, and [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and
Maintenance Framework for MPLS-Based Transport Networks", Maintenance Framework for MPLS-Based Transport Networks",
RFC 6371, September 2011. RFC 6371, September 2011.
Authors' Addresses Authors' Addresses
Rolf Winter (editor) Rolf Winter
NEC NEC
Email: rolf.winter@neclab.eu Email: rolf.winter@neclab.eu
Eric Gray (editor)
Eric Gray
Ericsson Ericsson
Email: eric.gray@ericsson.com Email: eric.gray@ericsson.com
Huub van Helvoort Huub van Helvoort
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
Email: huub.van.helvoort@huawei.com Email: huub.van.helvoort@huawei.com
Malcolm Betts Malcolm Betts
 End of changes. 17 change blocks. 
23 lines changed or deleted 45 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/