datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

A Thesaurus for the Interpretation of Terminology Used in MPLS Transport Profile (MPLS-TP) Internet-Drafts and RFCs in the Context of the ITU-T's Transport Network Recommendations
RFC 7087

Internet Engineering Task Force (IETF)              H. van Helvoort, Ed.
Request for Comments: 7087                             L. Andersson, Ed.
Category: Informational                              Huawei Technologies
ISSN: 2070-1721                                         N. Sprecher, Ed.
                                            Nokia Solutions and Networks
                                                           December 2013

         A Thesaurus for the Interpretation of Terminology Used
      in MPLS Transport Profile (MPLS-TP) Internet-Drafts and RFCs
    in the Context of the ITU-T's Transport Network Recommendations

Abstract

   The MPLS Transport Profile (MPLS-TP) is based on a profile of the
   MPLS and Pseudowire (PW) procedures as specified in the MPLS Traffic
   Engineering (MPLS-TE), PW, and Multi-Segment Pseudowire (MS-PW)
   architectures developed by the Internet Engineering Task Force
   (IETF).  The International Telecommunication Union Telecommunication
   Standardization Sector (ITU-T) has specified a Transport Network
   architecture.

   This document provides a thesaurus for the interpretation of MPLS-TP
   terminology within the context of the ITU-T Transport Network
   Recommendations.

   It is important to note that MPLS-TP is applicable in a wider set of
   contexts than just Transport Networks.  The definitions presented in
   this document do not provide exclusive or complete interpretations of
   MPLS-TP concepts.  This document simply allows the MPLS-TP terms to
   be applied within the Transport Network context.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   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).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see 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/rfc7087.

van Helvoort, et al.          Informational                     [Page 1]
RFC 7087                  MPLS-TP Rosetta Stone            December 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 ....................................................4
      1.1. Abbreviations ..............................................4
   2. Terminology .....................................................5
      2.1. MPLS-TP Terminology Sources ................................5
      2.2. ITU-T Transport Network Terminology Sources ................6
      2.3. Common Terminology Sources .................................6
   3. Thesaurus .......................................................6
      3.1. Associated Bidirectional Path ..............................6
      3.2. Bidirectional Path .........................................6
      3.3. Client-Layer Network .......................................6
      3.4. Communication Channel ......................................7
      3.5. Concatenated Segment .......................................7
      3.6. Control Plane ..............................................7
      3.7. Co-Routed Bidirectional Path ...............................7
      3.8. Data Communication Network (DCN) ...........................7
      3.9. Defect .....................................................8
      3.10. Domain ....................................................8
      3.11. Embedded Communication Channel (ECC) ......................8
      3.12. Equipment Management Function (EMF) .......................8
      3.13. Failure ...................................................8
      3.14. Fault .....................................................8
      3.15. Layer Network .............................................9
      3.16. Link ......................................................9
      3.17. Maintenance Entity (ME) ...................................9

[include full document text]