--- 1/draft-ietf-grow-bmp-local-rib-08.txt	2021-01-14 15:13:14.035203629 -0800
+++ 2/draft-ietf-grow-bmp-local-rib-09.txt	2021-01-14 15:13:14.067204449 -0800
@@ -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: 20 May 2021                                          P. Lucente
+Expires: 18 July 2021                                         P. Lucente
                                                       NTT Communications
-                                                        16 November 2020
+                                                         14 January 2021
 
          Support for Local RIB in BGP Monitoring Protocol (BMP)
-                    draft-ietf-grow-bmp-local-rib-08
+                    draft-ietf-grow-bmp-local-rib-09
 
 Abstract
 
    The BGP Monitoring Protocol (BMP) defines access to various 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,25 +26,25 @@
    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 20 May 2021.
+   This Internet-Draft will expire on 18 July 2021.
 
 Copyright Notice
 
-   Copyright (c) 2020 IETF Trust and the persons identified as the
+   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
    and restrictions with respect to this document.  Code Components
    extracted from this document must include Simplified BSD License text
    as described in Section 4.e of the Trust Legal Provisions and are
    provided without warranty as described in the Simplified BSD License.
@@ -429,23 +429,23 @@
 
    Multiple TLVs of the same type can be repeated as part of the same
    message, for example to convey a filtered view of a VRF.  A BMP
    receiver should append multiple TLVs of the same type to a set in
    order to support alternate or additional names for the same peer.  If
    multiple strings are included, their ordering MUST be preserved when
    they are reported.
 
 5.3.  Peer Down Notification
 
-   Peer down notification MUST use reason code TBD3.  Following the
-   reason is data in TLV format.  The following peer Down information
-   TLV type is defined:
+   Peer down notification MUST use reason code 6.  Following the reason
+   is data in TLV format.  The following peer Down information TLV type
+   is defined:
 
    *  Type = 3: VRF/Table Name.  The Information field contains a UTF-8
       string whose value MUST be equal to the value of the VRF or table
       name (e.g.  RD instance name) being conveyed.  The string size
       MUST be within the range of 1 to 255 bytes.  The VRF/Table Name
       informational TLV MUST be included if it was in the Peer UP.
 
 5.4.  Route Monitoring
 
    Route Monitoring messages are used for initial synchronization of the
@@ -574,21 +574,21 @@
    *  Type = 3: VRF/Table Name.  The Information field contains a UTF-8
       string whose value MUST be equal to the value of the VRF or table
       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 = TBD3: Local system closed, TLV data follows.
+   *  Type = 6: Local system closed, TLV data follows.
 
 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,