idnits 2.17.1 draft-ietf-detnet-tsn-vpn-over-mpls-04.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 (November 2, 2020) is 1270 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: 'Network' is mentioned on line 183, but not defined == Unused Reference: 'IEEE802.1AE-2018' is defined on line 590, but no explicit reference was found in the text == Unused Reference: 'RFC4301' is defined on line 617, but no explicit reference was found in the text == Outdated reference: A later version (-16) exists of draft-ietf-detnet-security-12 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: May 6, 2021 A. Malis 6 Malis Consulting 7 S. Bryant 8 Futurewei Technologies 9 D. Fedyk 10 LabN Consulting, L.L.C. 11 November 2, 2020 13 DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over MPLS 14 draft-ietf-detnet-tsn-vpn-over-mpls-04 16 Abstract 18 This document specifies the Deterministic Networking data plane when 19 TSN networks are interconnected over a DetNet MPLS Network. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 6, 2021. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3 58 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 59 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4 60 3. IEEE 802.1 TSN Over DetNet MPLS Data Plane Scenario . . . . . 4 61 4. DetNet MPLS Data Plane . . . . . . . . . . . . . . . . . . . 6 62 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 63 4.2. TSN over DetNet MPLS Encapsulation . . . . . . . . . . . 7 64 5. TSN over MPLS Data Plane Procedures . . . . . . . . . . . . . 8 65 5.1. Edge Node TSN Procedures . . . . . . . . . . . . . . . . 8 66 5.2. Edge Node DetNet Service Proxy Procedures . . . . . . . . 9 67 5.3. Edge Node DetNet Service and Forwarding Sub-Layer 68 Procedures . . . . . . . . . . . . . . . . . . . . . . . 10 69 6. Controller Plane (Management and Control) Considerations . . 11 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 71 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 72 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 73 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 74 10.1. Normative References . . . . . . . . . . . . . . . . . . 13 75 10.2. Informative References . . . . . . . . . . . . . . . . . 14 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 78 1. Introduction 80 The Time-Sensitive Networking Task Group (TSN TG) within IEEE 802.1 81 Working Group deals with deterministic services through IEEE 802 82 networks. Deterministic Networking (DetNet) defined by IETF is a 83 service that can be offered by a L3 network to DetNet flows. General 84 background and concepts of DetNet can be found in [RFC8655]. 86 This document specifies the use of a DetNet MPLS network to 87 interconnect TSN nodes/network segments. DetNet MPLS data plane is 88 defined in [I-D.ietf-detnet-mpls]. 90 2. Terminology 92 2.1. Terms Used in This Document 94 This document uses the terminology and concepts established in the 95 DetNet architecture [RFC8655] and 96 [I-D.ietf-detnet-data-plane-framework], and [I-D.ietf-detnet-mpls]. 97 The reader is assumed to be familiar with these documents and their 98 terminology. 100 2.2. Abbreviations 102 The following abbreviations are used in this document: 104 AC Attachment Circuit. 106 CE Customer Edge equipment. 108 CW Control Word. 110 DetNet Deterministic Networking. 112 DF DetNet Flow. 114 FRER Frame Replication and Elimination for Redundancy (TSN 115 function). 117 L2 Layer 2. 119 L2VPN Layer 2 Virtual Private Network. 121 L3 Layer 3. 123 LSR Label Switching Router. 125 MPLS Multiprotocol Label Switching. 127 MPLS-TE Multiprotocol Label Switching - Traffic Engineering. 129 MPLS-TP Multiprotocol Label Switching - Transport Profile. 131 NSP Native Service Processing. 133 OAM Operations, Administration, and Maintenance. 135 PE Provider Edge. 137 PREOF Packet Replication, Elimination and Ordering Functions. 139 PW PseudoWire. 141 S-PE Switching Provider Edge. 143 T-PE Terminating Provider Edge. 145 TSN Time-Sensitive Network. 147 2.3. Requirements Language 149 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 150 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 151 "OPTIONAL" in this document are to be interpreted as described in BCP 152 14 [RFC2119] [RFC8174] when, and only when, they appear in all 153 capitals, as shown here. 155 3. IEEE 802.1 TSN Over DetNet MPLS Data Plane Scenario 157 Figure 1 shows IEEE 802.1 TSN end stations operating over a TSN aware 158 DetNet service running over an MPLS network. DetNet Edge Nodes sit 159 at the boundary of a DetNet domain. They are responsible for mapping 160 non-DetNet aware L2 traffic to DetNet services. They also support 161 the imposition and disposition of the required DetNet encapsulation. 162 These are functionally similar to pseudowire (PW) Terminating 163 Provider Edge (T-PE) nodes which use MPLS-TE LSPs. In this example 164 TSN Streams are simple applications over DetNet flows. The specific 165 of this operation are discussed later in this document. 167 TSN Edge Transit Edge TSN 168 End System Node Node Node End System 169 (T-PE) (LSR) (T-PE) 171 +----------+ +----------+ 172 | TSN | <---------End to End TSN Service----------> | TSN | 173 | Applic. | | Applic. | 174 +----------+ +.........+ +.........+ +----------+ 175 | | | \S-Proxy: :S-Proxy/ | | | 176 | TSN | | +.+---+<-- DetNet flow -->+---+ | | | TSN | 177 | | |TSN| |Svc| |Svc| |TSN| | | 178 +----------+ +---+ +---+ +----------+ +---+ +---+ +----------+ 179 | L2 | | L2| |Fwd| |Forwarding| |Fwd| |L2 | | L2 | 180 +------.---+ +-.-+ +-.-+ +---.----.-+ +--.+ +-.-+ +---.------+ 181 : Link : / ,-----. \ : Link : / ,-----. \ 182 +........+ +-[ Sub ]-+ +........+ +-[ TSN ]-+ 183 [Network] [Network] 184 `-----' `-----' 186 |<------ DetNet MPLS ------>| 187 |<---------------------- TSN --------------------->| 189 Figure 1: A TSN over DetNet MPLS Enabled Network 191 In this example, edge nodes provide a service proxy function that 192 "associates" the DetNet flows and native flows (i.e., TSN Streams) at 193 the edge of the DetNet domain. TSN streams are treated as App-flows 194 for DetNet. The whole DetNet domain behaves as a TSN relay node for 195 the TSN streams. The service proxy behaves as a port of that TSN 196 relay node. 198 Figure 2 illustrates how DetNet can provide services for IEEE 802.1 199 TSN end systems, CE1 and CE2, over a DetNet enabled MPLS network. 200 Edge nodes, E1 and E2, insert and remove required DetNet data plane 201 encapsulation. The 'X' in the edge nodes and relay node, R1, 202 represent a potential DetNet compound flow packet replication and 203 elimination point. This conceptually parallels L2VPN services, and 204 could leverage existing related solutions as discussed below. 206 TSN |<------- End to End DetNet Service ------>| TSN 207 Service | Transit Transit | Service 208 TSN (AC) | |<-Tnl->| |<-Tnl->| | (AC) TSN 209 End | V V 1 V V 2 V V | End 210 System | +--------+ +--------+ +--------+ | System 211 +---+ | | E1 |=======| R1 |=======| E2 | | +---+ 212 | |--|----|._X_....|..DF1..|.._ _...|..DF3..|...._X_.|---|---| | 213 |CE1| | | \ | | X | | / | | |CE2| 214 | | | \_.|..DF2..|._/ \_..|..DF4..|._/ | | | 215 +---+ | |=======| |=======| | +---+ 216 ^ +--------+ +--------+ +--------+ ^ 217 | Edge Node Relay Node Edge Node | 218 | (T-PE) (S-PE) (T-PE) | 219 | | 220 |<- TSN -> <------- TSN Over DetNet MPLS -------> <- TSN ->| 221 | | 222 |<-------- Time Sensitive Networking (TSN) Service ------->| 224 X = Service protection 225 DFx = DetNet member flow x over a TE LSP 227 Figure 2: IEEE 802.1TSN Over DetNet 229 4. DetNet MPLS Data Plane 231 4.1. Overview 233 The basic approach defined in [I-D.ietf-detnet-mpls] supports the 234 DetNet service sub-layer based on existing pseudowire (PW) 235 encapsulations and mechanisms, and supports the DetNet forwarding 236 sub-layer based on existing MPLS Traffic Engineering encapsulations 237 and mechanisms. 239 A node operating on a DetNet flow in the Detnet service sub-layer, 240 i.e. a node processing a DetNet packet which has the S-Label as top 241 of stack uses the local context associated with that S-Label, for 242 example a received F-Label, to determine what local DetNet 243 operation(s) are applied to that packet. An S-Label may be unique 244 when taken from the platform label space [RFC3031], which would 245 enable correct DetNet flow identification regardless of which input 246 interface or LSP the packet arrives on. The service sub-layer 247 functions (i.e., PREOF) use a DetNet control word (d-CW). 249 The DetNet MPLS data plane builds on MPLS Traffic Engineering 250 encapsulations and mechanisms to provide a forwarding sub-layer that 251 is responsible for providing resource allocation and explicit routes. 253 The forwarding sub-layer is supported by one or more forwarding 254 labels (F-Labels). 256 DetNet edge/relay nodes are DetNet service sub-layer aware, 257 understand the particular needs of DetNet flows and provide both 258 DetNet service and forwarding sub-layer functions. They add, remove 259 and process d-CWs, S-Labels and F-labels as needed. MPLS DetNet 260 nodes and transit nodes include DetNet forwarding sub-layer 261 functions, support for notably explicit routes, and resources 262 allocation to eliminate (or reduce) congestion loss and jitter. 263 Unlike other DetNet node types, transit nodes provide no service sub- 264 layer processing. 266 4.2. TSN over DetNet MPLS Encapsulation 268 The basic encapsulation approach is to treat a TSN Stream as an App- 269 flow from the DetNet MPLS perspective. The corresponding example 270 shown in Figure 3. 272 /-> +------+ +------+ +------+ TSN ^ ^ 273 | | X | | X | | X |<- Appli : : 274 App-Flow <-+ +------+ +------+ +------+ cation : :(1) 275 for MPLS | |TSN-L2| |TSN-L2| |TSN-L2| : v 276 \-> +---+======+--+======+--+======+-----+ : 277 | d-CW | | d-CW | | d-CW | : 278 DetNet-MPLS +------+ +------+ +------+ :(2) 279 |Labels| |Labels| |Labels| v 280 +---+======+--+======+--+======+-----+ 281 Link/Sub-Network | L2 | | TSN | | UDP | 282 +------+ +------+ +------+ 283 | IP | 284 +------+ 285 | L2 | 286 +------+ 287 (1) TSN Stream 288 (2) DetNet MPLS Flow 290 Figure 3: Example TSN over MPLS Encapsulation Formats 292 In the figure, "Application" indicates the application payload 293 carried by the TSN network. "MPLS App-Flow" indicates that the TSN 294 Stream is the payload from the perspective of the DetNet MPLS data 295 plane defined in [I-D.ietf-detnet-mpls]. A single DetNet MPLS flow 296 can aggregate multiple TSN Streams. 298 5. TSN over MPLS Data Plane Procedures 300 Description of Edge Nodes procedures and functions for TSN over 301 DetNet MPLS scenario follows the concept of [RFC3985] and covers the 302 Edge Nodes components shown on Figure 1. In this section the 303 following procedures of DetNet Edge Nodes are described: 305 o TSN related (Section 5.1) 307 o DetNet Service Proxy (Section 5.2) 309 o DetNet service and forwarding sub-layer (Section 5.3) 311 The sub-sections describe procedures for forwarding packets by DetNet 312 Edge nodes, where such packets are received from either directly 313 connected CEs (TSN nodes) or some other DetNet Edge nodes. 315 5.1. Edge Node TSN Procedures 317 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 318 Working Group have defined (and are defining) a number of amendments 319 to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and 320 bounded latency in bridged networks. IEEE 802.1CB [IEEE8021CB] 321 defines packet replication and elimination functions for a TSN 322 network. 324 The implementation of TSN entity (i.e., TSN packet processing 325 functions) must be compliant with the relevant IEEE 802.1 standards. 327 TSN specific functions are executed on the data received by the 328 DetNet Edge Node from the connected CE before forwarded to connected 329 CE(s) or presentation to the DetNet Service Proxy function for 330 transmission across the DetNet domain, or on the data received from a 331 DetNet PW by a PE before it is output on the Attachment Circuit(s) 332 (AC). 334 TSN packet processing function(s) of Edge Nodes (T-PE) are belonging 335 to the native service processing (NSP) [RFC3985] block. This is 336 similar to other functionalities being defined by standard bodies 337 other than the IETF (for example in case of Ethernet: stripping, 338 overwriting or adding VLAN tags, etc.). Depending on the TSN role of 339 the Edge Node in the end-to-end TSN service selected TSN functions 340 are supported. 342 When a PE receives a packet from a CE, on a given AC with DetNet 343 service, it first checks via Stream Identification (see Clause 6. of 344 IEEE 802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb]) 345 whether the packet belongs to a configured TSN Stream (i.e., App-flow 346 from DetNet perspective). If no Stream ID is matched and no other 347 (VPN) service is configured for the AC then packet MUST be dropped. 348 If there is a matching TSN Stream then the Stream-ID specific TSN 349 functions are executed (e.g., ingress policing, header field 350 manipulation in case of active Stream Identification, FRER, etc.). 351 Source MAC lookup may also be used for local MAC address learning. 353 If the PE decides to forward the packet, the packet MUST be forwarded 354 according to the TSN Stream specific configuration to connected CE(s) 355 (in case of local bridging) and/or to the DetNet Service Proxy (in 356 case of forwarding to remote CE(s) required). If there are no TSN 357 Stream specific forwarding configurations the PE MUST flood the 358 packet to other locally attached CE(s) and to the DetNet Service 359 Proxy. If the administrative policy on the PE does not allow 360 flooding the PE MUST drop the packet. 362 When a TSN entity of the PE receives a packet from the DetNet Service 363 Proxy, it first checks via Stream Identification (see Clause 6. of 364 IEEE 802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb]) 365 whether the packet belongs to a configured TSN Stream. If no Stream 366 ID is matched then packet is dropped. If there is a matching TSN 367 Stream then the Stream ID specific TSN functions are executed (e.g., 368 header field manipulation in case of active Stream Identification, 369 FRER, etc.). Source MAC lookup may also be used for local MAC 370 address learning. 372 If the PE decides to forward the packet, the packet is forwarded 373 according to the TSN Stream specific configuration to connected 374 CE(s). If there are no TSN Stream specific forwarding configurations 375 the PE floods the packet to locally attached CE(s). If the 376 administrative policy on the PE does not allow flooding the PE drops 377 the packet. 379 Implementations of this document SHALL use management and control 380 information to ensure TSN specific functions of the Edge Node 381 according to the expectations of the connected TSN network. 383 5.2. Edge Node DetNet Service Proxy Procedures 385 The Service Proxy function maps between App-flows and DetNet flows. 386 The DetNet Edge Node TSN entity MUST support the TSN Stream 387 identification functions and the related managed objects as defined 388 in Clause 6. and Clause 9. of IEEE 802.1CB [IEEE8021CB] and IEEE 389 P802.1CBdb [IEEEP8021CBdb] to recognize the App-flow related packets. 390 The Service Proxy presents TSN Streams as an App-flow to a DetNet 391 Flow. 393 When a DetNet Service Proxy receives a packet from the TSN Entity it 394 MUST check whether such an App-flow is present in its mapping table. 395 If present it associates the internal DetNet flow-ID to the packet 396 and MUST forward it to the DetNet Service and Forwarding sub-layers. 397 If no matching statement is present it MUST drop the packet. 399 When a DetNet Service Proxy receives a packet from the DetNet Service 400 and Forwarding sub-layers it MUST be forwarded to the Edge Node TSN 401 Entity. 403 Implementations of this document SHALL use management and control 404 information to map a TSN Stream to a DetNet flow. N:1 mapping 405 (aggregating multiple TSN Streams in a single DetNet flow) SHALL be 406 supported. The management or control function that provisions flow 407 mapping SHALL ensure that adequate resources are allocated and 408 configured to provide proper service requirements of the mapped 409 flows. 411 Due to the (intentional) similarities of the DetNet PREOF and TSN 412 FRER functions service protection function interworking is possible 413 between the TSN and the DetNet domains. Such service protection 414 interworking scenarios MAY require to copy sequence number fields 415 from TSN (L2) to PW (MPLS) encapsulation. However, such interworking 416 is out-of-scope in this document and left for further study. 418 A MPLS DetNet flow is configured to carry any number of TSN flows. 419 The DetNet flow specific bandwidth profile SHOULD match the required 420 bandwidth of the App-flow aggregate. 422 5.3. Edge Node DetNet Service and Forwarding Sub-Layer Procedures 424 In the design of [I-D.ietf-detnet-mpls] an MPLS service label (the 425 S-Label), similar to a pseudowire (PW) label [RFC3985], is used to 426 identify both the DetNet flow identity and the payload MPLS payload 427 type. The DetNet sequence number is carried in the DetNet Control 428 word (d-CW) which carries the Data/OAM discriminator as well. In 429 [I-D.ietf-detnet-mpls] two sequence number sizes are supported: a 16 430 bit sequence number and a 28 bit sequence number. 432 PREOF functions and the provided service recovery is available only 433 within the DetNet domain as the DetNet flow-ID and the DetNet 434 sequence number are not valid outside the DetNet network. MPLS 435 (DetNet) Edge node terminates all related information elements 436 encoded in the MPLS labels. 438 The LSP used to forward the DetNet packet may be of any type (MPLS- 439 LDP, MPLS-TE, MPLS-TP [RFC5921], or MPLS-SR [RFC8660]). The LSP 440 (F-Label) label and/or the S-Label may be used to indicate the queue 441 processing as well as the forwarding parameters. 443 When a PE receives a packet from the Service Proxy function it MUST 444 add to the packet the DetNet flow-ID specific S-label and create a 445 d-CW. The PE MUST forward the packet according to the configured 446 DetNet Service and Forwarding sub-layer rules to other PE nodes. 448 When a PE receives an MPLS packet from a remote PE, then, after 449 processing the MPLS label stack, if the top MPLS label ends up being 450 a DetNet S-label that was advertised by this node, then the PE MUST 451 forward the packet according to the configured DetNet Service and 452 Forwarding sub-layer rules to other PE nodes or via the Detnet 453 Service Proxy function towards locally connected CE(s). 455 For further details on DetNet Service and Forwarding sub-layers see 456 [I-D.ietf-detnet-mpls]. 458 6. Controller Plane (Management and Control) Considerations 460 TSN Stream(s) to DetNet flow mapping related information are required 461 only for the service proxy function of MPLS (DetNet) Edge nodes. 462 From the Data Plane perspective there is no practical difference 463 based on the origin of flow mapping related information (management 464 plane or control plane). 466 The following summarizes the set of information that is needed to 467 configure TSN over DetNet MPLS: 469 o TSN related configuration information according to the TSN role of 470 the DetNet MPLS node, as per [IEEE8021Q], [IEEE8021CB] and 471 [IEEEP8021CBdb]. 473 o DetNet MPLS related configuration information according to the 474 DetNet role of the DetNet MPLS node, as per 475 [I-D.ietf-detnet-mpls]. 477 o App-Flow identification information to map received TSN Stream(s) 478 to the DetNet flow. Parameters of TSN stream identification are 479 defined in [IEEE8021CB] and [IEEEP8021CBdb]. 481 This information MUST be provisioned per DetNet flow. 483 Mappings between DetNet and TSN management and control planes are out 484 of scope of the document. Some of the challanges are highligthed 485 below. 487 MPLS DetNet Edge nodes are member of both the DetNet domain and the 488 connected TSN network. From the TSN network perspective the MPLS 489 (DetNet) Edge node has a "TSN relay node" role, so TSN specific 490 management and control plane functionalities must be implemented. 491 There are many similarities in the management plane techniques used 492 in DetNet and TSN, but that is not the case for the control plane 493 protocols. For example, RSVP-TE and MSRP behaves differently. 494 Therefore management and control plane design is an important aspect 495 of scenarios, where mapping between DetNet and TSN is required. 497 Note that, as the DetNet network is just a portion of the end to end 498 TSN path (i.e., single hop from Ethernet perspective), some 499 parameters (e.g., delay) may differ significantly. Since there is no 500 interworking function the bandwidth of DetNet network is assumed to 501 be set large enough to handle all TSN Flows it will support. At the 502 egress of the Detnet Domain the MPLS headers are stripped and the TSN 503 flow continues on as a normal TSN flow. 505 In order to use a DetNet network to interconnect TSN segments, TSN 506 specific information must be converted to DetNet domain specific 507 ones. TSN Stream ID(s) and stream(s) related parameters/requirements 508 must be converted to a DetNet flow-ID and flow related parameters/ 509 requirements. 511 In some case it may be challenging to determine some egress node 512 related information. For example, it may be not trivial to locate 513 the egress point/interface of a TSN Streams with a multicast 514 destination MAC address. Such scenarios may require interaction 515 between control and management plane functions and between DetNet and 516 TSN domains. 518 Mapping between DetNet flow identifiers and TSN Stream identifiers, 519 if not provided explicitly, can be done by the service proxy function 520 of an MPLS (DetNet) Edge node locally based on information provided 521 for configuration of the TSN Stream identification functions (e.g., 522 Mask-and-Match Stream identification). 524 Triggering the setup/modification of a DetNet flow in the DetNet 525 network is an example where management and/or control plane 526 interactions are required between the DetNet and the TSN network. 528 Configuration of TSN specific functions (e.g., FRER) inside the TSN 529 network is a TSN domain specific decision and may not be visible in 530 the DetNet domain. Service protection interworking scenarios are 531 left for further study. 533 7. Security Considerations 535 Security considerations for DetNet are described in detail in 536 [I-D.ietf-detnet-security]. General security considerations are 537 described in [RFC8655]. 539 DetNet MPLS data plane specific considerations are summarized and 540 described in [I-D.ietf-detnet-mpls] including any application flow 541 types. This document focuses on the scenario where TSN Streams are 542 the application flows for DetNet and it is already covered by those 543 DetNet MPLS data plane security considerations. 545 8. IANA Considerations 547 This document makes no IANA requests. 549 9. Acknowledgements 551 The authors wish to thank Norman Finn, Lou Berger, Craig Gunther, 552 Christophe Mangin and Jouni Korhonen for their various contributions 553 to this work. 555 10. References 557 10.1. Normative References 559 [I-D.ietf-detnet-mpls] 560 Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., 561 and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf- 562 detnet-mpls-13 (work in progress), October 2020. 564 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 565 Requirement Levels", BCP 14, RFC 2119, 566 DOI 10.17487/RFC2119, March 1997, 567 . 569 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 570 Label Switching Architecture", RFC 3031, 571 DOI 10.17487/RFC3031, January 2001, 572 . 574 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 575 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 576 May 2017, . 578 10.2. Informative References 580 [I-D.ietf-detnet-data-plane-framework] 581 Varga, B., Farkas, J., Berger, L., Malis, A., and S. 582 Bryant, "DetNet Data Plane Framework", draft-ietf-detnet- 583 data-plane-framework-06 (work in progress), May 2020. 585 [I-D.ietf-detnet-security] 586 Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic 587 Networking (DetNet) Security Considerations", draft-ietf- 588 detnet-security-12 (work in progress), October 2020. 590 [IEEE802.1AE-2018] 591 IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC 592 Security (MACsec)", 2018, 593 . 595 [IEEE8021CB] 596 IEEE 802.1, "Standard for Local and metropolitan area 597 networks - Frame Replication and Elimination for 598 Reliability (IEEE Std 802.1CB-2017)", 2017, 599 . 601 [IEEE8021Q] 602 IEEE 802.1, "Standard for Local and metropolitan area 603 networks--Bridges and Bridged Networks (IEEE Std 802.1Q- 604 2018)", 2018, . 606 [IEEEP8021CBdb] 607 Mangin, C., "Extended Stream identification functions", 608 IEEE P802.1CBdb /D1.0 P802.1CBdb, September 2020, 609 . 612 [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation 613 Edge-to-Edge (PWE3) Architecture", RFC 3985, 614 DOI 10.17487/RFC3985, March 2005, 615 . 617 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 618 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 619 December 2005, . 621 [RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau, 622 L., and L. Berger, "A Framework for MPLS in Transport 623 Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010, 624 . 626 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 627 "Deterministic Networking Architecture", RFC 8655, 628 DOI 10.17487/RFC8655, October 2019, 629 . 631 [RFC8660] Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S., 632 Decraene, B., Litkowski, S., and R. Shakir, "Segment 633 Routing with the MPLS Data Plane", RFC 8660, 634 DOI 10.17487/RFC8660, December 2019, 635 . 637 Authors' Addresses 639 Balazs Varga (editor) 640 Ericsson 641 Magyar Tudosok krt. 11. 642 Budapest 1117 643 Hungary 645 Email: balazs.a.varga@ericsson.com 647 Janos Farkas 648 Ericsson 649 Magyar Tudosok krt. 11. 650 Budapest 1117 651 Hungary 653 Email: janos.farkas@ericsson.com 655 Andrew G. Malis 656 Malis Consulting 658 Email: agmalis@gmail.com 660 Stewart Bryant 661 Futurewei Technologies 663 Email: stewart.bryant@gmail.com 665 Don Fedyk 666 LabN Consulting, L.L.C. 668 Email: dfedyk@labn.net