--- 1/draft-ietf-grow-bmp-adj-rib-out-03.txt	2019-03-24 12:13:17.433843241 -0700
+++ 2/draft-ietf-grow-bmp-adj-rib-out-04.txt	2019-03-24 12:13:17.461843933 -0700
@@ -1,24 +1,24 @@
 
 Global Routing Operations                                       T. Evens
 Internet-Draft                                              S. Bayraktar
 Updates: 7854 (if approved)                                Cisco Systems
 Intended status: Standards Track                              P. Lucente
-Expires: June 22, 2019                                NTT Communications
+Expires: September 25, 2019                           NTT Communications
                                                                    P. Mi
                                                                  Tencent
                                                                S. Zhuang
                                                                   Huawei
-                                                       December 19, 2018
+                                                          March 24, 2019
 
         Support for Adj-RIB-Out in BGP Monitoring Protocol (BMP)
-                   draft-ietf-grow-bmp-adj-rib-out-03
+                   draft-ietf-grow-bmp-adj-rib-out-04
 
 Abstract
 
    The BGP Monitoring Protocol (BMP) defines access to only the Adj-RIB-
    In Routing Information Bases (RIBs).  This document updates the BGP
    Monitoring Protocol (BMP) RFC 7854 by adding access to the Adj-RIB-
    Out RIBs.  It adds a new flag to the peer header to distinguish Adj-
    RIB-In and Adj-RIB-Out.
 
 Status of This Memo
@@ -29,25 +29,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 June 22, 2019.
+   This Internet-Draft will expire on September 25, 2019.
 
 Copyright Notice
 
-   Copyright (c) 2018 IETF Trust and the persons identified as the
+   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
    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
@@ -151,21 +151,21 @@
 
    o  The O flag indicates Adj-RIB-In if set to 0 and Adj-RIB-Out if set
       to 1.
 
    The existing flags are defined in section 4.2 [RFC7854] and the
    remaining bits are reserved for future use.  They SHOULD be
    transmitted as 0 and their values MUST be ignored on receipt.  The
    following fields in Per-Peer Header are redefined:
 
    o  Peer Address: The remote IP address associated with the TCP
-      session over which the encapsulated PDU was sent.
+      session over which the encapsulated PDU is sent.
 
    o  Peer AS: The Autonomous System number of the peer from which the
       encapsulated PDU was sent.
 
    o  Peer BGP ID: The BGP Identifier of the peer from which the
       encapsulated PDU was sent.
 
 5.  Adj-RIB-Out
 
 5.1.  Post-Policy