MPLS Transport Profile (MPLS-TP) Identifiers
RFC 6370
|
| Document |
Type |
|
RFC - Proposed Standard
(September 2011; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-swallow-mpls-tp-identifiers
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 6370 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Adrian Farrel
|
|
IESG note |
|
Ross Callon (rcallon@juniper.net) is the document shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) M. Bocci
Request for Comments: 6370 Alcatel-Lucent
Category: Standards Track G. Swallow
ISSN: 2070-1721 Cisco
E. Gray
Ericsson
September 2011
MPLS Transport Profile (MPLS-TP) Identifiers
Abstract
This document specifies an initial set of identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
The MPLS-TP requirements (RFC 5654) require that the elements and
objects in an MPLS-TP environment are able to be configured and
managed without a control plane. In such an environment, many
conventions for defining identifiers are possible. This document
defines identifiers for MPLS-TP management and Operations,
Administration, and Maintenance (OAM) functions compatible with IP/
MPLS conventions.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
(PWE3) architectures to support the capabilities and functionalities
of a packet transport network as defined by the 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/rfc6370.
Bocci, et al. Standards Track [Page 1]
RFC 6370 MPLS-TP Identifiers September 2011
Copyright Notice
Copyright (c) 2011 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 ....................................................3
1.1. Terminology ................................................3
1.2. Requirements Language ......................................4
1.3. Notational Conventions .....................................4
2. Named Entities ..................................................5
3. Uniquely Identifying an Operator - the Global_ID ................5
4. Node and Interface Identifiers ..................................6
5. MPLS-TP Tunnel and LSP Identifiers ..............................7
5.1. MPLS-TP Point-to-Point Tunnel Identifiers ..................8
5.2. MPLS-TP LSP Identifiers ....................................9
5.2.1. MPLS-TP Co-Routed Bidirectional LSP Identifiers .....9
5.2.2. MPLS-TP Associated Bidirectional LSP Identifiers ....9
5.3. Mapping to RSVP Signaling .................................10
6. Pseudowire Path Identifiers ....................................11
7. Maintenance Identifiers ........................................13
7.1. Maintenance Entity Group Identifiers ......................13
7.1.1. MPLS-TP Section MEG_IDs ............................13
7.1.2. MPLS-TP LSP MEG_IDs ................................13
7.1.3. Pseudowire MEG_IDs .................................14
7.2. Maintenance Entity Group End Point Identifiers ............14
7.2.1. MPLS-TP Section MEP_IDs ............................14
7.2.2. MPLS-TP LSP_MEP_ID .................................15
7.2.3. MEP_IDs for Pseudowires ............................15
7.3. Maintenance Entity Group Intermediate Point Identifiers ...15
8. Security Considerations ........................................15
9. References .....................................................16
Show full document text