MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions
RFC 6923
Internet Engineering Task Force (IETF) R. Winter
Request for Comments: 6923 NEC
Category: Standards Track E. Gray
ISSN: 2070-1721 Ericsson
H. van Helvoort
Huawei Technologies Co., Ltd.
M. Betts
ZTE
May 2013
MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions
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 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 is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6923.
Winter, et al. Standards Track [Page 1]
RFC 6923 MPLS-TP ITU-T IDs May 2013
Copyright Notice
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
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................3
1.2. Requirements Notation ......................................4
1.3. Notational Conventions .....................................4
2. Named Entities ..................................................4
3. Uniquely Identifying an Operator -- the ICC_Operator_ID .........5
3.1. Use of the ICC_Operator_ID .................................6
4. Node and Interface Identifiers ..................................7
5. MPLS-TP Tunnel and LSP Identifiers ..............................7
5.1. MPLS-TP Point-to-Point Tunnel Identifiers ..................7
5.2. MPLS-TP LSP Identifiers ....................................8
5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers .....8
5.2.2. MPLS-TP Associated Bidirectional LSP Identifiers ....9
6. Pseudowire Path Identifiers .....................................9
7. Maintenance Identifiers .........................................9
7.1. MEG Identifiers ...........................................10
7.2. MEP Identifiers ...........................................10
7.3. MIP Identifiers ...........................................10
8. Security Considerations ........................................11
9. References .....................................................11
9.1. Normative References ......................................11
9.2. Informative References ....................................12
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] by adding new identifiers based on ITU-T
conventions. It is not intended that both types of identifiers will
be used at the same time in the same domain.
Winter, et al. Standards Track [Page 2]
RFC 6923 MPLS-TP ITU-T IDs May 2013
[RFC6370] defines a set of MPLS-TP transport and management entity
identifiers to support bidirectional (co-routed and associated)
Show full document text