idnits 2.17.1 draft-ietf-detnet-mpls-over-udp-ip-01.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 (July 1, 2019) is 1761 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 (-07) exists of draft-ietf-detnet-ip-00 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-mpls-00 == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-21 == Outdated reference: A later version (-16) exists of draft-ietf-detnet-security-04 Summary: 0 errors (**), 0 flaws (~~), 5 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: January 2, 2020 L. Berger 6 LabN Consulting, L.L.C. 7 A. Malis 8 S. Bryant 9 Futurewei Technologies 10 J. Korhonen 11 July 1, 2019 13 DetNet Data Plane: MPLS over UDP/IP 14 draft-ietf-detnet-mpls-over-udp-ip-01 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 over UDP/IP packet switched 21 networks. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 2, 2020. 40 Copyright Notice 42 Copyright (c) 2019 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 60 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 61 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4 62 3. DetNet MPLS Operation over DetNet 63 IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 4. DetNet Data Plane Procedures . . . . . . . . . . . . . . . . 5 65 5. Management and Control Information Summary . . . . . . . . . 6 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 67 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 68 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 70 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 71 9.2. Informative References . . . . . . . . . . . . . . . . . 7 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 Deterministic Networking (DetNet) is a service that can be offered by 77 a network to DetNet flows. DetNet provides these flows with a low 78 packet loss rates and assured maximum end-to-end delivery latency. 79 General background and concepts of DetNet can be found in 80 [I-D.ietf-detnet-architecture]. 82 This document specifies use of the MPLS DetNet encapsulation over an 83 IP network. The approach is modeled on the operation of MPLS over an 84 IP Packet Switched Network (PSN) [RFC7510]. It maps the MPLS data 85 plane encapsulation described in [I-D.ietf-detnet-mpls] to the DetNet 86 IP data plane defined in [I-D.ietf-detnet-ip]. 88 To carry DetNet flows with full functionality at the DetNet layer 89 over an IP network, the following components are required (these are 90 a subset of the requirements for MPLS encapsulation listed in 91 [I-D.ietf-detnet-mpls]): 93 1. A method of identifying the DetNet flow group to the processing 94 element. 96 2. A method of carrying the DetNet sequence number. 98 3. A method of distinguishing DetNet OAM packets from DetNet data 99 packets. 101 4. A method of carrying queuing and forwarding indication. 103 These requirements are satisfied by the DetNet over MPLS 104 Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly 105 satisfied by the DetNet IP data plane defined in [I-D.ietf-detnet-ip] 107 2. Terminology 109 2.1. Terms Used in This Document 111 This document uses the terminology established in the DetNet 112 architecture [I-D.ietf-detnet-architecture], and the reader is 113 assumed to be familiar with that document and its terminology. 115 2.2. Abbreviations 117 The following abbreviations are used in this document: 119 d-CW A DetNet Control Word (d-CW) is used for sequencing and 120 identifying duplicate packets of a DetNet flow at the 121 DetNet service sub-layer. 123 DetNet Deterministic Networking. 125 A-Label A special case of an S-Label, whose properties are 126 known only at the aggregation and deaggregation end- 127 points. 129 F-Label A Detnet "forwarding" label that identifies the LSP 130 used to forward a DetNet flow across an MPLS PSN, e.g., 131 a hop-by-hop label used between label switching 132 routers. 134 MPLS Multiprotocol Label Switching. 136 OAM Operations, Administration, and Maintenance. 138 PEF Packet Elimination Function. 140 POF Packet Ordering Function. 142 PRF Packet Replication Function. 144 PSN Packet Switched Network. 146 S-Label A DetNet "service" label that is used between DetNet 147 nodes that implement also the DetNet service sub-layer 148 functions. An S-Label is also used to identify a 149 DetNet flow at DetNet service sub-layer. 151 2.3. Requirements Language 153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 155 "OPTIONAL" in this document are to be interpreted as described in BCP 156 14 [RFC2119] [RFC8174] when, and only when, they appear in all 157 capitals, as shown here. 159 3. DetNet MPLS Operation over DetNet IP PSNs 161 This document builds on the specification of MPLS over UDP defined in 162 [RFC7510]. It may replace partly or entirely the F-Label(s) used in 163 [I-D.ietf-detnet-mpls] with UDP and IP headers. The UDP and IP 164 header information is used to identify DetNet flows, including member 165 flows, per [I-D.ietf-detnet-ip]. The resulting encapsulation is 166 shown in Figure 1. There may be zero or more F-label(s) between the 167 S-label and the UDP header. 169 Note that this encapsulation works equally well with IPv4, IPv6, and 170 IPv6-based Segment Routing [I-D.ietf-6man-segment-routing-header]. 172 +---------------------------------+ 173 | | 174 | DetNet App-Flow | 175 | Payload Packet | 176 | | 177 +---------------------------------+ <--\ 178 | DetNet Control Word | | 179 +---------------------------------+ +--> DetNet data plane 180 | S-Label | | MPLS encapsulation 181 +---------------------------------+ | 182 | [ F-label(s) ] | | 183 +---------------------------------+ <--+ 184 | UDP Header | | 185 +---------------------------------+ +--> DetNet data plane 186 | IP Header | | IP encapsulation 187 +---------------------------------+ <--/ 188 | Data-Link | 189 +---------------------------------+ 190 | Physical | 191 +---------------------------------+ 193 Figure 1: UDP/IP Encapsulation of DetNet MPLS 195 d-CW, S-Labels and zero or more F-Labels are used as defined in 196 [I-D.ietf-detnet-mpls] and are not modified by this document. In 197 case of aggregates the A-Label is treated as an S-Label and it too is 198 not modified. 200 4. DetNet Data Plane Procedures 202 To support outgoing DetNet MPLS over UDP/IP encapsulation, an 203 implementation MUST support the provisioning of UDP and IP header 204 information in addition or in place of F-Label(s). Note, when PRF is 205 performed at the MPLS service sub-layer, there will be multiple 206 member flows, and each member flow will require the provisioning of 207 their own UDP and IP header information. The headers for each 208 outgoing packet MUST be formatted on the configuration information 209 and as defined in [RFC7510], with one exception. Note that the UDP 210 Source Port value MUST be set to uniquely identify the DetNet flow. 211 The packet MUST then be handed as a DetNet IP packet, per 212 [I-D.ietf-detnet-ip]. This includes QoS related traffic treatment. 214 To support receive processing an implementation MUST also support the 215 provisioning of received UDP and IP header information. The 216 provisioned information MUST be used to identify incoming app-flows 217 based on the combination of S-Label and incoming encapsulation header 218 information. Normal receive processing as defined in 219 [I-D.ietf-detnet-mpls], including PEF and POF, can then take place. 221 5. Management and Control Information Summary 223 The following summarizes the set of information that is needed to 224 configure DetNet MPLS over UDP/IP: 226 o Label information (S-label or F-label) to be mapped to UDP/IP 227 flow. Note that a single S-Label can map to multiple sets of UPD/ 228 IP information when PREOF is used. 230 o IPv4 and IPv6 source address field. 232 o IPv4 and IPv6 destination address field. 234 o IPv4 Type of Service and IPv6 Traffic Class Fields. 236 o UDP Source Port. 238 o UDP Destination Port. 240 This information MUST be provisioned per DetNet flow via 241 configuration, e.g., via the controller or management plane. 243 It is the responsibility of the DetNet controller plane to properly 244 provision both flow identification information and the flow specific 245 resources needed to provided the traffic treatment needed to meet 246 each flow's service requirements. This applies for aggregated and 247 individual flows. 249 6. Security Considerations 251 The security considerations of DetNet in general are discussed in 252 [I-D.ietf-detnet-architecture] and [I-D.ietf-detnet-security]. MPLS 253 and IP specific security considerations are described in 254 [I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip]. This draft does not 255 have additional security considerations. 257 7. IANA Considerations 259 This document makes no IANA requests. 261 8. Acknowledgements 263 The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson, 264 David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David 265 Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J. 266 Bernardos for their various contributions to this work. 268 9. References 270 9.1. Normative References 272 [I-D.ietf-detnet-ip] 273 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 274 Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", 275 draft-ietf-detnet-ip-00 (work in progress), May 2019. 277 [I-D.ietf-detnet-mpls] 278 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 279 Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", 280 draft-ietf-detnet-mpls-00 (work in progress), May 2019. 282 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 283 Requirement Levels", BCP 14, RFC 2119, 284 DOI 10.17487/RFC2119, March 1997, 285 . 287 [RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black, 288 "Encapsulating MPLS in UDP", RFC 7510, 289 DOI 10.17487/RFC7510, April 2015, 290 . 292 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 293 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 294 May 2017, . 296 9.2. Informative References 298 [I-D.ietf-6man-segment-routing-header] 299 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 300 Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment 301 Routing Header (SRH)", draft-ietf-6man-segment-routing- 302 header-21 (work in progress), June 2019. 304 [I-D.ietf-detnet-architecture] 305 Finn, N., Thubert, P., Varga, B., and J. Farkas, 306 "Deterministic Networking Architecture", draft-ietf- 307 detnet-architecture-13 (work in progress), May 2019. 309 [I-D.ietf-detnet-security] 310 Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, 311 J., Austad, H., Stanton, K., and N. Finn, "Deterministic 312 Networking (DetNet) Security Considerations", draft-ietf- 313 detnet-security-04 (work in progress), March 2019. 315 Authors' Addresses 317 Balazs Varga (editor) 318 Ericsson 319 Magyar Tudosok krt. 11. 320 Budapest 1117 321 Hungary 323 Email: balazs.a.varga@ericsson.com 325 Janos Farkas 326 Ericsson 327 Magyar Tudosok krt. 11. 328 Budapest 1117 329 Hungary 331 Email: janos.farkas@ericsson.com 333 Lou Berger 334 LabN Consulting, L.L.C. 336 Email: lberger@labn.net 338 Andrew G. Malis 339 Futurewei Technologies 341 Email: agmalis@gmail.com 343 Stewart Bryant 344 Futurewei Technologies 346 Email: stewart.bryant@gmail.com 348 Jouni Korhonen 350 Email: jouni.nospam@gmail.com