draft-ietf-mpls-tp-itu-t-identifiers-05.txt   draft-ietf-mpls-tp-itu-t-identifiers-06.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 20, 2013 Ericsson Expires: May 11, 2013 Ericsson
H. van Helvoort H. van Helvoort
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
M. Betts M. Betts
ZTE ZTE
October 17, 2012 November 7, 2012
MPLS-TP Identifiers Following ITU-T Conventions MPLS-TP Identifiers Following ITU-T Conventions
draft-ietf-mpls-tp-itu-t-identifiers-05 draft-ietf-mpls-tp-itu-t-identifiers-06
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 20, 2013. This Internet-Draft will expire on May 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 32 skipping to change at page 2, line 32
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 . . . . . . . . . . . . . . . . . 7
5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers . . . 7 5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers . . . 7
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 . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . . . . . . . . . . . 11
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].
skipping to change at page 9, line 8 skipping to change at page 9, line 8
A globally unique LSP_ID is constructed using the globally unique A globally unique LSP_ID is constructed using the globally unique
Node_IDs as defined before. Consequently, a globally unique LSP_ID Node_IDs as defined before. Consequently, a globally unique LSP_ID
is formulated as: is formulated as:
A1-{ICC_Operator_ID::Node_ID::Tunnel_Num::LSP_Num}:: A1-{ICC_Operator_ID::Node_ID::Tunnel_Num::LSP_Num}::
Z9-{ICC_Operator_ID::Node_ID::Tunnel_Num::LSP_Num} Z9-{ICC_Operator_ID::Node_ID::Tunnel_Num::LSP_Num}
6. Pseudowire Path Identifiers 6. Pseudowire Path Identifiers
The PW Path Identifier (PW_Path_ID) is structured in a similar manner The PW Path Identifier (PW_Path_ID) is structured in a similar manner
as the LSP IDs described before. It uses the concept of a group ID as the PW_Path_ID described in section 6 of [RFC6370]. In stead of
(Group_ID) as described in RFC 4447 together with a PW number the Global_ID used in [RFC6370] this document uses the
(PW_Num). Both are 16 bit quantaties. In a statically configure ICC_Operator_ID to make the PW-Path_ID globally unique. In this
environment, both the group ID and the PW number need to be equal on document the Attachment Individual Identifier (AII) is composed of
both ends of the PW. Together with the node ID these values form the three fields. These are the ICC_Operator_ID, the Node_ID and the
PW_Path_ID as follows: AC_ID. The AC-ID is as defined in [RFC5003]. The complete globally
unique PW_Path_ID is formulated as:
A1-{Node_ID::Group_ID::PW_Num}::Z9-{Node_ID::Group_ID::PW_Num}
A globally unique PW_Path_ID is constructed using the globally unique
Node_IDs as defined earlier in this document. A globally unique
PW_Path_ID is formulated as:
A1-{ICC_Operator_ID::Node_ID::Group_ID::PW_Num}:: A1-{ICC_Operator_ID::Node_ID::AC_ID}::
Z9-{ICC_Operator_ID::Node_ID::Group_ID::PW_Num} Z9-{ICC_Operator_ID::Node_ID::AC_ID}
7. Maintenance Identifiers 7. Maintenance Identifiers
A Maintenance Entity Group (MEG) as defined by [RFC6371] is a A Maintenance Entity Group (MEG) as defined by [RFC6371] is a
collection of one or more maintenance enties that belong to the same collection of one or more maintenance enties that belong to the same
transport path. These maintenance entities can be e.g. Maintenance transport path. These maintenance entities can be e.g. Maintenance
Entity Group End Points (MEPs) or Maintenance Entity Group Entity Group End Points (MEPs) or Maintenance Entity Group
Intermediate Points (MIPs). The following sub-sections define the Intermediate Points (MIPs). The following sub-sections define the
identifiers for the various maintenance-related groups and entities. identifiers for the various maintenance-related groups and entities.
In contrast to the IDs defined in [RFC6370], this document does not In contrast to the IDs defined in [RFC6370], this document does not
skipping to change at page 11, line 24 skipping to change at page 11, line 20
"Codes for the representation of names of countries and "Codes for the representation of names of countries and
their subdivisions -- Part 1: Country codes", ISO 3166-1. their subdivisions -- Part 1: Country codes", ISO 3166-1.
[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.
[RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto,
"Attachment Individual Identifier (AII) Types for
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.
[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
 End of changes. 8 change blocks. 
19 lines changed or deleted 18 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/