--- 1/draft-ietf-grow-bmp-local-rib-12.txt	2021-08-31 11:13:11.896270266 -0700
+++ 2/draft-ietf-grow-bmp-local-rib-13.txt	2021-08-31 11:13:11.928271068 -0700
@@ -1,21 +1,21 @@
 
 Global Routing Operations                                       T. Evens
 Internet-Draft                                              S. Bayraktar
 Updates: 7854 (if approved)                                  M. Bhardwaj
 Intended status: Standards Track                           Cisco Systems
-Expires: 16 December 2021                                     P. Lucente
+Expires: 4 March 2022                                         P. Lucente
                                                       NTT Communications
-                                                            14 June 2021
+                                                          31 August 2021
 
          Support for Local RIB in BGP Monitoring Protocol (BMP)
-                    draft-ietf-grow-bmp-local-rib-12
+                    draft-ietf-grow-bmp-local-rib-13
 
 Abstract
 
    The BGP Monitoring Protocol (BMP) defines access to local Routing
    Information Bases (RIBs).  This document updates BMP (RFC 7854) by
    adding access to the Local Routing Information Base (Loc-RIB), as
    defined in RFC 4271.  The Loc-RIB contains the routes that have been
    selected by the local BGP speaker's Decision Process.
 
 Status of This Memo
@@ -26,21 +26,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 16 December 2021.
+   This Internet-Draft will expire on 4 March 2022.
 
 Copyright Notice
 
    Copyright (c) 2021 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
@@ -72,20 +72,21 @@
      6.1.  Loc-RIB Implementation  . . . . . . . . . . . . . . . . .  11
        6.1.1.  Multiple Loc-RIB Peers  . . . . . . . . . . . . . . .  11
        6.1.2.  Filtering Loc-RIB to BMP Receivers  . . . . . . . . .  12
        6.1.3.  Changes to existing BMP sessions  . . . . . . . . . .  12
    7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
    8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
      8.1.  BMP Peer Type . . . . . . . . . . . . . . . . . . . . . .  12
      8.2.  BMP Loc-RIB Instance Peer Flags . . . . . . . . . . . . .  12
      8.3.  Peer Up Information TLV . . . . . . . . . . . . . . . . .  13
      8.4.  Peer Down Reason code . . . . . . . . . . . . . . . . . .  13
+     8.5.  Deprecated entries  . . . . . . . . . . . . . . . . . . .  13
    9.  Normative References  . . . . . . . . . . . . . . . . . . . .  13
    10. Informative References  . . . . . . . . . . . . . . . . . . .  14
    Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  14
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14
 
 1.  Introduction
 
    This document defines a mechanism to monitor the BGP Loc-RIB state of
    remote BGP instances without the need to establish BGP peering
    sessions.  BMP [RFC7854] does not define a method to send the BGP
@@ -540,21 +541,21 @@
 8.1.  BMP Peer Type
 
    This document defines a new peer type (Section 4.1):
 
    *  Peer Type = 3: Loc-RIB Instance Peer
 
 8.2.  BMP Loc-RIB Instance Peer Flags
 
    This document requests IANA to rename "BMP Peer Flags" to "BMP Peer
    Flags for Peer Types 0 through 2" and create a new registry named
-   "BMP Peer Flags for Loc-RIB Instance Peer Type 3" This document
+   "BMP Peer Flags for Loc-RIB Instance Peer Type 3."  This document
    defines that peer flags are specific to the Loc-RIB instance peer
    type.  As defined in (Section 4.2):
 
    *  Flag 0: The F flag indicates that the Loc-RIB is filtered.  This
       indicates that the Loc-RIB does not represent the complete routing
       table.
 
    Flags 0 through 3 and 5 through 7 are unassigned.  The registration
    procedure for the registry is "Standards Action".
 
@@ -571,20 +572,26 @@
       name (e.g., RD instance name) being conveyed.  The string size
       MUST be within the range of 1 to 255 bytes.
 
 8.4.  Peer Down Reason code
 
    This document defines the following new BMP Peer Down reason code
    (Section 5.3):
 
    *  Type = 6: Local system closed, TLV data follows.
 
+8.5.  Deprecated entries
+
+   This document also requests that IANA marks as "deprecated" the F
+   Flag entry in the "BMP Peer Flags for Peer Types 0 through 2"
+   registry.
+
 9.  Normative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC4271]  Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
               Border Gateway Protocol 4 (BGP-4)", RFC 4271,
               DOI 10.17487/RFC4271, January 2006,