idnits 2.17.1 draft-ietf-detnet-tsn-vpn-over-mpls-01.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 27, 2019) is 1643 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 198, but not defined == Outdated reference: A later version (-06) exists of draft-ietf-detnet-data-plane-framework-02 == Outdated reference: A later version (-13) exists of draft-ietf-detnet-mpls-01 == 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 29, 2020 A. Malis 6 Independent 7 S. Bryant 8 Futurewei Technologies 9 D. Fedyk 10 LabN Consulting, L.L.C. 11 October 27, 2019 13 DetNet Data Plane: IEEE 802.1 Time Sensitive Networking over MPLS 14 draft-ietf-detnet-tsn-vpn-over-mpls-01 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 April 29, 2020. 38 Copyright Notice 40 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . . . 9 69 6. Controller Plane (Management and Control) Considerations . . 10 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 71 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 72 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 73 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 74 10.1. Normative References . . . . . . . . . . . . . . . . . . 11 75 10.2. Informative References . . . . . . . . . . . . . . . . . 12 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 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 85 [I-D.ietf-detnet-architecture]. 87 This document specifies the use of a DetNet MPLS network to 88 interconnect TSN nodes/network segments. DetNet MPLS data plane is 89 defined in [I-D.ietf-detnet-mpls]. 91 2. Terminology 93 2.1. Terms Used in This Document 95 This document uses the terminology and concepts established in the 96 DetNet architecture [I-D.ietf-detnet-architecture] and 97 [I-D.ietf-detnet-data-plane-framework], and [I-D.ietf-detnet-mpls]. 98 The reader is assumed to be familiar with these documents and their 99 terminology. 101 2.2. Abbreviations 103 The following abbreviations are used in this document: 105 AC Attachment Circuit. 107 CE Customer Edge equipment. 109 CoS Class of Service. 111 CW Control Word. 113 DetNet Deterministic Networking. 115 DF DetNet Flow. 117 FRER Frame Replication and Elimination for Redundancy (TSN 118 function). 120 L2 Layer 2. 122 L2VPN Layer 2 Virtual Private Network. 124 L3 Layer 3. 126 LSR Label Switching Router. 128 MPLS Multiprotocol Label Switching. 130 MPLS-TE Multiprotocol Label Switching - Traffic Engineering. 132 MPLS-TP Multiprotocol Label Switching - Transport Profile. 134 MS-PW Multi-Segment PseudoWire (MS-PW). 136 NSP Native Service Processing. 138 OAM Operations, Administration, and Maintenance. 140 PE Provider Edge. 142 PEF Packet Elimination Function. 144 PRF Packet Replication Function. 146 PREOF Packet Replication, Elimination and Ordering Functions. 148 POF Packet Ordering Function. 150 PSN Packet Switched Network. 152 PW PseudoWire. 154 QoS Quality of Service. 156 S-PE Switching Provider Edge. 158 T-PE Terminating Provider Edge. 160 TSN Time-Sensitive Network. 162 2.3. Requirements Language 164 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 165 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 166 "OPTIONAL" in this document are to be interpreted as described in BCP 167 14 [RFC2119] [RFC8174] when, and only when, they appear in all 168 capitals, as shown here. 170 3. IEEE 802.1 TSN Over DetNet MPLS Data Plane Scenario 172 Figure 1 shows IEEE 802.1 TSN end stations operating over a TSN aware 173 DetNet service running over an MPLS network. DetNet Edge Nodes sit 174 at the boundary of a DetNet domain. They are responsible for mapping 175 non-DetNet aware L2 traffic to DetNet services. They also support 176 the imposition and disposition of the required DetNet encapsulation. 177 These are functionally similar to pseudowire (PW) Terminating 178 Provider Edge (T-PE) nodes which use MPLS-TE LSPs. In this example 179 TSN Streams are simple applicaions over DetNet flows. The specific 180 of this operation are discussed later in this document. 182 TSN Edge Transit Edge TSN 183 End System Node Node Node End System 184 (T-PE) (LSR) (T-PE) 186 +----------+ +----------+ 187 | TSN | <---------End to End TSN Service----------> | TSN | 188 | Applic. | | Applic. | 189 +----------+ +.........+ +.........+ +----------+ 190 | | | \S-Proxy: :S-Proxy/ | | | 191 | TSN | | +.+---+<-- DetNet flow -->+---+ | | | TSN | 192 | | |TSN| |Svc| |Svc| |TSN| | | 193 +----------+ +---+ +---+ +----------+ +---+ +---+ +----------+ 194 | L2 | | L2| |Fwd| |Forwarding| |Fwd| |L2 | | L2 | 195 +------.---+ +-.-+ +-.-+ +---.----.-+ +--.+ +-.-+ +---.------+ 196 : Link : / ,-----. \ : Link : / ,-----. \ 197 +........+ +-[ Sub ]-+ +........+ +-[ TSN ]-+ 198 [Network] [Network] 199 `-----' `-----' 201 |<------ DetNet MPLS ------>| 202 |<---------------------- TSN --------------------->| 204 Figure 1: A TSN over DetNet MPLS Enabled Network 206 In this example, edge nodes provide a service proxy function that 207 "associates" the DetNet flows and native flows (i.e., TSN Streams) at 208 the edge of the DetNet domain. TSN streams are treated as App-flows 209 for DetNet. The whole DetNet domain behaves as a TSN relay node for 210 the TSN streams. The service proxy behaves as a port of that TSN 211 relay node. 213 Figure 2 illustrates how DetNet can provide services for IEEE 802.1 214 TSN end systems, CE1 and CE2, over a DetNet enabled MPLS network. 215 Edge nodes, E1 and E2, insert and remove required DetNet data plane 216 encapsulation. The 'X' in the edge nodes and relay node, R1, 217 represent a potential DetNet compound flow packet replication and 218 elimination point. This conceptually parallels L2VPN services, and 219 could leverage existing related solutions as discussed below. 221 TSN |<------- End to End DetNet Service ------>| TSN 222 Service | Transit Transit | Service 223 TSN (AC) | |<-Tnl->| |<-Tnl->| | (AC) TSN 224 End | V V 1 V V 2 V V | End 225 System | +--------+ +--------+ +--------+ | System 226 +---+ | | E1 |=======| R1 |=======| E2 | | +---+ 227 | |--|----|._X_....|..DF1..|.._ _...|..DF3..|...._X_.|---|---| | 228 |CE1| | | \ | | X | | / | | |CE2| 229 | | | \_.|..DF2..|._/ \_..|..DF4..|._/ | | | 230 +---+ | |=======| |=======| | +---+ 231 ^ +--------+ +--------+ +--------+ ^ 232 | Edge Node Relay Node Edge Node | 233 | (T-PE) (S-PE) (T-PE) | 234 | | 235 |<- TSN -> <------- TSN Over DetNet MPLS -------> <- TSN ->| 236 | | 237 |<-------- Time Sensitive Networking (TSN) Service ------->| 239 X = Service protection 240 DFx = DetNet member flow x over a TE LSP 242 Figure 2: IEEE 802.1TSN Over DetNet 244 4. DetNet MPLS Data Plane 246 4.1. Overview 248 The basic approach defined in [I-D.ietf-detnet-mpls] supports the 249 DetNet service sub-layer based on existing pseudowire (PW) 250 encapsulations and mechanisms, and supports the DetNet forwarding 251 sub-layer based on existing MPLS Traffic Engineering encapsulations 252 and mechanisms. 254 A node operating on a DetNet flow in the Detnet service sub-layer, 255 i.e. a node processing a DetNet packet which has the S-Label as top 256 of stack uses the local context associated with that S-Label, for 257 example a received F-Label, to determine what local DetNet 258 operation(s) are applied to that packet. An S-Label may be unique 259 when taken from the platform label space [RFC3031], which would 260 enable correct DetNet flow identification regardless of which input 261 interface or LSP the packet arrives on. The service sub-layer 262 functions (i.e., PREOF) use a DetNet control word (d-CW). 264 The DetNet MPLS data plane builds on MPLS Traffic Engineering 265 encapsulations and mechanisms to provide a forwarding sub-layer that 266 is responsible for providing resource allocation and explicit routes. 268 The forwarding sub-layer is supported by one or more forwarding 269 labels (F-Labels). 271 DetNet edge/relay nodes are DetNet service sub-layer aware, 272 understand the particular needs of DetNet flows and provide both 273 DetNet service and forwarding sub-layer functions. They add, remove 274 and process d-CWs, S-Labels and F-labels as needed. MPLS enabled 275 DetNet nodes can enhance the reliability of delivery by enabling the 276 replication of packets where multiple copies, possibly over multiple 277 paths, are forwarded through the DetNet domain. They can also 278 eliminate surplus previously replicated copies of DetNet packets. 279 MPLS (DetNet) nodes also include DetNet forwarding sub-layer 280 functions, support for notably explicit routes, and resources 281 allocation to eliminate (or reduce) congestion loss and jitter. 283 DetNet transit nodes reside wholly within a DetNet domain, and also 284 provide DetNet forwarding sub-layer functions in accordance with the 285 performance required by a DetNet flow carried over an LSP. Unlike 286 other DetNet node types, transit nodes provide no service sub-layer 287 processing. 289 4.2. TSN over DetNet MPLS Encapsulation 291 The basic encapsulation approach is to treat a TSN Stream as an app- 292 flow from the DetNet MPLS perspective. The corresponding example 293 shown in Figure 3. 295 /-> +------+ +------+ +------+ TSN ^ ^ 296 | | X | | X | | X |<- Appli : : 297 App-Flow <-+ +------+ +------+ +------+ cation : :(1) 298 for MPLS | |TSN-L2| |TSN-L2| |TSN-L2| : v 299 \-> +---+======+--+======+--+======+-----+ : 300 | d-CW | | d-CW | | d-CW | : 301 DetNet-MPLS +------+ +------+ +------+ :(2) 302 |Labels| |Labels| |Labels| v 303 +---+======+--+======+--+======+-----+ 304 Link/Sub-Network | L2 | | TSN | | UDP | 305 +------+ +------+ +------+ 306 | IP | 307 +------+ 308 | L2 | 309 +------+ 310 (1) TSN Stream 311 (2) DetNet MPLS Flow 313 Figure 3: Example TSN over MPLS Encapsulation Formats 315 In the figure, "Application" indicates the application payload 316 carried by the TSN network. "MPLS App-Flow" indicates that the TSN 317 Stream is the payload from the perspective of the DetNet MPLS data 318 plane defined in [I-D.ietf-detnet-mpls]. A single DetNet MPLS flow 319 can aggregate multiple TSN Streams. 321 5. TSN over MPLS Data Plane Procedures 323 Description of Edge Nodes procedures and functions for TSN over 324 DetNet MPLS scenario follows the concept of [RFC3985] and covers the 325 Edge Nodes components shown on Figure 1. In this section the 326 following procedures of DetNet Edge Nodes are described: 328 o TSN related (Section 5.1) 330 o DetNet Service Proxy (Section 5.2) 332 o DetNet service and forwarding sub-layer (Section 5.3) 334 5.1. Edge Node TSN Procedures 336 The Time-Sensitive Networking (TSN) Task Group of the IEEE 802.1 337 Working Group have defined (and are defining) a number of amendments 338 to IEEE 802.1Q [IEEE8021Q] that provide zero congestion loss and 339 bounded latency in bridged networks. IEEE 802.1CB [IEEE8021CB] 340 defines packet replication and elimination functions for a TSN 341 network. 343 TSN specific functions are executed on the data received by the PE 344 from the CE before presentation to the DetNet PW for transmission 345 across the DetNet domain, or on the data received from a DetNet PW by 346 a PE before it is output on the Attachment Circuit (AC). 348 TSN specific function(s) of Edge Nodes (T-PE) are belonging to the 349 native service processing (NSP) [RFC3985] block. This is similar to 350 other functionalities being defined by standard bodies other than the 351 IETF (for example in case of Ethernet: stripping, overwriting or 352 adding VLAN tags, etc.). Depending on the TSN role of the Edge Node 353 in the end-to-end TSN service selected TSN functions must be 354 supported. 356 Implementations of this document SHALL use management and control 357 information to ensure TSN specific functions of the Edge Node 358 according to the expectations of the connected TSN network. 360 5.2. Edge Node DetNet Service Proxy Procedures 362 The Service Proxy function maps between App-flows and DetNet flows. 363 The DetNet Edge Node TSN function MUST support the TSN Stream 364 identification functions and the related managed objects as defined 365 in IEEE 802.1CB [IEEE8021CB] and IEEE P802.1CBdb [IEEEP8021CBdb] to 366 recognize the App-flow related packets. The Service Proxy presents 367 TSN Streams as an App-flow to a DetNet Flow. 369 Implementations of this document SHALL use management and control 370 information to map a TSN Stream to a DetNet flow. N:1 mapping 371 (aggregating multiple TSN Streams in a single DetNet flow) SHALL be 372 supported. The management or control function that provisions flow 373 mapping SHALL ensure that adequate resources are allocated and 374 configured to provide proper service requirements of the mapped 375 flows. 377 Due to the (intentional) similarities of the DetNet PREOF and TSN 378 FRER functions service protection function interworking is possible 379 between the TSN and the DetNet domains. Such service protection 380 interworking scenarios MAY require to copy sequence number fields 381 from TSN (L2) to PW (MPLS) encapsulation. However, such interworking 382 is out-of-scope in this document and left for further study. 384 A MPLS DetNet flow is configured to carry any number of TSN flows. 385 The DetNet flow specific bandwidth profile SHOULD match the required 386 bandwidth of the App-flow aggregate. 388 5.3. Edge Node DetNet Service and Forwarding Sub-Layer Procedures 390 In the design of [I-D.ietf-detnet-mpls] an MPLS service label (the 391 S-Label), similar to a pseudowire (PW) label [RFC3985], is used to 392 identify both the DetNet flow identity and the payload MPLS payload 393 type. The DetNet sequence number is carried in the DetNet Control 394 word (d-CW) which carries the Data/OAM discriminator as well. In 395 [I-D.ietf-detnet-mpls] two sequence number sizes are supported: a 16 396 bit sequence number and a 28 bit sequence number. 398 PREOF functions and the provided service recovery is available only 399 within the DetNet domain as the DetNet flow-ID and the DetNet 400 sequence number are not valid outside the DetNet network. MPLS 401 (DetNet) Edge node terminates all related information elements 402 encoded in the MPLS labels. 404 The LSP used to forward the DetNet packet may be of any type (MPLS- 405 LDP, MPLS-TE, MPLS-TP [RFC5921], or MPLS-SR 406 [I-D.ietf-spring-segment-routing-mpls]). The LSP (F-Label) label 407 and/or the S-Label may be used to indicate the queue processing as 408 well as the forwarding parameters. 410 For further details see [I-D.ietf-detnet-mpls]. 412 6. Controller Plane (Management and Control) Considerations 414 TSN Stream(s) to DetNet flow mapping related information are required 415 only for the service proxy function of MPLS (DetNet) Edge nodes. 416 From the Data Plane perspective there is no practical difference 417 based on the origin of flow mapping related information (management 418 plane or control plane). 420 MPLS DetNet Edge nodes are member of both the DetNet domain and the 421 connected TSN network. From the TSN network perspective the MPLS 422 (DetNet) Edge node has a "TSN relay node" role, so TSN specific 423 management and control plane functionalities must be implemented. 424 There are many similarities in the management plane techniques used 425 in DetNet and TSN, but that is not the case for the control plane 426 protocols. For example, RSVP-TE and MSRP behaves differently. 427 Therefore management and control plane design is an important aspect 428 of scenarios, where mapping between DetNet and TSN is required. 430 Note that, as the DetNet network is just a portion of the end to end 431 TSN path (i.e., single hop from Ethernet perspective), some 432 parameters (e.g., delay) may differ significantly. Since there is no 433 interworking function the bandwidth of DetNet network is assumed to 434 be set large enough to handle all TSN Flows it will support. At the 435 egress of the Detnet Domain the MPLS headers are stripped and the TSN 436 flow continues on as a normal TSN flow. 438 In order to use a DetNet network to interconnect TSN segments, TSN 439 specific information must be converted to DetNet domain specific 440 ones. TSN Stream ID(s) and stream(s) related parameters/requirements 441 must be converted to a DetNet flow-ID and flow related parameters/ 442 requirements. 444 In some case it may be challenging to determine some egress node 445 related information. For example, it may be not trivial to locate 446 the egress point/interface of a TSN Streams with a multicast 447 destination MAC address. Such scenarios may require interaction 448 between control and management plane functions and between DetNet and 449 TSN domains. 451 Mapping between DetNet flow identifiers and TSN Stream identifiers, 452 if not provided explicitly, can be done by the service proxy function 453 of an MPLS (DetNet) Edge node locally based on information provided 454 for configuration of the TSN Stream identification functions (e.g., 455 Mask-and-Match Stream identification). 457 Triggering the setup/modification of a DetNet flow in the DetNet 458 network is an example where management and/or control plane 459 interactions are required between the DetNet and the TSN network. 461 Configuration of TSN specific functions (e.g., FRER) inside the TSN 462 network is a TSN domain specific decision and may not be visible in 463 the DetNet domain. Service protection interworking scenarios are 464 left for further study. 466 7. Security Considerations 468 Security considerations for DetNet are described in detail in 469 [I-D.ietf-detnet-security]. General security considerations are 470 described in [I-D.ietf-detnet-architecture]. DetNet MPLS data plane 471 specific considerations are summarized in [I-D.ietf-detnet-mpls]. 472 The primary considerations for the data plane is to maintain 473 integrity of data and delivery of the associated DetNet service 474 traversing the DetNet network. Application flows can be protected 475 through whatever means is provided by the underlying technology. For 476 example, encryption may be used, such as that provided by IPSec 477 [RFC4301] for IP flows and/or by an underlying sub-net using MACSec 478 [IEEE802.1AE-2018] for IP over Ethernet (Layer-2) flows. 480 8. IANA Considerations 482 This document makes no IANA requests. 484 9. Acknowledgements 486 The authors wish to thank Norman Finn, Lou Berger, Craig Gunther, 487 Christophe Mangin and Jouni Korhonen for their various contributions 488 to this work. 490 10. References 492 10.1. Normative References 494 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 495 Requirement Levels", BCP 14, RFC 2119, 496 DOI 10.17487/RFC2119, March 1997, 497 . 499 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 500 Label Switching Architecture", RFC 3031, 501 DOI 10.17487/RFC3031, January 2001, 502 . 504 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 505 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 506 May 2017, . 508 10.2. Informative References 510 [I-D.ietf-detnet-architecture] 511 Finn, N., Thubert, P., Varga, B., and J. Farkas, 512 "Deterministic Networking Architecture", draft-ietf- 513 detnet-architecture-13 (work in progress), May 2019. 515 [I-D.ietf-detnet-data-plane-framework] 516 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 517 Bryant, S., and J. Korhonen, "DetNet Data Plane 518 Framework", draft-ietf-detnet-data-plane-framework-02 519 (work in progress), September 2019. 521 [I-D.ietf-detnet-mpls] 522 Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., 523 Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", 524 draft-ietf-detnet-mpls-01 (work in progress), July 2019. 526 [I-D.ietf-detnet-security] 527 Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, 528 J., Austad, H., Stanton, K., and N. Finn, "Deterministic 529 Networking (DetNet) Security Considerations", draft-ietf- 530 detnet-security-05 (work in progress), August 2019. 532 [I-D.ietf-spring-segment-routing-mpls] 533 Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., 534 Litkowski, S., and R. Shakir, "Segment Routing with MPLS 535 data plane", draft-ietf-spring-segment-routing-mpls-22 536 (work in progress), May 2019. 538 [IEEE802.1AE-2018] 539 IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC 540 Security (MACsec)", 2018, 541 . 543 [IEEE8021CB] 544 Finn, N., "Draft Standard for Local and metropolitan area 545 networks - Seamless Redundancy", IEEE P802.1CB 546 /D2.1 P802.1CB, December 2015, 547 . 550 [IEEE8021Q] 551 IEEE 802.1, "Standard for Local and metropolitan area 552 networks--Bridges and Bridged Networks (IEEE Std 802.1Q- 553 2014)", 2014, . 555 [IEEEP8021CBdb] 556 Mangin, C., "Extended Stream identification functions", 557 IEEE P802.1CBdb /D0.2 P802.1CBdb, August 2019, 558 . 561 [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation 562 Edge-to-Edge (PWE3) Architecture", RFC 3985, 563 DOI 10.17487/RFC3985, March 2005, 564 . 566 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 567 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 568 December 2005, . 570 [RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau, 571 L., and L. Berger, "A Framework for MPLS in Transport 572 Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010, 573 . 575 Authors' Addresses 577 Balazs Varga (editor) 578 Ericsson 579 Magyar Tudosok krt. 11. 580 Budapest 1117 581 Hungary 583 Email: balazs.a.varga@ericsson.com 584 Janos Farkas 585 Ericsson 586 Magyar Tudosok krt. 11. 587 Budapest 1117 588 Hungary 590 Email: janos.farkas@ericsson.com 592 Andrew G. Malis 593 Independent 595 Email: agmalis@gmail.com 597 Stewart Bryant 598 Futurewei Technologies 600 Email: stewart.bryant@gmail.com 602 Don Fedyk 603 LabN Consulting, L.L.C. 605 Email: dfedyk@labn.net