draft-ietf-idr-bgp-enhanced-route-refresh-01.txt   draft-ietf-idr-bgp-enhanced-route-refresh-02.txt 
Network Working Group K. Patel Network Working Group K. Patel
Internet Draft E. Chen Internet Draft E. Chen
Intended Status: Standards Track B. Venkatachalapathy Intended Status: Standards Track B. Venkatachalapathy
Expiration Date: June 17, 2012 Cisco Systems Expiration Date: December 18, 2012 Cisco Systems
December 16, 2011 June 17, 2012
Enhanced Route Refresh Capability for BGP-4 Enhanced Route Refresh Capability for BGP-4
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on June 17, 2012. This Internet-Draft will expire on December 18, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.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 on-line, route refresh. The enhancement can be used to facilitate on-line,
non-disruptive consistency validations of BGP routing updates. non-disruptive consistency validations of BGP routing updates.
1. Introduction 1. Introduction
skipping to change at page 3, line 5 skipping to change at page 3, line 5
The "Enhanced Route Refresh Capability" is a new BGP capability The "Enhanced Route Refresh Capability" is a new BGP capability
[RFC5492]. The Capability Code for this capability is specified in [RFC5492]. The Capability Code for this capability is specified in
the IANA Considerations section of this document. The Capability the IANA Considerations section of this document. The Capability
Length field of this capability is zero. Length field of this capability is zero.
By advertising this capability to a peer, a BGP speaker conveys to By advertising this capability to a peer, a BGP speaker conveys to
the peer that the speaker supports the message subtypes for the the peer that the speaker supports the message subtypes for the
ROUTE-REFRESH message and the related procedures described in this ROUTE-REFRESH message and the related procedures described in this
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.txt
document. document.
2.2. Subtypes for ROUTE-REFRESH Message 2.2. Subtypes for ROUTE-REFRESH Message
The "Reserved" field of the ROUTE-REFRESH message specified in The "Reserved" field of the ROUTE-REFRESH message specified in
[RFC2918] is re-defined as the "Message Subtype" with the following [RFC2918] is re-defined as the "Message Subtype" with the following
values: values:
0 - Normal route refresh request [RFC2918] 0 - Normal route refresh request [RFC2918]
skipping to change at page 4, line 5 skipping to change at page 4, line 5
the start of the route refresh. When a route entry in the "ADJ-RIB- the start of the route refresh. When a route entry in the "ADJ-RIB-
Out" changes, the advertisement of the modified route entry (instead Out" changes, the advertisement of the modified route entry (instead
of the snapshot entry) would suffice. of the snapshot entry) would suffice.
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 BGP speaker SHALL use the demarcations of appropriate actions. The BGP speaker SHALL use the demarcations of
the beginning and the ending of a route refresh to perform the beginning and the ending of a route refresh to perform
consistency validations of the updates received from the peer. All consistency validations of the updates received from the peer. All
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.txt
the routes that were not re-advertised in the route refresh MUST be the routes that were not re-advertised in the route refresh MUST be
purged, and SHOULD be logged for further analysis. purged, and SHOULD be logged for further analysis.
4. Error Handling 4. Error Handling
This document defines a new NOTIFICATION error code: This document defines a new NOTIFICATION error code:
Error Code Symbolic Name Error Code Symbolic Name
skipping to change at page 5, line 5 skipping to change at page 5, line 5
5. IANA Considerations 5. IANA Considerations
This document defines the Enhanced Route Refresh Capability for BGP. This document defines the Enhanced Route Refresh Capability for BGP.
The Capability Code 70 has been assigned by the IANA. The Capability Code 70 has been assigned by the IANA.
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. They need to several error subcodes for the ROUTE-REFRESH message. They need to
be registered with the IANA. be registered with the IANA.
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.txt
6. Security Considerations 6. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Pedro Marques, Pradosh Mohapatra, The authors would like to thank Pedro Marques, Pradosh Mohapatra,
Robert Raszuk, Pranav Mehta, and Shyam Sethuram for discussions and Robert Raszuk, Pranav Mehta, and Shyam Sethuram for discussions and
review. The authors would like to thank Martin Djernaes, Jeff haas, review. The authors would like to thank Martin Djernaes, Jeff haas,
skipping to change at page 6, line 5 skipping to change at page 6, line 5
Email: keyupate@cisco.com Email: keyupate@cisco.com
Enke Chen Enke Chen
Cisco Systems Cisco Systems
Email: enkechen@cisco.com Email: enkechen@cisco.com
Balaji Venkatachalapathy Balaji Venkatachalapathy
Cisco Systems Cisco Systems
draft-ietf-idr-bgp-enhanced-route-refresh-01.txt draft-ietf-idr-bgp-enhanced-route-refresh-02.txt
Email: bvenkata@cisco.com Email: bvenkata@cisco.com
 End of changes. 9 change blocks. 
10 lines changed or deleted 10 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/