| 1 |
<pre>Internet Engineering Task Force (IETF) M. Bocci |
| 2 |
Request for Comments: 6215 L. Levrau |
| 3 |
Updates: <a href="./rfc5921">5921</a> Alcatel-Lucent |
| 4 |
Category: Informational D. Frost |
| 5 |
ISSN: 2070-1721 Cisco |
| 6 |
April 2011 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">MPLS Transport Profile User-to-Network</span> |
| 10 |
<span class="h1">and Network-to-Network Interfaces</span> |
| 11 |
|
| 12 |
Abstract |
| 13 |
|
| 14 |
The framework for MPLS in transport networks (<a href="./rfc5921">RFC 5921</a>) provides |
| 15 |
reference models for the MPLS Transport Profile (MPLS-TP) Transport |
| 16 |
Service Interfaces, which are a User-to-Network Interface (UNI), and |
| 17 |
a Network-to-Network Interface (NNI). This document updates those |
| 18 |
reference models to show detailed reference points for these |
| 19 |
interfaces, along with further clarification of the functional |
| 20 |
architecture of MPLS-TP at a UNI and NNI. |
| 21 |
|
| 22 |
This document is a product of a joint Internet Engineering Task Force |
| 23 |
(IETF) / International Telecommunication Union Telecommunication |
| 24 |
Standardization Sector (ITU-T) effort to include an MPLS Transport |
| 25 |
Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge |
| 26 |
(PWE3) architectures to support the capabilities and functionalities |
| 27 |
of a packet transport network as defined by the ITU-T. |
| 28 |
|
| 29 |
Status of This Memo |
| 30 |
|
| 31 |
This document is not an Internet Standards Track specification; it is |
| 32 |
published for informational purposes. |
| 33 |
|
| 34 |
This document is a product of the Internet Engineering Task Force |
| 35 |
(IETF). It represents the consensus of the IETF community. It has |
| 36 |
received public review and has been approved for publication by the |
| 37 |
Internet Engineering Steering Group (IESG). Not all documents |
| 38 |
approved by the IESG are a candidate for any level of Internet |
| 39 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 40 |
|
| 41 |
Information about the current status of this document, any errata, |
| 42 |
and how to provide feedback on it may be obtained at |
| 43 |
<a href="http://www.rfc-editor.org/info/rfc6215">http://www.rfc-editor.org/info/rfc6215</a>. |
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Bocci, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6215">RFC 6215</a> MPLS-TP UNI and NNI April 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 73 |
|
| 74 |
The framework for MPLS in transport networks [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>] provides |
| 75 |
reference models for the MPLS Transport Profile (MPLS-TP) Transport |
| 76 |
Service Interfaces, which are a User-to-Network Interface (UNI) and a |
| 77 |
Network-to-Network Interface (NNI). This document updates those |
| 78 |
reference models to show detailed reference points for these |
| 79 |
interfaces, along with further clarification of the functional |
| 80 |
architecture of MPLS-TP at a UNI and NNI. |
| 81 |
|
| 82 |
This document is a product of a joint Internet Engineering Task Force |
| 83 |
(IETF) / International Telecommunication Union Telecommunication |
| 84 |
Standardization Sector (ITU-T) effort to include an MPLS Transport |
| 85 |
Profile within the IETF MPLS and PWE3 architectures to support the |
| 86 |
capabilities and functionalities of a packet transport network as |
| 87 |
defined by the ITU-T. |
| 88 |
|
| 89 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Updates to the MPLS-TP UNI and NNI</span> |
| 90 |
|
| 91 |
The Transport Service Interfaces for MPLS-TP are defined in <a href="./rfc5921#section-3.4.3">Section</a> |
| 92 |
<a href="./rfc5921#section-3.4.3">3.4.3 of [RFC5921]</a>. These definitions are illustrated by showing |
| 93 |
MPLS-TP Provider Edges (PEs) containing a UNI and an NNI. The |
| 94 |
figures illustrate the UNI and the NNI as a span. However, it is |
| 95 |
convention to illustrate these interfaces as reference points. |
| 96 |
Furthermore, in the case of a UNI, it is useful to illustrate the |
| 97 |
distribution of UNI functions between the Customer Edge (CE) side and |
| 98 |
the PE side of the UNI, i.e., the UNI-C (User-to-User Interface, |
| 99 |
Client side) and UNI-N (User-to-Network Interface, Network side), in |
| 100 |
order to show their relationship to one another. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Bocci, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6215">RFC 6215</a> MPLS-TP UNI and NNI April 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
This document provides updated illustrations of the MPLS-TP UNI and |
| 114 |
MPLS-TP NNI to show these additional details. These illustrations |
| 115 |
obsolete the corresponding ones in [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>]. This document also |
| 116 |
defines additional terminology referenced in the illustrations. No |
| 117 |
other updates are made by this document. |
| 118 |
|
| 119 |
Awareness of the Transport Service layer need exist only at PE nodes, |
| 120 |
and so only these nodes are illustrated in the figures. MPLS-TP |
| 121 |
Provider (P) nodes need have no awareness of this layer. Both PE and |
| 122 |
P nodes participate in the Transport Path layer. A PE terminates |
| 123 |
(i.e., is a Label Edge Router (LER) with respect to) the transport |
| 124 |
paths it supports, and is responsible for multiplexing and |
| 125 |
demultiplexing of Transport Service Instance traffic over such |
| 126 |
transport paths. |
| 127 |
|
| 128 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Terminology and Abbreviations</span> |
| 129 |
|
| 130 |
The terminology and abbreviations of [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>] apply. |
| 131 |
|
| 132 |
The following additional terminology is used in this document. |
| 133 |
|
| 134 |
Term Definition |
| 135 |
----- --------------------------------------- |
| 136 |
CP Control Plane |
| 137 |
NNI Network-to-Network Interface |
| 138 |
TSI Transport Service Instance |
| 139 |
UNI User-to-Network Interface |
| 140 |
UNI-C User-to-Network Interface, Client side |
| 141 |
UNI-N User-to-Network Interface, Network side |
| 142 |
|
| 143 |
Transport Service Instance: A single logical point-to-point |
| 144 |
connection at the Transport Service layer between the ingress PE |
| 145 |
providing a packet transport service to a CE, and the |
| 146 |
corresponding egress PE to which the peer CE is attached. |
| 147 |
|
| 148 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. MPLS-TP User-to-Network Interface</span> |
| 149 |
|
| 150 |
The MPLS-TP User-to-Network Interface (UNI) is illustrated in |
| 151 |
Figure 1. This figure obsoletes Figure 3 of [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>]. Note that |
| 152 |
the term "MPLS-TP UNI" is to be interpreted as a UNI to an MPLS-TP |
| 153 |
network and does not refer to the protocol transiting the UNI. The |
| 154 |
UNI for a particular client flow may involve signaling between the CE |
| 155 |
and PE. If signaling is used, it may traverse the same attachment |
| 156 |
circuit that supports the client flow. |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Bocci, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6215">RFC 6215</a> MPLS-TP UNI and NNI April 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
UNI |
| 170 |
: MPLS-TP |
| 171 |
:<-- UNI-C -->: : :<-- UNI-N ->: Network <-----> |
| 172 |
: function : : : function : |
| 173 |
--------------- : ------------:-------------------- |
| 174 |
: | : | : Transport | |
| 175 |
: | V | Client : Path | |
| 176 |
: | | Service : Mux/Demux | |
| 177 |
: | | Control : -- | |
| 178 |
: ---------- | | ----------: | | Transport| |
| 179 |
:| | | | | | | | Path | |
| 180 |
:|Signaling |_|___________|_|Signaling | | | ---------> |
| 181 |
:|Controller| | | |Controller| | | | |
| 182 |
: ---------- | | ---------- | | ---------> |
| 183 |
: :......|...........|......: : | | | |
| 184 |
: | Control | : | | Transport| |
| 185 |
: | Channel | : | | Path | |
| 186 |
: | | : | | ---------> |
| 187 |
: | | : | | -+----------->TSI |
| 188 |
: | | Transport : | | | ---------> |
| 189 |
: | Client | Service : | | | | |
| 190 |
: | Traffic | Data Plane: | | | | |
| 191 |
: ---------- | Flows | -------------- | | |Transport| |
| 192 |
:| Client |-|-----------|-|Client/Service|-| |- Path | |
| 193 |
:| Traffic |=|===========|=| Traffic | | | ---------> |
| 194 |
:|Processing| | | | Processing |=| |===+===========>TSI |
| 195 |
: ---------- | | -------------- | | ---------> |
| 196 |
: |______|___________|______| : | | | |
| 197 |
: | Data Link | : | | | |
| 198 |
: | | : -- | |
| 199 |
: | | : Transport | |
| 200 |
: | | : Path | |
| 201 |
: | | : Data Plane| |
| 202 |
--------------- --------------------------------- |
| 203 |
|
| 204 |
Customer Edge Node MPLS-TP Provider Edge Node |
| 205 |
|
| 206 |
Note: The client service control plane may be a control protocol |
| 207 |
belonging to the native service, or GMPLS. |
| 208 |
|
| 209 |
Figure 1: UNI between CE Node and MPLS-TP PE Node |
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Bocci, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6215">RFC 6215</a> MPLS-TP UNI and NNI April 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MPLS-TP Network-to-Network Interface</span> |
| 226 |
|
| 227 |
The MPLS-TP Network-to-Network Interface (NNI) is illustrated in |
| 228 |
Figure 2. This figure obsoletes Figure 5 of [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>]. The NNI for |
| 229 |
a particular Transport Service Instance may involve signaling between |
| 230 |
the two PEs. If signaling is used, it may traverse the same data- |
| 231 |
link that supports the service instance. |
| 232 |
NNI |
| 233 |
:<--- NNI --->: : :<--- NNI ---->: |
| 234 |
: Function : : : Function : |
| 235 |
--------------------------- : -------------------------- |
| 236 |
| : Transport | : | Transport : | |
| 237 |
| : Service CP | V | Service CP : | |
| 238 |
| : ---------- |Signaling| ---------- : | |
| 239 |
| : |Signaling |_| _______ |_|Signaling | : | |
| 240 |
| : |Controller| | | |Controller| : | |
| 241 |
| : ---------- | | ---------- : | |
| 242 |
| : :....... Control .......: : | |
| 243 |
| : | Channel | : | |
| 244 |
| - : Transport | | Transport : - | |
| 245 |
| | | : Path CP | | Path CP : | | | |
| 246 |
| | | : ---------- |Signaling| ---------- : | | | |
| 247 |
-----| | : |Signaling |_| _______ |_|Signaling | : | |----- |
| 248 |
---+-| | : |Controller| | | |Controller| : | |-+--- |
| 249 |
-----| | : ---------- | | ---------- : | |----- |
| 250 |
| | | : :....... Control .......: : | | | |
| 251 |
| | | : | Channel | : | | | |
| 252 |
| | | Transport Path | | Transport Path | | | |
| 253 |
| | | / mux/demux \ | | / mux/demux \| | | |
| 254 |
| | |/ : \-- | | -- / : | | | |
| 255 |
| | | ---------- | | |Transport| | | ---------- | | | |
| 256 |
| | |--|Transport |---| | | Path | | |---|Transport |--| | | |
| 257 |
-----| | | Service | | |-------------| | | Service | | |----- |
| 258 |
TSI+=| |==|Processing|===| |<+===TSI===+>| |===|Processing|==| |=+TSI |
| 259 |
-----| | ---------- | |-------------| | ---------- | |----- |
| 260 |
| | | : | | | | | | : | | | |
| 261 |
| | | : | | | | | | : | | | |
| 262 |
| - : -- | | -- : - | |
| 263 |
| : | | : | |
| 264 |
| Transport Path | | Transport Path | |
| 265 |
| Data Plane | Data Plane | |
| 266 |
--------------------------- -------------------------- |
| 267 |
MPLS-TP Provider MPLS-TP Provider |
| 268 |
Edge Node A Edge Node B |
| 269 |
|
| 270 |
Figure 2: NNI between MPLS-TP PE Nodes |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Bocci, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6215">RFC 6215</a> MPLS-TP UNI and NNI April 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 282 |
|
| 283 |
The security considerations of [<a href="./rfc5921" title=""A Framework for MPLS in Transport Networks"">RFC5921</a>] apply. The updated |
| 284 |
reference models provided by this document introduce no new security |
| 285 |
considerations. |
| 286 |
|
| 287 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span> |
| 288 |
|
| 289 |
The editors wish to thank the following for their contribution to |
| 290 |
this document: |
| 291 |
|
| 292 |
o Eve Varma |
| 293 |
|
| 294 |
o Dieter Beller |
| 295 |
|
| 296 |
o Lou Berger |
| 297 |
|
| 298 |
o Stewart Bryant |
| 299 |
|
| 300 |
o Italo Busi |
| 301 |
|
| 302 |
o The experts of ITU-T Study Group 15 and the IETF MPLS and PWE3 |
| 303 |
working groups. |
| 304 |
|
| 305 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span> |
| 306 |
|
| 307 |
[<a id="ref-RFC5921">RFC5921</a>] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. |
| 308 |
Berger, "A Framework for MPLS in Transport Networks", |
| 309 |
<a href="./rfc5921">RFC 5921</a>, July 2010. |
| 310 |
|
| 311 |
Authors' Addresses |
| 312 |
|
| 313 |
Matthew Bocci |
| 314 |
Alcatel-Lucent |
| 315 |
|
| 316 |
EMail: [email protected] |
| 317 |
|
| 318 |
|
| 319 |
Lieven Levrau |
| 320 |
Alcatel-Lucent |
| 321 |
|
| 322 |
EMail: [email protected] |
| 323 |
|
| 324 |
|
| 325 |
Dan Frost |
| 326 |
Cisco |
| 327 |
|
| 328 |
EMail: [email protected] |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Bocci, et al. Informational [Page 6] |
| 333 |
</pre> |