idnits 2.17.1 draft-xiong-idr-detnet-flow-mapping-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 (May 27, 2021) is 1064 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 186, but not defined == Missing Reference: 'IEEEP8021CBdb' is mentioned on line 186, but not defined == Missing Reference: 'Network' is mentioned on line 171, but not defined ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-ip-over-tsn (ref. 'I-D.ietf-detnet-ip-over-tsn') ** Downref: Normative reference to an Informational draft: draft-ietf-detnet-mpls-over-tsn (ref. 'I-D.ietf-detnet-mpls-over-tsn') == Outdated reference: A later version (-02) exists of draft-ietf-idr-bgp-flowspec-label-01 == Outdated reference: A later version (-23) exists of draft-ietf-idr-flowspec-l2vpn-16 == Outdated reference: A later version (-02) exists of draft-ietf-idr-flowspec-mpls-match-01 ** Downref: Normative reference to an Informational RFC: RFC 8938 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: November 28, 2021 May 27, 2021 7 BGP Flow Specification for DetNet Flow Mapping 8 draft-xiong-idr-detnet-flow-mapping-00 10 Abstract 12 This document proposes extensions to BGP Flow Specification for the 13 flow mapping of Deterministic Networking (DetNet) when interconnected 14 with IEEE 802.1 Time-Sensitive Networking (TSN). The BGP flowspec is 15 used for the filtering of the packets that match the DetNet newtworks 16 and the mapping between TSN streams and DetNet flows in the control 17 plane. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on November 28, 2021. 36 Copyright Notice 38 Copyright (c) 2021 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions used in this document . . . . . . . . . . . . . . 3 55 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 57 3. The Flow Mapping of DetNet . . . . . . . . . . . . . . . . . 3 58 4. BGP Extensions for Flow Specification Encoding . . . . . . . 4 59 4.1. Filtering Rules for TSN Streams . . . . . . . . . . . . . 4 60 4.2. Traffic Action for TSN Streams . . . . . . . . . . . . . 5 61 4.3. Filtering Rules for DetNet Flows . . . . . . . . . . . . 6 62 4.4. Traffic Action for DetNet Flows . . . . . . . . . . . . . 7 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 65 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 66 8. Normative References . . . . . . . . . . . . . . . . . . . . 8 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 69 1. Introduction 71 [RFC8655] specifies the architecture of Deterministic Networking 72 (DetNet), which provide a capability for the delivery of data flows 73 with extremely low packet loss rates and bounded end-to-end delivery 74 latency. DetNet-enabled end systems and DetNet nodes can be 75 interconnected by sub-networks, i.e., Layer 2 technologies such as 76 IEEE 802.1 Time-Sensitive Networking (TSN). 78 As defined in [RFC8655], the DetNet IP and MPLS flows can be carried 79 over TSN sub-networks. DetNet needs to be mapped to the sub-networks 80 technology used to interconnect DetNet nodes. For example, a TSN 81 node may be used to interconnect DetNet-aware nodes, and these DetNet 82 nodes can map DetNet flows to TSN streams. When the Detnet provide 83 the deterministic service for the TSN end system, a DetNet edge node 84 may be used to interconnect the TSN end system, and the DetNet nodes 85 can map the TSN streams to DetNet flows. 87 As described in [RFC8938], one of the primary requirements of the 88 DetNet Controller Plane is restricting flows to IEEE 802.1 TSN and 89 the requirement could use the centralized network management 90 provisioning mechanisms such as BGP protocol. As defined in 91 [RFC8955], the Flow Specifications for BGP is an n-tuple consisting 92 of several matching criteria which is comprised of traffic filtering 93 rules and is associated with actions that can be applied to the 94 traffic flows. The DetNet edge nodes can provide the capability to 95 process the traffic including classifing, shaping, rate limiting, 96 filtering, and redirecting packets based on the policies configured 97 by the BGP Flow Specification. 99 This document proposes extensions to BGP Flow Specification for the 100 interconnection of DetNet and TSN. The BGP flowspec is used for the 101 filtering of the packets that match the DetNet newtworks and the 102 mapping between TSN streams and DetNet flows in the control plane. 104 2. Conventions used in this document 106 2.1. Terminology 108 The terminology is defined as [RFC8655], [RFC8938], and [RFC8955]. 110 2.2. Requirements Language 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 "OPTIONAL" in this document are to be interpreted as described in BCP 115 14 [RFC2119] [RFC8174] when, and only when, they appear in all 116 capitals, as shown here. 118 3. The Flow Mapping of DetNet 120 As described in [I-D.ietf-detnet-tsn-vpn-over-mpls], TSN networks can 121 be interconnected over a DetNet MPLS Network. And as discussed in 122 [I-D.ietf-detnet-ip-over-tsn] and [I-D.ietf-detnet-mpls-over-tsn], 123 DetNet IP or MPLS networks can be operating over a TSN sub-network. 124 The mapping between TSN Streams and DetNet flows is required for the 125 service proxy function at DetNet Edge nodes. And the mapping table 126 can be configured and maintained in the control plane. When a DetNet 127 Edge Node receives a packet, it MUST identify and check whether such 128 flow is present in its mapping table and decide to drop (when not 129 match) or to forward the packet (when match) to the associated 130 service. 1:1 and N:1 mapping (aggregating multiple TSN Streams in a 131 single DetNet flow) MUST be supported. 133 As Figure 1 shows, it is required to configue the identification 134 information when mapping received TSN Streams to the DetNet flows at 135 Edge Node-1. Mechanisms and Parameters of TSN stream identification 136 (e.g.,Mask-and-Match Stream identification) defined in [IEEE8021CB] 137 and [IEEEP8021CBdb] can be used for service proxy function. After 138 the identification of the TSN stream, it need to map the packet to 139 the DetNet flow information such as S-Label, d-CW when in DetNet MPLS 140 data plane and handle the packet as defined in [RFC8964]. 142 When the DetNet Edge Node-2 receives a DetNet flow, it MUST identify 143 the DetNet flow-ID information such as IP 6-tuple in DetNet IP data 144 plane or S-Label and d-CW information in DetNet MPLS data plane. 145 Then the Service proxy function need to map the DetNet flow-ID and 146 flow related parameters to the associated TSN Stream IDs and streams 147 related parameters. 149 As defined in [RFC8955], the nodes that applied a Flow Specification 150 can fillter the received pakects according to the matching criteria 151 and can forward the flows based on the associated actions. This 152 document proposes extensions to BGP Flow Specification for the 153 mapping of DetNet flows and TSN streams by using the traffic 154 filtering rules to identify the packet and using the associated 155 action to map the packet to the related service. 157 TSN Edge Transit Edge TSN 158 End System Node-1 Node Node-2 End System 159 +----------+ +----------+ 160 | TSN | <---------End to End TSN Service----------> | TSN | 161 | Applic. | | Applic. | 162 +----------+ +.........+ +.........+ +----------+ 163 | | |Service-Proxy Service-Proxy| | | 164 | TSN | | +.+---+<-- DetNet flow -->+---+.| | | TSN | 165 | | |TSN| |Svc| |Svc| |TSN| | | 166 +----------+ +---+ +---+ +----------+ +---+ +---+ +----------+ 167 | L2 | | L2| |Fwd| |Forwarding| |Fwd| |L2 | | L2 | 168 +------.---+ +-.-+ +-.-+ +---.----.-+ +--.+ +-.-+ +---.------+ 169 : Link : / ,-----. \ : Link : / ,-----. \ 170 +........+ +-[ Sub ]-+ +........+ +-[ TSN ]-+ 171 [Network] [Network] 172 `-----' `-----' 173 Flow Mapping: 174 |TSN N:1 DetNet|<--------- DetNet ---------->|DetNet 1:N TSN| 176 Figure 1: Flow Mapping in TSN over DetNet Network 178 4. BGP Extensions for Flow Specification Encoding 180 4.1. Filtering Rules for TSN Streams 182 As IEEE Std 802.1Q defined, a Stream ID is a 64-bit field that 183 uniquely identifies a stream and can be generated by the system 184 offering the stream, or possibly a device controlling that system. 185 But it is not carried in the header of the TSN Stream. As defined in 186 [IEEE8021CB] and [IEEEP8021CBdb], five specific Stream identification 187 functions are described: Null Stream identification, Source MAC and 188 VLAN Stream identification, Active Destination MAC and VLAN Stream 189 identification, and IP Stream identification, and Mask-and-match 190 Stream identification. It needs to examines the header of the 191 streams such as destination_address, vlan_identifier, IP source 192 address, IP destination address, DSCP, IP next protocol, source port, 193 destination port and mac_service_data_unit. 195 As defined in [I-D.ietf-idr-flowspec-l2vpn], the Ethernet Layer 2 196 (L2) related fields has been covered by the L2 traffic filtering 197 rules except the mac_service_data_unit in Mask-and-Match Stream 198 identification. A mac_service_data_unit mask is defined to identify 199 communication flows supported by various higher-layer protocols. 200 This document proposes a new type in L2 components flowspec Type for 201 TSN Streams. 203 Type TBD1 - Mac Service Data Unit 205 Encoding: 207 Defines a list of {operation, value} pairs used to match 6-octet Mac 208 Service Data Unit field. Values are encoded as 6-octet quantities. 209 op is encoded as specified in Section 4.2.1.1 of [RFC8955]. 211 4.2. Traffic Action for TSN Streams 213 The action for an TSN traffic filtering flowspec is to accept the TSN 214 streams that matches that particular rule and map the streams to the 215 DetNet flows. The action for L3 traffic with extended communities 216 types per [RFC8955] and [RFC8956] such as traffic-rate, traffic- 217 marking, traffic-action, and redirect can be used for TSN to DetNet 218 IP flow mapping. 220 The DetNet flow is identified by a S-Label and the DetNet Header 221 consists of d-CW and F-Labels. The MPLS label related action for an 222 TSN stream mapping to a DetNet MPLS network can use the Label-action 223 defined in [I-D.ietf-idr-bgp-flowspec-label]. And the action for the 224 sequence in d-CW field, this document specifies the following BGP 225 extended communitiy for TSN Streams as following shown. 227 +--------+----------------------+------------+ 228 | type | extended community | encoding | 229 +--------+----------------------+------------+ 230 | TBD2 | Sequence-action | bitmask | 231 +--------+----------------------+------------+ 233 Table 1 235 The The Sequence-action extended community is shown as the Figure 2. 237 0 15 238 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 239 |Type | Resv | 240 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 241 | Resv | Sequence Number | 242 +--+--+--+--+ + 243 | ~ | 244 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 246 Figure 2: Sequence-action 248 Type: 2 bits, indicates the length of the sequence number: 250 0: 0 bits 252 1: 16 bits 254 2: 28 bits 256 Resv: 18 bits, reserved for future use. MUST be sent as zero and 257 ignored on receipt. 259 Sequence Number: 28 bits, an unsigned value implementing the DetNet 260 sequence number. 262 4.3. Filtering Rules for DetNet Flows 264 The L3 traffic filtering rules defined in [RFC8955] and [RFC8956] can 265 be used for DetNet IP flow. 267 As defined in RFC8964, the MPLS-based DetNet data plane encapsulation 268 consists of d-CW, S-Label and F-Labels. The MPLS label filtering 269 rules have been defined in [I-D.ietf-idr-flowspec-mpls-match]. 271 This document proposes a new community type in L3 components flowspec 272 Type for DetNet MPLS flows. 274 Type TBD3 - d-CW 276 Encoding: 278 Defines a list of {operation, value} pairs used to match Sequence. 279 Values are encoded as 4-octet quantities, where the four most 280 significant bits are set to zero and ignored for matching and the 28 281 least significant bits contain the sequence value. op is encoded as 282 specified in Section 4.2.1.1 of [RFC8955]. 284 4.4. Traffic Action for DetNet Flows 286 The extended action for an DetNet traffic filtering flowspec is to 287 accept the DetNet flows that matches that particular rule and map the 288 flows to the TSN streams. This document specifies the following BGP 289 extended communitiy as the following shown. 291 +--------+----------------------+------------+ 292 | type | extended community | encoding | 293 +--------+----------------------+------------+ 294 | TBD4 | TSN-action | bitmask | 295 +--------+----------------------+------------+ 297 Table 2 299 The The TSN-action extended community is shown as the Figure 3. 301 0 15 302 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 303 | Type | Resv | 304 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 305 | TSN-Profile | 306 | ~ | 307 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 309 Figure 3: TSN-action 311 Type: 1-octet, indicates the type of TSN profiles. The value of the 312 types is TBD: 314 Resv: 1-octet, reserved for future use. MUST be sent as zero and 315 ignored on receipt. 317 TSN-profile: 4-octet, can be converted to the TSN Stream ID and 318 stream related parameters and requirements as the following shown. 320 stream_handle: identifying the Stream to which the packet belongs in 321 TSN networks. 323 sequence_number: identifying the order in which the packet was 324 transmitted relative to other packets in the same Compound Stream in 325 TSN networks. 327 traffic_scheduling: identifying the traffic scheduling mechanisms 328 including traffic policy, queuing and forwarding methods in TSN 329 networks. 331 5. Security Considerations 333 TBA 335 6. Acknowledgements 337 TBA 339 7. IANA Considerations 341 TBA 343 8. Normative References 345 [I-D.ietf-detnet-ip-over-tsn] 346 Varga, B., Farkas, J., Malis, A. G., and S. Bryant, 347 "DetNet Data Plane: IP over IEEE 802.1 Time Sensitive 348 Networking (TSN)", draft-ietf-detnet-ip-over-tsn-07 (work 349 in progress), February 2021. 351 [I-D.ietf-detnet-mpls-over-tsn] 352 Varga, B., Farkas, J., Malis, A. G., and S. Bryant, 353 "DetNet Data Plane: MPLS over IEEE 802.1 Time-Sensitive 354 Networking (TSN)", draft-ietf-detnet-mpls-over-tsn-07 355 (work in progress), February 2021. 357 [I-D.ietf-detnet-tsn-vpn-over-mpls] 358 Varga, B., Farkas, J., Malis, A. G., Bryant, S., and D. 359 Fedyk, "DetNet Data Plane: IEEE 802.1 Time Sensitive 360 Networking over MPLS", draft-ietf-detnet-tsn-vpn-over- 361 mpls-07 (work in progress), February 2021. 363 [I-D.ietf-idr-bgp-flowspec-label] 364 Liang, Q., Hares, S., You, J., Raszuk, R., and D. Ma, 365 "Carrying Label Information for BGP FlowSpec", draft-ietf- 366 idr-bgp-flowspec-label-01 (work in progress), December 367 2016. 369 [I-D.ietf-idr-flowspec-l2vpn] 370 Hao, W., Eastlake, D. E., Litkowski, S., and S. Zhuang, 371 "BGP Dissemination of L2 Flow Specification Rules", draft- 372 ietf-idr-flowspec-l2vpn-16 (work in progress), November 373 2020. 375 [I-D.ietf-idr-flowspec-mpls-match] 376 Yong, L., Hares, S., Liang, Q., and J. You, "BGP Flow 377 Specification Filter for MPLS Label", draft-ietf-idr- 378 flowspec-mpls-match-01 (work in progress), December 2016. 380 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 381 Requirement Levels", BCP 14, RFC 2119, 382 DOI 10.17487/RFC2119, March 1997, 383 . 385 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 386 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 387 May 2017, . 389 [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, 390 "Deterministic Networking Architecture", RFC 8655, 391 DOI 10.17487/RFC8655, October 2019, 392 . 394 [RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S. 395 Bryant, "Deterministic Networking (DetNet) Data Plane 396 Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020, 397 . 399 [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. 400 Bacher, "Dissemination of Flow Specification Rules", 401 RFC 8955, DOI 10.17487/RFC8955, December 2020, 402 . 404 [RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed., 405 "Dissemination of Flow Specification Rules for IPv6", 406 RFC 8956, DOI 10.17487/RFC8956, December 2020, 407 . 409 [RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant, 410 S., and J. Korhonen, "Deterministic Networking (DetNet) 411 Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January 412 2021, . 414 Authors' Addresses 416 Quan Xiong 417 ZTE Corporation 418 No.6 Huashi Park Rd 419 Wuhan, Hubei 430223 420 China 422 Email: xiong.quan@zte.com.cn 423 Haisheng Wu 424 ZTE Corporation 425 Nanjing, Jiangsu 426 China 428 Email: wu.haisheng@zte.com.cn