]> Cisco

170 W. Tasman Drive San Jose 95134 CA USA kriswamy@cisco.com

Cisco

170 W. Tasman Drive San Jose 95134 CA USA mankamis@cisco.com

Cisco

170 W. Tasman Drive San Jose 95134 CA USA lkrattig@cisco.com

Arrcus

keyur@arrcus.com

Routing Inter-Domain Routing BGP BGP supports different route types, which defines the encoding of Network Layer Reachability Information (NLRI) for a some of the Address Family Identifier (AFI)/Subsequent Address Family Identifier (SAFI) like Ethernet VPN (EVPN), Multicast VPN(MVPN) and so on. BGP speaker will reset the BGP session if a given route type is not supported. This document defines an Optional Capabilities to exchange the route types supported for a given AFI/SAFI such that session are not reset. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

BGP Ethernet VPN (EVPN), Multicast VPN(MVPN), and other address families support multiple route types. Different route types will have different key lengths consisting of multiple fields which are used as a BGP Route Key. If a particular route type is not supported on a BGP speaker then the session will be reset as there is no way to determine the key. When a new Route-type is added to EVPN, MVPN and any other address families that support route types, then all routers in the network to be updated to make sure that there is no session reset. Resetting a BGP session is expensive as we have seen from deployments that multiple AFI/SAFI are negotiated between the BGP neighbors and resetting a session will impact the network adversely. This document defines an optional capability exchange of route types per AFI/SAFI such that BGP speakers negotiate the route types and only if the neighbor has advertised a particular route-type capability support then only advertise the given route-type in MP_REACH_NLRI.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The Rout type capability is a new BGP capability [ that can be used by BGP speaker to indicate the route types of a given AF/SAFI supported. This capability is defined as follows: Capability code: To be assigned by IANA Capability length: variable Capability value: Consists of 0 to 63 of the tuples "AFI, SAFI, Route-Type length and Route-type values for address family"

The AFI and SAFI, taken in combination, indicate that Route-types supported for routes that are advertised with the same AFI and SAFI. Route-types may be explicitly associated with a AFI and SAFI using the encoding of [BGP-MP] Route-Type length: This field specifies the total length in octets, of Route-Types field. Route-Type: This field specifies the Route-Types. A speaker that supports multiple "AFI, SAFI" tuples that requires route-type capability exchanges includes them as multiple Capabilities in the Capabilities Optional Parameter. If route type capabilities are exchanged between BGP speakers for a specific AFI/SAFI, and the BGP peer does not support a particular route type, that route should not be advertised to the peer.

TBD

TBD

This document defines a new optional route type capability dnd request the BGP optional capability registry:

Contributors In addition to the authors listed on the front page, the following coauthors have also contributed to this document: