--- 1/draft-ietf-grow-bmp-local-rib-05.txt	2019-11-04 09:13:48.565915286 -0800
+++ 2/draft-ietf-grow-bmp-local-rib-06.txt	2019-11-04 09:13:48.601916193 -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: February 6, 2020                                     P. Lucente
+Expires: May 6, 2020                                          P. Lucente
                                                       NTT Communications
-                                                          August 5, 2019
+                                                        November 3, 2019
 
          Support for Local RIB in BGP Monitoring Protocol (BMP)
-                    draft-ietf-grow-bmp-local-rib-05
+                    draft-ietf-grow-bmp-local-rib-06
 
 Abstract
 
    The BGP Monitoring Protocol (BMP) defines access to the Adj-RIB-In
    and locally originated routes (e.g. routes distributed into BGP from
    protocols such as static) but not access to the BGP instance Loc-RIB.
    This document updates the BGP Monitoring Protocol (BMP) RFC 7854 by
    adding access to the BGP instance Local-RIB, as defined in RFC 4271
    the routes that have been selected by the local BGP speaker's
    Decision Process.  These are the routes over all peers, locally
@@ -29,21 +29,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 February 6, 2020.
+   This Internet-Draft will expire on May 6, 2020.
 
 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
@@ -371,24 +371,23 @@
    All peer messages that include a per-peer header MUST use the
    following values:
 
    o  Peer Type: Set to 3 to indicate Loc-RIB Instance Peer.
 
    o  Peer Distinguisher: Zero filled if the Loc-RIB represents the
       global instance.  Otherwise set to the route distinguisher or
       unique locally defined value of the particular instance the Loc-
       RIB belongs to.
 
-   o  Peer Address: The remote IP address associated with the TCP
-      session over which the encapsulated PDU was received.  If zero-
-      filled, the information is not available and setting the V flag is
-      not applicable.
+   o  Peer Address: Zero-filled.  Remote peer address is not applicable.
+      The V flag is not applicable with Local-RIB Instance peer type
+      considering addresses are zero-filed.
 
    o  Peer AS: Set to the BGP instance global or default ASN value.
 
    o  Peer BGP ID: Set to the BGP instance global or RD (e.g.  VRF)
       specific router-id section 1.1 of [RFC7854].
 
    o  Timestamp: The time when the encapsulated routes were installed in
       The Loc-RIB, expressed in seconds and microseconds since midnight
       (zero hour), January 1, 1970 (UTC).  If zero, the time is
       unavailable.  Precision of the timestamp is implementation-