idnits 2.17.1 draft-ietf-mpls-tp-uni-nni-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5921, but the abstract doesn't seem to directly say this. It does mention RFC5921 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 7, 2011) is 4857 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Bocci 3 Internet-Draft L. Levrau 4 Updates: 5921 (if approved) Alcatel-Lucent 5 Intended status: Informational D. Frost 6 Expires: July 11, 2011 Cisco 7 January 7, 2011 9 MPLS Transport Profile User-to-Network and Network-to-Network Interfaces 10 draft-ietf-mpls-tp-uni-nni-03 12 Abstract 14 The framework for MPLS in transport networks (RFC 5921) 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 an MPLS-TP Network-to-Network Interface (NNI). This document updates 18 those 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. 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. 29 This Informational Internet-Draft is aimed at achieving IETF 30 Consensus before publication as an RFC and will be subject to an IETF 31 Last Call. 33 [RFC Editor, please remove this note before publication as an RFC and 34 insert the correct Streams Boilerplate to indicate that the published 35 RFC has IETF consensus.] 37 Status of this Memo 39 This Internet-Draft is submitted in full conformance with the 40 provisions of BCP 78 and BCP 79. 42 Internet-Drafts are working documents of the Internet Engineering 43 Task Force (IETF). Note that other groups may also distribute 44 working documents as Internet-Drafts. The list of current Internet- 45 Drafts is at http://datatracker.ietf.org/drafts/current/. 47 Internet-Drafts are draft documents valid for a maximum of six months 48 and may be updated, replaced, or obsoleted by other documents at any 49 time. It is inappropriate to use Internet-Drafts as reference 50 material or to cite them other than as "work in progress." 52 This Internet-Draft will expire on July 11, 2011. 54 Copyright Notice 56 Copyright (c) 2011 IETF Trust and the persons identified as the 57 document authors. All rights reserved. 59 This document is subject to BCP 78 and the IETF Trust's Legal 60 Provisions Relating to IETF Documents 61 (http://trustee.ietf.org/license-info) in effect on the date of 62 publication of this document. Please review these documents 63 carefully, as they describe your rights and restrictions with respect 64 to this document. Code Components extracted from this document must 65 include Simplified BSD License text as described in Section 4.e of 66 the Trust Legal Provisions and are provided without warranty as 67 described in the Simplified BSD License. 69 1. Introduction 71 The framework for MPLS in transport networks [RFC5921] provides 72 reference models for the MPLS Transport Profile (MPLS-TP) transport 73 service interfaces, which are a User-to-Network Interface (UNI), and 74 an MPLS-TP Network-to-Network Interface (NNI). This document updates 75 those reference models to show detailed reference points for these 76 interfaces, along with further clarification of the functional 77 architecture of MPLS-TP at a UNI and NNI. 79 This document is a product of a joint Internet Engineering Task Force 80 (IETF) / International Telecommunication Union Telecommunication 81 Standardization Sector (ITU-T) effort to include an MPLS Transport 82 Profile within the IETF MPLS and PWE3 architectures to support the 83 capabilities and functionalities of a packet transport network as 84 defined by the ITU-T. 86 1.1. Updates to the MPLS-TP UNI and NNI 88 The transport service interfaces for MPLS-TP are defined in Section 89 3.4.3 of [RFC5921]. These definitions are illustrated by showing 90 MPLS-TP PEs containing a UNI and an NNI. The figures illustrate the 91 UNI and the NNI as a span. However, it is convention to illustrate 92 these interfaces as reference points. Furthermore, in the case of a 93 UNI, it is useful to illustrate the distribution of UNI functions 94 between the Customer Edge (CE) side and the Provider Edge (PE) side 95 of the UNI, i.e. the UNI-C (User-to-User Interface, Client side) and 96 UNI-N (User-to-Network Interface, Network side), in order to show 97 their relationship to one another. 99 This document provides updated illustrations of the MPLS-TP UNI and 100 MPLS-TP NNI to show these additional details. These illustrations 101 obsolete the corresponding ones in [RFC5921]. This document also 102 defines additional terminology referenced in the illustrations. No 103 other updates are made by this document. 105 Awareness of the Transport Service layer need exist only at PE nodes, 106 and so only these nodes are illustrate in the figures. MPLS-TP 107 Provider (P) nodes need have no awareness of this layer. Both PE and 108 P nodes participate in the Transport Path layer. A PE terminates 109 (i.e., is an LER with respect to) the transport paths it supports, 110 and is responsible for multiplexing and demultiplexing of Transport 111 Service Instance traffic over such transport paths. 113 1.2. Terminology and Abbreviations 115 The terminology and abbreviations of [RFC5921] apply. 117 The following additional terminology is used in this document. 119 Term Definition 120 ----- --------------------------------------- 121 CP Control Plane 122 NNI Network-to-Network Interface 123 TSI Transport Service Instance 124 UNI User-to-Network Interface 125 UNI-C User-to-Network Interface, Client side 126 UNI-N User-to-Network Interface, Network side 128 Transport Service Instance: A single logical point-to-point 129 connection at the Transport Service layer between the ingress PE 130 providing a packet transport service to a CE, and the 131 corresponding egress PE to which the peer CE is attached. 133 2. MPLS-TP User-to-Network Interface 135 The MPLS-TP User-to-Network Interface (UNI) is illustrated in 136 Figure 1. This figure obsoletes Figure 3 of [RFC5921]. Note that 137 the term MPLS-TP UNI is to be interpreted as a UNI to an MPLS-TP 138 network and does not refer to the protocol transiting the UNI. The 139 UNI for a particular client flow may involve signaling between the CE 140 and PE. If signaling is used, it may traverse the same attachment 141 circuit that supports the client flow. 143 UNI 144 : MPLS-TP 145 :<-- UNI-C -->: : :<-- UNI-N ->: Network <-----> 146 : function : : : function : 147 --------------- : ------------:-------------------- 148 : | : | : Transport | 149 : | V | Client : Path | 150 : | | Service : Mux/Demux | 151 : | | Control : -- | 152 : ---------- | | ----------: | | Transport| 153 :| | | | | | | | Path | 154 :|Signaling |_|___________|_|Signaling | | | ---------> 155 :|Controller| | | |Controller| | | | 156 : ---------- | | ---------- | | ---------> 157 : :......|...........|......: : | | | 158 : | Control | : | | Transport| 159 : | Channel | : | | Path | 160 : | | : | | ---------> 161 : | | : | | -+----------->TSI 162 : | | Transport : | | | ---------> 163 : | Client | Service : | | | | 164 : | Traffic | Data Plane: | | | | 165 : ---------- | Flows | -------------- | | |Transport| 166 :| Client |-|-----------|-|Client/Service|-| |- Path | 167 :| Traffic |=|===========|=| Traffic | | | ---------> 168 :|Processing| | | | Processing |=| |===+===========>TSI 169 : ---------- | | -------------- | | ---------> 170 : |______|___________|______| : | | | 171 : | Data Link | : | | | 172 : | | : -- | 173 : | | : Transport | 174 : | | : Path | 175 : | | : Data Plane| 176 --------------- --------------------------------- 178 Customer Edge Node MPLS-TP Provider Edge Node 180 Note: The client service control plane may be a control protocol 181 belonging to the native service, or GMPLS. 183 Figure 1: UNI Between CE Node and MPLS-TP PE Node 185 3. MPLS-TP Network-to-Network Interface 187 The MPLS-TP Network-to-Network Interface (NNI) is illustrated in 188 Figure 2. This figure obsoletes Figure 5 of [RFC5921]. The NNI for 189 a particular Transport Service Instance may involve signaling between 190 the two PEs. If signaling is used, it may traverse the same data- 191 link that supports the service instance. 192 NNI 193 :<--- NNI --->: : :<--- NNI ---->: 194 : Function : : : Function : 195 --------------------------- : -------------------------- 196 | : Transport | : | Transport : | 197 | : Service CP | V | Service CP : | 198 | : ---------- |Signaling| ---------- : | 199 | : |Signaling |_| _______ |_|Signaling | : | 200 | : |Controller| | | |Controller| : | 201 | : ---------- | | ---------- : | 202 | : :....... Control .......: : | 203 | : | Channel | : | 204 | - : Transport | | Transport : - | 205 | | | : Path CP | | Path CP : | | | 206 | | | : ---------- |Signaling| ---------- : | | | 207 -----| | : |Signaling |_| _______ |_|Signaling | : | |----- 208 ---+-| | : |Controller| | | |Controller| : | |-+--- 209 -----| | : ---------- | | ---------- : | |----- 210 | | | : :....... Control .......: : | | | 211 | | | : | Channel | : | | | 212 | | | Transport Path | | Transport Path | | | 213 | | | / mux/demux \ | | / mux/demux \| | | 214 | | |/ : \-- | | -- / : | | | 215 | | | ---------- | | |Transport| | | ---------- | | | 216 | | |--|Transport |---| | | Path | | |---|Transport |--| | | 217 -----| | | Service | | |-------------| | | Service | | |----- 218 TSI+=| |==|Processing|===| |<+===TSI===+>| |===|Processing|==| |=+TSI 219 -----| | ---------- | |-------------| | ---------- | |----- 220 | | | : | | | | | | : | | | 221 | | | : | | | | | | : | | | 222 | - : -- | | -- : - | 223 | : | | : | 224 | Transport Path | | Transport Path | 225 | Data Plane | Data Plane | 226 --------------------------- -------------------------- 227 MPLS-TP Provider MPLS-TP Provider 228 Edge Node A Edge Node B 230 Figure 2: NNI Between MPLS-TP PE Nodes 232 4. IANA Considerations 234 This document makes no request of IANA. 236 Note to RFC Editor: this section may be removed on publication as an 237 RFC. 239 5. Security Considerations 241 The security considerations of [RFC5921] apply. The updated 242 reference models provided by this document introduce no new security 243 considerations. 245 6. Acknowledgements 247 The editors wish to thank the following for their contribution to 248 this document: 250 o Eve Varma. 252 o Dieter Beller. 254 o Lou Berger. 256 o Stewart Bryant. 258 o Italo Busi. 260 o The experts of ITU-T Study Group 15 and the IETF MPLS and PWE3 261 working groups. 263 7. Normative References 265 [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. 266 Berger, "A Framework for MPLS in Transport Networks", 267 RFC 5921, July 2010. 269 Authors' Addresses 271 Matthew Bocci 272 Alcatel-Lucent 274 Email: matthew.bocci@alcatel-lucent.com 275 Lieven Levrau 276 Alcatel-Lucent 278 Email: lieven.levrau@alcatel-lucent.com 280 Dan Frost 281 Cisco 283 Email: danfrost@cisco.com