idnits 2.17.1 draft-ietf-detnet-mpls-over-udp-ip-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 5, 2019) is 1817 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-18 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-architecture-12 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DetNet B. Varga, Ed. 3 Internet-Draft J. Farkas 4 Intended status: Standards Track Ericsson 5 Expires: November 6, 2019 L. Berger 6 LabN Consulting, L.L.C. 7 A. Malis 8 S. Bryant 9 Huawei Technologies 10 J. Korhonen 11 May 5, 2019 13 DetNet Data Plane: MPLS over IP 14 draft-ietf-detnet-mpls-over-udp-ip-00 16 Abstract 18 This document specifies the MPLS Deterministic Networking data plane 19 operation and encapsulation over an IP network. The approach is 20 modeled on the operation of MPLS and PseudoWires (PW) over IP. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on November 6, 2019. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 59 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 60 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 61 4. DetNet MPLS Operation over DetNet 62 IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 64 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 65 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 67 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 9.1. Normative References . . . . . . . . . . . . . . . . . . 8 69 9.2. Informative References . . . . . . . . . . . . . . . . . 8 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 72 1. Introduction 74 Deterministic Networking (DetNet) is a service that can be offered by 75 a network to DetNet flows. DetNet provides these flows with a low 76 packet loss rates and assured maximum end-to-end delivery latency. 77 General background and concepts of DetNet can be found in 78 [I-D.ietf-detnet-architecture]. 80 The DetNet Architecture decomposes the DetNet related data plane 81 functions into two sub-layers: a service sub-layer and a forwarding 82 sub-layer. The service sub-layer is used to provide DetNet service 83 protection and reordering. The forwarding sub-layer is used to 84 provides congestion protection (low loss, assured latency, and 85 limited reordering) leveraging MPLS Traffic Engineering mechanisms. 87 This document specifies use of the MPLS DetNet encapsulation over an 88 IP network. The approach is modeled on the operation of MPLS and 89 PseudoWires (PW) over an IP Packet Switched Network (PSN) 90 [RFC3985][RFC4385][RFC7510]. It maps the MPLS data plane 91 encapsulation described in [I-D.ietf-detnet-mpls] to the DetNet IP 92 data plane defined in [I-D.ietf-detnet-ip]. 94 To carry DetNet with full functionality at the DetNet layer over an 95 IP network, the following components are required (these are a subset 96 of the requirements for MPLS encapsulation listed in 97 [I-D.ietf-detnet-mpls]): 99 1. A method of identifying the DetNet flow group to the processing 100 element. 102 2. A method of carrying the DetNet sequence number. 104 3. A method of distinguishing DetNet OAM packets from DetNet data 105 packets. 107 4. A method of carrying queuing and forwarding indication. 109 These requirements are satisfied by the DetNet over MPLS 110 Encapsulation described in [I-D.ietf-detnet-mpls]. 112 2. Terminology 114 2.1. Terms Used in This Document 116 This document uses the terminology established in the DetNet 117 architecture [I-D.ietf-detnet-architecture], and the reader is 118 assumed to be familiar with that document and its terminology. 120 2.2. Abbreviations 122 The following abbreviations are used in this document: 124 CW Control Word. 126 d-CW A DetNet Control Word (d-CW) is used for sequencing and 127 identifying duplicate packets of a DetNet flow at the 128 DetNet service sub-layer. 130 DetNet Deterministic Networking. 132 F-Label A Detnet "forwarding" label that identifies the LSP 133 used to forward a DetNet flow across an MPLS PSN, e.g., 134 a hop-by-hop label used between label switching routers 135 (LSR). 137 LSR Label Switching Router. 139 MPLS Multiprotocol Label Switching. 141 OAM Operations, Administration, and Maintenance. 143 PEF Packet Elimination Function. 145 PRF Packet Replication Function. 147 PREOF Packet Replication, Elimination and Ordering Functions. 149 POF Packet Ordering Function. 151 PSN Packet Switched Network. 153 PW PseudoWire. 155 S-Label A DetNet "service" label that is used between DetNet 156 nodes that implement also the DetNet service sub-layer 157 functions. An S-Label is also used to identify a 158 DetNet flow at DetNet service sub-layer. 160 3. Requirements Language 162 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 163 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 164 "OPTIONAL" in this document are to be interpreted as described in BCP 165 14 [RFC2119] [RFC8174] when, and only when, they appear in all 166 capitals, as shown here. 168 4. DetNet MPLS Operation over DetNet IP PSNs 170 This document builds on the specification of MPLS over UDP and IP 171 defined in [RFC7510]. It replaces the F-Label(s) used in 172 [I-D.ietf-detnet-mpls] with UDP and IP headers. The UDP and IP 173 header information is used to identify DetNet flows, including member 174 flows, per [I-D.ietf-detnet-ip]. The resulting encapsulation is 175 shown in Figure 1. 177 Note that this encapsulation works equally well with IPv4, IPv6, and 178 IPv6-based Segment Routing [I-D.ietf-6man-segment-routing-header]. 180 +---------------------------------+ 181 | | 182 | DetNet App-Flow | 183 | Payload Packet | 184 | | 185 +---------------------------------+ <--\ 186 | DetNet Control Word | | 187 +---------------------------------+ +--> DetNet data plane 188 | S-Label | | MPLS encapsulation 189 +---------------------------------+ <--+ 190 | UDP Header | | 191 +---------------------------------+ +--> DetNet data plane 192 | IP Header | | IP encapsulation 193 +---------------------------------+ <--/ 194 | Data-Link | 195 +---------------------------------+ 196 | Physical | 197 +---------------------------------+ 199 Figure 1: IP Encapsulation of DetNet MPLS 201 d-CW and and S-Labels are used as defined in [I-D.ietf-detnet-mpls] 202 and are not modified by this document. 204 To support outgoing DetNet MPLS over IP, an implementation MUST 205 support the provisioning of IP/UDP header information in place of 206 sets of F-Labels. Note that multiple sets of F-Labels can be 207 provisioned to support PRF on transmitted DetNet flows and therefore, 208 when PRF is supported, multiple IP/UDP headers MAY be provisioned. 209 When multiple IP/UDP headers are provisioned for a particular 210 outgoing app-flow, a copy of the outgoing packet, including the 211 pushed S-Label, MUST be made for each. The headers for each outgoing 212 packet MUST be based on the configuration information and as defined 213 in [RFC7510], with one exception. The one exception is that the UDP 214 Source Port value MUST be set to uniquely identify the DetNet 215 (forwarding sub-layer) flow. The packet MUST then be handed as a 216 DetNet IP packet, per [I-D.ietf-detnet-ip]. 218 To support receive processing an implementation MUST also support the 219 provisioning of received IP/UDP header information. When S-Labels 220 are taken from platform label space, all that is required is to 221 provision that receiving IP/UDP encapsulated DetNet MPLS packets is 222 permitted. Once the IP/UDP header is stripped, the S-label uniquely 223 identifies the app-flow. When S-Labels are not taken from platform 224 label space, IP/UDP header information MUST be provisioned. The 225 provisioned information MUST then be used to identify incoming app- 226 flows based on the combination of S-Label and incoming IP/UDP header. 227 Normal receive processing, including PEOF can then take place. 229 5. Security Considerations 231 The security considerations of DetNet in general are discussed in 232 [I-D.ietf-detnet-architecture] and [I-D.sdt-detnet-security]. Other 233 security considerations will be added in a future version of this 234 draft. 236 6. IANA Considerations 238 This document makes no IANA requests. 240 7. Contributors 242 RFC7322 limits the number of authors listed on the front page of a 243 draft to a maximum of 5, far fewer than the many individuals below 244 who made important contributions to this draft. The editor wishes to 245 thank and acknowledge each of the following authors for contributing 246 text to this draft. See also Section 8. 248 Loa Andersson 249 Huawei 250 Email: loa@pi.nu 252 Yuanlong Jiang 253 Huawei 254 Email: jiangyuanlong@huawei.com 256 Norman Finn 257 Huawei 258 3101 Rio Way 259 Spring Valley, CA 91977 260 USA 261 Email: norman.finn@mail01.huawei.com 263 Janos Farkas 264 Ericsson 265 Magyar Tudosok krt. 11. 266 Budapest 1117 267 Hungary 268 Email: janos.farkas@ericsson.com 270 Carlos J. Bernardos 271 Universidad Carlos III de Madrid 272 Av. Universidad, 30 273 Leganes, Madrid 28911 274 Spain 275 Email: cjbc@it.uc3m.es 277 Tal Mizrahi 278 Marvell 279 6 Hamada st. 280 Yokneam 281 Israel 282 Email: talmi@marvell.com 284 Lou Berger 285 LabN Consulting, L.L.C. 286 Email: lberger@labn.net 288 Stewart Bryant 289 Huawei Technologies 290 Email: stewart.bryant@gmail.com 292 Mach Chen 293 Huawei Technologies 294 Email: mach.chen@huawei.com 296 Andrew G. Malis 297 Huawei Technologies 298 Email: agmalis@gmail.com 300 8. Acknowledgements 302 The author(s) ACK and NACK. 304 The following people were part of the DetNet Data Plane Solution 305 Design Team: 307 Jouni Korhonen 309 Janos Farkas 311 Norman Finn 313 Balazs Varga 315 Loa Andersson 317 Tal Mizrahi 319 David Mozes 321 Yuanlong Jiang 322 Andrew Malis 324 Carlos J. Bernardos 326 The DetNet chairs serving during the DetNet Data Plane Solution 327 Design Team: 329 Lou Berger 331 Pat Thaler 333 9. References 335 9.1. Normative References 337 [I-D.ietf-detnet-ip] 338 Korhonen, J., Varga, B., "DetNet IP", 2019. 340 [I-D.ietf-detnet-mpls] 341 Korhonen, J., Varga, B., "DetNet MPLS", 2019. 343 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 344 Requirement Levels", BCP 14, RFC 2119, 345 DOI 10.17487/RFC2119, March 1997, 346 . 348 [RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, 349 "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for 350 Use over an MPLS PSN", RFC 4385, DOI 10.17487/RFC4385, 351 February 2006, . 353 [RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black, 354 "Encapsulating MPLS in UDP", RFC 7510, 355 DOI 10.17487/RFC7510, April 2015, 356 . 358 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 359 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 360 May 2017, . 362 9.2. Informative References 364 [I-D.ietf-6man-segment-routing-header] 365 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 366 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 367 (SRH)", draft-ietf-6man-segment-routing-header-18 (work in 368 progress), April 2019. 370 [I-D.ietf-detnet-architecture] 371 Finn, N., Thubert, P., Varga, B., and J. Farkas, 372 "Deterministic Networking Architecture", draft-ietf- 373 detnet-architecture-12 (work in progress), March 2019. 375 [I-D.sdt-detnet-security] 376 Mizrahi, T., Grossman, E., Hacker, A., Das, S., 377 "Deterministic Networking (DetNet) Security 378 Considerations, draft-sdt-detnet-security, work in 379 progress", 2017. 381 [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation 382 Edge-to-Edge (PWE3) Architecture", RFC 3985, 383 DOI 10.17487/RFC3985, March 2005, 384 . 386 Authors' Addresses 388 Balazs Varga (editor) 389 Ericsson 390 Magyar Tudosok krt. 11. 391 Budapest 1117 392 Hungary 394 Email: balazs.a.varga@ericsson.com 396 Janos Farkas 397 Ericsson 398 Magyar Tudosok krt. 11. 399 Budapest 1117 400 Hungary 402 Email: janos.farkas@ericsson.com 404 Lou Berger 405 LabN Consulting, L.L.C. 407 Email: lberger@labn.net 409 Andrew G. Malis 410 Huawei Technologies 412 Email: agmalis@gmail.com 413 Stewart Bryant 414 Huawei Technologies 416 Email: stewart.bryant@gmail.com 418 Jouni Korhonen 420 Email: jouni.nospam@gmail.com