idnits 2.17.00 (12 Aug 2021) /tmp/idnits62213/draft-ietf-idr-flowspec-srv6-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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (April 8, 2022) is 36 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) -- Looks like a reference, but probably isn't: '0' on line 130 -- Looks like a reference, but probably isn't: '1' on line 132 == Unused Reference: 'RFC7153' is defined on line 340, but no explicit reference was found in the text == Outdated reference: draft-ietf-6man-segment-routing-header has been published as RFC 8754 == Outdated reference: A later version (-19) exists of draft-ietf-idr-flowspec-l2vpn-18 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Li 3 Internet-Draft L. Li 4 Intended status: Standards Track Huawei 5 Expires: October 10, 2022 H. Chen 6 Futurewei 7 C. Loibl 8 Next Layer Communications 9 G. Mishra 10 Verizon Inc. 11 Y. Fan 12 Casa Systems 13 Y. Zhu 14 China Telecom 15 L. Liu 16 Fujitsu 17 X. Liu 18 Volta Networks 19 April 8, 2022 21 BGP Flow Specification for SRv6 22 draft-ietf-idr-flowspec-srv6-01 24 Abstract 26 This document proposes extensions to BGP Flow Specification for SRv6 27 for filtering packets with a SRv6 SID that matches a sequence of 28 conditions. 30 Requirements Language 32 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 33 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 34 document are to be interpreted as described in BCP 14 35 [RFC2119][RFC8174] when, and only when, they appear in all capitals, 36 as shown here. 38 Status of This Memo 40 This Internet-Draft is submitted in full conformance with the 41 provisions of BCP 78 and BCP 79. 43 Internet-Drafts are working documents of the Internet Engineering 44 Task Force (IETF). Note that other groups may also distribute 45 working documents as Internet-Drafts. The list of current Internet- 46 Drafts is at https://datatracker.ietf.org/drafts/current/. 48 Internet-Drafts are draft documents valid for a maximum of six months 49 and may be updated, replaced, or obsoleted by other documents at any 50 time. It is inappropriate to use Internet-Drafts as reference 51 material or to cite them other than as "work in progress." 53 This Internet-Draft will expire on October 10, 2022. 55 Copyright Notice 57 Copyright (c) 2022 IETF Trust and the persons identified as the 58 document authors. All rights reserved. 60 This document is subject to BCP 78 and the IETF Trust's Legal 61 Provisions Relating to IETF Documents 62 (https://trustee.ietf.org/license-info) in effect on the date of 63 publication of this document. Please review these documents 64 carefully, as they describe your rights and restrictions with respect 65 to this document. Code Components extracted from this document must 66 include Simplified BSD License text as described in Section 4.e of 67 the Trust Legal Provisions and are provided without warranty as 68 described in the Simplified BSD License. 70 Table of Contents 72 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 73 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4 74 3. The Flow Specification Encoding for SRv6 . . . . . . . . . . 4 75 3.1. Type TBD1 - Some Parts of SID . . . . . . . . . . . . . . 4 76 3.2. Encoding Examples . . . . . . . . . . . . . . . . . . . . 6 77 3.2.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 6 78 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 79 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 80 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 81 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 82 7.1. Normative References . . . . . . . . . . . . . . . . . . 7 83 7.2. Informative References . . . . . . . . . . . . . . . . . 8 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 86 1. Introduction 88 [RFC8955] describes in details about a new BGP NLRI to distribute a 89 flow specification, which is an n-tuple comprising a sequence of 90 matching criteria that can be applied to IP traffic. [RFC8956] 91 extends [RFC8955] to make it also usable and applicable to IPv6 data 92 packets. [I-D.ietf-idr-flowspec-l2vpn] extends the flow-spec rules 93 for layer 2 Ethernet packets. [I-D.hares-idr-flowspec-v2] specifies 94 BGP Flow Specification Version 2. 96 Segment Routing (SR) for unicast traffic has been proposed to cope 97 with the usecases in traffic engineering, fast re-reroute, service 98 chain, etc. SR architecture can be implemented over an IPv6 data 99 plane using a new type of IPv6 extension header called Segment 100 Routing Header (SRH) [I-D.ietf-6man-segment-routing-header]. SRv6 101 Network Programming [RFC8986] defines the SRv6 network programming 102 concept and its most basic functions. An SRv6 SID may have the form 103 of LOC:FUNCT:ARG::. 105 LOC: Each operator is free to use the locator length it chooses. 106 Most often the LOC part of the SID is routable and leads to the node 107 which instantiates that SID. 109 FUNCT: The FUNCT part of the SID is an opaque identification of a 110 local function bound to the SID. E.g., End.X, End.T, End.DX2, etc. 112 ARG: A function may require additional arguments that would be placed 113 immediately after the FUNCT. 115 This document specifies one new BGP Flow Specification (FS) component 116 type to support Segment Routing over IPv6 data plane (SRv6) filtering 117 for BGP Flow Specification Version 2. The match field is destination 118 address of IPv6 header, but it's a SRv6 SID from SRH rather than a 119 traditional IPv6 address (refer to Figure 1). To support these 120 features, a Flowspec version that is IPv6 capable (i.e., AFI = 2) 121 MUST be used. These match capabilities of the features MAY be 122 permitted to match when there is an accompanying SRH. 124 +-----------------------------+ 125 IPv6 Header| SA | DA |<--Match field of this document 126 +--------------------^--------+ 127 | 128 +--------------------|--------+ 129 | +-------------+ | +-------------------+ 130 | | Segment[0] +-------> Loc | Func | Arg | 131 | +-------------+ | +-------------------+ 132 | | Segment[1] | | 133 | +-------------+ | 134 | | ... | | 135 SR Header| +-------------+ | 136 | | Segment[n] | | 137 | +-------------+ | 138 | +-------------+ | 139 | ~ Option TLV ~ | 140 | +-------------+ | 141 +-----------------------------+ 143 Figure 1: Match Field 145 2. Definitions and Acronyms 147 o FS: Flow Specification 149 o BGP-FS: Border Gateway Protocol (BGP) Flow Specification (FS) 151 o SR: Segment Routing 153 o SRH: SR Header. 155 o SRv6: IPv6 Segment Routing, SRv6 is a method of forwarding IPv6 156 packets on the network based on the concept of source routing. 158 o SID: Segment Identifier 160 o BSID: Binding SID 162 3. The Flow Specification Encoding for SRv6 164 The Flow Specification NLRI-type consists of several optional 165 components, each of which begins with a type field (1 octet) followed 166 by a variable length parameter. 13 component types are defined in 167 [RFC8955] and [RFC8956] for IPv4 and IPv6. This document defines one 168 component type for SRv6. 170 3.1. Type TBD1 - Some Parts of SID 172 [RFC8986] defines the format of SID is LOC:FUNCT:ARG::. In some 173 scenarios, traffic packets can just match Locator, Function ID, 174 Arguments or some combinations of these different fields. In order 175 to match a part of SID, its prior parts need to be examined and 176 matched first. For example, in order to match the Function ID 177 (FUNCT), the Locator (LOC) needs to be examined and matched first. 178 The new component type TBD1 defined below is for matching some parts 179 of SID. 181 Encoding: 183 o type (1 octet): This indicates the new component type (TBD1, which 184 is to be assigned by IANA). 186 o LOC-Len (1 octet): This indicates the length in bits of LOC in 187 SID. 189 o FUNCT-Len (1 octet): This indicates the length in bits of FUNCT in 190 SID. 192 o ARG-Len (1 octet): This indicates the length in bits of ARG in 193 SID. 195 o [op, value]+: This contains a list of {operator, value} pairs that 196 are used to match some parts of SID. 198 The total of three lengths (i.e., LOC length + FUNCT length + ARG 199 length) MUST NOT be greater than 128. If it is greater than 128, an 200 error occurs and Error Handling is applied according to [RFC7606] and 201 [RFC4760]. 203 The operator (op) byte is encoded as: 205 0 1 2 3 4 5 6 7 206 +---+---+---+---+---+---+---+---+ 207 | e | a | field type|lt |gt |eq | 208 +---+---+---+---+---+---+---+---+ 210 where the behavior of each operator bit has clear symmetry with that 211 of [RFC8955]'s Numeric Operator field. 213 e - end-of-list bit. Set in the last {op, value} pair in the 214 sequence. 216 a - AND bit. If unset, the previous term is logically ORed with the 217 current one. If set, the operation is a logical AND. It should be 218 unset in the first operator byte of a sequence. The AND operator has 219 higher priority than OR for the purposes of evaluating logical 220 expressions. 222 field type: 224 000: SID's LOC 226 001: SID's FUNCT 228 010: SID's ARG 230 011: SID's LOC:FUNCT 232 100: SID's FUNCT:ARG 234 101: SID's LOC:FUNCT:ARG 236 For an unknown type, Error Handling is applied according to [RFC7606] 237 and [RFC4760]. 239 lt - less than comparison between data' and value'. 241 gt - greater than comparison between data' and value'. 243 eq - equality between data' and value'. 245 The data' and value' used in lt, gt and eq are indicated by the field 246 type in a operator and the value field following the operator. 248 The value field depends on the field type and has the value of SID's 249 some parts rounding up to bytes (refer to the table below). 251 +-----------------------+------------------------------+ 252 | Field Type | Value | 253 +=======================+==============================+ 254 | SID's LOC | value of LOC bits | 255 +-----------------------+------------------------------+ 256 | SID's FUNCT | value of FUNCT bits | 257 +-----------------------+------------------------------+ 258 | SID's ARG | value of ARG bits | 259 +-----------------------+------------------------------+ 260 | SID's LOC:FUNCT | value of LOC:FUNCT bits | 261 +-----------------------+------------------------------+ 262 | SID's FUNCT:ARG | value of FUNCT:ARG bits | 263 +-----------------------+------------------------------+ 264 | SID's LOC:FUNCT:ARG | value of LOC:FUNCT:ARG bits | 265 +-----------------------+------------------------------+ 267 3.2. Encoding Examples 269 3.2.1. Example 1 271 An example of a Flow Specification NLRI encoding for: all SRv6 272 packets to LOC 2001:db8:3::/48 and FUNCT {range [0100, 0300]}. 274 Some Parts of SID 275 | 276 length v LOC==20010db80003 FUN>=100 FUN<=300 277 0x12 0f 30 10 40 01 2001 0db8 0003 4b 0100 bd 0300 278 ^ ^ ^ 279 | | | 280 Length of LOC FUN ARG 282 Decoded: 283 Value 284 0x12 length 18 octets (if len<240, 1 octet) 285 TBD1(0x0f) type type TBD1(0x0f) - Some Parts of SID 286 0x30 LOC Length = 48 (bits) 287 0x10 FUNCT Length = 16 (bits) 288 0x40 ARG Length = 64 (bits) 289 0x01 op LOC == 290 0x2001 value LOC's value = 2001:db8:3 291 0x0db8 292 0x0003 293 0x4b op "AND", FUNCT >= 294 0x0100 value FUNCT's value = 0100 295 0xbd op end-of-list, "AND", FUNCT <= 296 0x0300 value FUNCT's value = 0300 298 4. Security Considerations 300 No new security issues are introduced to the BGP protocol by this 301 specification over the security considerations in [RFC8955] and 302 [RFC8956]. 304 5. IANA Considerations 306 Under "Flow Spec Component Types" registry, IANA is requested to 307 assign the following values: 309 +-----------+------------+-------------------+----------------+ 310 | Value | IPv4 Name | IPv6 Name | Reference | 311 +-----------+------------+-------------------+----------------+ 312 | TBD1 | Unassigned | Some Parts of SID | This Document | 313 +-----------+------------+-------------------+----------------+ 315 6. Acknowledgments 317 The authors would like to thank Joel Halpern, Jeffrey Haas, Ketan 318 Talaulikar, Aijun Wang, Dhruv Dhody, Shunwan Zhuang and Rainsword 319 Wang for their valuable suggestions and comments on this draft. 321 7. References 323 7.1. Normative References 325 [I-D.hares-idr-flowspec-v2] 326 Hares, S., Eastlake, D., Yadlapalli, C., and S. Maduschke, 327 "BGP Flow Specification Version 2", draft-hares-idr- 328 flowspec-v2-05 (work in progress), February 2022. 330 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 331 Requirement Levels", BCP 14, RFC 2119, 332 DOI 10.17487/RFC2119, March 1997, 333 . 335 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 336 "Multiprotocol Extensions for BGP-4", RFC 4760, 337 DOI 10.17487/RFC4760, January 2007, 338 . 340 [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP 341 Extended Communities", RFC 7153, DOI 10.17487/RFC7153, 342 March 2014, . 344 [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. 345 Patel, "Revised Error Handling for BGP UPDATE Messages", 346 RFC 7606, DOI 10.17487/RFC7606, August 2015, 347 . 349 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 350 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 351 May 2017, . 353 [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. 354 Bacher, "Dissemination of Flow Specification Rules", 355 RFC 8955, DOI 10.17487/RFC8955, December 2020, 356 . 358 [RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed., 359 "Dissemination of Flow Specification Rules for IPv6", 360 RFC 8956, DOI 10.17487/RFC8956, December 2020, 361 . 363 7.2. Informative References 365 [I-D.ietf-6man-segment-routing-header] 366 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 367 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 368 (SRH)", draft-ietf-6man-segment-routing-header-26 (work in 369 progress), October 2019. 371 [I-D.ietf-idr-flowspec-l2vpn] 372 Hao, W., Eastlake, D. E., Litkowski, S., and S. Zhuang, 373 "BGP Dissemination of L2 Flow Specification Rules", draft- 374 ietf-idr-flowspec-l2vpn-18 (work in progress), October 375 2021. 377 [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, 378 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 379 (SRv6) Network Programming", RFC 8986, 380 DOI 10.17487/RFC8986, February 2021, 381 . 383 Authors' Addresses 385 Zhenbin Li 386 Huawei 387 156 Beiqing Road 388 Beijing, 100095 389 P.R. China 391 Email: lizhenbin@huawei.com 393 Lei Li 394 Huawei 395 156 Beiqing Road 396 Beijing 100095 397 P.R. China 399 Email: lily.lilei@huawei.com 401 Huaimo Chen 402 Futurewei 403 Boston, MA 404 USA 406 Email: Huaimo.chen@futurewei.com 408 Christoph Loibl 409 Next Layer Communications 410 Mariahilfer Guertel 37/7 411 Vienna 1150 412 AT 414 Email: cl@tix.at 415 Gyan S. Mishra 416 Verizon Inc. 417 13101 Columbia Pike 418 Silver Spring MD 20904 419 USA 421 Phone: 301 502-1347 422 Email: gyan.s.mishra@verizon.com 424 Yanhe Fan 425 Casa Systems 426 USA 428 Email: yfan@casa-systems.com 430 Yongqing Zhu 431 China Telecom 432 109, West Zhongshan Road, Tianhe District 433 Guangzhou 510000 434 China 436 Email: zhuyq8@chinatelecom.cn 438 Lei Liu 439 Fujitsu 440 USA 442 Email: liulei.kddi@gmail.com 444 Xufeng Liu 445 Volta Networks 446 McLean, VA 447 USA 449 Email: xufeng.liu.ietf@gmail.com