draft-ietf-idr-bgp-enhanced-route-refresh-07.txt   draft-ietf-idr-bgp-enhanced-route-refresh-08.txt 
IDR K. Patel IDR K. Patel
Internet-Draft E. Chen Internet-Draft E. Chen
Updates: 2918 (if approved) Cisco Systems Updates: 2918 (if approved) Cisco Systems
Intended status: Standards Track B. Venkatachalapathy Intended status: Standards Track B. Venkatachalapathy
Expires: December 7, 2014 Expires: December 8, 2014
June 5, 2014 June 6, 2014
Enhanced Route Refresh Capability for BGP-4 Enhanced Route Refresh Capability for BGP-4
draft-ietf-idr-bgp-enhanced-route-refresh-07.txt draft-ietf-idr-bgp-enhanced-route-refresh-08.txt
Abstract Abstract
In this document we enhance the existing BGP route refresh mechanisms In this document we enhance the existing BGP route refresh mechanisms
to provide for the demarcation of the beginning and the ending of a to provide for the demarcation of the beginning and the ending of a
route refresh. The enhancement can be used to facilitate correction route refresh. The enhancement can be used to facilitate correction
of BGP RIB inconsistencies in a non-disruptive manner. of BGP RIB inconsistencies in a non-disruptive manner.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 7, 2014. This Internet-Draft will expire on December 8, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 51 skipping to change at page 3, line 51
Before the speaker starts a route refresh that is either initiated Before the speaker starts a route refresh that is either initiated
locally, or in response to a "normal route refresh request" from the locally, or in response to a "normal route refresh request" from the
peer, the speaker MUST send a BoRR message. After the speaker peer, the speaker MUST send a BoRR message. After the speaker
completes the re-advertisement of the entire Adj-RIB-Out to the peer, completes the re-advertisement of the entire Adj-RIB-Out to the peer,
it MUST send an EoRR message. it MUST send an EoRR message.
Conceptually the "entire Adj-RIB-Out" for a peer in this section Conceptually the "entire Adj-RIB-Out" for a peer in this section
refers to all the route entries in the "Adj-RIB-Out" for the peer at refers to all the route entries in the "Adj-RIB-Out" for the peer at
the start of the route refresh operation. These route entries the start of the route refresh operation. These route entries
comprise of both, the reachability as well as unreachability comprise both the reachability as well as unreachability information.
information. When a route entry in the "ADJ-RIB-Out" changes, only
the modified route entry needs to be advertised. When a route entry in the "Adj-RIB-Out" changes, only the modified
route entry needs to be advertised.
In processing a ROUTE-REFRESH message from a peer, the BGP speaker In processing a ROUTE-REFRESH message from a peer, the BGP speaker
MUST examine the "message subtype" field of the message and take the MUST examine the "message subtype" field of the message and take the
appropriate actions. The message processing rules for ROUTE-REFRESH appropriate actions. The message processing rules for ROUTE-REFRESH
message with subtype of 0 are described in [RFC2918] and [RFC5291]. message with subtype of 0 are described in [RFC2918] and [RFC5291].
A BGP speaker can receive a BoRR message from a peer at anytime, A BGP speaker can receive a BoRR message from a peer at any time,
either as a result of a peer responding to a ROUTE-REFESH message, or either as a result of a peer responding to a ROUTE-REFESH message, or
as a result of a peer unilaterally initiating a route refresh. When as a result of a peer unilaterally initiating a route refresh. When
a BGP speaker receives a BoRR message from a peer, it MUST mark all a BGP speaker receives a BoRR message from a peer, it MUST mark all
the routes with the given <AFI, SAFI> from that peer as stale. As it the routes with the given <AFI, SAFI> from that peer as stale. As it
receives routes from its peer's subsequent Adj-RIB-Out re- receives routes from its peer's subsequent Adj-RIB-Out re-
advertisement, these replace any corresponding stale routes. When a advertisement, these replace any corresponding stale routes. When a
BGP speaker receives an EoRR message from a peer, it MUST immediately BGP speaker receives an EoRR message from a peer, it MUST immediately
remove any routes from the peer that are still marked as stale for remove any routes from the peer that are still marked as stale for
that <AFI, SAFI>. Such purged routes MAY be logged for future that <AFI, SAFI>. Such purged routes MAY be logged for future
analysis. A BGP speaker MAY ignore any EoRR message received without analysis. A BGP speaker MAY ignore any EoRR message received without
skipping to change at page 4, line 35 skipping to change at page 4, line 36
An implementation MAY impose a locally configurable upper bound on An implementation MAY impose a locally configurable upper bound on
how long it would retain any stale routes. Once the upper bound is how long it would retain any stale routes. Once the upper bound is
reached, the implementation MAY remove any routes from the peer that reached, the implementation MAY remove any routes from the peer that
are still marked as stale for that <AFI, SAFI> without waiting for an are still marked as stale for that <AFI, SAFI> without waiting for an
EoRR message. EoRR message.
The following procedures are specified in order to simplify the The following procedures are specified in order to simplify the
interaction with the BGP Graceful Restart [RFC4724]. In particular, interaction with the BGP Graceful Restart [RFC4724]. In particular,
these procedures ensure that End-of-RIB (EoR) defined in Graceful these procedures ensure that End-of-RIB (EoR) defined in Graceful
Restart and EoRR as defined in this specification are kept separate, Restart and EoRR as defined in this specification are kept separate,
thereby avoiding any premature cleanup of stale routes. For a BGP thereby avoiding any premature cleanup of stale routes. For a BGP
speaker that supports the BGP Graceful Restart, it MUST NOT send a speaker that supports the BGP Graceful Restart, it MUST NOT send a
BoRR for an AFI/SAFI to a neighbor before it sends the EOR for the BoRR for an AFI/SAFI to a neighbor before it sends the EoR for the
AFI/SAFI to the neighbor. A BGP speaker that has received the AFI/SAFI to the neighbor. A BGP speaker that has received the
Graceful Restart Capability from its neighbor, MUST ignore any BoRRs Graceful Restart Capability from its neighbor, MUST ignore any BoRRs
for an AFI/SAFI from the neighbor before the speaker receives the EoR for an AFI/SAFI from the neighbor before the speaker receives the EoR
for the given AFI/SAFI from the neighbor. The BGP speaker SHOULD log for the given AFI/SAFI from the neighbor. The BGP speaker SHOULD log
an error of the condition for further analysis. an error of the condition for further analysis.
5. Error Handling 5. Error Handling
This document defines a new NOTIFICATION error code: This document defines a new NOTIFICATION error code:
skipping to change at page 5, line 44 skipping to change at page 5, line 44
Under "Border Gateway Protocol (BGP) Parameters": Under "Border Gateway Protocol (BGP) Parameters":
Registry: "BGP Route Refresh Subcodes" Registry: "BGP Route Refresh Subcodes"
Reference: [draft-ietf-idr-bgp-enhanced-refresh-06.txt] Reference: [draft-ietf-idr-bgp-enhanced-refresh-06.txt]
Registration Procedure(s): Values 0-127 Standards Action, values Registration Procedure(s): Values 0-127 Standards Action, values
128-254 First Come, First Served, Value 255 reserved 128-254 First Come, First Served, Value 255 reserved
Value Code Reference Value Code Reference
0 Route-Refresh [RFC2918], [RFC5291] 0 Route-Refresh [RFC2918], [RFC5291]
1 BoRR [draft-ietf-idr-bgp-enhanced-refresh-06.txt] 1 BoRR [draft-ietf-idr-bgp-enhanced-refresh-06.txt]
2 EoRR [draft-ietf-idr-bgp-enhanced-refresh-06.txt] 2 EoRR [draft-ietf-idr-bgp-enhanced-refresh-06.txt]
255 Reserved 3-255 Reserved
In addition, this document defines an NOTIFICATION error code and In addition, this document defines an NOTIFICATION error code and
several error subcodes for the ROUTE-REFRESH message. The several error subcodes for the ROUTE-REFRESH message. The
NOTIFICATION error code need to be registered with the IANA. We NOTIFICATION error code needs to be registered with the IANA. We
request IANA to create a new registry for the error subcodes as request IANA to create a new registry for the error subcodes as
follows: follows:
Under "BGP Error Subcodes": Under "BGP Error Subcodes":
Registry: "BGP ROUTE-REFRESH Message Error subcodes" Registry: "BGP ROUTE-REFRESH Message Error subcodes"
Reference: [draft-ietf-idr-bgp-enhanced-refresh-06.txt] Reference: [draft-ietf-idr-bgp-enhanced-refresh-06.txt]
Registration Procedure(s): Values 0-127 Standards Action, values Registration Procedure(s): Values 0-127 Standards Action, values
128-255 First Come, First Served 128-255 First Come, First Served
Value Code Reference Value Code Reference
skipping to change at page 7, line 10 skipping to change at page 7, line 10
Capability for BGP-4", RFC 5291, August 2008. Capability for BGP-4", RFC 5291, August 2008.
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, February 2009. with BGP-4", RFC 5492, February 2009.
Authors' Addresses Authors' Addresses
Keyur Patel Keyur Patel
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95124 95134 San Jose, CA 95134
USA USA
Email: keyupate@cisco.com Email: keyupate@cisco.com
Enke Chen Enke Chen
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95124 95134 San Jose, CA 95134
USA USA
Email: enkechen@cisco.com Email: enkechen@cisco.com
Balaji Venkatachalapathy Balaji Venkatachalapathy
Email: balaji_pv@hotmail.com Email: balaji_pv@hotmail.com
 End of changes. 11 change blocks. 
14 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/