One document matched: draft-ietf-mpls-tp-uni-nni-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="no"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-ietf-mpls-tp-uni-nni-03" ipr="trust200902"
updates="5921">
<front>
<title abbrev="MPLS-TP UNI and NNI">MPLS Transport Profile User-to-Network
and Network-to-Network Interfaces</title>
<author fullname="Matthew Bocci" initials="M." surname="Bocci">
<organization>Alcatel-Lucent</organization>
<address>
<email>matthew.bocci@alcatel-lucent.com</email>
</address>
</author>
<author fullname="Lieven Levrau" initials="L." surname="Levrau">
<organization>Alcatel-Lucent</organization>
<address>
<email>lieven.levrau@alcatel-lucent.com</email>
</address>
</author>
<author fullname="Dan Frost" initials="D." surname="Frost">
<organization>Cisco</organization>
<address>
<email>danfrost@cisco.com</email>
</address>
</author>
<date day="7" month="January" year="2011" />
<abstract>
<t>The framework for MPLS in transport networks (RFC 5921) provides
reference models for the MPLS Transport Profile (MPLS-TP) transport
service interfaces, which are a 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.</t>
<t>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.</t>
<t>This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.</t>
<t>[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 consensus.]</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>The framework for MPLS in transport networks <xref
target="RFC5921"></xref> provides reference models for the MPLS
Transport Profile (MPLS-TP) transport service interfaces, which are a
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.</t>
<t>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.</t>
<section title="Updates to the MPLS-TP UNI and NNI">
<t>The transport service interfaces for MPLS-TP are defined in Section
3.4.3 of <xref target="RFC5921"></xref>. 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
convention 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 Customer Edge (CE) side and
the Provider Edge (PE) side of the UNI, i.e. the UNI-C (User-to-User
Interface, Client side) and UNI-N (User-to-Network Interface, Network
side), in order to show their relationship to one another.</t>
<t>This document provides updated illustrations of the MPLS-TP UNI and
MPLS-TP NNI to show these additional details. These illustrations
obsolete the corresponding ones in <xref target="RFC5921"></xref>.
This document also defines additional terminology referenced in the
illustrations. No other updates are made by this document.</t>
<t>Awareness of the Transport Service layer need exist only at PE
nodes, and so only these nodes are illustrate in the figures. MPLS-TP
Provider (P) nodes need have no awareness of this layer. Both PE and P
nodes participate in the Transport Path layer. A PE terminates (i.e.,
is an LER with respect to) the transport paths it supports, and is
responsible for multiplexing and demultiplexing of Transport Service
Instance traffic over such transport paths.</t>
</section>
<section title="Terminology and Abbreviations">
<t>The terminology and abbreviations of <xref target="RFC5921"></xref>
apply.</t>
<t>The following additional terminology is used in this document.</t>
<texttable align="left" style="headers">
<ttcol>Term</ttcol>
<ttcol>Definition</ttcol>
<c>CP</c>
<c>Control Plane</c>
<c>NNI</c>
<c>Network-to-Network Interface</c>
<c>TSI</c>
<c>Transport Service Instance</c>
<c>UNI</c>
<c>User-to-Network Interface</c>
<c>UNI-C</c>
<c>User-to-Network Interface, Client side</c>
<c>UNI-N</c>
<c>User-to-Network Interface, Network side</c>
</texttable>
<t><list style="hanging">
<t hangText="Transport Service Instance:">A single logical
point-to-point connection at the Transport Service layer between
the ingress PE providing a packet transport service to a CE, and
the corresponding egress PE to which the peer CE is attached. </t>
</list> </t>
</section>
</section>
<section title="MPLS-TP User-to-Network Interface">
<t>The MPLS-TP User-to-Network Interface (UNI) is illustrated in <xref
target="tp-uni"></xref>. This figure obsoletes Figure 3 of <xref
target="RFC5921"></xref>. Note that the term MPLS-TP 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.
<figure anchor="tp-uni" title="UNI Between CE Node and MPLS-TP PE Node">
<artwork><![CDATA[
UNI
: MPLS-TP
:<-- UNI-C -->: : :<-- UNI-N ->: Network <----->
: function : : : function :
--------------- : ------------:--------------------
: | : | : Transport |
: | V | Client : 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: The client service control plane may be a control protocol
belonging to the native service, or GMPLS.
]]></artwork>
</figure></t>
</section>
<section title="MPLS-TP Network-to-Network Interface">
<t>The MPLS-TP Network-to-Network Interface (NNI) is illustrated in
<xref target="tp-nni"></xref>. This figure obsoletes Figure 5 of <xref
target="RFC5921"></xref>. 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. <figure anchor="tp-nni" title="NNI Between MPLS-TP PE Nodes">
<artwork><![CDATA[ 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
]]></artwork>
</figure></t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document makes no request of IANA.</t>
<t>Note to RFC Editor: this section may be removed on publication as an
RFC.</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>The security considerations of <xref target="RFC5921"></xref> apply.
The updated reference models provided by this document introduce no new
security considerations.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t></t>
<t>The editors wish to thank the following for their contribution to
this document:</t>
<t><list style="symbols">
<t>Eve Varma.</t>
<t>Dieter Beller.</t>
<t>Lou Berger.</t>
<t>Stewart Bryant.</t>
<t>Italo Busi.</t>
<t>The experts of ITU-T Study Group 15 and the IETF MPLS and PWE3
working groups.</t>
</list></t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include='reference.RFC.5921'?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-22 16:56:02 |