| Inter-Domain Routing | |
| Internet-Draft | |
| Intended status: Standards Track | G. Dawra, Ed. |
| Expires: September 13, 2017 | C. Filsfils |
| D. Dukes | |
| P. Brissette | |
| P. Camarilo | |
| Cisco Systems | |
| J. Leddy | |
| Comcast | |
| D. Voyer | |
| D. Bernier | |
| Bell Canada | |
| D. Steinberg | |
| Steinberg Consulting | |
| R. Raszuk | |
| Bloomberg LP | |
| B. Decraene | |
| Orange | |
| S. Matsushima | |
| SoftBank Telecom Japan | |
| March 12, 2017 |
BGP Signaling of IPv6-Segment-Routing-based VPN Networks
draft-dawra-bgp-srv6-vpn-00.txt
This draft defines procedures and messages for BGP SRv6-based EVPNs and L3 VPNs. It builds on RFC7432 “BGP MPLS-Based Ethernet VPN” and RFC4364 “BGP/MPLS IP Virtual Private Networks (VPNs)” to provide a migration path from MPLS-based VPNs to SRv6 based VPNs.
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 http://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 September 13, 2017.
Copyright (c) 2017 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 (http://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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
SRv6 refers to Segment Routing instantiated on the IPv6 dataplane [I-D.filsfils-spring-srv6-network-programming][I-D.ietf-6man-segment-routing-header].
SRv6-based VPN (SRv6-VPN) refers to the creation of VPN between PE’s leveraging the SRv6 dataplane and more specifically the END.DT* (crossconnect to a VRF) and END.DX* (crossconnect to a nexthop) functions defined in the SRv6 network programming document [I-D.filsfils-spring-srv6-network-programming]. SRv6-L3VPN refers to the creation of Layer3 VPN service between PE’s supporting an SRv6 data plane.
SRv6 SID refers to a SRv6 Segment Identifier as defined in [I-D.filsfils-spring-srv6-network-programming].
SRv6-VPN SID refers to an SRv6 SID that MAY be associated with one of the END.DT or END.DX functions as defined in [I-D.filsfils-spring-srv6-network-programming].
To provide SRv6-VPN service with best-effort connectivity, the egress PE signals an SRv6-VPN SID with the VPN route. The ingress PE encapsulates the VPN packet in an outer IPv6 header where the destination address is the SRv6-VPN SID provided by the egress PE. The underlay between the PE’s only need to support plain IPv6 forwarding [RFC2460].
To provide SRv6-VPN service in conjunction with an underlay SLA from the ingress PE to the egress PE, the egress PE colors the VPN route with a color extended community. The ingress PE encapsulates the VPN packet in an outer IPv6 header with an SRH that contains the SR policy associated with the related SLA followed by the SRv6-VPN SID associated with the route. The underlay nodes whose SRv6 SID’s are part of the SRH must support SRv6 data plane.
BGP is used to advertise the reachability of prefixes in a particular VPN from an egress Provider Edge (egress-PE) to ingress Provider Edge (ingress-PE) nodes.
This document describes how existing BGP messages between PEs may carry SRv6 Segment IDs (SIDs) as the means to interconnect PEs and form VPNs.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
BGP egress nodes (egress-PEs) advertise a set of reachable prefixes. Standard BGP update propagation schemes [RFC4271], which MAY make use of route reflectors [RFC4456], are used to propagate these prefixes. BGP ingress nodes (ingress-PE) receive these advertisements and may add the prefix to the RIB in an appropriate VRF.
For PEs supporting SRv6 the egress-PE advertises an SRv6-VPN SID with VPN routes. This SRv6-VPN SID only has local significance at the egress-PE where it is allocated or configured on a per-CE or per-VRF basis. In practice the SID encodes a cross-connect to a specific Address Family table (END.DT) or next-hop/interface (END.DX) as defined in the SRv6 Network Programming Document [I-D.filsfils-spring-srv6-network-programming]
The SRv6 VPN SID MAY be routable within the AS of the egress-PE and serves the dual purpose of providing reachability between ingress-PE and egress-PE while also encoding the VPN identifier.
For each NLRI, the egress-PE includes a new optional, transitive BGP SRv6-VPN SID Path TLV as part of the BGP Prefix-SID Attribute[I-D.ietf-idr-bgp-prefix-sid]. It contains a list of SIDs, for L3VPN only a single SRv6-VPN SID is necessary. See Section 3.1 below for details on the SRv6-VPN SID TLV.
At an ingress-PE, BGP installs the advertised prefix in the correct RIB table, recursive via an SR Policy leveraging the received SRv6-VPN SID.
Assuming best-effort connectivity to the egress PE, the SR policy has a single path with a single SID list made of a single SID: the SRv6-VPN SID received with the related route.
When the VPN route is colored with an extended color community C and the SID is next-hop N and the ingress PE has a valid SRv6 Policy (N, C) associated with SID list <S1,S2, S3> [I-D.filsfils-spring-segment-routing-policy] then the SR Policy is <S1, S2, S3, SRv6-VPN SID>.
Multiple VPN routes MAY recurse on the same SR Policy.
The SRv6-VPN SID TLV is defined as another TLV for BGP-Prefix-SID Attribute [I-D.ietf-idr-bgp-prefix-sid]. The value field of the BGP Prefix SID attribute is defined here to be a set of elements encoded as "Type/Length/Value" (i.e., a set of TLVs). Type for SRv6-VPN SID TLV is defined to be TBD.
The IPv6-SID TLV MUST be present in the Prefix-SID attribute attached to MP-BGP VPN NLRI defined in [RFC4659][RFC5549][RFC7432] when egress-PE is capable of SRv6 data-plane.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SRv6 SID information(Variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SRv6 SID information is encoded as follows:
+---------------------------------------+
| SID Type (1 Octet) |
+---------------------------------------+
| SRv6 SID (16 octet) |
+---------------------------------------+
Where:
Current Type of SID defined as:
IPv4 VPN Over IPv6 Core is defined in [RFC5549], the MP_REACH_NLRI is encoded as follows for an SRv6 Core:
SRv6-VPN SID are encoded as part of the SRv6-VPN SID TLV defined in Section 3.1. The function of the SRv6 SID is entirely up to the originator of the advertisement. In practice the function would likely be End.DX4 or End.DT4.
IPv6 VPN over IPv6 Core is defined in [RFC4659], the MP_REACH_NLRI is enclosed as follows for an SRv6 Core:
SRv6-VPN SID are encoded as part of the SRv6-VPN SID TLV defined in Section 3.1. The function of the IPv6 SRv6 SID is entirely up to the originator of the advertisement. In practice the function would likely be End.DX6 or End.DT6.
Migration from IPv4 MPLS based underlay to an SRv6 underlay with BGP speakers is achieved with BGP sessions per BGP instance, one for IPv4 and a one for IPv6. Migration from IPv4 to IPv6 is independent of SRv6 BGP endpoints, and the selection of which route to use (received via the IPv4 or IPv6 session) is a local configurable decision of the ingress-PE, and is outside the scope of this document.
At Egress-PE
If BGP offers an SRv6-VPN service
Then BGP allocates an SRv6-VPN SID for the VPN service
and adds the BGP SRv6-VPN SID TLV while advertising VPN prefixes.
If BGP offers an MPLS VPN service
Then BGP allocates an MPLS Label for the VPN service and
use it in NLRI as normal for MPLS L3 VPNs.
At Ingress-PE
*Selection of which encapsulation below (SRv6-VPN or MPLS-VPN) is
defined by local BGP policy
If BGP supports SRv6-VPN service, and
receives a BGP SRv6-VPN SID Attribute with an SRv6 SID
Then BGP programs the destination prefix in RIB recursive via
the related SR Policy.
If BGP supports MPLS VPN service, and
the MPLS Label is not Implicit-Null
Then the MPLS label is used as a VPN label and inserted with the
prefix into RIB via the BGP Nexthop.
Migration from IPv6 MPLS based underlay to an SRv6 underlay with BGP speakers is achieved with a few simple rules at each BGP speaker.
The EVPN SRv6 solution is actively under definition and will be added in a later revision.
When a BGP Speaker receives a BGP Update message containing a malformed SRv6-VPN SID TLV, it MUST ignore the received BGP attributes and not pass it to other BGP peers. This is equivalent to the -attribute discard- action specified in [RFC7606]. When discarding an attribute, a BGP speaker MAY log an error for further analysis.
This memo includes no request to IANA.
This document introduces no new security considerations beyond those already specified in [RFC4271] and [RFC3107].
This document proposes extensions to the BGP to allow advertising certain attributes and functionalities related to SRv6.
Bart Peirens Proximus Belgium Email: bart.peirens@proximus.com