SRv6 Inter Domain Routing Architecture

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 11 May 2025.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

This draft describes the SRv6 Inter Domain routing architecture with IP VPN and EVPN overlays and seamlessly stitching the overlays across inter domain boundaries. This draft analyzes the SRv6 Design and Operational considerations regarding SRv6 Inter Domain routing and the SRv6 forwarding plane. This draft also describes three real world use cases of SRv6 Compression Next CSID and operational considrations with regards to SRv6 inter domain routing.¶

[RFC4364] describes BGP/MPLS IPv4 VPN and [RFC4659] describes BGP/MPLS IPv6 VPN. [RFC4364] describes BGP/MPLS IPv4 VPN Section 10 (a) describes Inter-AS Options A known as back to back PE-CE style peering, Section (b) Inter-AS Option B BGP-LU with Direct eBGP peering VPN overlay, Section (c) describes Inter-AS Option-C ASBR to ASBR interdomain loopbacks advertised with RR to RR eBGP multihop peering with next-hop unchangd.¶

With SRv6 MPLS Inter-AS options described in [RFC4364] and [RFC4659] are not applicable. However the knobs and concepts used in overaly stitching are still very applicable and are used with SRv6. SRv6 Service SID refers to the SRv6 specific endpoint behaviors defined in SRv6 Programming [RFC8986]. In this draft we discuss in detail the end to end service stitching of the L2 VPN EVPN and IP VPN SRv6 Service SID endpoint behaviors which includes L2 VPN endpoint behaviors End.DX2, End.DX2V, End.DX2U, End.DX2M and IP VPN endpoint behaviors End.DX4, End.DX6, End.DT4 and End.DT6.¶

SRv6 inter domain routting L2 VPN EVPN and IP VPN SRv6 service stitching is applicable to SRv6 Programming [RFC8986] 128 bit full SID and SRv6 Compression [I-D.ietf-spring-srv6-srh-compression] C-SID Next C-SID (uSID) endpoint flavor and Replace SID C-SID (G-SID) endpoint flavor.¶

[RFC9252] describes BGP Overlay services over SRv6 forwarding plane. For SRv6 Best effort (BE) service, the egress PE signals an SRv6 service SID with ingress PE for the BGP service overlay route. The ingress PE encapsulates the payload packet from the CE in an outer IPv6 header where the desitnation address is the SRv6 Service SID provided by the egress PE. In this case the underlay intermediate notes only need to support IPv6 data plane. In order to provide SRv6 service with an SLA from ingress PE to egress PE, the ingress PE colors the overlay service route with a color extended community [RFC9012] so the overlay color extended community maps to SR Policy [RFC9012], overlay color to underlay intent mapping. The ingress PE encapsulates the payload paacket from the CE in an outer IPv6 header with SR Policy candidate SID list related to the SLA path bound to the forwarding plane with Binding SID (BSID) set with the SRv6 service SID associated with the overlay service route active segment in the SRH for 128 bit Full SID or SRv6 Compression Next SID carrier uN endpoint function to forward along the static SID list or dynamic SID list path end to end steering.¶

SRv6 Prefix SID attribute [RFC8669] is extended by [RFC9252] to carry the SRv6 L2 VPN and IP VPN Service SIDs and their associated information in BGP NLRI AFI / SAFI. SRv6 L3 Service TLV encodes the service SID information for the SRv6 based L3 services providing the equivalent functionality of MPLS service label when received with a Layer 3 Service route as defined in BGP/MPLS VPN-IPv4 [RFC4364] and BGP/MPLS VPN-IPv6 [RFC4659]. Essentially the SRv6 L3 Service TLV encodes the L3 Service SID for SRv6 based services as an MPLS label for SRv6 Programming [RFC8986] endpoint behaviors End.DX4, End.DX6, End.DT4 and End.DT6. SRv6 L2 Service TLV encodes the service SID information for the SRv6 based L2 services providing the equivalent functionality of MPLS service label for an Ethernet VPN (EVPN) Route Types for L2 services as defined in BGP/MPLS EVPN [RFC7432]. Essentially the SRv6 L2 Service TLV encodes the L2 VPN Service SID for SRv6 based services as an MPLS label for SRv6 Programming [RFC8986] endpoint behaviors End.DX2, End.DX2V, End.DX2U, End.DX2M.¶

[RFC9252] defines the encoding of the SRv6 SID information. The SRv6 Service SIDs for a BGP service prefix is carried in the SRv6 Service TLVs of the BGP Prefix SID attribute as described above [RFC8669]. BGP services such as IP VPN BGP/MPLS VPN-IPv4 [RFC4364] and BGP/MPLS VPN-IPv6 [RFC4659] where Per VRF SID allocation is used End.DT4 and End.DT6 endpoint behaviors the same SID is shared across multiple NLRIs, thus providing efficient packing. However for BGP services such as Ethernet VPN (EVPN) [RFC7432] and VPLS / H-VPLS where where per-PW SID allocation is required such as for End.DX2 endpoint behavior, each NLRI would have its own unique SID, resulting in inefficient update packing. [RFC9252] defines an efficient method for update packing for cases such as EVPN NLRI using a transposition scheme, where the SRv6 SID Structure Sub-Sub-TLV describes the sizes of the parts of the SRv6 SID and indicates the offsets such that the common part locator is encoded into the BGP Prefix SID attribute and the variable part Service label encoded into the func / arg field of the SRv6 Service SID is encoded into the NLRI.¶

This draft describes how to successfully implement end to end inter domain routing over an SRv6 forwarding plane where the L2 VPN EVPN and IP VPN overlay services SRv6 Service SIDs can be stitched end to end.¶

[RFC9252] BGP Service Overlay Section 2 last 2 paragraphs discusses the use of Next hop Unchanged (NHU) operational guideline at all eBGP boundaries to signal End-to-End SID. The signaling must be done on both side of the eBGP peering for the SID to be propagated End-to-End in both directions. A BGP speaker receiving a route containing the BGP Prefix-SID attribute with one or more SRv6 service TLVs observes the following rules when advertising the received route to other peers:¶

[RFC9252] Rule-1: BGP Service Overlay Section 2 2nd to last paragraph - SID not signalled when the Next hop is changed. If the BGP Next Hop is changed, the TLVs, Sub TLVs, or Sub-Sub-TLVs SHOULD be updated with the locally allocated SRv6 SID information from the SID Manager. Any received Sub-TLVs and Sub-Sub-TLVs that are unrecognized must be removed. SRv6 summary locators are advertised for all Algo's between domains for reachability inter domain routing. When the next hop changes between the inter-as PE for L2 VPN or L3 VPN service route the inter domain loopback propagated however since the next hop changes on the eBGP peering the next hop is set to the directly connected eBGP subnet and not the Loopback for the service route and has the locally generated SRv6 Service SID resulting in SID not signalled end to end.¶

[RFC9252] Rule-2: BGP Service Overlay Section 2 last paragraph - Solutoin for propagating L2 VPN and L3 VPN SRv6 Service SID end to end If the BGP Next Hop is Unchanged during the advertisement, the SRv6 Service TLVs, including any unrecognized types of of Sub-TLVs and Sub-Sub-TLVs, SHOULD be propagated further. In addition, all Reserved fields in the TLV, Sub-TLV, or Sub-Sub-TLV MUST be propagated Unchanged. When the next hop is unchanged between the inter-as PE for L2 VPN or L3 VPN service route the inter domain Loopback is now propagated and has the SRv6 Service SID propagated resulting in SRv6 Data Plane being intact and working end to end.¶

2. Terminology

Terminolgoy used in defining the SRv6 Inter Domain Routing specification.¶

IDR: SRv6 Inter Domain Routing End to End¶

NH: BGP Next Hop¶

NHC: BGP Next Hop Changed¶

NHU: BGP Next Hop Unchanged¶

NHS: BGP Next Hop Self¶

Service SID Preserved: Service SID is does not change and is propagated¶

Service SID Locally Generated: Service SID is locally generated by SRv6 SID Manager¶

3. SRv6 Inter Domain Routing Topology

SRv6 Inter Domain Routing topology is made up of a two domains. Domain-1 AS1 is made up of PE1 and PE2 which have iBGP peering between them. Domain-2 AS2 is made up of PE3. PE2 is the inter-as ASBR eBGP peering to AS2 PE3 ASBR. ALl nodes PE1, PE2 and PE3 are running [I-D.ietf-spring-srv6-srh-compression] C-SID Next C-SID (uSID) endpoint flavor.¶

                             SRv6 Next SID Topology


  Loc:fc00:0:1::/48             Loc:fc00:0:2::/48       Loc:fc00:0:3::/48
  Lo0:fc00:0:1::1               Lo0:fc00:0:2::1         Lo0:fc00:0:3::1
   +-------+                     +-------+                    +-------+
   |   AS1 |2001:1::2/127        |   AS1 |       2001:1::5/127|  AS2  |
   |   PE1 |---------------------|   PE2 |--------------------|  PE3  |
   |       |        2001:1::3/127| (ASBR)|2001:1::4/127       |(ASBR) |
   +-------+                     +-------+                    +-------+

             iBGP (Remote Peer)             eBGP (Local Peer)

4. SRv6 Inter Domain Routing - Inter-AS Local Peer

         eBGP Direct Peering  (NHC = Next Hop Changed) - (Local Peer)
                           ::4 - ::5 - SID Changes

          Loc:fc00:0:2::/48           Loc:fc00:0:3::/48
          Lo0:fc00:0:2::1             Lo0:fc00:0:3::1
         +-------+                    +-------+
         |   AS1 |       2001:1::5/127|  AS2  |
         |   PE2 |--------------------|  PE3  |
         | (ASBR)|2001:1::4/127       |(ASBR) |
         +-------+                    +-------+
         NHC:2001:1::4
         vpn sid:fc00:0:2::db8a::

                       eBGP (Local Peer)


 If R2 advertised with NHC 2001:1::4
 vpn sid not preserved fc00:0:1:db8a::
 when NH changes the service sid changes
 R3 Sees valid/best path but SID is locally generated

        eBGP Direct Peering  (NHU = Next Hop Unchanged) - (Local Peer)


          Loc:fc00:0:2::/48           Loc:fc00:0:3::/48
          Lo0:fc00:0:2::1             Lo0:fc00:0:3::1
         +-------+                    +-------+
         |   AS1 |       2001:1::5/127|  AS2  |
         |   PE2 |--------------------|  PE3  |
         | (ASBR)|2001:1::4/127       |(ASBR) |
         +-------+                    +-------+
         NHU:fc00:0:2::1
         vpn sid:fc00:0:2::e005::

                       eBGP (Local Peer)


 If R2 advertised with NHU fc00:0:2::1
 vpn sid is preserved fc00:0:1:e005::
 when NH changes the service sid changes
 R3 sees valid/best path next hop is accessible

5. SRv6 Inter Domain Routing E2E - Inter-AS Remote Peer

              SRv6 SID not signalled     (NHC = Next Hop Changed)
                                                      ::4 - ::5
              NHS re-write Loopback0
  Loc:fc00:0:1::/48             Loc:fc00:0:2::/48       Loc:fc00:0:3::/48
  Lo0:fc00:0:1::1               Lo0:fc00:0:2::1         Lo0:fc00:0:3::1
   +-------+                     +-------+                    +-------+
   |   AS1 |2001:1::2/127        |   AS1 |       2001:1::5/127|  AS2  |
   |   PE1 |---------------------|   PE2 |--------------------|  PE3  |
   |       |        2001:1::3/127| (ASBR)|2001:1::4/127       |(ASBR) |
   +-------+                     +-------+                    +-------+
NHC:fc00:0:1::1           NHC:2001:1::4              NHC:2001:1::4
vpn sid:fc00:0:1::abdf::  vpn sid:fc00:0:2::db8a::   vpn sid:fc00:0:2::db8a::

             iBGP (Remote Peer)             eBGP (Local Peer)
    ---------------------------------------------------------------->>
NHC:fc00:0:1::1          If R2 advertises with NHC 2001:1::4
vpn sid:fc00:0:1::abdf:: vpn sid not preserved fc00:0:2::db8a::
SID Not Preserved        R3 sees valid/best but sid locally generated on PE2

                 SRv6 SID Signalled       (NHU = Next Hop Unchanged)
                                                      ::4 - ::5
             No NHS re-write Loopback0
  Loc:fc00:0:1::/48             Loc:fc00:0:2::/48           Loc:fc00:0:3::/48
  Lo0:fc00:0:1::1               Lo0:fc00:0:2::1             Lo0:fc00:0:3::1
   +-------+                     +-------+                    +-------+
   |   AS1 |2001:1::2/127        |   AS1 |       2001:1::5/127|  AS2  |
   |   PE1 |---------------------|   PE2 |--------------------|  PE3  |
   |       |        2001:1::3/127| (ASBR)|2001:1::4/127       |(ASBR) |
   +-------+                     +-------+                    +-------+
NHU:fc00:0:1::1           NHU:fc00:0:1::1           NHU:fc00:0:1::1
vpn sid:fc00:0:1::e006::  vpn sid:fc00:0:1::e006::  vpn sid:fc00:0:1::e006::

              iBGP (Remote Peer)             eBGP (Local Peer)
  ---------------------------------------------------------------->>
   If R1 advertises with NHC fc00:0:1::1
   vpn sid preserved fc00:0:1::e006::
   R2 sees valid/best NH is accessible

                                   If R2 advertises with NHC fc00:0:1::1
                                   vpn sid preserved fc00:0:1::e006::
                                   R3 sees valid/best NH is accessible

6. Operational Considerations

Operational Guidance to always use Next-Hop-Unchanged (NHU) on all eBGP boundaries on both sides of the eBGP peering to signal "End to End SID" for SID propagation End-to-End in both directions.¶

Operational Guidance to not use Next-Hop-Self on iBGP PE-RR peering so that the received service SID from an Ingress Domain is propagated "End to End" to an Egress Domain and vice versa in both directions.¶

Operational Guidance is applicable to both SRv6 (Full SID) and SRv6 compression.¶

7. IANA Considerations

There are not any IANA considerations.¶

8. Security Considerations

No new extensions are defined in this document. As such, no new security issues are raised beyond those that already exist in BGP-4 and use of MP-BGP for IPv6.¶

The security features of BGP and corresponding security policy defined in the ISP domain are applicable.¶

For the inter-AS distribution of IPv6 prefixes according to case (a) of Section 4 of this document, no new security issues are raised beyond those that already exist in the use of eBGP for IPv6 [RFC2545].¶

9. Acknowledgments

Appendix A. APPENDIX-A

SRv6 Compression [I-D.ietf-spring-srv6-srh-compression] C-SID Next C-SID (uSID) endpoint flavor Inter Domain Routing development work is all contained in GitHub link below.¶

https://github.com/segmentrouting/srv6-labs/tree/main/3-srv6-dc-case-studies¶

Authors' Addresses