--- 1/draft-ietf-idr-capabilities-registry-change-04.txt	2019-05-28 23:13:13.000902632 -0700
+++ 2/draft-ietf-idr-capabilities-registry-change-05.txt	2019-05-28 23:13:13.016903036 -0700
@@ -1,19 +1,19 @@
 
 Network Working Group                                         J. Scudder
 Internet-Draft                                          Juniper Networks
-Updates: 5492 (if approved)                                 May 23, 2019
+Updates: 5492 (if approved)                                 May 28, 2019
 Intended status: Standards Track
-Expires: November 24, 2019
+Expires: November 29, 2019
 
           Revision to Capability Codes Registration Procedures
-           draft-ietf-idr-capabilities-registry-change-04.txt
+           draft-ietf-idr-capabilities-registry-change-05.txt
 
 Abstract
 
    This document updates RFC 5492 by making a change to the registration
    procedures for BGP Capability Codes.  Specifically, the range
    formerly designated "Reserved for Private Use" is divided into three
    new ranges, respectively designated as "First Come First Served",
    "Experimental" and "Reserved".
 
 Status of This Memo
@@ -24,21 +24,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 https://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 November 24, 2019.
+   This Internet-Draft will expire on November 29, 2019.
 
 Copyright Notice
 
    Copyright (c) 2019 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -116,57 +116,60 @@
 
    Reference: [RFC5492] and this document.
 
    Registry Owner/Change Controller: IESG
 
    Registration procedures:
 
                    +---------+-------------------------+
                    |  Range  | Registration Procedures |
                    +---------+-------------------------+
-                   |    0    | Reserved                |
                    |   1-63  | IETF Review             |
                    |  64-238 | First Come First Served |
                    | 239-254 | Experimental            |
                    |   255   | Reserved                |
                    +---------+-------------------------+
 
    Note: a separate "owner" column is not provided because the owner of
    all registrations, once made, is "IESG".
 
    IANA is requested to perform the following new allocations within the
    "Capability Codes" registry:
 
-   +-------+-------------------------------------------+---------------+
+   +-------+-----------------------------------------------+-----------+
    | Value | Description                               | Reference     |
-   +-------+-------------------------------------------+---------------+
+   +-------+-----------------------------------------------+-----------+
    |  128  | Prestandard Route Refresh (deprecated)    | (this         |
    |       |                                           | document)     |
+   +-------+-----------------------------------------------+-----------+
    |  129  | Prestandard Outbound Route Filtering      | (this         |
-   |       | (deprecated)                              | document)     |
+   |       | (deprecated), prestandard draft-li-idr-       | document) |
+   |       | flowspec-rpd-04 (deprecated)                  |           |
+   +-------+-----------------------------------------------+-----------+
    |  130  | Prestandard Outbound Route Filtering      | (this         |
    |       | (deprecated)                              | document)     |
+   +-------+-----------------------------------------------+-----------+
    |  255  | Reserved                                  | (this         |
    |       |                                           | document)     |
-   +-------+-------------------------------------------+---------------+
+   +-------+-----------------------------------------------+-----------+
 
 4.  Security Considerations
 
    This revision to registration procedures does not change the
    underlying security issues inherent in the existing [RFC5492] and
    [RFC4271].
 
 5.  Acknowledgements
 
-   Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jeff Haas, Sue
-   Hares, Acee Lindem, Thomas Mangin, and Tom Petch for review and
-   comments.
+   Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jie Dong, Jeff
+   Haas, Sue Hares, Acee Lindem, Thomas Mangin, and Tom Petch for review
+   and comments.
 
 6.  References
 
 6.1.  Normative References
 
    [RFC5492]  Scudder, J. and R. Chandra, "Capabilities Advertisement
               with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
               2009, <https://www.rfc-editor.org/info/rfc5492>.
 
    [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for