| TOC |
|
The framework for MPLS in transport networks [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.) provides reference models for an MPLS-TP User-to-Network Interface (UNI), and an MPLS-TP Network-to-Network interface (NNI). This document updates those reference models to show detailed reference points for these interfaces, along with further clarification of the functional architecture of MPLS-TP at a UNI and NNI.
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.
This Informational Internet-Draft is aimed at achieving IETF Consensus before publication as an RFC and will be subjet to an IETF Last Call.
[RFC Editor, please remove this note before publication as an RFC and insert the correct Streams Boilerplate to indicate that the published RFC has IETF onsensus.]
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”
This Internet-Draft will expire on May 30, 2011.
Copyright (c) 2010 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.
1.
Introduction
1.1.
Updates to the MPLS-TP UNI and NNI
1.2.
Terminology and Abbreviations
2.
MPLS-TP User-to-Network Interface
3.
MPLS-TP Network-to-Network Interface
4.
IANA Considerations
5.
Security Considerations
6.
Acknowledgements
7.
Normative References
§
Authors' Addresses
| TOC |
The framework for MPLS in transport networks [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.) provides reference models for an MPLS-TP User-to-Network Interface (UNI), and an MPLS-TP Network-to-Network interface (NNI). This document updates those reference models to show detailed reference points for these interfaces, along with further clarification of the functional architecture of MPLS-TP at a UNI and NNI.
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 PWE3 architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T.
| TOC |
The transport service interfaces for MPLS-TP are defined in Section 3.4.3 of [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.). These definitions are illustrated by showing MPLS-TP PEs containing a UNI and an NNI. The figures illustrate the UNI and the NNI as a span. However, it is more conventional to illustrate these interfaces as reference points. Furthermore, in the case of a UNI, it is useful to illustrate the distribution of UNI functions between the CE side and the PE side of the UNI (the UNI-C and UNI-N).
This document provides updated illustrations of the MPLS-TP UNI and MPLS-TP NNI to show these additional details. These illustrations are intended to obsolete the corresponding ones in [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.). This document also defines additional terminology referenced in the illustrations. No other updates are proposed by this document.
| TOC |
The terminology and abbreviations of [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.) apply.
The following additional terminology is used in this document.
| Term | Definition |
|---|---|
| CP | Control Plane |
| NNI | Network-to-Network Interface |
| TSI | Transport Service Instance |
| UNI | User-to-Network Interface |
| UNI-C | User-to-Network Interface, Customer Edge side |
| UNI-N | User-to-Network Interface, PE Side |
| TOC |
The MPLS-TP User-Network interface (UNI) is illustrated in Figure 1 (UNI Between CE Node and MPLS-TP PE Node). This figure obsoletes Figure 3 of [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.). Note that the term MPLS UNI is to be
interpreted as a UNI to an MPLS-TP network and does not refer to the
protocol transiting the UNI. The UNI for a particular client flow may
involve signaling between the CE and PE. If signaling is used, it may
traverse the same attachment circuit that supports the client flow.
UNI
: MPLS-TP
:<-- UNI-C -->: : :<-- UNI-N ->: Network <----->
: function : : : function :
------------- : ------------:--------------------
: | : | : Transport |
: | V | Native : Path |
: | | Service : Mux/Demux |
: | | Control : -- |
: ---------- | | ----------: | | Transport|
:| | | | | | | | Path |
:|Signaling |_|___________|_|Signaling | | | --------->
:|Controller| | | |Controller| | | |
: ---------- | | ---------- | | --------->
: :......|...........|......: : | | |
: | Control | : | | Transport|
: | Channel | : | | Path |
: | | : | | --------->
: | | : | | -+----------->TSI
: | | Transport : | | | --------->
: | Client | Service : | | | |
: | Traffic | Data Plane: | | | |
: ---------- | Flows | -------------- | | |Transport|
:| Client |-|-----------|-|Client/Service|-| |- Path |
:| Traffic |=|===========|=| Traffic | | | --------->
:|Processing| | | | Processing |=| |===+===========>TSI
: ---------- | | -------------- | | --------->
: |______|___________|______| : | | |
: | Data Link | : | | |
: | | : -- |
: | | : Transport |
: | | : Path |
: | | : Data Plane|
------------- ---------------------------------
Customer Edge Node MPLS-TP Provider Edge Node
Note: Native service control = Control plane belonging to the native
service and/or GMPLS UNI
TSI = Transport Service Instance
| Figure 1: UNI Between CE Node and MPLS-TP PE Node |
| TOC |
The MPLS-TP NNI is illustrated in Figure 2 (NNI Between MPLS-TP PE Nodes). This
figure obsoletes Figure 5 of [RFC5921] (Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” July 2010.). The NNI for
a particular Transport Service Instance may involve signaling between
the two PEs. If signaling is used, it may traverse the same data-link
that supports the service instance.
NNI
:<--- NNI --->: : :<--- NNI ---->:
: Function : : : Function :
--------------------------- : --------------------------
| : Transport | : | Transport : |
| : Service CP | V | Service CP : |
| : ---------- |Signaling| ---------- : |
| : |Signaling |_| _______ |_|Signaling | : |
| : |Controller| | | |Controller| : |
| : ---------- | | ---------- : |
| : :....... Control .......: : |
| : | Channel | : |
| - : Transport | | Transport : - |
| | | : Path CP | | Path CP : | | |
| | | : ---------- |Signaling| ---------- : | | |
-----| | : |Signaling |_| _______ |_|Signaling | : | |-----
---+-| | : |Controller| | | |Controller| : | |-+---
-----| | : ---------- | | ---------- : | |-----
| | | : :....... Control .......: : | | |
| | | : | Channel | : | | |
| | | Transport Path | | Transport Path | | |
| | | / mux/demux \ | | / mux/demux \| | |
| | |/ : \-- | | -- / : | | |
| | | ---------- | | |Transport| | | ---------- | | |
| | |--|Transport |---| | | Path | | |---|Transport |--| | |
-----| | | Service | | |-------------| | | Service | | |-----
TSI+=| |==|Processing|===| |<+===TSI===+>| |===|Processing|==| |=+TSI
-----| | ---------- | |-------------| | ---------- | |-----
| | | : | | | | | | : | | |
| | | : | | | | | | : | | |
| - : -- | | -- : - |
| : | | : |
| Transport Path | | Transport Path |
| Data Plane | Data Plane |
--------------------------- --------------------------
MPLS-TP Provider MPLS-TP Provider
Edge Node A Edge Node B
TSI = Transport Service Instance
| Figure 2: NNI Between MPLS-TP PE Nodes |
| TOC |
This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an RFC.
| TOC |
The security considerations of RFC5921 apply. The updated reference models provided by this document introduce no new security considerations.
| TOC |
The editors wish to thank the following for their contribution to this document:
| TOC |
| [RFC2119] | Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). |
| [RFC5921] | Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, “A Framework for MPLS in Transport Networks,” RFC 5921, July 2010 (TXT). |
| TOC |
| Matthew Bocci | |
| Alcatel-Lucent | |
| Email: | matthew.bocci@alcatel-lucent.com |
| Lieven Levrau | |
| Alcatel-Lucent | |
| Phone: | |
| Fax: | |
| Email: | lieven.levrau@alcatel-lucent.com |
| URI: | |
| Dan Frost | |
| Cisco | |
| Phone: | |
| Fax: | |
| Email: | danfrost@cisco.com |
| URI: |