Extension to BGP's Route Refresh Message
draft-idr-bgp-route-refresh-options-05

Document Type Expired Internet-Draft (individual)
Last updated 2019-03-02 (latest revision 2018-08-29)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-idr-bgp-route-refresh-options-05.txt

Abstract

[RFC2918] defines a route refresh capability to be exchanged between BGP speakers. BGP speakers that support this capability are advertising that they can resend the entire BGP Adj-RIB-Out on receipt of a refresh request. By supporting this capability, BGP speakers are more flexible in applying any inbound routing policy changes as they no longer have to store received routes in their unchanged form or reset the session when an inbound routing policy change occurs. The route refresh capability is advertised per AFI, SAFI combination. There are newer AFI, SAFI types that have been introduced to BGP that support a variety of route types (e.g. IPv4/MVPN, L2VPN/EVPN). Currently, there is no way to request a subset of routes in a Route Refresh message for a given AFI, SAFI. This draft defines route refresh capability extensions that help BGP speakers to request a subset of routes for a given address family. This is expected to reduce the amount of update traffic being generated by route refresh requests as well as lessen the burden on the router servicing such requests.

Authors

Keyur Patel (keyur@arrcus.com)
Aamod Vyavaharkar (avyavaha@cisco.com)
Niloofar Fazlollahi (niloofar_fazlollahi@yahoo.com)
Tony Przygienda (prz@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)