idnits 2.17.1 draft-ietf-bess-srv6-services-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 : ---------------------------------------------------------------------------- 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 (February 27, 2020) is 1517 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) == Outdated reference: A later version (-21) exists of draft-ietf-bess-evpn-igmp-mld-proxy-04 == Outdated reference: A later version (-08) exists of draft-ietf-bess-evpn-vpws-fxc-01 == Outdated reference: A later version (-06) exists of draft-ietf-bess-rfc5549revision-03 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-10 == Outdated reference: A later version (-26) exists of draft-ietf-idr-segment-routing-te-policy-08 == Outdated reference: A later version (-22) exists of draft-ietf-spring-segment-routing-policy-06 == Outdated reference: A later version (-15) exists of draft-matsushima-spring-srv6-deployment-status-05 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BESS Working Group G. Dawra, Ed. 3 Internet-Draft LinkedIn 4 Intended status: Standards Track C. Filsfils 5 Expires: August 30, 2020 Cisco Systems 6 R. Raszuk 7 Bloomberg LP 8 B. Decraene 9 Orange 10 S. Zhuang 11 Huawei Technologies 12 J. Rabadan 13 Nokia 14 February 27, 2020 16 SRv6 BGP based Overlay services 17 draft-ietf-bess-srv6-services-02 19 Abstract 21 This draft defines procedures and messages for SRv6-based BGP 22 services including L3VPN, EVPN and Internet services. It builds on 23 RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 24 "BGP MPLS-Based Ethernet VPN". 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on August 30, 2020. 43 Copyright Notice 45 Copyright (c) 2020 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 62 2. SRv6 Services TLVs . . . . . . . . . . . . . . . . . . . . . 4 63 3. SRv6 Service Sub-TLVs . . . . . . . . . . . . . . . . . . . . 5 64 3.1. SRv6 SID Information Sub-TLV . . . . . . . . . . . . . . 6 65 3.2. SRv6 Service Data Sub-Sub-TLVs . . . . . . . . . . . . . 7 66 3.2.1. SRv6 SID Structure Sub-Sub-TLV . . . . . . . . . . . 7 67 4. Encoding SRv6 SID information . . . . . . . . . . . . . . . . 9 68 5. BGP based L3 service over SRv6 . . . . . . . . . . . . . . . 10 69 5.1. IPv4 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 11 70 5.2. IPv6 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 11 71 5.3. Global IPv4 over SRv6 Core . . . . . . . . . . . . . . . 12 72 5.4. Global IPv6 over SRv6 Core . . . . . . . . . . . . . . . 12 73 6. BGP based Ethernet VPN (EVPN) over SRv6 . . . . . . . . . . . 12 74 6.1. Ethernet Auto-discovery route over SRv6 Core . . . . . . 13 75 6.1.1. Per-ES A-D route . . . . . . . . . . . . . . . . . . 13 76 6.1.2. Per-EVI A-D route . . . . . . . . . . . . . . . . . . 14 77 6.2. MAC/IP Advertisement route over SRv6 Core . . . . . . . . 14 78 6.2.1. MAC/IP Advertisement route with MAC Only . . . . . . 15 79 6.2.2. MAC/IP Advertisement route with MAC+IP . . . . . . . 16 80 6.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core . . 16 81 6.4. Ethernet Segment route over SRv6 Core . . . . . . . . . . 18 82 6.5. IP prefix route over SRv6 Core . . . . . . . . . . . . . 18 83 6.6. EVPN multicast routes (Route Types 6, 7, 8) over SRv6 84 core . . . . . . . . . . . . . . . . . . . . . . . . . . 19 85 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 86 8. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 19 87 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 88 9.1. BGP Prefix-SID TLV Types registry . . . . . . . . . . . . 20 89 9.2. SRv6 Service Sub-TLV Types registry . . . . . . . . . . . 21 90 9.3. SRv6 Service Data Sub-Sub-TLV Types registry . . . . . . 21 91 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 92 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 93 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 94 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 95 13.1. Normative References . . . . . . . . . . . . . . . . . . 23 96 13.2. Informative References . . . . . . . . . . . . . . . . . 26 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 99 1. Introduction 101 SRv6 refers to Segment Routing [RFC8402] instantiated on the IPv6 102 dataplane [I-D.ietf-6man-segment-routing-header]. 104 SRv6 based BGP services refers to the L3 and L2 overlay services with 105 BGP as control plane and SRv6 as dataplane. 107 SRv6 SID refers to a SRv6 Segment Identifier as defined in [RFC8402]. 109 SRv6 Service SID refers to an SRv6 SID associated with one of the 110 service specific behavior on the advertising Provider Edge (PE) 111 router, such as (but not limited to), END.DT (Table lookup in a VRF) 112 or END.DX (cross-connect to a nexthop) behaviors in the case of L3VPN 113 service as defined in [I-D.ietf-spring-srv6-network-programming]. 115 To provide SRv6 service with best-effort connectivity, the egress PE 116 signals an SRv6 Service SID with the BGP overlay service route. The 117 ingress PE encapsulates the payload in an outer IPv6 header where the 118 destination address is the SRv6 Service SID provided by the egress 119 PE. The underlay between the PEs only need to support plain IPv6 120 forwarding [RFC8200]. 122 To provide SRv6 service in conjunction with an underlay SLA from the 123 ingress PE to the egress PE, the egress PE colors the overlay service 124 route with a Color extended community 125 [I-D.ietf-idr-segment-routing-te-policy]. The ingress PE 126 encapsulates the payload packet in an outer IPv6 header with the 127 segment list of SR policy associated with the related SLA followed by 128 the SRv6 Service SID associated with the route. The underlay nodes 129 whose SRv6 SID's are part of the segment list MUST support SRv6 data 130 plane. 132 BGP is used to advertise the reachability of prefixes of a particular 133 service from an egress PE to ingress PE nodes. 135 This document describes how existing BGP messages between PEs may 136 carry SRv6 Service SIDs as a means to interconnect PEs and form VPNs. 138 1.1. Requirements Language 140 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 141 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 142 "OPTIONAL" in this document are to be interpreted as described in BCP 143 14 [RFC2119] [RFC8174] when, and only when, they appear in all 144 capitals, as shown here. 146 2. SRv6 Services TLVs 148 This document extends the BGP Prefix-SID attribute [RFC8669] to carry 149 SRv6 SIDs and associated information. 151 The SRv6 Service TLVs are defined as two new TLVs of the BGP Prefix- 152 SID Attribute to achieve signaling of SRv6 SIDs for L3 and L2 153 services. 155 o SRv6 L3 Service TLV: This TLV encodes Service SID information for 156 SRv6 based L3 services. It corresponds to the equivalent 157 functionality provided by an MPLS Label when received with a Layer 158 3 service route. Some behaviors which MAY be encoded, but not 159 limited to, are End.DX4, End.DT4, End.DX6, End.DT6, etc. 161 o SRv6 L2 Service TLV: This TLV encodes Service SID information for 162 SRv6 based L2 services. It corresponds to the equivalent 163 functionality provided by an MPLS Label1 for EVPN Route-Types as 164 defined in[RFC7432]. Some behaviors which MAY be encoded, but not 165 limited to, are End.DX2, End.DX2V, End.DT2U, End.DT2M etc. 167 When an egress PE is enabled for BGP Services over SRv6 data-plane, 168 it MUST signal one or more SRv6 Service SIDs enclosed in SRv6 Service 169 TLV(s) within the BGP Prefix-SID Attribute attached to MP-BGP NLRIs 170 defined in [RFC4760] [RFC4659] [I-D.ietf-bess-rfc5549revision] 171 [RFC7432] [RFC4364] where applicable as described in Section 5 and 172 Section 6. 174 The following depicts the SRv6 Service TLVs encoded in the BGP 175 Prefix-SID Attribute: 177 0 1 2 3 178 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | TLV Type | TLV Length | RESERVED | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 // SRv6 Service Sub-TLVs // 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 o TLV Type (1 octet): This field is assigned values from the IANA 186 registry "BGP Prefix-SID TLV Types". It is set to TBD1 (to be 187 assigned by IANA) for SRv6 L3 Service TLV. It is set to TBD2 (to 188 be assigned by IANA) for SRv6 L2 Service TLV. 190 o TLV Length (2 octets): Specifies the total length of the TLV 191 Value. 193 o RESERVED (1 octet): This field is reserved; it SHOULD be set to 0 194 by the sender and MUST be ignored by the receiver. 196 o SRv6 Service Sub-TLVs (variable): This field contains SRv6 Service 197 related information and is encoded as an unordered list of Sub- 198 TLVs whose format is described below. 200 A BGP speaker receiving a route containing BGP Prefix-SID Attribute 201 with one or more SRv6 Service TLVs observes the following rules when 202 advertising the received route to other peers: 204 o if the nexthop is unchanged during advertisement, the SRv6 Service 205 TLVs, including any unrecognized Types of Sub-TLV and Sub-Sub-TLV, 206 SHOULD be propagated further. In addition, all Reserved fields in 207 the TLV or Sub-TLV or Sub-Sub-TLV MUST be propagated unchanged. 209 o if the nexthop is changed, the TLVs, Sub-TLVs and Sub-Sub-TLVs 210 SHOULD be updated as appropriate. Any unrecognized received sub- 211 TLVs and Sub-Sub-TLVs MUST be removed. 213 3. SRv6 Service Sub-TLVs 215 The format of a single SRv6 Service Sub-TLV is depicted below: 217 0 1 2 3 218 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | SRv6 Service | SRv6 Service | SRv6 Service // 221 | Sub-TLV | Sub-TLV | Sub-TLV // 222 | Type | Length | value // 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 o SRv6 Service Sub-TLV Type (1 octet): Identifies the type of SRv6 226 service information. It is assigned values from the IANA Registry 227 "SRv6 Service Sub-TLV Types". 229 o SRv6 Service Sub-TLV Length (2 octets): Specifies the total length 230 of the Sub-TLV Value field. 232 o SRv6 Service Sub-TLV Value (variable): Contains data specific to 233 the Sub-TLV Type. In addition to fixed length data, it contains 234 other properties of the SRv6 Service encoded as a set of SRv6 235 Service Data Sub-Sub-TLVs whose format is described in Section 3.2 236 below. 238 3.1. SRv6 SID Information Sub-TLV 240 SRv6 Service Sub-TLV Type 1 is assigned for SRv6 SID Information Sub- 241 TLV. This Sub-TLV contains a single SRv6 SID along with its 242 properties. Its encoding is depicted below: 244 0 1 2 3 245 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | SRv6 Service | SRv6 Service | | 248 | Sub-TLV | Sub-TLV | | 249 | Type=1 | Length | RESERVED1 | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 // SRv6 SID Value (16 bytes) // 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | SRv6 SID Flags| SRv6 Endpoint Behavior | RESERVED2 | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 // SRv6 Service Data Sub-Sub-TLVs // 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 o SRv6 Service Sub-TLV Type (1 octet): This field is set to 1 to 259 represent SRv6 SID Information Sub-TLV. 261 o SRv6 Service Sub-TLV Length (2 octets): This field contains the 262 total length of the Value field of the Sub-TLV. 264 o RESERVED1 (1 octet): SHOULD be set to 0 by the sender and MUST be 265 ignored by the receiver. 267 o SRv6 SID Value (16 octets): Encodes an SRv6 SID as defined in 268 [I-D.ietf-spring-srv6-network-programming] 270 o SRv6 SID Flags (1 octet): Encodes SRv6 SID Flags - none are 271 currently defined. 273 o SRv6 Endpoint Behavior (2 octets): Encodes SRv6 Endpoint behavior 274 codepoint value from the IANA registry defined in section 9.2 of 275 [I-D.ietf-spring-srv6-network-programming] that is associated with 276 SRv6 SID. 278 o RESERVED2 (1 octet): SHOULD be set to 0 by the sender and MUST be 279 ignored by the receiver. 281 o SRv6 Service Data Sub-Sub-TLV Value (variable): Used to advertise 282 properties of the SRv6 SID. It is encoded as a set of SRv6 283 Service Data Sub-Sub-TLVs. 285 When multiple SRv6 SID Information Sub-TLVs are present, the ingress 286 PE SHOULD use the SRv6 SID from the first instance of the Sub-TLV. 287 An implementation MAY provide a local policy to override this 288 selection. 290 3.2. SRv6 Service Data Sub-Sub-TLVs 292 The format of the SRv6 Service Data Sub-Sub-TLV is depicted below: 294 0 1 2 3 295 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | Service Data | Sub-Sub-TLV Length |Sub-Sub TLV // 298 | Sub-Sub-TLV | | Value // 299 | Type | | // 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 o SRv6 Service Data Sub-Sub-TLV Type (1 octet): Identifies the type 303 of Sub-Sub-TLV. It is assigned values from the IANA Registry 304 "SRv6 Service Data Sub-Sub-TLVs". 306 o SRv6 Service Data Sub-Sub-TLV Length (2 octets): Specifies the 307 total length of the Sub-Sub-TLV Value field. 309 o SRv6 Service Data Sub-Sub-TLV Value (variable): Contains data 310 specific to the Sub-Sub-TLV Type. 312 3.2.1. SRv6 SID Structure Sub-Sub-TLV 314 SRv6 Service Data Sub-Sub-TLV Type 1 is assigned for SRv6 SID 315 structure Sub-Sub-TLV. SRv6 SID Structure Sub-Sub-TLV is used to 316 advertise the lengths of each individual parts of the SRv6 SID as 317 defined in [I-D.ietf-spring-srv6-network-programming]. It is carried 318 as Sub-Sub-TLV in SRv6 SID Information Sub-TLV 320 0 1 2 3 321 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 | SRv6 Service | SRv6 Service | Locator Block | 324 | Data Sub-Sub | Data Sub-Sub-TLV | Length | 325 | -TLV Type=1 | Length=6 | | 326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 | Locator Node | Function | Argument | Transposition | 328 | Length | Length | Length | Length | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Transposition | 331 | Offset | 332 +-+-+-+-+-+-+-+-+ 334 o SRv6 Service Data Sub-Sub-TLV Type (1 octet): This field is set to 335 1 to represent SRv6 SID Structure Sub-Sub-TLV. 337 o SRv6 Service Data Sub-Sub-TLV Length (2 octets): This field 338 contains the total length of 6 bytes. 340 o Locator Block Length (1 octet): Contains length of SRv6 SID 341 locator Block in bits. 343 o Locator Node Length (1 octet): Contains length of SRv6 SID locator 344 Node in bits. 346 o Function Length (1 octet): Contains length of SRv6 SID Function in 347 bits. 349 o Argument Length (1 octet): Contains length of SRv6 SID argument in 350 bits. 352 o Transposition Length (1 octet): Size in bits for the part of SID 353 that has been transposed (or shifted) into a label field 355 o Transposition Offset (1 octet): The offset position in bits for 356 the part of SID that has been transposed (or shifted) into a label 357 field. 359 Section 4 describes mechanisms for signaling of the SRv6 Service SID 360 by transposing a variable part of the SRv6 SID value (function and/or 361 the argument parts) and carrying them in existing label fields to 362 achieve more efficient packing of those service prefix NLRIs in BGP 363 update messages. The SRv6 SID Structure Sub-Sub-TLV contains 364 appropriate length fields when the SRv6 Service SID is signaled in 365 split parts to enable the receiver to put together the SID 366 accurately. 368 Transposition Offset indicates the bit position and Transposition 369 Length indicates the number of bits that are being taken out of the 370 SRv6 SID value and put into high order bits of label field. The bits 371 that have been shifted out MUST be set to 0 in the SID value. 373 Transposition Length of 0 indicates nothing is transposed and that 374 the entire SRv6 SID value is encoded in the SID Information sub-TLV. 375 In this case, the Transposition Offset MUST be set to 0. 377 Since size of label field is 24 bits, only that many bits can be 378 transposed from the SRv6 SID value into it. 380 As an example, when the entire function part of size 16 of an SRv6 381 SID is transposed and the sum of the locator block and locator node 382 parts is 64, then the transposition offset would be set to 64 and the 383 transposition length is set to 16. 385 BGP speakers that do not support this specification may misinterpret, 386 on reception of an SRv6-based BGP service route update, the function 387 and/or argument parts of the SRv6 SID encoded in label field(s) as 388 MPLS label values for MPLS-based services. Implementations 389 supporting this specification SHOULD provide a mechanism to control 390 advertisement of SRv6-based BGP service routes on a per neighbor and 391 per service basis. 393 Arguments MAY be generally applicable for SIDs of only specific 394 behaviors (e.g. End.DT2M) and therefore the argument length MUST be 395 set to 0 for SIDs where the argument is not applicable. 397 4. Encoding SRv6 SID information 399 The SRv6 Service SID(s) for a BGP Service Prefix are carried in the 400 SRv6 Services TLVs of the BGP Prefix-SID Attribute. 402 For certain types of BGP Services like L3VPN where a per-VRF SID 403 allocation is used (i.e. End.DT4 or End.DT6 behaviors), the same SID 404 is shared across multiple NLRIs thus providing efficient packing. 405 However, for certain other types of BGP Services like EVPN VPWS where 406 a per-PW SID allocation is required (i.e. End.DX2 behavior), each 407 NLRI would have its own unique SID there by resulting in inefficient 408 packing. 410 To achieve efficient packing, this document allows the encoding of 411 the SRv6 Service SID either as a whole in the SRv6 Services TLVs or 412 the encoding of only the common part of the SRv6 SID (e.g. Locator) 413 in the SRv6 Services TLVs and encoding the variable (e.g. Function 414 and Argument parts) in the existing label fields specific to that 415 service encoding. This later form of encoding is referred to as the 416 Transposition Scheme where the SRv6 SID Structure Sub-Sub-TLV 417 describes the sizes of the parts of the SRv6 SID and to also indicate 418 offset of variable part along with its length in SRv6 SID value. The 419 use of the Transposition Scheme is RECOMMENDED for the specific 420 service encodings that allow it as described further in Section 5 and 421 Section 6. 423 As an example, for the EVPN VPWS service prefix described further in 424 Section 6.1.2, the function part of the SRv6 SID is encoded in the 425 MPLS Label field of the NLRI and the SID value in the SRv6 Services 426 TLV carries only the locator part with the SRv6 SID Structure Sub- 427 Sub-TLV. The SRv6 SID Structure sub-sub-TLV defines the lengths of 428 locator block, locator node and function parts (arguments are not 429 applicable for the End.DX2 behavior). Transposition Offset indicates 430 the bit position and Transposition Length indicates the number of 431 bits that are being taken out of the SID and put into label field. 433 In yet another example, for the EVPN Per-ES A-D route described 434 further in Section 6.1.1, only the argument of the SID needs to be 435 signaled. This argument part of the SRv6 SID MAY be transposed in 436 the ESI Label field of the ESI Label Extended Community and the SID 437 value in the SRv6 Services TLV is set to 0 with the SRv6 SID 438 Structure Sub-Sub-TLV. The SRv6 SID Structure sub-sub-TLV defines 439 the lengths of locator block, locator node, function and argument 440 parts. The offset and length of argument part SID value moved to 441 label field is set in transposition offset and length of SID 442 structure TLV. The receiving router is then able to put together the 443 entire SRv6 Service SID (e.g. for the End.DT2M behavior) placing the 444 label value received in the ESI Label field of the Per-ES A-D route 445 into the correct transposition offset and length in the SRv6 SID with 446 the End.DT2M behavior received for a EVPN Route Type 3 value. 448 5. BGP based L3 service over SRv6 450 BGP egress nodes (egress PEs) advertise a set of reachable prefixes. 451 Standard BGP update propagation schemes[RFC4271], which may make use 452 of route reflectors [RFC4456], are used to propagate these prefixes. 453 BGP ingress nodes (ingress PEs) receive these advertisements and may 454 add the prefix to the RIB in an appropriate VRF. 456 Egress PEs which supports SRv6 based L3 services advertises overlay 457 service prefixes along with a Service SID enclosed in a SRv6 L3 458 Service TLV within the BGP Prefix-SID Attribute. This TLV serves two 459 purposes - first, it indicates that the egress PE supports SRv6 460 overlay and the BGP ingress PE receiving this route MUST choose to 461 perform IPv6 encapsulation and optionally insert an SRH when 462 required; second ,it indicates the value of the Service SID to be 463 used in the encapsulation. 465 The Service SID thus signaled only has local significance at the 466 egress PE, where it may be allocated or configured on a per-CE or 467 per-VRF basis. In practice, the SID may encode a cross-connect to a 468 specific Address Family table (END.DT) or next-hop/interface (END.DX) 469 as defined in [I-D.ietf-spring-srv6-network-programming]. 471 The SRv6 Service SID SHOULD be routable within the AS of the egress 472 PE and serves the dual purpose of providing reachability between 473 ingress PE and egress PE while also encoding the endpoint behavior. 475 When the egress PE sets the next-hop to a value that is not covered 476 by the SRv6 Locator from which the SRv6 Service SID is allocated, 477 then the ingress PE SHOULD perform reachability check for the SRv6 478 Service SID in addition to the BGP next-hop reachability procedures. 480 At an ingress PE, BGP installs the received prefix in the correct RIB 481 table, recursing via an SR Policy leveraging the received SRv6 482 Service SID. 484 Assuming best-effort connectivity to the egress PE, the ingress PE 485 encapsulates the payload in an outer IPv6 header where the 486 destination address is the SRv6 Service SID associated with the 487 related BGP route update. 489 However, when the received route is colored with an extended color 490 community 'C' and Next-Hop 'N', and the ingress PE has a valid SRv6 491 Policy (C, N) associated with SID list 492 [I-D.ietf-spring-segment-routing-policy], then the effective SR 493 Policy is . 495 Multiple VPN routes MAY resolve recursively via the same SR Policy. 497 5.1. IPv4 VPN Over SRv6 Core 499 The MP_REACH_NLRI for SRv6 core is encoded according to IPv4 VPN Over 500 IPv6 Core defined in [I-D.ietf-bess-rfc5549revision]. 502 Label field of IPv4-VPN NLRI carries the Function part of the SRv6 503 SID when the Transposition Scheme of encoding (Section 4) is used and 504 otherwise set to Implicit NULL. 506 SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The 507 behavior of the SRv6 SID is entirely up to the originator of the 508 advertisement. In practice, the behavior is End.DX4 or End.DT4. 510 5.2. IPv6 VPN Over SRv6 Core 512 The MP_REACH_NLRI for SRv6 core is encoded according to IPv6 VPN over 513 IPv6 Core is defined in [RFC4659]. 515 Label field of the IPv6-VPN NLRI carries the Function part of the 516 SRv6 SID when the Transposition Scheme of encoding (Section 4) is 517 used and otherwise set to Implicit NULL. 519 SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The 520 behavior of the SRv6 SID is entirely up to the originator of the 521 advertisement. In practice, the behavior is End.DX6 or End.DT6. 523 5.3. Global IPv4 over SRv6 Core 525 The MP_REACH_NLRI for SRv6 core is encoded according to IPv4 over 526 IPv6 Core is defined in [I-D.ietf-bess-rfc5549revision]. 528 SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The 529 behavior of the SRv6 SID is entirely up to the originator of the 530 advertisement. In practice, the behavior is End.DX4 or End.DT4. 532 5.4. Global IPv6 over SRv6 Core 534 The MP_REACH_NLRI for SRv6 core is encoded according to [RFC2545] 536 SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The 537 behavior of the SRv6 SID is entirely up to the originator of the 538 advertisement. In practice, the behavior is End.DX6 or End.DT6. 540 6. BGP based Ethernet VPN (EVPN) over SRv6 542 [RFC7432] provides an extendable method of building an Ethernet VPN 543 (EVPN) overlay. It primarily focuses on MPLS based EVPNs and 544 [RFC8365] extends to IP based EVPN overlays. [RFC7432] defines Route 545 Types 1, 2 and 3 which carry prefixes and MPLS Label fields; the 546 Label fields have specific use for MPLS encapsulation of EVPN 547 traffic. Route Type 5 carrying MPLS label information (and thus 548 encapsulation information) for EVPN is defined in 549 [I-D.ietf-bess-evpn-prefix-advertisement]. Route Types 6,7 and 8 are 550 defined in [I-D.ietf-bess-evpn-igmp-mld-proxy]. 552 o Ethernet Auto-discovery Route (Route Type 1) 554 o MAC/IP Advertisement Route (Route Type 2) 556 o Inclusive Multicast Ethernet Tag Route (Route Type 3) 558 o Ethernet Segment route (Route Type 4) 560 o IP prefix route (Route Type 5) 562 o Selective Multicast Ethernet Tag route (Route Type 6) 564 o IGMP join sync route (Route Type 7) 566 o IGMP leave sync route (Route Type 8) 568 To support SRv6 based EVPN overlays, one or more SRv6 Service SIDs 569 are advertised with Route Type 1,2,3 and 5. The SRv6 Service SID(s) 570 per Route Type are advertised in SRv6 L3/L2 Service TLVs within the 571 BGP Prefix-SID Attribute. Signaling of SRv6 Service SID(s) serves 572 two purposes - first, it indicates that the BGP egress device 573 supports SRv6 overlay and the BGP ingress device receiving this route 574 MUST perform IPv6 encapsulation and optionally insert an SRH when 575 required; second, it indicates the value of the Service SID(s) to be 576 used in the encapsulation. 578 The SRv6 Service SID SHOULD be routable within the AS of the egress 579 PE and serves the dual purpose of providing reachability between 580 ingress PE and egress PE while also encoding the endpoint behavior. 582 When the egress PE sets the next-hop to a value that is not covered 583 by the SRv6 Locator from which the SRv6 Service SID is allocated, 584 then the ingress PE SHOULD perform reachability check for the SRv6 585 Service SID in addition to the BGP next-hop reachability procedures. 587 6.1. Ethernet Auto-discovery route over SRv6 Core 589 Ethernet Auto-Discovery (A-D) routes are Route Type 1 defined in 590 [RFC7432] and may be used to achieve split horizon filtering, fast 591 convergence and aliasing. EVPN Route Type 1 is also used in EVPN- 592 VPWS as well as in EVPN flexible cross-connect; mainly used to 593 advertise point-to-point services ID. 595 As a reminder, EVPN Route Type 1 is encoded as follows: 597 +---------------------------------------+ 598 | RD (8 octets) | 599 +---------------------------------------+ 600 |Ethernet Segment Identifier (10 octets)| 601 +---------------------------------------+ 602 | Ethernet Tag ID (4 octets) | 603 +---------------------------------------+ 604 | MPLS label (3 octets) | 605 +---------------------------------------+ 607 6.1.1. Per-ES A-D route 609 Per-ES A-D route for SRv6 overlay is advertised as follows: 611 o BGP next-hop: IPv6 address of an egress PE 613 o Ethernet Tag ID: set as per [RFC7432] 615 o MPLS Label: set as per [RFC7432] 617 o ESI label extended community ESI label field: carries the Argument 618 part of the SRv6 SID when ESI filtering approach is used along 619 with the Transposition Scheme of encoding (Section 4) and 620 otherwise set to Implicit NULL. 622 A Service SID enclosed in a SRv6 L2 Service TLV within the BGP 623 Prefix-SID attribute is advertised along with the A-D route. The 624 behavior of the Service SID thus signaled is entirely up to the 625 originator of the advertisement. When ESI filtering approach is 626 used, the Service SID is used to signal Arg.FE2 SID argument for 627 applicable End.DT2M SIDs. When local-bias approach is used, the 628 Service SID MAY be of value 0. 630 6.1.2. Per-EVI A-D route 632 Per-EVI A-D route for SRv6 overlay is advertised as follows: 634 o BGP next-hop: IPv6 address of an egress PE 636 o Ethernet Tag ID: Set as per [RFC7432], [RFC8214] and 637 [I-D.ietf-bess-evpn-vpws-fxc] 639 o MPLS Label: carries the Function part of the SRv6 SID when the 640 Transposition Scheme of encoding (Section 4) is used and otherwise 641 set to Implicit NULL. 643 A Service SID enclosed in a SRv6 L2 Service TLV within the BGP 644 Prefix-SID attribute is advertised along with the A-D route. The 645 behavior of the Service SID thus signaled is entirely up to the 646 originator of the advertisement. In practice, the behavior is 647 END.DX2, END.DX2V or END.DT2U. 649 6.2. MAC/IP Advertisement route over SRv6 Core 651 EVPN Route Type 2 is used to advertise unicast traffic MAC+IP address 652 reachability through MP-BGP to all other PEs in a given EVPN 653 instance. 655 As a reminder, EVPN Route Type 2 is encoded as follows: 657 +---------------------------------------+ 658 | RD (8 octets) | 659 +---------------------------------------+ 660 |Ethernet Segment Identifier (10 octets)| 661 +---------------------------------------+ 662 | Ethernet Tag ID (4 octets) | 663 +---------------------------------------+ 664 | MAC Address Length (1 octet) | 665 +---------------------------------------+ 666 | MAC Address (6 octets) | 667 +---------------------------------------+ 668 | IP Address Length (1 octet) | 669 +---------------------------------------+ 670 | IP Address (0, 4, or 16 octets) | 671 +---------------------------------------+ 672 | MPLS Label1 (3 octets) | 673 +---------------------------------------+ 674 | MPLS Label2 (0 or 3 octets) | 675 +---------------------------------------+ 677 o BGP next-hop: IPv6 address of an egress PE 679 o MPLS Label1: Is associated with the SRv6 L2 Service TLV. It 680 carries the Function part of the SRv6 SID when the Transposition 681 Scheme of encoding (Section 4) is used and otherwise set to 682 Implicit NULL. 684 o MPLS Label2: Is associated with the SRv6 L3 Service TLV. It 685 carries the Function part of the SRv6 SID when the Transposition 686 Scheme of encoding (Section 4) is used and otherwise set to 687 Implicit NULL. 689 Service SIDs enclosed in SRv6 L2 Service TLV and optionally in SRv6 690 L3 Service TLV within the BGP Prefix-SID attribute is advertised 691 along with the MAC/IP Advertisement route. 693 Described below are different types of Route Type 2 advertisements. 695 6.2.1. MAC/IP Advertisement route with MAC Only 697 o MPLS Label1: Is associated with the SRv6 L2 Service TLV. It 698 carries the Function part of the SRv6 SID when the Transposition 699 Scheme of encoding (Section 4) is used and otherwise set to 700 Implicit NULL. 702 A Service SID enclosed in a SRv6 L2 Service TLV within the BGP 703 Prefix-SID attribute is advertised along with the route. The 704 behavior of the Service SID thus signaled is entirely up to the 705 originator of the advertisement. In practice, the behavior is 706 END.DX2 or END.DT2U. 708 6.2.2. MAC/IP Advertisement route with MAC+IP 710 o MPLS Label1: Is associated with the SRv6 L2 Service TLV. It 711 carries the Function part of the SRv6 SID when the Transposition 712 Scheme of encoding (Section 4) is used and otherwise set to 713 Implicit NULL. 715 o MPLS Label2: Is associated with the SRv6 L3 Service TLV. It 716 carries the Function part of the SRv6 SID when the Transposition 717 Scheme of encoding (Section 4) is used and otherwise set to 718 Implicit NULL. 720 An L2 Service SID enclosed in a SRv6 L2 Service TLV within the BGP 721 Prefix-SID attribute is advertised along with the route. In 722 addition, an L3 Service SID enclosed in a SRv6 L3 Service TLV within 723 the BGP Prefix-SID attribute MAY also be advertised along with the 724 route. The behavior of the Service SID(s) thus signaled is entirely 725 up to the originator of the advertisement. In practice, the behavior 726 is END.DX2 or END.DT2U for the L2 Service SID, and END.DT6/4 or 727 END.DX6/4 for the L3 Service SID. 729 6.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core 731 EVPN Route Type 3 is used to advertise multicast traffic reachability 732 information through MP-BGP to all other PEs in a given EVPN instance. 734 As a reminder, EVPN Route Type 3 is encoded as follows: 736 +---------------------------------------+ 737 | RD (8 octets) | 738 +---------------------------------------+ 739 | Ethernet Tag ID (4 octets) | 740 +---------------------------------------+ 741 | IP Address Length (1 octet) | 742 +---------------------------------------+ 743 | Originating Router's IP Address | 744 | (4 or 16 octets) | 745 +---------------------------------------+ 747 o BGP next-hop: IPv6 address of egress PE 749 PMSI Tunnel Attribute [RFC6514] is used to identify the P-tunnel used 750 for sending BUM traffic. The format of PMSI Tunnel Attribute is 751 encoded as follows for SRv6 Core: 753 +---------------------------------------+ 754 | Flag (1 octet) | 755 +---------------------------------------+ 756 | Tunnel Type (1 octet) | 757 +---------------------------------------+ 758 | MPLS label (3 octet) | 759 +---------------------------------------+ 760 | Tunnel Identifier (variable) | 761 +---------------------------------------+ 763 o Flag: zero value defined per [RFC7432] 765 o Tunnel Type: defined per [RFC6514] 767 o MPLS label: It carries the Function part of the SRv6 SID when 768 ingress replication is used and the Transposition Scheme of 769 encoding (Section 4) is used and otherwise it is set as defined in 770 [RFC6514] 772 o Tunnel Identifier: IP address of egress PE 774 A Service SID enclosed in a SRv6 L2 Service TLV within the BGP 775 Prefix-SID attribute is advertised along with the route. The 776 behavior of the Service SID thus signaled, is entirely up to the 777 originator of the advertisement. In practice, the behavior of the 778 SRv6 SID is as follows: 780 o END.DT2M behavior. 782 o When ESI-based filtering is used for Multi-Homing or E-Tree 783 procedures, the ESI Filtering argument (Arg.FE2) of the Service 784 SID carried along with EVPN Route Type 1 route SHOULD be merged 785 together with the applicable End.DT2M SID of Type 3 route 786 advertised by remote PE by doing a bitwise logical-OR operation to 787 create a single SID on the ingress PE. Details of split-horizon 788 ESI-based filtering mechanisms for multihoming are described in 789 [RFC7432]. Details of filtering mechanisms for Leaf-originated 790 BUM traffic in EVPN E-Tree services are provided in [RFC8317]. 792 o When "local-bias" is used as the Multi-Homing split-horizon 793 method, the ESI Filtering argument SHOULD NOT be merged with the 794 corresponding End.DT2M SID on the ingress PE. Details of the 795 "local-bias" procedures are described in [RFC8365]. 797 The setup of multicast trees for use as P-tunnels is outside the 798 scope of this document. 800 6.4. Ethernet Segment route over SRv6 Core 802 As a reminder, an Ethernet Segment route i.e. EVPN Route Type 4 is 803 encoded as follows: 805 +---------------------------------------+ 806 | RD (8 octets) | 807 +---------------------------------------+ 808 | Ethernet Tag ID (4 octets) | 809 +---------------------------------------+ 810 | IP Address Length (1 octet) | 811 +---------------------------------------+ 812 | Originating Router's IP Address | 813 | (4 or 16 octets) | 814 +---------------------------------------+ 816 o BGP next-hop: IPv6 address of egress PE 818 SRv6 Service TLVs within BGP Prefix-SID attribute are not advertised 819 along with this route. The processing of the route has not changed - 820 it remains as described in [RFC7432]. 822 6.5. IP prefix route over SRv6 Core 824 EVPN Route Type 5 is used to advertise IP address reachability 825 through MP-BGP to all other PEs in a given EVPN instance. IP address 826 may include host IP prefix or any specific subnet. 828 As a reminder, EVPN Route Type 5 is encoded as follows: 830 +---------------------------------------+ 831 | RD (8 octets) | 832 +---------------------------------------+ 833 |Ethernet Segment Identifier (10 octets)| 834 +---------------------------------------+ 835 | Ethernet Tag ID (4 octets) | 836 +---------------------------------------+ 837 | IP Prefix Length (1 octet) | 838 +---------------------------------------+ 839 | IP Prefix (4 or 16 octets) | 840 +---------------------------------------+ 841 | GW IP Address (4 or 16 octets) | 842 +---------------------------------------+ 843 | MPLS Label (3 octets) | 844 +---------------------------------------+ 846 o BGP next-hop: IPv6 address of egress PE 847 o MPLS Label: It carries the Function part of the SRv6 SID when the 848 Transposition Scheme of encoding (Section 4) is used and otherwise 849 set to Implicit NULL. 851 SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The 852 function of the SRv6 SID is entirely up to the originator of the 853 advertisement. In practice, the behavior is End.DT4/6 or End.DX4/6. 855 6.6. EVPN multicast routes (Route Types 6, 7, 8) over SRv6 core 857 These routes do not require the advertisement of SRv6 Service TLVs 858 along with them. Similar to EVPN Route Type 4, the BGP Nexthop is 859 equal to the IPv6 address of egress PE. 861 7. Implementation Status 863 The [I-D.matsushima-spring-srv6-deployment-status] describes the 864 current deployment and implementation status of SRv6 which also 865 includes the BGP services over SRv6 as specified in this document. 867 8. Error Handling 869 In case of any errors encountered while processing SRv6 Service TLVs, 870 the details of the error SHOULD be logged for further analysis. 872 If multiple instances of SRv6 L3 Service TLV is encountered, all but 873 the first instance MUST be ignored. 875 If multiple instances of SRv6 L2 Service TLV is encountered, all but 876 the first instance MUST be ignored. 878 An SRv6 Service TLV is considered malformed in the following cases: 880 o the TLV Length is less than 1 882 o the TLV Length is inconsistent with the length of BGP Prefix-SID 883 attribute 885 o atleast one of the constituent Sub-TLVs is malformed 887 An SRv6 Service Sub-TLV is considered malformed in the following 888 cases: 890 o the Sub-TLV Length is inconsistent with the length of the 891 enclosing SRv6 Service TLV 893 An SRv6 SID Information Sub-TLV is considered malformed in the 894 following cases: 896 * the Sub-TLV Length is less than 21 898 * the Sub-TLV Length is inconsistent with the length of the 899 enclosing SRv6 Service TLV 901 * atleast one of the constituent Sub-Sub-TLVs is malformed 903 An SRv6 Service Data Sub-sub-TLV is considered malformed in the 904 following cases: 906 o the Sub-Sub-TLV Length is inconsistent with the length of the 907 enclosing SRv6 service Sub-TLV 909 Any TLV or Sub-TLV or Sub-Sub-TLV is not considered malformed because 910 its Type is unrecognized. 912 Any TLV or Sub-TLV or Sub-Sub-TLV is not considered malformed because 913 of failing any semantic validation of its Value field. 915 SRv6 overlay service requires Service SID for forwarding. The treat- 916 as-withdraw action [RFC7606] MUST be performed when at least one 917 malformed SRV6 Service TLV is present in the BGP Prefix-SID 918 attribute. 920 SRv6 SID value in SRv6 Service Sub-TLV is invalid when SID Structure 921 Sub-Sub-TLV transposition length is greater than 24 or addition of 922 transposition offset and length is greater than 128. Path having 923 such Prefix-SID Attribute should be ineligible during the selection 924 of best path for the corresponding prefix. 926 9. IANA Considerations 928 9.1. BGP Prefix-SID TLV Types registry 930 This document defines two new TLV Types of the BGP Prefix-SID 931 attribute. IANA is requested to assign Type values in the registry 932 "BGP Prefix-SID TLV Types" as follows: 934 Value Type Reference 935 -------------------------------------------- 936 4 Deprecated 937 TBD1 SRv6 L3 Service TLV 938 TBD2 SRv6 L2 Service TLV 940 The value 4 previously corresponded to the SRv6-VPN SID TLV, which 941 was specified in previous versions of this document and used by early 942 implementations of this specification. It was deprecated and 943 replaced by the SRv6 L3 Service and SRv6 L2 Service TLVs. 945 9.2. SRv6 Service Sub-TLV Types registry 947 IANA is requested to create and maintain a new registry called "SRv6 948 Service Sub-TLV Types". The allocation policy for this registry is: 950 0 : Reserved 951 1-127 : IETF Review 952 128-254 : First Come First Served 953 255 : Reserved 955 The following Sub-TLV Types are defined in this document: 957 Value Type Reference 958 ---------------------------------------------------- 959 1 SRv6 SID Information Sub-TLV 961 9.3. SRv6 Service Data Sub-Sub-TLV Types registry 963 IANA is requested to create and maintain a new registry called "SRv6 964 Service Data Sub-Sub-TLV Types". The allocation policy for this 965 registry is: 967 0 : Reserved 968 1-127 : IETF Review 969 128-254 : First Come First Served 970 255 : Reserved 972 The following Sub-Sub-TLV Types are defined in this document: 974 Value Type Reference 975 ---------------------------------------------------- 976 1 SRv6 SID Structure Sub-Sub-TLV 978 10. Security Considerations 980 This document introduces no new security considerations beyond those 981 already specified in [RFC4271]. 983 11. Acknowledgments 985 The authors of this document would like to thank Stephane Litkowski, 986 Rishabh Parekh and Xiejingrong for their comments and review of this 987 document. 989 12. Contributors 991 Satoru Matsushima 992 SoftBank 994 Email: satoru.matsushima@g.softbank.co.jp 996 Dirk Steinberg 997 Steinberg Consulting 999 Email: dws@steinberg.net 1001 Daniel Bernier 1002 Bell Canada 1004 Email: daniel.bernier@bell.ca 1006 Daniel Voyer 1007 Bell Canada 1009 Email: daniel.voyer@bell.ca 1011 Jonn Leddy 1012 Individual 1014 Email: john@leddy.net 1016 Swadesh Agrawal 1017 Cisco 1019 Email: swaagraw@cisco.com 1021 Patrice Brissette 1022 Cisco 1024 Email: pbrisset@cisco.com 1026 Ali Sajassi 1027 Cisco 1029 Email: sajassi@cisco.com 1031 Bart Peirens 1032 Proximus 1033 Belgium 1035 Email: bart.peirens@proximus.com 1036 Darren Dukes 1037 Cisco 1039 Email: ddukes@cisco.com 1041 Pablo Camarilo 1042 Cisco 1044 Email: pcamaril@cisco.com 1046 Shyam Sethuram 1047 Cisco 1049 Email: shyam.ioml@gmail.com 1051 Zafar Ali 1052 Cisco 1054 Email: zali@cisco.com 1056 Ketan Talaulikar 1057 Cisco 1059 Email: ketant@cisco.com 1061 13. References 1063 13.1. Normative References 1065 [I-D.ietf-6man-segment-routing-header] 1066 Filsfils, C., Dukes, D., Previdi, S., Leddy, J., 1067 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 1068 (SRH)", draft-ietf-6man-segment-routing-header-26 (work in 1069 progress), October 2019. 1071 [I-D.ietf-bess-evpn-igmp-mld-proxy] 1072 Sajassi, A., Thoria, S., Patel, K., Drake, J., and W. Lin, 1073 "IGMP and MLD Proxy for EVPN", draft-ietf-bess-evpn-igmp- 1074 mld-proxy-04 (work in progress), September 2019. 1076 [I-D.ietf-bess-evpn-prefix-advertisement] 1077 Rabadan, J., Henderickx, W., Drake, J., Lin, W., and A. 1078 Sajassi, "IP Prefix Advertisement in EVPN", draft-ietf- 1079 bess-evpn-prefix-advertisement-11 (work in progress), May 1080 2018. 1082 [I-D.ietf-bess-evpn-vpws-fxc] 1083 Sajassi, A., Brissette, P., Uttaro, J., Drake, J., Lin, 1084 W., Boutros, S., and J. Rabadan, "EVPN VPWS Flexible 1085 Cross-Connect Service", draft-ietf-bess-evpn-vpws-fxc-01 1086 (work in progress), June 2019. 1088 [I-D.ietf-bess-rfc5549revision] 1089 Litkowski, S., Agrawal, S., ananthamurthy, k., and K. 1090 Patel, "Advertising IPv4 Network Layer Reachability 1091 Information with an IPv6 Next Hop", draft-ietf-bess- 1092 rfc5549revision-03 (work in progress), February 2020. 1094 [I-D.ietf-spring-srv6-network-programming] 1095 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 1096 Matsushima, S., and Z. Li, "SRv6 Network Programming", 1097 draft-ietf-spring-srv6-network-programming-10 (work in 1098 progress), February 2020. 1100 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1101 Requirement Levels", BCP 14, RFC 2119, 1102 DOI 10.17487/RFC2119, March 1997, 1103 . 1105 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 1106 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 1107 DOI 10.17487/RFC2545, March 1999, 1108 . 1110 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 1111 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 1112 DOI 10.17487/RFC4271, January 2006, 1113 . 1115 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 1116 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 1117 2006, . 1119 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 1120 Reflection: An Alternative to Full Mesh Internal BGP 1121 (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, 1122 . 1124 [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, 1125 "BGP-MPLS IP Virtual Private Network (VPN) Extension for 1126 IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, 1127 . 1129 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1130 "Multiprotocol Extensions for BGP-4", RFC 4760, 1131 DOI 10.17487/RFC4760, January 2007, 1132 . 1134 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 1135 Encodings and Procedures for Multicast in MPLS/BGP IP 1136 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 1137 . 1139 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 1140 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 1141 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 1142 2015, . 1144 [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. 1145 Patel, "Revised Error Handling for BGP UPDATE Messages", 1146 RFC 7606, DOI 10.17487/RFC7606, August 2015, 1147 . 1149 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1150 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1151 May 2017, . 1153 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1154 (IPv6) Specification", STD 86, RFC 8200, 1155 DOI 10.17487/RFC8200, July 2017, 1156 . 1158 [RFC8214] Boutros, S., Sajassi, A., Salam, S., Drake, J., and J. 1159 Rabadan, "Virtual Private Wire Service Support in Ethernet 1160 VPN", RFC 8214, DOI 10.17487/RFC8214, August 2017, 1161 . 1163 [RFC8317] Sajassi, A., Ed., Salam, S., Drake, J., Uttaro, J., 1164 Boutros, S., and J. Rabadan, "Ethernet-Tree (E-Tree) 1165 Support in Ethernet VPN (EVPN) and Provider Backbone 1166 Bridging EVPN (PBB-EVPN)", RFC 8317, DOI 10.17487/RFC8317, 1167 January 2018, . 1169 [RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R., 1170 Uttaro, J., and W. Henderickx, "A Network Virtualization 1171 Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365, 1172 DOI 10.17487/RFC8365, March 2018, 1173 . 1175 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1176 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1177 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1178 July 2018, . 1180 [RFC8669] Previdi, S., Filsfils, C., Lindem, A., Ed., Sreekantiah, 1181 A., and H. Gredler, "Segment Routing Prefix Segment 1182 Identifier Extensions for BGP", RFC 8669, 1183 DOI 10.17487/RFC8669, December 2019, 1184 . 1186 13.2. Informative References 1188 [I-D.ietf-idr-segment-routing-te-policy] 1189 Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., 1190 Rosen, E., Jain, D., and S. Lin, "Advertising Segment 1191 Routing Policies in BGP", draft-ietf-idr-segment-routing- 1192 te-policy-08 (work in progress), November 2019. 1194 [I-D.ietf-spring-segment-routing-policy] 1195 Filsfils, C., Sivabalan, S., Voyer, D., Bogdanov, A., and 1196 P. Mattes, "Segment Routing Policy Architecture", draft- 1197 ietf-spring-segment-routing-policy-06 (work in progress), 1198 December 2019. 1200 [I-D.matsushima-spring-srv6-deployment-status] 1201 Matsushima, S., Filsfils, C., Ali, Z., and Z. Li, "SRv6 1202 Implementation and Deployment Status", draft-matsushima- 1203 spring-srv6-deployment-status-05 (work in progress), 1204 January 2020. 1206 Authors' Addresses 1208 Gaurav Dawra (editor) 1209 LinkedIn 1210 USA 1212 Email: gdawra.ietf@gmail.com 1214 Clarence Filsfils 1215 Cisco Systems 1216 Belgium 1218 Email: cfilsfil@cisco.com 1219 Robert Raszuk 1220 Bloomberg LP 1221 USA 1223 Email: robert@raszuk.net 1225 Bruno Decraene 1226 Orange 1227 France 1229 Email: bruno.decraene@orange.com 1231 Shunwan Zhuang 1232 Huawei Technologies 1233 China 1235 Email: zhuangshunwan@huawei.com 1237 Jorge Rabadan 1238 Nokia 1239 USA 1241 Email: jorge.rabadan@nokia.com