--- 1/draft-ietf-grow-bmp-tlv-00.txt	2019-10-15 03:13:10.081784556 -0700
+++ 2/draft-ietf-grow-bmp-tlv-01.txt	2019-10-15 03:13:10.121785572 -0700
@@ -1,21 +1,21 @@
 
 Global Routing Operations                                     P. Lucente
 Internet-Draft                                                       NTT
 Updates: 7854 (if approved)                                        Y. Gu
 Intended status: Standards Track                                  Huawei
-Expires: March 6, 2020                                           H. Smit
+Expires: April 17, 2020                                          H. Smit
                                                              Independent
-                                                       September 3, 2019
+                                                        October 15, 2019
 
       TLV support for BMP Route Monitoring and Peer Down Messages
-                       draft-ietf-grow-bmp-tlv-00
+                       draft-ietf-grow-bmp-tlv-01
 
 Abstract
 
    Most of the message types defined by the BGP Monitoring Protocol
    (BMP) do provision for optional trailing data; however Route
    Monitoring message (to provide a snapshot of the monitored Routing
    Information Base) and Peer Down message (to indicate that a peering
    session was terminated) do not.  Supporting optional data in TLV
    format across all BMP message types allows for an homogeneous and
    extensible surface that would be useful for the most different use-
@@ -32,21 +32,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 March 6, 2020.
+   This Internet-Draft will expire on April 17, 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
@@ -59,21 +59,21 @@
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
    2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
    3.  TLV encoding  . . . . . . . . . . . . . . . . . . . . . . . .   3
    4.  BMP Message Format  . . . . . . . . . . . . . . . . . . . . .   4
      4.1.  Common Header . . . . . . . . . . . . . . . . . . . . . .   4
      4.2.  TLV data in Route Monitoring  . . . . . . . . . . . . . .   4
      4.3.  TLV data in Peer Down . . . . . . . . . . . . . . . . . .   4
      4.4.  TLV data in other BMP messages  . . . . . . . . . . . . .   4
-   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
+   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
    6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
    7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
    Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   6
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6
 
 1.  Introduction
 
    The BGP Monitoring Protocol (BMP) is defined in RFC 7854 [RFC7854].
 
    The Route Monitoring message consists of:
@@ -162,21 +162,25 @@
 
    o  Type = TBD2: the BGP Update PDU is encoded with ADD-PATH
       capability RFC 7911 [RFC7911], value MUST be boolean.
 
    o  Type = TBD3: the BGP Update PDU is encoded with Multiple Labels
       capability RFC 8277 [RFC8277], value MUST be boolean.
 
 4.3.  TLV data in Peer Down
 
    The Peer Down Notification message type is defined in Section 4.9 of
-   [RFC7854].  TLV data MAY now follow any Reason code.
+   [RFC7854].  In case of Reason code 1 and 3, a BGP Notification PDU
+   follows; the PDU MAY be followed by TLV data.  In case of Reason code
+   2, a 2-byte field to give additional FSM info follows; this field MAY
+   be followed by TLV data.  For all other Reason codes, TLV data MAY
+   follow the Reason field.
 
 4.4.  TLV data in other BMP messages
 
    All other message types defined in RFC7854 [RFC7854] do already
    provision for TLV data.  It is RECOMMENDED that all future BMP
    message types will provision for trailing TLV data.
 
 5.  Security Considerations
 
    It is not believed that this document adds any additional security