--- 1/draft-ietf-idr-bgp-gr-notification-10.txt 2017-05-02 11:13:23.718874928 -0700 +++ 2/draft-ietf-idr-bgp-gr-notification-11.txt 2017-05-02 11:13:23.734875312 -0700 @@ -1,22 +1,22 @@ Internet Engineering Task Force K. Patel Internet-Draft Arrcus Intended status: Standards Track R. Fernando -Expires: September 28, 2017 Cisco Systems +Expires: November 3, 2017 Cisco Systems J. Scudder J. Haas Juniper Networks - March 27, 2017 + May 2, 2017 Notification Message support for BGP Graceful Restart - draft-ietf-idr-bgp-gr-notification-10.txt + draft-ietf-idr-bgp-gr-notification-11.txt Abstract The current BGP Graceful Restart mechanism limits the usage of BGP Graceful Restart to BGP protocol messages other than a BGP NOTIFICATION message. This document defines an extension to the BGP Graceful Restart that permits the Graceful Restart procedures to be performed when the BGP speaker receives a BGP NOTIFICATION Message or the Hold Time expires. This document also defines a new BGP NOTIFICATION Cease Error subcode whose effect is to request a full @@ -30,21 +30,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 28, 2017. + This Internet-Draft will expire on November 3, 2017. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -232,23 +232,24 @@ are as specified in [RFC4724] S. 4.2. 5. Acknowledgements The authors would like to thank Jim Uttaro for the suggestion, and Emmanuel Baccelli, Bruno Decraene, Chris Hall, Paul Mattes and Robert Raszuk for their review and comments. 6. IANA Considerations - IANA is requested to assign a new subcode in the "BGP Cease - NOTIFICATION message subcodes" registry. The suggested name for the - code point is "Hard Reset". + IANA has temporarily assigned subcode 9, named "Hard Reset", in the + "BGP Cease NOTIFICATION message subcodes" registry. Upon publication + of this document as an RFC, IANA is requested to make this allocation + permanent. 7. Security Considerations This extension to BGP does not change the underlying security issues inherent in the existing [RFC4724] and [RFC4271]. 8. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119,