idnits 2.17.1 draft-xiong-idr-detnet-flow-mapping-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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 2022) is 770 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: 'IEEE8021CB' is mentioned on line 205, but not defined == Missing Reference: 'IEEEP8021CBdb' is mentioned on line 205, but not defined == Missing Reference: 'Network' is mentioned on line 170, but not defined == Outdated reference: A later version (-02) exists of draft-ietf-idr-bgp-flowspec-label-01 == Outdated reference: A later version (-23) exists of draft-ietf-idr-flowspec-l2vpn-18 == Outdated reference: A later version (-02) exists of draft-ietf-idr-flowspec-mpls-match-01 ** Downref: Normative reference to an Informational RFC: RFC 8938 ** Downref: Normative reference to an Informational RFC: RFC 9023 ** Downref: Normative reference to an Informational RFC: RFC 9037 Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Q. Xiong 3 Internet-Draft H. Wu 4 Intended status: Standards Track ZTE Corporation 5 Expires: 7 September 2022 J. Zhao 6 CAICT 7 March 2022 9 BGP Flow Specification for DetNet and TSN Flow Mapping 10 draft-xiong-idr-detnet-flow-mapping-02 12 Abstract 14 This document proposes extensions to BGP Flow Specification for the 15 flow mapping of Deterministic Networking (DetNet) when interconnected 16 with IEEE 802.1 Time-Sensitive Networking (TSN). The BGP flowspec is 17 used for the filtering of the packets that match the DetNet newtworks 18 and the mapping between TSN streams and DetNet flows in the control 19 plane. 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 2 September 2022. 38 Copyright Notice 40 Copyright (c) 2022 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 (https://trustee.ietf.org/ 45 license-info) in effect on the date of publication of this document. 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. Code Components 48 extracted from this document must include Revised BSD License text as 49 described in Section 4.e of the Trust Legal Provisions and are 50 provided without warranty as described in the Revised BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions used in this document . . . . . . . . . . . . . . 3 56 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 57 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 58 3. The Requirements for DetNet Control Plane . . . . . . . . . . 3 59 3.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 3 60 3.2. Aggregation during DetNet Flow to TSN Stream Mapping . . 5 61 4. BGP Extensions for Flow Specification Encoding . . . . . . . 5 62 4.1. Filtering Rules for TSN Streams . . . . . . . . . . . . . 5 63 4.2. Traffic Action for TSN Streams . . . . . . . . . . . . . 6 64 4.3. Filtering Rules for DetNet Flows . . . . . . . . . . . . 7 65 4.4. Traffic Action for DetNet Flows . . . . . . . . . . . . . 8 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 67 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 68 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 69 8. Normative References . . . . . . . . . . . . . . . . . . . . 10 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 72 1. Introduction 74 [RFC8655] specifies the architecture of Deterministic Networking 75 (DetNet), which provide a capability for the delivery of data flows 76 with extremely low packet loss rates and bounded end-to-end delivery 77 latency. DetNet-enabled end systems and DetNet nodes can be 78 interconnected by sub-networks, i.e., Layer 2 technologies such as 79 IEEE 802.1 Time-Sensitive Networking (TSN). 81 As defined in [RFC8655], the DetNet IP and MPLS flows can be carried 82 over TSN sub-networks. DetNet needs to be mapped to the sub-networks 83 technology used to interconnect DetNet nodes. For example, a TSN 84 node may be used to interconnect DetNet-aware nodes, and these DetNet 85 nodes can map DetNet flows to TSN streams. When the Detnet provide 86 the deterministic service for the TSN end system, a DetNet edge node 87 may be used to interconnect the TSN end system, and the DetNet nodes 88 can map the TSN streams to DetNet flows. 90 As described in [RFC8938], one of the primary requirements of the 91 DetNet Controller Plane is restricting flows to IEEE 802.1 TSN and 92 the requirement could use the centralized network management 93 provisioning mechanisms such as BGP protocol. As defined in 94 [RFC8955], the Flow Specifications for BGP is an n-tuple consisting 95 of several matching criteria which is comprised of traffic filtering 96 rules and is associated with actions that can be applied to the 97 traffic flows. The DetNet edge nodes can provide the capability to 98 process the traffic including classifing, shaping, rate limiting, 99 filtering, and redirecting packets based on the policies configured 100 by the BGP Flow Specification. 102 BGP flow specification version 1 (FSv1) has been defined in [RFC8955] 103 and version 2 of the BGP flow specification (FSv2) protocol has been 104 proposed in [I-D.hares-idr-flowspec-v2]. This document proposes 105 extensions to BGP FSv2 for the interconnection of DetNet and TSN. 106 The BGP flowspec is used for the filtering of the packets that match 107 the DetNet newtworks and the mapping between TSN streams and DetNet 108 flows in the control plane. 110 2. Conventions used in this document 112 2.1. Terminology 114 The terminology is defined as [RFC8655], [RFC8938], [RFC8955] and 115 [I-D.hares-idr-flowspec-v2]. 117 2.2. Requirements Language 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 121 "OPTIONAL" in this document are to be interpreted as described in BCP 122 14 [RFC2119] [RFC8174] when, and only when, they appear in all 123 capitals, as shown here. 125 3. The Requirements for DetNet Control Plane 127 3.1. Functions for DetNet Flow to TSN Stream Mapping 129 As described in [RFC9024], TSN networks can be interconnected over a 130 DetNet MPLS Network. And as discussed in [RFC9023] and [RFC9037], 131 DetNet IP or MPLS networks can be operating over a TSN sub-network. 132 The mapping between TSN Streams and DetNet flows is required for the 133 service proxy function at DetNet Edge nodes. And the mapping table 134 can be configured and maintained in the control plane. When a DetNet 135 Edge Node receives a packet, it MUST identify and check whether such 136 flow is present in its mapping table and decide to drop (when not 137 match) or to forward the packet (when match) to the associated 138 service. 140 As Figure 1 shows, it is required to configue the identification 141 information when mapping received TSN Streams to the DetNet flows at 142 Edge Node-1. Mechanisms and Parameters of TSN stream identification 143 (e.g.,Mask-and-Match Stream identification) defined in [IEEE8021CB] 144 and [IEEEP8021CBdb] can be used for service proxy function. After 145 the identification of the TSN stream, it need to map the packet to 146 the DetNet flow information such as S-Label, d-CW when in DetNet MPLS 147 data plane and handle the packet as defined in [RFC8964]. 149 When the DetNet Edge Node-2 receives a DetNet flow, it MUST identify 150 the DetNet flow-ID information such as IP 6-tuple in DetNet IP data 151 plane or S-Label and d-CW information in DetNet MPLS data plane. 152 Then the Service proxy function need to map the DetNet flow-ID and 153 flow related parameters to the associated TSN Stream IDs and streams 154 related parameters. 156 TSN Edge Transit Edge TSN 157 End System Node-1 Node Node-2 End System 158 +----------+ +----------+ 159 | TSN | <---------End to End TSN Service----------> | TSN | 160 | Applic. | | Applic. | 161 +----------+ +.........+ +.........+ +----------+ 162 | | |Service-Proxy Service-Proxy| | | 163 | TSN | | +.+---+<-- DetNet flow -->+---+.| | | TSN | 164 | | |TSN| |Svc| |Svc| |TSN| | | 165 +----------+ +---+ +---+ +----------+ +---+ +---+ +----------+ 166 | L2 | | L2| |Fwd| |Forwarding| |Fwd| |L2 | | L2 | 167 +------.---+ +-.-+ +-.-+ +---.----.-+ +--.+ +-.-+ +---.------+ 168 : Link : / ,-----. \ : Link : / ,-----. \ 169 +........+ +-[ Sub ]-+ +........+ +-[ TSN ]-+ 170 [Network] [Network] 171 `-----' `-----' 172 Flow Mapping: 173 |TSN : DetNet|<--------- DetNet ---------->|DetNet : TSN| 175 Figure 1: Figure 1: Flow Mapping in TSN over DetNet Network 177 3.2. Aggregation during DetNet Flow to TSN Stream Mapping 179 As described in [RFC8938], the DetNet data plane allows for the 180 aggregation of DetNet flows, which should also be accomplished in the 181 control plane. IP, MPLS and TSN aggregation has both data plane and 182 controller Plane aspects. Bandwidth reservations, resource 183 assignment, path computation, delay, delay variation and aggregate 184 number should be taken into considerations in the controller plane. 185 Moreover, as defined in [RFC9023] and [RFC9037], 1:1 and N:1 mapping 186 (aggregating multiple TSN Streams in a single DetNet flow) MUST be 187 supported. 189 4. BGP Extensions for Flow Specification Encoding 191 As defined in [RFC8955], the nodes that applied a Flow Specification 192 can fillter the received pakects according to the matching criteria 193 and can forward the flows based on the associated actions. This 194 document proposes extensions to BGP Flow Specification for the 195 mapping of DetNet flows and TSN streams by using the traffic 196 filtering rules to identify the packet and using the associated 197 action to map the packet to the related service. 199 4.1. Filtering Rules for TSN Streams 201 As IEEE Std 802.1Q defined, a Stream ID is a 64-bit field that 202 uniquely identifies a stream and can be generated by the system 203 offering the stream, or possibly a device controlling that system. 204 But it is not carried in the header of the TSN Stream. As defined in 205 [IEEE8021CB] and [IEEEP8021CBdb], five specific Stream identification 206 functions are described: Null Stream identification, Source MAC and 207 VLAN Stream identification, Active Destination MAC and VLAN Stream 208 identification, and IP Stream identification, and Mask-and-match 209 Stream identification. It needs to examines the header of the 210 streams such as destination_address, vlan_identifier, IP source 211 address, IP destination address, DSCP, IP next protocol, source port, 212 destination port and mac_service_data_unit. 214 As defined in [I-D.ietf-idr-flowspec-l2vpn], the Ethernet Layer 2 215 (L2) related fields has been covered by the L2 traffic filtering 216 rules except the mac_service_data_unit in Mask-and-Match Stream 217 identification. A mac_service_data_unit mask is defined to identify 218 communication flows supported by various higher-layer protocols. L2 219 Traffic Rules and L2 header TLV in BGP FSv2 of has been defined in 220 [I-D.hares-idr-flowspec-v2] section 3.4. This document proposes a 221 new L2 SubTLV for TSN Streams in L2 Flow Specification Component 222 shown in Figure 2. 224 +----------------------------------+ 225 | SubTLV type = TBD1 (1 octet) | 226 +----------------------------------+ 227 | length (1 octet) | 228 + ---------------------------------+ 229 | Mac Service Data Unit (6 octets)| 230 +----------------------------------+ 232 Figure 2: Figure 2: TSN SubTLV 234 SubTLV type = TBD1: Mac Service Data Unit 236 Encoding: 238 Defines a list of {operation, value} pairs used to match 6-octet Mac 239 Service Data Unit field. Values are encoded as 6-octet quantities. 240 op is encoded as specified in Section 4.2.1.1 of [RFC8955]. 242 4.2. Traffic Action for TSN Streams 244 The action for an TSN traffic filtering flowspec is to accept the TSN 245 streams that matches that particular rule and map the streams to the 246 DetNet flows. The action for L3 traffic with extended communities 247 types per [RFC8955] and [RFC8956] such as traffic-rate, traffic- 248 marking, traffic-action, and redirect can be used for TSN to DetNet 249 IP flow mapping. The Wide Community has been proposed for FSv2 250 actions in [I-D.hares-idr-flowspec-v2] section 3.2. 252 The DetNet flow is identified by a S-Label and the DetNet Header 253 consists of d-CW and F-Labels. The MPLS label related action for an 254 TSN stream mapping to a DetNet MPLS network can use the Label-action 255 defined in [I-D.ietf-idr-bgp-flowspec-label]. And the action for the 256 sequence in d-CW field, this document proposes a new Action SubTLV in 257 BGP FSv2 Wide Community for TSN Streams as following shown. 259 +======+=================+==========+ 260 | type | Wide Community | encoding | 261 +======+=================+==========+ 262 | TBD2 | Sequence Action | bitmask | 263 +------+-----------------+----------+ 265 Table 1 267 The The Sequence Action SubTLV is shown in Figure 3. 269 0 15 270 +-----------------------------------------------+ 271 | SubTLV type = TBD2 (2 octet) | 272 +-----------------------------------------------+ 273 | length (2 octet) | 274 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 275 | Type | Sequence Number | 276 +--+--+--+--+ + 277 | ~ | 278 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 280 Figure 3: Figure 3: Sequence Action 282 Type: 4 bits, indicates the length type of the sequence number: 284 0: 0 bits 286 1: 16 bits 288 2: 28 bits 290 Sequence Number: 28 bits, an unsigned value implementing the DetNet 291 sequence number. 293 4.3. Filtering Rules for DetNet Flows 295 The L3 traffic filtering rules defined in [RFC8955] and [RFC8956] can 296 be used for DetNet IP flow. 298 As defined in RFC8964, the MPLS-based DetNet data plane encapsulation 299 consists of d-CW, S-Label and F-Labels. The MPLS label filtering 300 rules have been defined in [I-D.ietf-idr-flowspec-mpls-match]. IP 301 header TLV in BGP FSv2 of has been defined in 302 [I-D.hares-idr-flowspec-v2] section 3.1. 304 This document proposes a new IP header SubTLV for DetNet MPLS flows 305 shown in Figure 4. 307 +----------------------------------+ 308 | SubTLV type = TBD3 (1 octet) | 309 +----------------------------------+ 310 | length (1 octet) | 311 + ---------------------------------+ 312 | d-CW (4 octets) | 313 +----------------------------------+ 315 Figure 4: Figure 4: DetNet SubTLV 317 MPLS Match Type TBD3: d-CW , indicates Sequence in Label stack. 319 Encoding: 321 Defines a list of {operation, value} pairs used to match Sequence. 322 Values are encoded as 4-octet quantities, where the four most 323 significant bits are set to zero and ignored for matching and the 28 324 least significant bits contain the sequence value. op is encoded as 325 specified in Section 4.2.1.1 of [RFC8955]. 327 4.4. Traffic Action for DetNet Flows 329 The extended action for an DetNet traffic filtering flowspec is to 330 accept the DetNet flows that matches that particular rule and map the 331 flows to the TSN streams. This document proposes a new Action SubTLV 332 in BGP FSv2 Wide Community for DetNet flows as the following shown. 334 +======+================+==========+ 335 | type | Wide Community | encoding | 336 +======+================+==========+ 337 | TBD4 | TSN Action | bitmask | 338 +------+----------------+----------+ 340 Table 2 342 The TSN Action SubTLV is shown in Figure 3. 344 0 15 345 +-----------------------------------------------+ 346 | SubTLV type = TBD4 (2 octet) | 347 +-----------------------------------------------+ 348 | length (2 octet) | 349 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 350 | Type | Resv | 351 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 352 | TSN-Profile | 353 | ~ | 354 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 356 Figure 5: Figure 5: TSN Action 358 Type: 1-octet, indicates the type of TSN profiles. The value of the 359 types is TBD: 361 Resv: 1-octet, reserved for future use. MUST be sent as zero and 362 ignored on receipt. 364 TSN-profile: 4-octet, can be converted to the TSN Stream ID and 365 stream related parameters and requirements as the following shown. 367 stream_handle: identifying the Stream to which the packet belongs in 368 TSN networks. 370 sequence_number: identifying the order in which the packet was 371 transmitted relative to other packets in the same Compound Stream in 372 TSN networks. 374 traffic_scheduling: identifying the traffic scheduling mechanisms 375 including traffic policy, queuing and forwarding methods in TSN 376 networks. 378 5. Security Considerations 380 TBA 382 6. Acknowledgements 384 TBA 386 7. IANA Considerations 388 TBA 390 8. Normative References 392 [I-D.hares-idr-flowspec-v2] 393 Hares, S., Eastlake, D., Yadlapalli, C., and S. Maduschke, 394 "BGP Flow Specification Version 2", Work in Progress, 395 Internet-Draft, draft-hares-idr-flowspec-v2-05, 4 February 396 2022, . 399 [I-D.ietf-idr-bgp-flowspec-label] 400 Liang, Q., Hares, S., You, J., Raszuk, R., and D. Ma, 401 "Carrying Label Information for BGP FlowSpec", Work in 402 Progress, Internet-Draft, draft-ietf-idr-bgp-flowspec- 403 label-01, 6 December 2016, 404 . 407 [I-D.ietf-idr-flowspec-l2vpn] 408 Hao, W., Eastlake, D. E., Litkowski, S., and S. Zhuang, 409 "BGP Dissemination of L2 Flow Specification Rules", Work 410 in Progress, Internet-Draft, draft-ietf-idr-flowspec- 411 l2vpn-18, 24 October 2021, 412 . 415 [I-D.ietf-idr-flowspec-mpls-match] 416 Yong, L., Hares, S., Liang, Q., and J. You, "BGP Flow 417 Specification Filter for MPLS Label", Work in Progress, 418 Internet-Draft, draft-ietf-idr-flowspec-mpls-match-01, 6 419 December 2016, . 422 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 423 Requirement Levels", BCP 14, RFC 2119, 424 DOI 10.17487/RFC2119, March 1997, 425 . 427 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 428 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 429 May 2017, . 431 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 432 "Deterministic Networking Architecture", RFC 8655, 433 DOI 10.17487/RFC8655, October 2019, 434 . 436 [RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S. 437 Bryant, "Deterministic Networking (DetNet) Data Plane 438 Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020, 439 . 441 [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. 442 Bacher, "Dissemination of Flow Specification Rules", 443 RFC 8955, DOI 10.17487/RFC8955, December 2020, 444 . 446 [RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed., 447 "Dissemination of Flow Specification Rules for IPv6", 448 RFC 8956, DOI 10.17487/RFC8956, December 2020, 449 . 451 [RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant, 452 S., and J. Korhonen, "Deterministic Networking (DetNet) 453 Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January 454 2021, . 456 [RFC9023] Varga, B., Ed., Farkas, J., Malis, A., and S. Bryant, 457 "Deterministic Networking (DetNet) Data Plane: IP over 458 IEEE 802.1 Time-Sensitive Networking (TSN)", RFC 9023, 459 DOI 10.17487/RFC9023, June 2021, 460 . 462 [RFC9024] Varga, B., Ed., Farkas, J., Malis, A., Bryant, S., and D. 463 Fedyk, "Deterministic Networking (DetNet) Data Plane: IEEE 464 802.1 Time-Sensitive Networking over MPLS", RFC 9024, 465 DOI 10.17487/RFC9024, June 2021, 466 . 468 [RFC9037] Varga, B., Ed., Farkas, J., Malis, A., and S. Bryant, 469 "Deterministic Networking (DetNet) Data Plane: MPLS over 470 IEEE 802.1 Time-Sensitive Networking (TSN)", RFC 9037, 471 DOI 10.17487/RFC9037, June 2021, 472 . 474 Authors' Addresses 476 Quan Xiong 477 ZTE Corporation 478 No.6 Huashi Park Rd 479 Wuhan 480 Hubei, 430223 481 China 482 Email: xiong.quan@zte.com.cn 483 Haisheng Wu 484 ZTE Corporation 485 Nanjing 486 Jiangsu, 487 China 488 Email: wu.haisheng@zte.com.cn 490 Junfeng Zhao 491 CAICT 492 China 493 Email: zhaojunfeng@caict.ac.cn