draft-ietf-idr-bgp-gr-notification-02.txt   draft-ietf-idr-bgp-gr-notification-03.txt 
Network Working Group K. Patel Network Working Group K. Patel
Internet-Draft R. Fernando Internet-Draft R. Fernando
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: November 17, 2014 J. Scudder Expires: December 5, 2014 J. Scudder
J. Haas J. Haas
Juniper Networks Juniper Networks
May 16, 2014 June 3, 2014
Notification Message support for BGP Graceful Restart Notification Message support for BGP Graceful Restart
draft-ietf-idr-bgp-gr-notification-02.txt draft-ietf-idr-bgp-gr-notification-03.txt
Abstract Abstract
The current BGP Graceful Restart mechanism limits the usage of BGP The current BGP Graceful Restart mechanism limits the usage of BGP
Graceful Restart to BGP protocol messages other than a BGP Graceful Restart to BGP protocol messages other than a BGP
NOTIFICATION message. This document defines an extension to the BGP NOTIFICATION message. This document defines an extension to the BGP
Graceful Restart that permits the Graceful Restart procedures to be Graceful Restart that permits the Graceful Restart procedures to be
performed when the BGP speaker receives a BGP NOTIFICATION Message. performed when the BGP speaker receives a BGP NOTIFICATION Message.
This document also defines a new BGP NOTIFICATION Cease Error subcode This document also defines a new BGP NOTIFICATION Cease Error subcode
to prevent BGP speakers supporting the extension defined in this to prevent BGP speakers supporting the extension defined in this
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 November 17, 2014. This Internet-Draft will expire on December 5, 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 4, line 44 skipping to change at page 4, line 44
BGP Hard Reset Subcode. The value of this subcode is discussed in BGP Hard Reset Subcode. The value of this subcode is discussed in
Section 6. We refer to a BGP NOTIFICATION Cease message with the Section 6. We refer to a BGP NOTIFICATION Cease message with the
Hard Reset subcode as a Hard Reset message, or just a Hard Reset. Hard Reset subcode as a Hard Reset message, or just a Hard Reset.
3.1. Sending a Hard Reset 3.1. Sending a Hard Reset
A Hard Reset message is used to indicate to a peer with which the A Hard Reset message is used to indicate to a peer with which the
Graceful Notification flag has been exchanged, that the session is to Graceful Notification flag has been exchanged, that the session is to
be fully terminated. be fully terminated.
When sending a Hard Reset, the data portion of the NOTIFICATION When sending a Hard Reset, the data portion of the NOTIFICATION is
message MUST be used to indicate the reason for the hard reset. The encoded as follows:
reason is encoded using a standard BGP Cease error subcode and MAY
also include any relevant data subsequent to the subcode. +--------+--------+--------
| ErrCode| Subcode| Data
+--------+--------+--------
ErrCode is a BGP Error Code (as documented in the IANA BGP Error
Codes registry) that indicates the reason for the hard reset.
Subcode is a BGP Error Subcode (as documented in the IANA BGP Error
Subcodes registry) as appropriate for the ErrCode. Similarly, Data
is as appropriate for the ErrCode and Subcode.
3.2. Receiving a Hard Reset 3.2. Receiving a Hard Reset
Whenever a BGP speaker receives a Hard Reset, the speaker MUST Whenever a BGP speaker receives a Hard Reset, the speaker MUST
terminate the BGP session following the standard procedures in terminate the BGP session following the standard procedures in
[RFC4271]. [RFC4271].
4. Operation 4. Operation
A BGP speaker that is willing to receive and send BGP NOTIFICATION A BGP speaker that is willing to receive and send BGP NOTIFICATION
skipping to change at page 6, line 11 skipping to change at page 6, line 15
in the newly received Graceful Restart Capability, no new actions are in the newly received Graceful Restart Capability, no new actions are
triggered on the Receiving Speaker -- in particular, a clear "N" bit triggered on the Receiving Speaker -- in particular, a clear "N" bit
does not trigger deletion of stale routes. does not trigger deletion of stale routes.
Other than these modifications, the rules for the Receiving Speaker Other than these modifications, the rules for the Receiving Speaker
are as specified in [RFC4724] S. 4.2. are as specified in [RFC4724] S. 4.2.
5. Acknowledgements 5. Acknowledgements
The authors would like to thank Jim Uttaro for the suggestion, and The authors would like to thank Jim Uttaro for the suggestion, and
Robert Raszuk for the review and comments. Chris Hall, Paul Mattes and Robert Raszuk for the review and
comments.
6. IANA Considerations 6. IANA Considerations
IANA is requested to assign a new subcode in the "BGP Cease IANA is requested to assign a new subcode in the "BGP Cease
NOTIFICATION message subcodes" registry. The suggested name for the NOTIFICATION message subcodes" registry. The suggested name for the
code point is "Hard Reset". The suggested value is 9. code point is "Hard Reset". The suggested value is 9.
7. Security Considerations 7. Security Considerations
This extension to BGP does not change the underlying security issues This extension to BGP does not change the underlying security issues
 End of changes. 6 change blocks. 
9 lines changed or deleted 19 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/