idnits 2.17.1 draft-ietf-detnet-mpls-over-udp-ip-02.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 (October 16, 2019) is 1652 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-01 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-mpls-01 == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-24 == Outdated reference: A later version (-16) exists of draft-ietf-detnet-security-05 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: April 18, 2020 L. Berger 6 LabN Consulting, L.L.C. 7 A. Malis 8 Independent 9 S. Bryant 10 Futurewei Technologies 11 J. Korhonen 12 October 16, 2019 14 DetNet Data Plane: MPLS over UDP/IP 15 draft-ietf-detnet-mpls-over-udp-ip-02 17 Abstract 19 This document specifies the MPLS Deterministic Networking data plane 20 operation and encapsulation over an IP network. The approach is 21 modeled on the operation of MPLS and over UDP/IP packet switched 22 networks. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on April 18, 2020. 41 Copyright Notice 43 Copyright (c) 2019 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 61 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 62 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4 63 3. DetNet MPLS Operation over DetNet 64 IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 4. DetNet Data Plane Procedures . . . . . . . . . . . . . . . . 5 66 5. Management and Control Information Summary . . . . . . . . . 6 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 68 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 69 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 70 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 72 9.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 with a low 79 packet loss rates and assured maximum end-to-end delivery latency. 80 General background and concepts of DetNet can be found in 81 [I-D.ietf-detnet-architecture]. 83 This document specifies use of the MPLS DetNet encapsulation over an 84 IP network. The approach is modeled on the operation of MPLS over an 85 IP Packet Switched Network (PSN) [RFC7510]. It maps the MPLS data 86 plane encapsulation described in [I-D.ietf-detnet-mpls] to the DetNet 87 IP data plane defined in [I-D.ietf-detnet-ip]. 89 To carry DetNet flows with full functionality at the DetNet layer 90 over an IP network, the following components are required (these are 91 a subset of the requirements for MPLS encapsulation listed in 92 [I-D.ietf-detnet-mpls]): 94 1. A method of identifying the DetNet flow group to the processing 95 element. 97 2. A method of carrying the DetNet sequence number. 99 3. A method of distinguishing DetNet OAM packets from DetNet data 100 packets. 102 4. A method of carrying queuing and forwarding indication. 104 These requirements are satisfied by the DetNet over MPLS 105 Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly 106 satisfied by the DetNet IP data plane defined in [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 [I-D.ietf-detnet-architecture], and the reader is 114 assumed to be familiar with 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 PRF Packet Replication Function. 145 PSN Packet Switched Network. 147 S-Label A DetNet "service" label that is used between DetNet 148 nodes that implement also the DetNet service sub-layer 149 functions. An S-Label is also used to identify a 150 DetNet flow at DetNet service sub-layer. 152 2.3. Requirements Language 154 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 155 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 156 "OPTIONAL" in this document are to be interpreted as described in BCP 157 14 [RFC2119] [RFC8174] when, and only when, they appear in all 158 capitals, as shown here. 160 3. DetNet MPLS Operation over DetNet IP PSNs 162 This document builds on the specification of MPLS over UDP defined in 163 [RFC7510]. It may replace partly or entirely the F-Label(s) used in 164 [I-D.ietf-detnet-mpls] with UDP and IP headers. The UDP and IP 165 header information is used to identify DetNet flows, including member 166 flows, per [I-D.ietf-detnet-ip]. The resulting encapsulation is 167 shown in Figure 1. There may be zero or more F-label(s) between the 168 S-label and the UDP header. 170 Note that this encapsulation works equally well with IPv4, IPv6, and 171 IPv6-based Segment Routing [I-D.ietf-6man-segment-routing-header]. 173 +---------------------------------+ 174 | | 175 | DetNet App-Flow | 176 | Payload Packet | 177 | | 178 +---------------------------------+ <--\ 179 | DetNet Control Word | | 180 +---------------------------------+ +--> DetNet data plane 181 | S-Label | | MPLS encapsulation 182 +---------------------------------+ | 183 | [ F-label(s) ] | | 184 +---------------------------------+ <--+ 185 | UDP Header | | 186 +---------------------------------+ +--> DetNet data plane 187 | IP Header | | IP encapsulation 188 +---------------------------------+ <--/ 189 | Data-Link | 190 +---------------------------------+ 191 | Physical | 192 +---------------------------------+ 194 Figure 1: UDP/IP Encapsulation of DetNet MPLS 196 d-CW, S-Labels and zero or more F-Labels are used as defined in 197 [I-D.ietf-detnet-mpls] and are not modified by this document. In 198 case of aggregates the A-Label is treated as an S-Label and it too is 199 not modified. 201 4. DetNet Data Plane Procedures 203 To support outgoing DetNet MPLS over UDP/IP encapsulation, an 204 implementation MUST support the provisioning of UDP and IP header 205 information in addition or in place of F-Label(s). Note, when PRF is 206 performed at the MPLS service sub-layer, there will be multiple 207 member flows, and each member flow will require the provisioning of 208 their own UDP and IP header information. The headers for each 209 outgoing packet MUST be formatted on the configuration information 210 and as defined in [RFC7510], with one exception. Note that the UDP 211 Source Port value MUST be set to uniquely identify the DetNet flow. 212 The packet MUST then be handed as a DetNet IP packet, per 213 [I-D.ietf-detnet-ip]. This includes QoS related traffic treatment. 215 To support receive processing an implementation MUST also support the 216 provisioning of received UDP and IP header information. The 217 provisioned information MUST be used to identify incoming app-flows 218 based on the combination of S-Label and incoming encapsulation header 219 information. Normal receive processing as defined in 220 [I-D.ietf-detnet-mpls], including PEF and POF, can then take place. 222 5. Management and Control Information Summary 224 The following summarizes the set of information that is needed to 225 configure DetNet MPLS over UDP/IP: 227 o Label information (S-label or F-label) to be mapped to UDP/IP 228 flow. Note that a single S-Label can map to multiple sets of UPD/ 229 IP information when PREOF is used. 231 o IPv4 and IPv6 source address field. 233 o IPv4 and IPv6 destination address field. 235 o IPv4 Type of Service and IPv6 Traffic Class Fields. 237 o UDP Source Port. 239 o UDP Destination Port. 241 This information MUST be provisioned per DetNet flow via 242 configuration, e.g., via the controller or management plane. 244 It is the responsibility of the DetNet controller plane to properly 245 provision both flow identification information and the flow specific 246 resources needed to provided the traffic treatment needed to meet 247 each flow's service requirements. This applies for aggregated and 248 individual flows. 250 6. Security Considerations 252 The security considerations of DetNet in general are discussed in 253 [I-D.ietf-detnet-architecture] and [I-D.ietf-detnet-security]. MPLS 254 and IP specific security considerations are described in 255 [I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip]. This draft does not 256 have additional security considerations. 258 7. IANA Considerations 260 This document makes no IANA requests. 262 8. Acknowledgements 264 The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson, 265 David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David 266 Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J. 267 Bernardos for their various contributions to this work. 269 9. References 271 9.1. Normative References 273 [I-D.ietf-detnet-ip] 274 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 275 Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", 276 draft-ietf-detnet-ip-01 (work in progress), July 2019. 278 [I-D.ietf-detnet-mpls] 279 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 280 Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", 281 draft-ietf-detnet-mpls-01 (work in progress), July 2019. 283 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 284 Requirement Levels", BCP 14, RFC 2119, 285 DOI 10.17487/RFC2119, March 1997, 286 . 288 [RFC7510] Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black, 289 "Encapsulating MPLS in UDP", RFC 7510, 290 DOI 10.17487/RFC7510, April 2015, 291 . 293 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 294 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 295 May 2017, . 297 9.2. Informative References 299 [I-D.ietf-6man-segment-routing-header] 300 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 301 Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment 302 Routing Header (SRH)", draft-ietf-6man-segment-routing- 303 header-24 (work in progress), October 2019. 305 [I-D.ietf-detnet-architecture] 306 Finn, N., Thubert, P., Varga, B., and J. Farkas, 307 "Deterministic Networking Architecture", draft-ietf- 308 detnet-architecture-13 (work in progress), May 2019. 310 [I-D.ietf-detnet-security] 311 Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, 312 J., Austad, H., Stanton, K., and N. Finn, "Deterministic 313 Networking (DetNet) Security Considerations", draft-ietf- 314 detnet-security-05 (work in progress), August 2019. 316 Authors' Addresses 318 Balazs Varga (editor) 319 Ericsson 320 Magyar Tudosok krt. 11. 321 Budapest 1117 322 Hungary 324 Email: balazs.a.varga@ericsson.com 326 Janos Farkas 327 Ericsson 328 Magyar Tudosok krt. 11. 329 Budapest 1117 330 Hungary 332 Email: janos.farkas@ericsson.com 334 Lou Berger 335 LabN Consulting, L.L.C. 337 Email: lberger@labn.net 339 Andrew G. Malis 340 Independent 342 Email: agmalis@gmail.com 344 Stewart Bryant 345 Futurewei Technologies 347 Email: stewart.bryant@gmail.com 349 Jouni Korhonen 351 Email: jouni.nospam@gmail.com