draft-ietf-mpls-tp-itu-t-identifiers-01.txt   draft-ietf-mpls-tp-itu-t-identifiers-02.txt 
Network Working Group R. Winter, Ed. Network Working Group R. Winter, Ed.
Internet-Draft NEC Internet-Draft NEC
Intended status: Standards Track E. Gray, Ed. Intended status: Standards Track E. Gray, Ed.
Expires: April 30, 2012 Ericsson Expires: May 3, 2012 Ericsson
H. van Helvoort H. van Helvoort
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
M. Betts M. Betts
ZTE ZTE
October 28, 2011 October 31, 2011
MPLS-TP Identifiers Following ITU-T Conventions MPLS-TP Identifiers Following ITU-T Conventions
draft-ietf-mpls-tp-itu-t-identifiers-01 draft-ietf-mpls-tp-itu-t-identifiers-02
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 OAM functions to include identifier information in a management and OAM functions to include identifier information in a
format typically used by the ITU-T. format typically used by the ITU-T.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 April 30, 2012. This Internet-Draft will expire on May 3, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 24 skipping to change at page 2, line 24
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Requirements notation . . . . . . . . . . . . . . . . . . . 4 1.2. Requirements notation . . . . . . . . . . . . . . . . . . . 4
2. Uniquely Identifying an Operator - the ICC_Operator_ID . . . . 4 2. Uniquely Identifying an Operator - the ICC_Operator_ID . . . . 4
3. Use of the ICC_Operator_ID . . . . . . . . . . . . . . . . . . 4 3. Use of the ICC_Operator_ID . . . . . . . . . . . . . . . . . . 4
4. ICC_Operator_ID-based MEG Identifiers . . . . . . . . . . . . . 5 4. ICC_Operator_ID-based MEG Identifiers . . . . . . . . . . . . . 5
5. ICC_Operator_ID-based MEP Identifiers . . . . . . . . . . . . . 5 5. ICC_Operator_ID-based MEP Identifiers . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
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)
specified in RFC 6370 [RFC6370]. specified in RFC 6370 [RFC6370].
RFC 6370 [RFC6370] defines a set of MPLS-TP transport and management RFC 6370 [RFC6370] defines a set of MPLS-TP transport and management
entity identifiers to support bidirectional (co-routed and entity identifiers to support bidirectional (co-routed and
skipping to change at page 5, line 23 skipping to change at page 5, line 23
in RFC 6370 [RFC6370] except for the other alternatives mentioned in in RFC 6370 [RFC6370] except for the other alternatives mentioned in
this document. this document.
4. ICC_Operator_ID-based MEG Identifiers 4. ICC_Operator_ID-based MEG Identifiers
The ITU-T format of MEG_IDs for MPLS-TP Sections, LSPs and The ITU-T format of MEG_IDs for MPLS-TP Sections, LSPs and
Pseudowires is based on the globally unique ICC_Operator_ID. In this Pseudowires is based on the globally unique ICC_Operator_ID. In this
case, the MEG_ID is a string of up to 15 characters. It consists of case, the MEG_ID is a string of up to 15 characters. It consists of
three subfields: the Country Code (as described in Section 2), the three subfields: the Country Code (as described in Section 2), the
ICC (as described in Section 2) which together form the ICC (as described in Section 2) which together form the
ICC_Operator_ID, followed by a Unique MEG ID Code (UMC). ICC_Operator_ID, followed by a Unique MEG ID Code (UMC) as defined in
[Y.1731_cor1].
The resulting MEG_ID therefore looks like the following: The resulting MEG_ID therefore looks like the following:
CC:ICC:UMC CC:ICC:UMC
To avoid the potential for a short (i.e. less than 6 Character) ICC To avoid the potential for a short (i.e. less than 6 Character) ICC
code in combination with a UMC not being unique the UMC MUST start code in combination with a UMC not being unique the UMC MUST start
with a special character that is not allowed in the ICC such as the with a special character that is not allowed in the ICC such as the
"/" character. A side effect of this is that the MEG_ID can be "/" character. A side effect of this is that the MEG_ID can be
decomposed into its individual components by a receiver. decomposed into its individual components by a receiver.
skipping to change at page 6, line 44 skipping to change at page 6, line 45
[M1400] "Designations for interconnections among operators' [M1400] "Designations for interconnections among operators'
networks", ITU-T Recommendation M.1400, July 2006, networks", ITU-T Recommendation M.1400, July 2006,
<http://www.itu.int/rec/T-REC-M.1400-200607-I/en>. <http://www.itu.int/rec/T-REC-M.1400-200607-I/en>.
[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.
[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.
[Y.1731_cor1]
"OAM functions and mechanisms for Ethernet based networks
- Corrigendum 1", ITU-T Recommendation ITU-T G.8013/Y.1731
(2011) Corrigendum 1.
8.2. Informative References 8.2. Informative References
[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>.
Authors' Addresses Authors' Addresses
Rolf Winter (editor) Rolf Winter (editor)
NEC NEC
 End of changes. 7 change blocks. 
6 lines changed or deleted 12 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/