idnits 2.17.1 draft-wang-detnet-tsn-over-srv6-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 (Nov 1, 2019) is 1632 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) == Missing Reference: 'RFC 8655' is mentioned on line 119, but not defined == Missing Reference: 'RFC8174' is mentioned on line 158, but not defined -- Looks like a reference, but probably isn't: '0' on line 290 == Missing Reference: 'SL' is mentioned on line 402, but not defined == Unused Reference: 'I-D.ietf-detnet-dp-sol-mpls' is defined on line 565, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-spring-segment-routing-policy' is defined on line 570, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-flow-information-model' is defined on line 576, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-spring-segment-routing-mpls' is defined on line 581, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-ip-over-mpls' is defined on line 593, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-ip-over-tsn' is defined on line 598, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-mpls-over-tsn' is defined on line 604, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-mpls-over-udp-ip' is defined on line 610, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-detnet-tsn-vpn-over-mpls' is defined on line 616, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-geng-detnet-dp-sol-srv6' is defined on line 622, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-geng-spring-srv6-for-detnet' is defined on line 627, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-21 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-03 == Outdated reference: A later version (-14) exists of draft-ietf-detnet-flow-information-model-03 ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-flow-information-model (ref. 'I-D.ietf-detnet-flow-information-model') ** Downref: Normative reference to an Informational draft: draft-sdt-detnet-security (ref. 'I-D.sdt-detnet-security') == Outdated reference: A later version (-09) exists of draft-ietf-detnet-ip-over-mpls-01 == Outdated reference: A later version (-07) exists of draft-ietf-detnet-ip-over-tsn-00 ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-ip-over-tsn (ref. 'I-D.ietf-detnet-ip-over-tsn') == Outdated reference: A later version (-07) exists of draft-ietf-detnet-mpls-over-tsn-00 ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-mpls-over-tsn (ref. 'I-D.ietf-detnet-mpls-over-tsn') == Outdated reference: A later version (-08) exists of draft-ietf-detnet-mpls-over-udp-ip-01 -- No information found for draft-ietf-detnet-tsn-vpn-overmpls - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-detnet-tsn-vpn-over-mpls' == Outdated reference: A later version (-02) exists of draft-geng-detnet-dp-sol-srv6-01 ** Downref: Normative reference to an Experimental draft: draft-geng-detnet-dp-sol-srv6 (ref. 'I-D.ietf-geng-detnet-dp-sol-srv6') == Outdated reference: A later version (-01) exists of draft-geng-spring-srv6-for-detnet-00 ** Downref: Normative reference to an Informational draft: draft-geng-spring-srv6-for-detnet (ref. 'I-D.ietf-geng-spring-srv6-for-detnet') -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021CB' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021Q' Summary: 6 errors (**), 0 flaws (~~), 24 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DetNet 3 Internet-Draft X. Wang 4 Intended status: Standards Track J. Dai 5 Expires: May 1, 2020 J. Liu 6 J. Xu 7 Fiberhome Telecom LTD 8 Nov 1, 2019 10 DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over SRv6 11 draft-wang-detnet-tsn-over-srv6-00 12 Abstract 14 This document specifies the Deterministic Networking data plane when 15 TSN networks interconnected over an Segment Routing IPv6 Packet 16 Switched Networks. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 1, 2020. 35 Copyright Notice 37 Copyright (c) 2019 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 54 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 56 4. IEEE 802.1 TSN Over SRv6 Data Plane Scenario . . . . . . . . . 4 57 5. IEEE 802.1 TSN Operation Over SRv6 Sub-Networks. . . . . . . 5 58 5.1. Mapping of TSN Stream ID and Sequence Number . . . . . . . 5 59 5.2. SRv6 Network Programming new Functions . . . . . . . . . . 8 60 5.2.1. End. B.Replication DetNet SID: Packet Replication 61 Function . . . . . . . . . . . . . . . . . . . . . . 8 62 5.2.2. End. B. Elimination: Packet Elimination Function. . . . 9 63 6. SRv6 Data Plane Considerations . . . . . . . . . . . . . . . . 9 64 6.1. DetNet PREOF . . . . . . . . . . . . . . . . . . . . . . 9 65 6.2. Edge Node Processing . . . . . . . . . . . . . . . . . . 10 66 7. Management and Control Information Summary. . . . . . . . . . . 11 67 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 68 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 70 11. Normative References. . . . . . . . . . . . . . . . . . . . . 12 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 73 1. Introduction 75 Deterministic Networking (DetNet) is a service that can be offered by 76 a network to DetNet flows. DetNet provides these flows extremely low 77 packet loss rates and assured bounded end-to-end delivery latency. 78 General background and concepts of DetNet can be found in the DetNet 79 Architecture [RFC8655]. 81 Segment Routing(SR) leverages the source routing paradigm. An ingress 82 node steers a packet through an ordered list of instructions, called 83 "segments". SR can be applied over IPv6 data plane using Routing 84 Extension Header(SRH,[I-D.ietf-6man-segment-routing-header]). A 85 segment in Segment Routing is not limited to a routing/forwarding 86 function. A SRv6 Segment can indicate functions that are executed 87 locally in the node where they are defined. [I-D.ietf-spring-srv6- 88 network-programming] describes some well-known functions and segments 89 associated to them. SRH TLVs([I-D.ietf-6man-segment-routing-header]) 90 also provides meta-data for segment processing. All these features 91 make SRv6 suitable to carry DetNet flows, by defining new segments 92 associated with DetNet functions and Meta data for DetNet. 94 The Time-Sensitive Networking (TSN) is to provide deterministic 95 services through IEEE 802 networks, i.e., guaranteed packet transport 96 with bounded latency, low packet delay variation,and low packet loss. 97 The TSN is a unified industrial Ethernet standard, and supports 98 production control and information application. 100 TSN through DetNet needs to focus on the real-time interconnection of 101 multi-subnet network layer. Based on the existing mechanism of TSN, 102 interface scheduling is carried out for routers, firewalls, servers 103 and other devices, in order to ensure the deterministic network 104 services between cross-domain subnets. The remote control 105 requirements across networks of TSN need deterministic transmission 106 of network services through DetNet technology. TSN needs to be 107 deployed with DetNet technology in larger areas such as networking 108 of plant equipment, automatic building control of plant and office 109 buildings. 111 This document defines how to carry DetNet IEEE 802.1 TSN flows over 112 SRv6 networks. 114 2. Terminology 116 2.1. Terms Used in This Document 118 This document uses the terminology and concepts established in the 119 DetNet architecture [RFC 8655] and [I-D.ietf-detnet-data-plane- 120 framework]. The reader is assumed to be familiar with these 121 documents and their terminology 123 2.2. Abbreviations 125 Terminologies for DetNet go along with the definition in [RFC8655]. 126 The following abbreviations are used in this document: 128 CE: Customer Edge equipment. 129 CoS: Class of Service. 130 DetNet: Deterministic Networking. 131 DF: DetNet Flow. 132 L2: Layer 2. 133 L2VPN: Layer 2 Virtual Private Network. 134 L3: Layer 3. 135 OAM: Operations, Administration, and Maintenance. 136 PE: Provider Edge. 137 PEF: Packet Elimination Function. 138 PRF: Packet Replication Function. 139 PREOF: Packet Replication, Elimination and Ordering Functions. 140 POF: Packet Ordering Function. 141 QoS: Quality of Service. 142 TSN: IEEE 802.1 Time-Sensitive Network. 143 SR: Segment Routing. 144 SRv6: Segment Routing IPv6. 145 NH: The IPv6 next-header field. 147 SID: A Segment Identifier ([RFC8402]). 148 SRH: The Segment Routing Header ([I-D.ietf-6man-segment-routing- 149 header]). 151 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 4. IEEE 802.1 TSN over SRv6 Data Plane Scenario 161 Figure 1 illustrates how DetNet can provide services for IEEE 802.1 162 TSN end systems, CE1 and CE2, over a DetNet enabled SRv6 network. 163 DetNet Edge Nodes sit at the boundary of a DetNet domain. They are 164 responsible for mapping non-DetNet aware L2 traffic to DetNet 165 services. They also support the imposition and disposition of the 166 required DetNet encapsulation. They understand and support IEEE 802.1 167 TSN and are able to map TSN flows into DetNet flows. Edge nodes, PE1 168 and PE2, insert and remove required DetNet SRv6 data plane 169 encapsulation. The 'X' in the edge nodes and relay node, R1, 170 represent a potential DetNet compound flow packet replication and 171 elimination point. 173 TSN |<------- End to End DetNet Service ------>| TSN 174 Service | Sub Sub | Service 175 TSN (AC) | |network| |network| | (AC) TSN 176 Talker/ | V V V V V V | Talker/ 177 Listener| +--------+ +--------+ +--------+ |Listener 178 +---+ | | PE1 | | R1 | | PE2 | | +---+ 179 | |---|----| X |------ | X |------ | X |---|--| | 180 |CE1| | | | | | | | | |CE2| 181 +---+ +--------+ +--------+ +--------+ +---+ 182 | Edge Node Relay Node Edge Node | 183 | | 184 |<- TSN -> <------- TSN Over DetNet SRv6 -------> <- TSN ->| 185 | | 186 |<--- Emulated Time Sensitive Networking (TSN) Service --->| 188 X = Service protection 190 Figure 1: IEEE 802.1TSN Over DetNet SRv6 192 Native TSN flow and DetNet SRv6 flow differ not only by the 193 additional SRH specific encapsulation, but DetNet SRv6 flows have on 194 each DetNet node an associated DetNet specific data structure, what 195 defines flow related characteristics and required forwarding 196 functions. In this example, edge Nodes provide a service proxy 197 function that "associates" the DetNet flows and native flows at the 198 edge of the DetNet domain. This ensures that the DetNet SRv6 Flow is 199 properly served at the Edge node (and inside the domain). 201 5. IEEE 802.1 TSN Operation Over SRv6 Sub-Networks 203 A classical SRv6 data plane solution is showed in the picture below: 205 +-------------------+ 206 | DATA | 207 +-----------------------+ +-------------------+ 208 | DATA | | SRH | 209 +-----------------------+ +-------------------+ 210 | TSN Ethernet Header | ----> | Ipv6 Header | 211 +-----------------------+ +-------------------+ 212 Figure 2: SRv6 DetNet data plane solution 214 In SRv6 for DetNet, the DATA with the SRH is used for 215 carrying DetNet flows. Traffic Engineering is instantiated in the 216 segment list of SRH, and other functions and arguments for service 217 protection (packet replication, elimination and ordering) and 218 congestion control (packet queuing and forwarding) are also defined 219 in the SRH. 221 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 222 Working Group have defined (and are defining) a number of amendments 223 to IEEE 802.1Q [IEEE8021Q] that provides zero congestion loss and 224 bounded latency in bridged networks. Furthermore IEEE 802.1CB 225 [IEEE8021CB] defines frame replication and elimination functions for 226 reliability that should prove both compatible with and useful to, 227 DetNet networks. All these functions have to identify flows those 228 require TSN treatment. 230 The challenge for SRv6 flows is that the protocol interworking 231 function defined in IEEE 802.1CB [IEEE8021CB] does not works for 232 segment list of SRH flows. The aim of the protocol interworking 233 function is to convert a TSN ingress flow (for examples, identified 234 by a specific destination MAC address and VLAN) to segment list of 235 SRH. A similar interworking pair at the other end of the SRv6 sub- 236 network would restore the packet to its original TSN packet. 238 The TSN layer 2 header and application payload carried by the TSN 239 network are encapsulated in 'DATA' field of figure 2. 241 5.1. Mapping of TSN Stream ID and Sequence Number 242 The Edge node MUST provide the SRv6 sub-network specific segment list 243 of SRH encapsulation over the link(s) towards the sub-network. A 244 SRv6-aware edge node MUST support the following TSN components: 246 1. For recognizing flows: 247 * Stream Identification (SRv6-flow-aware) 249 2. For FRER used inside the TSN domain, additionally: 250 * Sequencing function (SRv6-flow-aware) 251 * Sequence encode/decode function 253 3. For FRER when the node is a TSN replication or elimination point, 255 additionally: 256 * Stream splitting function 257 * Individual recovery function 259 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 260 Working Group has defined Stream identification in section 6.1 of 261 IEEE 802.1CB [IEEE8021CB]. Four specific Stream identification 262 functions are described: Null Stream identification, Source MAC and 263 VLAN Stream identification, Active Destination MAC and VLAN Stream 264 identification, and IP Stream identification. These Stream 265 identification functions are summarized as follow: 267 o Null Stream identification: destination MAC address, vlan 268 identifier. 269 o Source MAC and VLAN Stream identification: source MAC address, vlan 270 identifier. 271 o Active Destination MAC and VLAN Stream identification: destination 272 MAC address, vlan identifier. 273 o IP Stream identification: destination MAC address, vlan identifier, 274 IP source address, IP destination address, DSCP, IP next protocol, 275 source port, destination port. 277 The SRH for DetNet in the IPv6 header is showed as follows, according 278 to [I-D.ietf-6man-segment-routing-header] and 279 [I-D.ietf-spring-srv6-network-programming]: 281 0 1 2 3 282 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | Next Header | Hdr Ext Len | Routing Type | Segment Left | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | Last Entry | Flags | Tag | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | | 289 | DetNet SID | 290 | (Segment List[0] for relay node or edge node) | 291 | | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 | ... | 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | | 296 | Segment List[n] | 297 | | 298 | | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | Optional TLVs or other | 301 | ... | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 Figure 3: SRH for DetNet 306 The DetNet SRv6 flow is identified by DetNet SID in SRH. DetNet SID 307 is defined as a 128-bit value. 309 A new DetNet SID is defined to support DetNet service protection for 310 TSN stream. It is used to uniquely identify a DetNet flow in a SRv6 311 DetNet node and to discriminate packets in the same DetNet flow by 312 sequence number. DetNet SID is defined as follows: 314 0 1 2 3 315 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 | Type | Length | Flow Identification | 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 | Flow Identification | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | Flow Identification | RESERVED | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 |RESERVD| Sequence Number | 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 Figure 4: DetNet SID for Flow Identification 328 Where: 329 o Type: 8bits, to be assigned by IANA. 330 o Length: 8 bits. 331 o Flow Identification: 64 bits, which is used for identifying DetNet 332 flow. 333 o RESERVED: 20 bits, MUST be 0 on transmission and ignored on 334 receipt. 335 o Sequence Number: 28 bits, which is used for indicating sequence 336 number of a DetNet flow. 338 When TSN stream is transmitted over a SRv6 network, TSN Stream 339 Identification MUST pair SRv6 flows and TSN Streams and encode that 340 in data plane formats as well. When the new DetNet SID is used to 341 identify DetNet flow and the mapping for TSN stream is as follows: 343 o Type: 8bits, to be assigned by IANA, used to identify sources from 344 the TSN stream. 345 o Length: 8 bits, the value is 16 octets. 346 o Flow Identification: 64 bits, which is used for identifying DetNet 347 flow. The former 48 bit corresponds to the MAC address identified 348 by the TSN stream, and the post 16 bit comes from the VLAN-ID and 349 priority parameters in TSN packet. 350 o RESERVED: 20 bits, MUST be 0 on transmission and ignored on 351 receipt. 352 o Sequence Number: 28 bits, which is used for indicating sequence 353 number of a DetNet flow. The value comes from the Redundancy tag 354 (R-TAG) in TSN packet as defined in Clause 7.8 of IEEE 802.1CB 355 [IEEE8021CB]. 357 Flow Identification in SRH can identify Null Stream, Source MAC and 358 VLAN Stream, Active Destination MAC and VLAN Stream in TSN stream. 359 For TSN IP Stream, destination MAC address and vlan is still 360 indicated by flow Identification, other IP-based fields correspond 361 to IP fields in SRv6 one by one, such as IP source address, IP 362 destination address, DSCP, IP next protocol, source port, destination 363 port etc. 365 5.2. SRv6 Network Programming new Functions 367 New SRv6 Network Programming functions are defined as follows: 369 5.2.1. End. B.Replication DetNet SID: Packet Replication Function 371 When N receives a packet whose IPv6 DA is S and S is a local End.B. 372 Replication DetNet SID, does: 374 S01. IF NH=SRH & SL>0 THEN { 375 S02. Extract the DetNet SID values from the SRH or TSN Stream 376 identification and TSN Rtag. 377 S03. Create two new outer IPv6+SRH headers: IPv6-SRH-1 and 378 IPv6-SRH-2 Insert the policy-instructed segment lists in each 379 newly created SRH (SRH-1 and SRH-2). Also, add the extracted 380 DetNet SID into SRH-1 and SRH-2. 381 S04. Remove the incoming outer IPv6+SRH header, restore DATA as the 382 original packet. 383 S05. Create a duplication of the restore DATA as the duplicate 384 packet. 385 S06. Encapsulate the original packet into the first outer IPv6+SRH 386 header: (IPv6-SRH-1) (original packet) 387 S07. Encapsulate the duplicate packet into the second outer IPv6+SRH 388 header: (IPv6-SRH-2) (duplicate packet) 389 S08. Set the IPv6 SA as the local address of this node. 390 S09. Set the IPv6 DA of IPv6-SRH-1 to the first segment of the SRv6 391 Policy in of SRH-1 segment list. 392 S10. Set the IPv6 DA of IPv6-SRH-2 to the first segment of the SRv6 393 Policy in of SRH-2 segment list. 394 S11. } 396 5.2.2. End. B. Elimination: Packet Elimination Function 398 When N receives a packet whose IPv6 DA is S and S is a local End.B. 399 Elimination DetNet SID, does: 401 S01. IF NH=SRH & SL>0 & "the packet is not a redundant packet" THEN { 402 S02. Do not decrement SL nor update the IPv6 DA with SRH[SL] 403 S03. Extract the value of DetNet SID from the SRH 404 S04. Extract Flow Identification and Sequence Number from DetNet 405 SID. 406 S05. IF NOT receive the packet with the same Flow Identification 407 and Sequence Number { 408 S06. Create a new outer IPv6+SRH header 409 S07. Insert the policy-instructed segment lists in the newly 410 created SRH and add the retrieved DetNet SID in the newly 411 created SRH 412 S08. Remove the incoming outer IPv6+SRH header. 413 S09. Set the IPv6 DA to the first segment of the SRv6 Policy in 414 the newly created SRH 415 S10. } Else { 416 S11. Drop the packet 417 S12. } 418 S13. } 420 6. SRv6 Data Plane Considerations 422 6.1. DetNet PREOF 423 Flow Identification and sequence number are necessary in the 424 encapsulation of SRv6 for DetNet in order to support service 425 protection. Replication nodes decide which DetNet flows are supposed 426 to be replicated by the flow identification. Elimination nodes 427 decide whether a packet should be dropped because of redundancy by 428 the flow identification and sequence number. 430 FRER function and the provided service recovery is available in that 431 the Stream-ID and the TSN sequence number are paired with the SRv6 432 flow parameters they can be combined with PREOF functions. 434 SRv6 supporting DetNet flows may use Packet Replication, Elimination 435 and Ordering Functions (PREOF) based on the DetNet SID in SRH, which 436 is derived from TSN Stream. The specific operation of Frame 437 Replication and Elimination for Redundancy (FRER) [802.1CB] is not 438 modified by the use of DetNet and follows IEEE 802.1CB [IEEE8021CB]. 440 6.2. Edge Node Processing 442 An edge node is responsible for matching ingress packets to the 443 service they require and encapsulating them accordingly. An edge node 444 is a SRv6 DetNet-aware forwarder, and may participate in the packet 445 replication and duplication elimination. 447 The Controller sends Detnet SRv6 polices to the edge node. These 448 polices include mapping of ingress TSN stream to DetNet SRv6 flow. 449 The detnet SID is associated with an SR Policy, and its value comes 450 from a TSN packet. When the edge node forwards a TSN packet to SRv6 451 network, inserting an SRH with the policy and adds an outer IPv6 452 header. The TSN flow identification and sequence number is copied to 453 DetNet SID in SRv6 SRH. 455 Additionally the DetNet-aware edge node does duplicate frame 456 elimination based on the flow identification and the sequence number 457 combination. The packet replication is also done within the 458 DetNet-aware forwarder. During elimination and the replication 459 process the sequence number of the DetNet member flow MUST be 460 preserved and copied to the egress DetNet member flow. 462 7. Management and Control Information Summary 464 The following summarizes the set of information that is needed to 465 support TSN over SRv6 at the ingress edge node: 467 o TSN Stream identification and TSN R-tag information to be mapped to 468 SRv6 SRH SID. Note that a single TSN Stream identification can map 469 to one SRH DetNet SID, and it can used for PREOF. 470 o IPv6 source address. 472 o IPv6 destination address. 473 o IPv6 Traffic Class. 475 This information MUST be provisioned per DetNet flow via 476 configuration, e.g., via the controller or management plane. 478 It is the responsibility of the DetNet controller plane to properly 479 provision both flow identification information and the flow specific 480 resources needed to be provided the traffic treatment needed to meet 481 each flow's service requirements. This applies for aggregated and 482 individual flows. 484 DetNet SRv6 flow and TSN Stream mapping related information are 485 required only for DetNet SRv6 edge nodes; the edge node is TSN-aware 486 and DetNet SRv6-aware node. These DetNet SRv6 edge nodes are member 487 of both the DetNet SRv6 domain and the TSN sub-network. Within the 488 TSN sub-network the DetNet SRv6 node may has a TSM-aware role, so TSN 489 specific management and control plane functionalities must be 490 implemented. There are many similarities in the management plane 491 techniques used in DetNet and TSN, but that is not the case for the 492 control plane protocols. For example, RSVP-TE and MSRP behaves 493 differently. Therefore management and control plane design is an 494 important aspect of scenarios, where mapping between DetNet SRv6 and 495 TSN is required. 497 In order to use a DetNet SRv6 sub-network between TSN nodes, TSN 498 stream specific information must be converted to SRv6 DetNet SRH. TSN 499 Stream ID and stream related parameters/requirements must be 500 converted to a SRv6 DetNet flow ID and flow related parameters/ 501 requirements. Note that, as the DetNet SRv6 sub-network is just a 502 portion of the end2end TSN path (i.e., single hop from IP 503 perspective), some parameters (e.g., delay) may differ significantly. 504 Other TSN stream parameters (like bandwidth) also may have to be 505 tuned due to the SRv6 encapsulation used in the DetNet sub-network. 507 In some case it may be challenging to determine some TSN Stream 508 related information. For example which DetNet SRv6 paths are 509 multi-Listener of the mapped TSN stream to one TSN stream Talker? 510 However it may be not trivial to locate the point/interface where 511 that Listener is connected to the TSN sub-network. Such 512 attributes may require interaction between control and management 513 plane functions and between DetNet SRv6 and TSN domains. 515 Mapping between DetNet SRv6 flow identifiers and TSN Stream 516 identifiers, if not provided explicitly, can be done by a DetNet SRv6 517 node locally based on the configuration of SRv6 Behaviors associated 518 with a SID. 520 8. Security Considerations 522 The security considerations of DetNet in general are discussed in 523 [RFC8655] and [I-D.sdt-detnet-security]. Other security 524 considerations will be added in a future version of this draft. 526 9. IANA Considerations 528 This document requests assigning new DetNet SID TLV code-points as 529 described in section 5. 531 10. Acknowledgements 533 Thanks for Guanghua Lan and Ximing Dong for their comments and 534 contributions. 536 11. Normative References 538 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 539 Requirement Levels", BCP 14, RFC 2119, 540 DOI 10.17487/RFC2119, March 1997, 541 . 543 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 544 Decraene, B., Litkowski, S., and R. Shakir, "Segment 545 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 546 July 2018, . 548 [I-D.ietf-spring-srv6-network-programming] 549 Filsfils, C., Camarillo, P., Leddy, J., 550 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 551 Network Programming", draft-filsfils-spring-srv6-network- 552 programming-07 (work in progress), February 2019. 554 [I-D.ietf-6man-segment-routing-header] 555 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 556 Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment 557 Routing Header (SRH)", draft-ietf-6man-segment-routing- 558 header-21 (work in progress), June 2019. 560 [RFC8655] 561 Finn, N., Thubert, P., Varga, B., and J. Farkas, 562 "Deterministic Networking Architecture", RFC 8655, May 563 2019, . 565 [I-D.ietf-detnet-dp-sol-mpls] 566 Korhonen, J. and B. Varga, "DetNet MPLS Data Plane 567 Encapsulation", draft-ietf-detnet-dp-sol-mpls-02 (work in 568 progress), March 2019. 570 [I-D.ietf-spring-segment-routing-policy] 571 Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d., 572 bogdanov@google.com, b., and P. Mattes, "Segment Routing 573 Policy Architecture", draft-ietf-spring-segment-routing- 574 policy-03 (work in progress), May 2019. 576 [I-D.ietf-detnet-flow-information-model] 577 Farkas, J., Varga, B., Cummings, R., and Y. Jiang, "DetNet 578 Flow Information Model", draft-ietf-detnet-flow- 579 information-model-03 (work in progress), March 2019. 581 [I-D.ietf-spring-segment-routing-mpls] 582 Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., 583 Litkowski, S., and R. Shakir, "Segment Routing with MPLS 584 data plane", draft-ietf-spring-segment-routing-mpls-22 585 (work in progress), May 2019. 587 [I-D.sdt-detnet-security] 588 Mizrahi, T., Grossman, E., Hacker, A., Das, S., 589 "Deterministic Networking (DetNet) Security 590 Considerations, draft-sdt-detnet-security, work in 591 progress", 2017. 593 [I-D.ietf-detnet-ip-over-mpls] 594 Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., 595 and J. Korhonen, "DetNet Data Plane: IP over MPLS", draft- 596 ietf-detnet-ip-over-mpls-01 (work in progress), July 2019. 598 [I-D.ietf-detnet-ip-over-tsn] 599 Varga, B., Farkas, J., Malis, A., Bryant, S., and J. 600 Korhonen, "DetNet Data Plane: IP over IEEE 802.1 Time 601 Sensitive Networking (TSN)", draft-ietf-detnet-ip-over-tsn- 602 00 (work in progress), May 2019. 604 [I-D.ietf-detnet-mpls-over-tsn] 605 Farkas, J., Malis, A., Bryant, S., and J. 606 Korhonen, "DetNet Data Plane: MPLS over IEEE 802.1 Time 607 Sensitive Networking (TSN)", draft-ietf-detnet-mpls-over- 608 tsn-00 (work in progress), May 2019. 610 [I-D.ietf-detnet-mpls-over-udp-ip] 611 Varga, B., Farkas, J.,Beger, L., Malis, A., Bryant, S., 612 and J. Korhonen, "DetNet Data Plane: MPLS over UDP/IP", 613 draft-ietf-detnet-mpls-over-udp-ip-01 (work in progress), 614 May 2019. 616 [I-D.ietf-detnet-tsn-vpn-over-mpls] 617 Varga, B., Farkas, J., Malis, A., Bryant, S., and J. 618 Korhonen, "DetNet Data Plane: IEEE 802.1 Time Sensitive 619 Networking over MPLS", draft-ietf-detnet-tsn-vpn-overmpls- 620 00 (work in progress), May 2019. 622 [I-D.ietf-geng-detnet-dp-sol-srv6] 623 Geng, X., Chen, M., Zhu, Y. 624 "DetNet SRv6 Data Plane Encapsulation", draft-geng-detnet- 625 dp-sol-srv6-01(work in progress), May 2019. 627 [I-D.ietf-geng-spring-srv6-for-detnet] 628 Geng, X., Li, Z., Chen, M. 629 "SRv6 for Deterministic Networking (DetNet)", draft-geng- 630 spring-srv6-for-detnet-00(work in progress), July 2019. 632 [IEEE8021CB] 633 Finn, N., "Draft Standard for Local and metropolitan area 634 networks - Seamless Redundancy", IEEE P802.1CB 635 /D2.1 P802.1CB, December 2015, 636 . 639 [IEEE8021Q] 640 IEEE 802.1, "Standard for Local and metropolitan area 641 networks--Bridges and Bridged Networks (IEEE Std 802.1Q- 642 2014)", 2014, . 644 Authors' Addresses 646 Xueshun Wang 647 Fiberhome Telecom LTD 648 Email: xswang@fiberhome.com 650 Jinyou Dai 651 Fiberhome Telecom LTD 652 Email: djy@fiberhome.com 654 Jianhua Liu 655 Fiberhome Telecom LTD 656 Email: liujianhua@fiberhome.com 658 Jing Xu 659 Fiberhome Telecom LTD 660 Email: xujing2010@fiberhome.com