idnits 2.17.1 draft-ietf-detnet-mpls-over-udp-ip-05.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 (February 3, 2020) is 1545 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-04 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-mpls-04 == Outdated reference: A later version (-16) exists of draft-ietf-detnet-security-07 Summary: 0 errors (**), 0 flaws (~~), 4 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: August 6, 2020 L. Berger 6 LabN Consulting, L.L.C. 7 A. Malis 8 Independent 9 S. Bryant 10 Futurewei Technologies 11 February 3, 2020 13 DetNet Data Plane: MPLS over UDP/IP 14 draft-ietf-detnet-mpls-over-udp-ip-05 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 August 6, 2020. 40 Copyright Notice 42 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . 7 69 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 70 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 72 10.2. Informative References . . . . . . . . . . . . . . . . . 7 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 75 1. Introduction 77 Deterministic Networking (DetNet) is a service that can be offered by 78 a network to DetNet flows. DetNet provides these flows extremely low 79 packet loss rates and assured maximum end-to-end delivery latency. 80 General background and concepts of DetNet can be found in [RFC8655]. 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 MPLS flows with full functionality at the DetNet 89 layer over an IP network, the following components are required 90 (these are a subset of the requirements for MPLS encapsulation listed 91 in [I-D.ietf-detnet-mpls]): 93 1. A method for identifying DetNet flows to the processing element. 95 2. A method for carrying the DetNet sequence number. 97 3. A method for distinguishing DetNet OAM packets from DetNet data 98 packets. 100 4. A method for carrying queuing and forwarding indication. 102 These requirements are satisfied by the DetNet over MPLS 103 Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly 104 satisfied (i.e., IP flows can be identified however no DetNet 105 sequence number is carried) by the DetNet IP data plane defined in 106 [I-D.ietf-detnet-ip] 108 2. Terminology 110 2.1. Terms Used in This Document 112 This document uses the terminology established in the DetNet 113 architecture [RFC8655], and the reader is assumed to be familiar with 114 that document and its terminology. 116 2.2. Abbreviations 118 The following abbreviations are used in this document: 120 d-CW A DetNet Control Word (d-CW) is used for sequencing and 121 identifying duplicate packets of a DetNet flow at the 122 DetNet service sub-layer. 124 DetNet Deterministic Networking. 126 A-Label A special case of an S-Label, whose properties are 127 known only at the aggregation and deaggregation end- 128 points. 130 F-Label A Detnet "forwarding" label that identifies the LSP 131 used to forward a DetNet flow across an MPLS PSN, e.g., 132 a hop-by-hop label used between label switching 133 routers. 135 MPLS Multiprotocol Label Switching. 137 OAM Operations, Administration, and Maintenance. 139 PEF Packet Elimination Function. 141 POF Packet Ordering Function. 143 PREOF Packet Replication, Elimination and Ordering Functions. 145 PRF Packet Replication Function. 147 PSN Packet Switched Network. 149 S-Label A DetNet "service" label that is used between DetNet 150 nodes that also implement the DetNet service sub-layer 151 functions. An S-Label is also used to identify a 152 DetNet flow at DetNet service sub-layer. 154 2.3. Requirements Language 156 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 157 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 158 "OPTIONAL" in this document are to be interpreted as described in BCP 159 14 [RFC2119] [RFC8174] when, and only when, they appear in all 160 capitals, as shown here. 162 3. DetNet MPLS Operation over DetNet IP PSNs 164 This document builds on the specification of MPLS over UDP defined in 165 [RFC7510]. It may replace partly or entirely the F-Label(s) used in 166 [I-D.ietf-detnet-mpls] with UDP and IP headers. The UDP and IP 167 header information is used to identify DetNet flows, including member 168 flows, per [I-D.ietf-detnet-ip]. The resulting encapsulation is 169 shown in Figure 1. There may be zero or more F-label(s) between the 170 S-label and the UDP header. 172 Note that this encapsulation works equally well with IPv4, IPv6, and 173 IPv6-based Segment Routing [I-D.ietf-6man-segment-routing-header]. 175 +---------------------------------+ 176 | | 177 | DetNet App-Flow | 178 | Payload Packet | 179 | | 180 +---------------------------------+ <--\ 181 | DetNet Control Word | | 182 +---------------------------------+ +--> DetNet data plane 183 | S-Label | | MPLS encapsulation 184 +---------------------------------+ | 185 | [ F-label(s) ] | | 186 +---------------------------------+ <--+ 187 | UDP Header | | 188 +---------------------------------+ +--> DetNet data plane 189 | IP Header | | IP encapsulation 190 +---------------------------------+ <--/ 191 | Data-Link | 192 +---------------------------------+ 193 | Physical | 194 +---------------------------------+ 196 Figure 1: UDP/IP Encapsulation of DetNet MPLS 198 S-Labels, A-Labels (when present), d-CW and zero or more F-Labels are 199 used as defined in [I-D.ietf-detnet-mpls] and are not modified by 200 this document. 202 4. DetNet Data Plane Procedures 204 To support outgoing DetNet MPLS over UDP/IP encapsulation, an 205 implementation MUST support the provisioning of UDP and IP header 206 information in addition or in place of F-Label(s). Note, when PRF is 207 performed at the MPLS service sub-layer, there will be multiple 208 member flows, and each member flow will require the provisioning of 209 their own UDP and IP header information. The headers for each 210 outgoing packet MUST be formatted according to the configuration 211 information and as defined in [RFC7510], and the UDP Source Port 212 value MUST be set to uniquely identify the DetNet flow. The packet 213 MUST then be handled as a DetNet IP packet, per [I-D.ietf-detnet-ip]. 214 This includes QoS related traffic treatment. 216 To support the receive processing defined in this document, an 217 implementation MUST also support the provisioning of received UDP and 218 IP header information. The provisioned information MUST be used to 219 identify incoming app-flows based on the combination of S-Label and 220 incoming encapsulation header information. Normal receive processing 221 as defined in [I-D.ietf-detnet-mpls], including PEF and POF, can then 222 take place. 224 5. Management and Control Information Summary 226 The following summarizes the set of information that is needed to 227 configure DetNet MPLS over UDP/IP: 229 o Label information (A-labels, S-labels and F-labels) to be mapped 230 to UDP/IP flow. Note that for example, a single S-Label can map 231 to multiple sets of UDP/IP information when PREOF is used. 233 o IPv4 or IPv6 source address field. 235 o IPv4 or IPv6 destination address field. 237 o DSCP Field in either IPv4 Type of Service or IPv6 Traffic Class 238 Fields. 240 o UDP Source Port. 242 o UDP Destination Port. 244 This information MUST be provisioned per DetNet flow via 245 configuration, e.g., via the controller [RFC8655] or management 246 plane. 248 It is the responsibility of the DetNet controller plane to properly 249 provision both flow identification information and the flow specific 250 resources needed to provide the traffic treatment needed to meet each 251 flow's service requirements. This applies for aggregated and 252 individual flows. 254 6. Security Considerations 256 The security considerations of DetNet in general are discussed in 257 [RFC8655] and [I-D.ietf-detnet-security]. MPLS and IP specific 258 security considerations are described in [I-D.ietf-detnet-mpls] and 259 [I-D.ietf-detnet-ip]. This draft does not have additional security 260 considerations. 262 7. IANA Considerations 264 This document makes no IANA requests. 266 8. Acknowledgements 268 The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson, 269 David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David 270 Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J. 271 Bernardos for their various contributions to this work. 273 9. Contributors 275 This document is derived from an earlier draft that was edited by 276 Jouni Korhonen (jouni.nospam@gmail.com) and as such, he contributed 277 to and authored text in this document. 279 10. References 281 10.1. Normative References 283 [I-D.ietf-detnet-ip] 284 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 285 Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", 286 draft-ietf-detnet-ip-04 (work in progress), November 2019. 288 [I-D.ietf-detnet-mpls] 289 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 290 Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", 291 draft-ietf-detnet-mpls-04 (work in progress), November 292 2019. 294 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 295 Requirement Levels", BCP 14, RFC 2119, 296 DOI 10.17487/RFC2119, March 1997, 297 . 299 [RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black, 300 "Encapsulating MPLS in UDP", RFC 7510, 301 DOI 10.17487/RFC7510, April 2015, 302 . 304 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 305 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 306 May 2017, . 308 10.2. Informative References 310 [I-D.ietf-6man-segment-routing-header] 311 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 312 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 313 (SRH)", draft-ietf-6man-segment-routing-header-26 (work in 314 progress), October 2019. 316 [I-D.ietf-detnet-security] 317 Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, 318 J., Austad, H., and N. Finn, "Deterministic Networking 319 (DetNet) Security Considerations", draft-ietf-detnet- 320 security-07 (work in progress), January 2020. 322 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 323 "Deterministic Networking Architecture", RFC 8655, 324 DOI 10.17487/RFC8655, October 2019, 325 . 327 Authors' Addresses 329 Balazs Varga (editor) 330 Ericsson 331 Magyar Tudosok krt. 11. 332 Budapest 1117 333 Hungary 335 Email: balazs.a.varga@ericsson.com 337 Janos Farkas 338 Ericsson 339 Magyar Tudosok krt. 11. 340 Budapest 1117 341 Hungary 343 Email: janos.farkas@ericsson.com 345 Lou Berger 346 LabN Consulting, L.L.C. 348 Email: lberger@labn.net 350 Andrew G. Malis 351 Independent 353 Email: agmalis@gmail.com 354 Stewart Bryant 355 Futurewei Technologies 357 Email: stewart.bryant@gmail.com