--- 1/draft-ietf-idr-bgp-open-policy-23.txt	2022-04-01 08:13:18.545520656 -0700
+++ 2/draft-ietf-idr-bgp-open-policy-24.txt	2022-04-01 08:13:18.577521466 -0700
@@ -1,26 +1,26 @@
 
 Network Working Group                                          A. Azimov
 Internet-Draft                                      Qrator Labs & Yandex
 Intended status: Standards Track                            E. Bogomazov
-Expires: 4 September 2022                                    Qrator Labs
+Expires: 3 October 2022                                      Qrator Labs
                                                                  R. Bush
                                 Internet Initiative Japan & Arrcus, Inc.
                                                                 K. Patel
                                                                   Arrcus
                                                                K. Sriram
                                                                 USA NIST
-                                                            3 March 2022
+                                                            1 April 2022
 
    Route Leak Prevention and Detection using Roles in UPDATE and OPEN
                                 Messages
-                   draft-ietf-idr-bgp-open-policy-23
+                   draft-ietf-idr-bgp-open-policy-24
 
 Abstract
 
    Route leaks are the propagation of BGP prefixes that violate
    assumptions of BGP topology relationships, e.g., announcing a route
    learned from one transit provider to another transit provider or a
    lateral (i.e., non-transit) peer or announcing a route learned from
    one lateral peer to another lateral peer or a transit provider.
    These are usually the result of misconfigured or absent BGP route
    filtering or lack of coordination between autonomous systems (ASes).
@@ -50,21 +50,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 4 September 2022.
+   This Internet-Draft will expire on 3 October 2022.
 
 Copyright Notice
 
    Copyright (c) 2022 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 carefully, as they describe your rights
@@ -451,25 +451,31 @@
          +-------+-------------------------------+---------------+
          |   4   | Peer (i.e., Lateral Peer)     | This document |
          +-------+-------------------------------+---------------+
          | 5-255 | To be assigned by IETF Review |               |
          +-------+-------------------------------+---------------+
 
                     Table 3: IANA Registry for BGP Role
 
    IANA has registered a new OPEN Message Error subcode named the "Role
    Mismatch" (see Section 3.2) in the OPEN Message Error subcodes
-   registry.  IANA has assigned the value TBD [to be removed upon
+   registry.  IANA has assigned the value 11 [to be removed upon
    publication: https://www.iana.org/assignments/bgp-parameters/bgp-
    parameters.xhtml#bgp-parameters-6].  This document is the reference
    for the new subcode.
 
+   Due to improper use of the values 8, 9, and 10 in the OPEN Message
+   Error subcodes registry, this document requested IANA to mark these
+   values as "Deprecated".  IANA has marked values 8-10 as "Deprecated"
+   in the OPEN Message Error subcodes registry.  This document is listed
+   as the reference.
+
    IANA has also registered a new path attribute named "Only to Customer
    (OTC)" (see Section 4) in the "BGP Path Attributes" registry.  IANA
    has assigned code value 35 [To be removed upon publication:
    http://www.iana.org/assignments/bgp-parameters/bgp-
    parameters.xhtml#bgp-parameters-2].  This document is the reference
    for the new attribute.
 
 7.  Security Considerations
 
    The security considerations of BGP (as specified in [RFC4271] and