idnits 2.17.1 draft-wang-detnet-tsn-over-srv6-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 29, 2020) is 1274 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021CB' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021Q' == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-14 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 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: April 30, 2021 J. Liu 6 J. Xu 7 Fiberhome Telecom LTD 8 October 29, 2020 10 DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over SRv6 11 draft-wang-detnet-tsn-over-srv6-02 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 April 30, 2021. 35 Copyright Notice 37 Copyright (c) 2020 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 6.3. MTU and Fragmentation . . . . . . . . . . . . . . . . . . 10 67 7. Management and Control Information Summary. . . . . . . . . . . 11 68 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 69 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 70 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 71 11. Normative References. . . . . . . . . . . . . . . . . . . . . 12 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 74 1. Introduction 76 Deterministic Networking (DetNet) is a service that can be offered as 77 DetNet flows in network. DetNet provides these flows extremely low 78 packet loss rates and assured bounded end-to-end delivery latency. 79 General background and concepts of DetNet can be found in the DetNet 80 Architecture [RFC8655]. 82 Segment Routing(SR) leverages the source routing paradigm. An ingress 83 node steers a packet through an ordered list of instructions, called 84 "segments". SR can be applied over IPv6 data plane using Routing 85 Extension Header [RFC8754]. A segment in Segment Routing is not 86 limited to a routing/forwarding function. A SRv6 Segment can 87 indicate functions that are executed locally in the node where they 88 are defined. [I-D.ietf-spring-srv6-network-programming] describes 89 some well-known functions and segments associated to them. SRH TLVs 90 ([RFC8754]) also provides meta-data for segment processing. All 91 these features make SRv6 suitable to carry DetNet flows by defining 92 new segments associated with DetNet functions and Meta data for 93 DetNet. 95 The Time-Sensitive Networking (TSN) is to provide deterministic 96 services through IEEE 802 networks, i.e., guaranteed packet transport 97 with bounded latency, low packet delay variation,and low packet loss. 99 The TSN is a unified industrial Ethernet standard, and supports 100 production control and information application. 102 TSN over DetNet needs to focus on the real-time interconnection of 103 multi-subnet network layer. Based on the existing mechanism of TSN, 104 interface scheduling is carried out for routers, firewalls, servers 105 and other devices, in order to ensure the deterministic network 106 services between cross-domain subnets. The remote control 107 requirements across networks of TSN need deterministic transmission 108 of network services through DetNet technology. TSN needs to be 109 deployed with DetNet technology in larger areas such as networking 110 of plant equipment, automatic building control of plant and office 111 buildings. 113 This document defines how to carry DetNet IEEE 802.1 TSN flows over 114 SRv6 networks. 116 2. Terminology 118 2.1. Terms Used in This Document 120 This document uses the terminology and concepts established in the 121 DetNet architecture [RFC8655] and [I-D.ietf-detnet-data-plane- 122 framework]. The reader is assumed to be familiar with these 123 documents and their terminology 125 2.2. Abbreviations 127 Terminologies for DetNet go along with the definition in [RFC8655]. 128 The following abbreviations are used in this document: 130 CE: Customer Edge equipment. 131 CoS: Class of Service. 132 DetNet: Deterministic Networking. 133 DF: DetNet Flow. 134 L2: Layer 2. 135 L3: Layer 3. 136 OAM: Operations, Administration, and Maintenance. 137 PE: Provider Edge. 138 PEF: Packet Elimination Function. 139 PRF: Packet Replication Function. 140 PREOF: Packet Replication, Elimination and Ordering Functions. 141 POF: Packet Ordering Function. 142 QoS: Quality of Service. 143 TSN: IEEE 802.1 Time-Sensitive Network. 144 SR: Segment Routing. 145 SRv6: Segment Routing IPv6. 146 SL: Segment Left. 148 NH: The IPv6 next-header field. 149 SID: A Segment Identifier ([RFC8402]). 150 SRH: The Segment Routing Header ([RFC8754]). 152 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 4. IEEE 802.1 TSN over SRv6 Data Plane Scenario 162 Realize the DetNet network in the Internet and connect with the time 163 sensitive network in the factory. Figure 1 illustrates how DetNet can 164 provide services for IEEE 802.1 TSN end systems, CE1 and CE2, over a 165 DetNet enabled SRv6 network. DetNet Edge Nodes sit at the boundary of 166 a DetNet domain. They are responsible for mapping non-DetNet aware L2 167 traffic to DetNet services. They also support the imposition and 168 disposition of the required DetNet encapsulation. They understand and 169 support IEEE 802.1 TSN and are able to map TSN flows into DetNet 170 flows. Edge nodes, PE1 and PE2, insert and remove required DetNet 171 SRv6 data plane encapsulation. The 'X' in the edge nodes and relay 172 node, R1, represent a potential DetNet compound flow packet 173 replication and elimination point. 175 TSN |<------- End to End DetNet Service ------>| TSN 176 Service | Sub Sub | Service 177 TSN (AC) | |network| |network| | (AC) TSN 178 Talker/ | V V V V V V | Talker/ 179 Listener| +--------+ +--------+ +--------+ |Listener 180 +---+ | | PE1 | | R1 | | PE2 | | +---+ 181 | |---|----| X |------ | X |------ | X |---|--| | 182 |CE1| | | | | | | | | |CE2| 183 +---+ +--------+ +--------+ +--------+ +---+ 184 | Edge Node Relay Node Edge Node | 185 | | 186 |<- TSN -> <------- TSN Over DetNet SRv6 -------> <- TSN ->| 187 | | 188 |<--- Emulated Time Sensitive Networking (TSN) Service --->| 190 X = Service protection 192 Figure 1: IEEE 802.1TSN Over DetNet SRv6 194 Native TSN flow and DetNet SRv6 flow differ not only by the 195 additional SRH specific encapsulation, but DetNet SRv6 flows have on 196 each DetNet node an associated DetNet specific data structure, what 197 defines flow related characteristics and required forwarding 198 functions. In this example, edge Nodes provide a service proxy 199 function that "associates" the DetNet flows and native flows at the 200 edge of the DetNet domain. This ensures that the DetNet SRv6 Flow is 201 properly served at the Edge node (and inside the domain). 203 5. IEEE 802.1 TSN Operation Over SRv6 Sub-Networks 205 A classical SRv6 data plane solution is showed in the picture below: 207 +-------------------+ 208 | DATA | 209 +-----------------------+ +-------------------+ 210 | DATA | | SRH | 211 +-----------------------+ +-------------------+ 212 | TSN Ethernet Header | ----> | Ipv6 Header | 213 +-----------------------+ +-------------------+ 214 Figure 2: SRv6 DetNet data plane solution 216 In SRv6 for DetNet, the DATA with the SRH is used for 217 carrying DetNet flows. Traffic Engineering is instantiated in the 218 segment list of SRH, and other functions and arguments for service 219 protection (packet replication, elimination and ordering) and 220 congestion control (packet queuing and forwarding) are also defined 221 in the SRH. 223 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 224 Working Group have defined (and are defining) a number of amendments 225 to IEEE 802.1Q [IEEE8021Q] that provides zero congestion loss and 226 bounded latency in bridged networks. Furthermore IEEE 802.1CB 227 [IEEE8021CB] defines frame replication and elimination functions for 228 reliability that should prove both compatible with and useful to 229 DetNet networks. All these functions have to identify flows those 230 require TSN treatment. 232 The challenge for SRv6 flows is that the protocol interworking 233 function defined in IEEE 802.1CB [IEEE8021CB] does not works for 234 segment list of SRH flows. The aim of the protocol interworking 235 function is to convert a TSN ingress flow (for examples, identified 236 by a specific destination MAC address and VLAN) to segment list of 237 SRH. A similar interworking pair at the other end of the SRv6 sub- 238 network would restore the packet to its original TSN packet. 240 The TSN layer 2 header and application payload carried by the TSN 241 network are encapsulated in 'DATA' field of figure 2. 243 5.1. Mapping of TSN Stream ID and Sequence Number 244 The Srv6 network edge node uses BGP protocol to announce SRv6 service 245 Sid. SRv6 edge node encapsulates the data payload in the outer IPv6 246 header and sets the outer destination address as the service Sid. The 247 underlying network between the edge nodes needs to support IPv6 248 according to [RFC8200], and can transform TSN data flow into srv6 249 service. 251 The Edge node MUST provide the SRv6 sub-network specific 252 segment list of SRH encapsulation over the link(s) towards the sub- 253 network. A SRv6-aware edge node MUST support the following TSN 254 components: 256 1. For recognizing flows: 257 * Stream Identification (SRv6-flow-aware). 259 2. For FRER used inside the TSN domain, additionally: 260 * Sequencing function (SRv6-flow-aware); 261 * Sequence encode/decode function. 263 3. For FRER when the node is a TSN replication or elimination point. 265 additionally: 266 * Stream splitting function; 267 * Individual recovery function. 269 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 270 Working Group has defined Stream identification in section 6.1 of 271 IEEE 802.1CB [IEEE8021CB]. Four specific Stream identification 272 functions are described: Null Stream identification, Source MAC and 273 VLAN Stream identification, Active Destination MAC and VLAN Stream 274 identification, and IP Stream identification. These Stream 275 identification functions are summarized as follow: 277 o Null Stream identification: destination MAC address, vlan 278 identifier. 279 o Source MAC and VLAN Stream identification: source MAC address, vlan 280 identifier. 281 o Active Destination MAC and VLAN Stream identification: destination 282 MAC address, vlan identifier. 283 o IP Stream identification: destination MAC address, vlan identifier, 284 IP source address, IP destination address, DSCP, IP next protocol, 285 source port, destination port. 287 The SRH for DetNet in the IPv6 header is showed as follows, according 288 to [RFC8754] and [I-D.ietf-spring-srv6-network-programming]: 290 0 1 2 3 291 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 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 | Next Header | Hdr Ext Len | Routing Type | Segment Left | 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | Last Entry | Flags | Tag | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | | 298 | DetNet SID | 299 | Segment List(0) (128-bit) | 300 | | 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 | ... | 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | | 305 | Segment List(n) (128-bit IPv6 address) | 306 | | 307 | | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 // Optional Type Length Value objects (variable) // 310 // // 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 Figure 3: SRH for DetNet 315 The DetNet SRv6 flow is identified by DetNet SID in SRH. DetNet SID 316 is defined as a 128-bit value. 318 A new DetNet SID is defined to support DetNet service protection for 319 TSN stream. It is used to uniquely identify a DetNet flow in a SRv6 320 DetNet node and to discriminate packets in the same DetNet flow by 321 sequence number. DetNet SID is defined as follows: 323 0 1 2 3 324 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 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | Type | Length | Flow Identification | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | Flow Identification | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Flow Identification | RESERVED | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | Frag | Sequence Number | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 Figure 4: DetNet SID for Flow Identification 337 Where: 338 o Type: 8bits, to be assigned by IANA. 339 o Length: 8 bits. 340 o Flow Identification: 64 bits, which is used for identifying DetNet 341 flow. 342 o RESERVED: 20 bits, MUST be 0 on transmission and ignored on 343 receipt. 344 o Sequence Number: 28 bits, which is used for indicating sequence 345 number of a DetNet flow. 346 o Frag: 4 bits, if a packet must be divided into multiple packages 347 for transmission, record the fragmentation number. 349 When TSN stream is transmitted over a SRv6 network, TSN Stream 350 Identification MUST pair SRv6 flows and TSN Streams and encode that 351 in data plane formats as well. When the new DetNet SID is used to 352 identify DetNet flow and the mapping for TSN stream is as follows: 354 o Type: 8bits, to be assigned by IANA, used to identify sources from 355 the TSN stream. 356 o Length: 8 bits, the value is 16 octets. 357 o Flow Identification: 64 bits, which is used for identifying DetNet 358 flow. The former 48 bit corresponds to the MAC address identified 359 by the TSN stream, and the post 16 bit comes from the VLAN-ID and 360 priority parameters in TSN packet. 361 o RESERVED: 20 bits, MUST be 0 on transmission and ignored on 362 receipt. 363 o Sequence Number: 28 bits, which is used for indicating sequence 364 number of a DetNet flow. The value comes from the Redundancy tag 365 (R-TAG) in TSN packet as defined in Clause 7.8 of IEEE 802.1CB 366 [IEEE8021CB]. 368 Flow Identification in SRH can identify Null Stream, Source MAC and 369 VLAN Stream, Active Destination MAC and VLAN Stream in TSN stream. 370 For TSN IP Stream, destination MAC address and vlan is still 371 indicated by flow Identification, other IP-based fields correspond 372 to IP fields in SRv6 one by one, such as IP source address, IP 373 destination address, DSCP, IP next protocol, source port, destination 374 port etc. 376 5.2. SRv6 Network Programming new Functions 378 New SRv6 Network Programming functions are defined as follows: 380 5.2.1. End. B.Replication DetNet SID: Packet Replication Function 382 When N receives a packet whose IPv6 DA is S and S is a local End.B. 383 SL is Segment Left(SL), Replication DetNet SID, does: 385 S01. IF NH=SRH & SL>0 THEN { 386 S02. Extract the DetNet SID values from the SRH or TSN Stream 387 identification and TSN Rtag. 388 S03. Create two new outer IPv6+SRH headers: IPv6-SRH-1 and 389 IPv6-SRH-2 Insert the policy-instructed segment lists in each 390 newly created SRH (SRH-1 and SRH-2). Also, add the extracted 391 DetNet SID into SRH-1 and SRH-2. 392 S04. Remove the incoming outer IPv6+SRH header, restore DATA as the 393 original packet. 394 S05. Create a duplication of the restore DATA as the duplicate 395 packet. 396 S06. Encapsulate the original packet into the first outer IPv6+SRH 397 header: (IPv6-SRH-1) (original packet) 398 S07. Encapsulate the duplicate packet into the second outer IPv6+SRH 399 header: (IPv6-SRH-2) (duplicate packet) 400 S08. Set the IPv6 SA as the local address of this node. 401 S09. Set the IPv6 DA of IPv6-SRH-1 to the first segment of the SRv6 402 Policy in of SRH-1 segment list. 403 S10. Set the IPv6 DA of IPv6-SRH-2 to the first segment of the SRv6 404 Policy in of SRH-2 segment list. 405 S11. } 407 5.2.2. End. B. Elimination: Packet Elimination Function 409 When N receives a packet whose IPv6 DA is S and S is a local End.B. 410 SL is Segment Left(SL), Elimination DetNet SID, does: 412 S01. IF NH=SRH & SL>0 & "the packet is not a redundant packet" THEN { 413 S02. Do not decrement SL nor update the IPv6 DA with SRH(SL) 414 S03. Extract the value of DetNet SID from the SRH 415 S04. Extract Flow Identification and Sequence Number from DetNet 416 SID. 417 S05. IF NOT receive the packet with the same Flow Identification 418 and Sequence Number { 419 S06. Create a new outer IPv6+SRH header 420 S07. Insert the policy-instructed segment lists in the newly 421 created SRH and add the retrieved DetNet SID in the newly 422 created SRH 423 S08. Remove the incoming outer IPv6+SRH header. 424 S09. Set the IPv6 DA to the first segment of the SRv6 Policy in 425 the newly created SRH 426 S10. } Else { 427 S11. Drop the packet 428 S12. } 429 S13. } 431 6. SRv6 Data Plane Considerations 432 6.1. DetNet PREOF 434 Flow Identification and sequence number are necessary in the 435 encapsulation of SRv6 for DetNet in order to support service 436 protection. Replication nodes decide which DetNet flows are supposed 437 to be replicated by the flow identification. Elimination nodes 438 decide whether a packet should be dropped because of redundancy by 439 the flow identification and sequence number. 441 FRER function and the provided service recovery is available in that 442 the Stream-ID and the TSN sequence number are paired with the SRv6 443 flow parameters they can be combined with PREOF functions. 445 SRv6 supporting DetNet flows may use Packet Replication, Elimination 446 and Ordering Functions (PREOF) based on the DetNet SID in SRH, which 447 is derived from TSN Stream. The specific operation of Frame 448 Replication and Elimination for Redundancy (FRER) [802.1CB] is not 449 modified by the use of DetNet and follows IEEE 802.1CB [IEEE8021CB]. 451 6.2. Edge Node Processing 453 An edge node is responsible for matching ingress packets to the 454 service they require and encapsulating them accordingly. An edge node 455 is a SRv6 DetNet-aware forwarder, and may participate in the packet 456 replication and duplication elimination. 458 The Controller sends Detnet SRv6 polices to the edge node. These 459 polices include mapping of ingress TSN stream to DetNet SRv6 flow. 460 The detnet SID is associated with an SR Policy, and its value comes 461 from a TSN packet. When the edge node forwards a TSN packet to SRv6 462 network, inserting an SRH with the policy and adds an outer IPv6 463 header. The TSN flow identification and sequence number is copied to 464 DetNet SID in SRv6 SRH. 466 Additionally the DetNet-aware edge node does duplicate frame 467 elimination based on the flow identification and the sequence number 468 combination. The packet replication is also done within the 469 DetNet-aware forwarder. During elimination and the replication 470 process the sequence number of the DetNet member flow MUST be 471 preserved and copied to the egress DetNet member flow. 473 6.3. MTU and Fragmentation 475 Because the SRH field is added during transmission in the srv6 476 network, the data packet may exceed the MTU of the device interface, 477 so it is necessary to divide the packet. The serial number of the 478 fragment packet is recorded in the frag field of DetNet Sid for flow 479 identification. At the SRv6 network edge node, reorganize these 480 received fragment packets as one packet and send it to the TSN 481 network. 483 In the process of fragment, the Flow Identification number and 484 Sequence Number of the packet are consistent with the original 485 packet. Based on the Flow Identification number of each stream, the 486 transmission node sends the fragment alarm information to the 487 controller. 489 7. Management and Control Information Summary 491 The following summarizes the set of information that is needed to 492 support TSN over SRv6 at the ingress edge node: 494 o TSN Stream identification and TSN R-tag information to be mapped to 495 SRv6 SRH SID. Note that a single TSN Stream identification can map 496 to one SRH DetNet SID, and it can used for PREOF. 497 o IPv6 source address. 498 o IPv6 destination address. 499 o IPv6 Traffic Class. 501 This information MUST be provisioned per DetNet flow via 502 configuration, e.g., via the controller or management plane. 504 It is the responsibility of the DetNet controller plane to properly 505 provision both flow identification information and the flow specific 506 resources needed to be provided the traffic treatment needed to meet 507 each flow's service requirements. This applies for aggregated and 508 individual flows. 510 DetNet SRv6 flow and TSN Stream mapping related information are 511 required only for DetNet SRv6 edge nodes; the edge node is TSN-aware 512 and DetNet SRv6-aware node. These DetNet SRv6 edge nodes are member 513 of both the DetNet SRv6 domain and the TSN sub-network. Within the 514 TSN sub-network the DetNet SRv6 node may has a TSM-aware role, so TSN 515 specific management and control plane functionalities must be 516 implemented. There are many similarities in the management plane 517 techniques used in DetNet and TSN, but that is not the case for the 518 control plane protocols. For example, RSVP-TE and MSRP behaves 519 differently. Therefore management and control plane design is an 520 important aspect of scenarios, where mapping between DetNet SRv6 and 521 TSN is required. 523 In order to use a DetNet SRv6 sub-network between TSN nodes, TSN 524 stream specific information must be converted to SRv6 DetNet SRH. TSN 525 Stream ID and stream related parameters/requirements must be 526 converted to a SRv6 DetNet flow ID and flow related parameters/ 527 requirements. Note that, as the DetNet SRv6 sub-network is just a 528 portion of the end2end TSN path (i.e., single hop from IP 529 perspective), some parameters (e.g., delay) may differ significantly. 530 Other TSN stream parameters (like bandwidth) also may have to be 531 tuned due to the SRv6 encapsulation used in the DetNet sub-network. 533 In some case it may be challenging to determine some TSN Stream 534 related information. For example which DetNet SRv6 paths are 535 multi-Listener of the mapped TSN stream to one TSN stream Talker? 536 However it may be not trivial to locate the point/interface where 537 that Listener is connected to the TSN sub-network. Such 538 attributes may require interaction between control and management 539 plane functions and between DetNet SRv6 and TSN domains. 541 Mapping between DetNet SRv6 flow identifiers and TSN Stream 542 identifiers, if not provided explicitly, can be done by a DetNet SRv6 543 node locally based on the configuration of SRv6 Behaviors associated 544 with a SID. 546 8. Security Considerations 548 This document will not introduce new security problems. 550 9. IANA Considerations 552 This document requests assigning new DetNet SID TLV code-points as 553 described in section 5. 555 10. Acknowledgements 557 Thanks for Guanghua Lan and Ximing Dong for their comments and 558 contributions. 560 11. Normative References 562 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 563 Requirement Levels", BCP 14, RFC 2119, 564 DOI 10.17487/RFC2119, March 1997, 565 . 567 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 568 2119 Key Words", RFC 8174, May 2017, 569 . 571 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 572 (IPv6) Specification", RFC 8200, July 2017, 573 . 575 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 576 Decraene, B., Litkowski, S., and R. Shakir, "Segment 577 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 578 July 2018, . 580 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 581 "Deterministic Networking Architecture", RFC 8655, May 582 2019, . 584 [RFC8754] Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 585 Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment 586 Routing Header (SRH)", RFC 8754, June 2019. 587 . 589 [IEEE8021CB] 590 Finn, N., "Draft Standard for Local and metropolitan area 591 networks - Seamless Redundancy", IEEE P802.1CB 592 /D2.1 P802.1CB, December 2015, 593 . 596 [IEEE8021Q] 597 IEEE 802.1, "Standard for Local and metropolitan area 598 networks--Bridges and Bridged Networks (IEEE Std 802.1Q- 599 2014)", 2014, . 601 [I-D.ietf-spring-srv6-network-programming] 602 Filsfils, C., Camarillo, P., Leddy, J., 603 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 604 Network Programming", draft-ietf-spring-srv6-network- 605 programming-14 (work in progress), March 2020. 607 Authors' Addresses 609 Xueshun Wang 610 Fiberhome Telecom LTD 611 Email: xswang@fiberhome.com 613 Jinyou Dai 614 Fiberhome Telecom LTD 615 Email: djy@fiberhome.com 617 Jianhua Liu 618 Fiberhome Telecom LTD 619 Email: liujianhua@fiberhome.com 621 Jing Xu 622 Fiberhome Telecom LTD 623 Email: xujing2010@fiberhome.com