BMP Extension for Configuration Monitoring TLV
draft-gao-grow-bmp-config-monitor-tlv-01

grow                                                              X. Gao
Internet-Draft                                                   J. Zhao
Intended status: Standards Track                            China Unicom
Expires: 31 January 2027                                         Z. Wang
                                                                  Huawei
                                                                 T. Tong
                                                            China Unicom
                                                            30 July 2026

             BMP Extension for Configuration Monitoring TLV
                draft-gao-grow-bmp-config-monitor-tlv-01

Abstract

   This document defines two types of BMP extended TLV, which are used
   to carry configuration information and configuration effective time
   related to BGP route changes.  Through this extension, the BGP
   monitoring platform can associate various BGP events with
   configuration operations, providing traceable evidence for
   identifying network failures caused by configuration changes.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 31 January 2027.

Copyright Notice

   Copyright (c) 2026 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

Gao, et al.              Expires 31 January 2027                [Page 1]
Internet-Draft            BMP Config Change TLV                July 2026

   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   2
   3.  Sample Use Cases  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Case1:New service configuration conflicts with the existing
           network configuration . . . . . . . . . . . . . . . . . .   3
     3.2.  Case2:RIB overflow fault caused by relaxed import route
           filter policy . . . . . . . . . . . . . . . . . . . . . .   3
   4.  BMP Extended TLVs . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Configure message TLV . . . . . . . . . . . . . . . . . .   3
     4.2.  Configure effective timestamp TLV . . . . . . . . . . . .   4
   5.  Scope of application of BMP message type  . . . . . . . . . .   5
     5.1.  Peer Up Notification  . . . . . . . . . . . . . . . . . .   5
     5.2.  Peer Down Notification  . . . . . . . . . . . . . . . . .   5
     5.3.  Route Monitoring Messages . . . . . . . . . . . . . . . .   5
     5.4.  Routing Event Logging (REL) Messages  . . . . . . . . . .   6
   6.  Safety considerations . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  BMP TLV type registration: configuring message TLVs . . .   6
     7.2.  Registration of BMP Timestamp TLV Subtype . . . . . . . .   6
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document defines two types of BMP extension TLVs: one is the
   configuration message TLV, which is used to carry configuration
   information associated with BGP route changes; The other is configure
   effective timestamp TLV.  Based on the above expansion capabilities,
   the BGP monitoring platform can establish the correlation between BGP
   events such as route revocation and neighbor session changes, and
   corresponding configuration operations, providing data support for
   fault tracing in scenarios where configuration changes induce routing
   anomalies and lead to network failures.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119][RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Gao, et al.              Expires 31 January 2027                [Page 2]
Internet-Draft            BMP Config Change TLV                July 2026

3.  Sample Use Cases

3.1.  Case1:New service configuration conflicts with the existing
      network configuration

   When launching new services, an additional VPN binding was configured
   on the Loopback interface bearing the base station management VPN,
   which triggered a VPN instance configuration conflict on the
   interface.  The new configuration overwrote the original parameters
   of the base station management VPN, deleting the corresponding
   private network routes.  Route withdrawal messages were then
   propagated to all BGP peers throughout the network.  This VPN acts as
   the transport for base station management channels.  Once the routes
   became invalid, all base stations went offline from management.  Due
   to the absence of logs correlating configuration changes in BMP
   monitoring, operation and maintenance engineers spent a substantial
   amount of time reconstructing the full fault chain ranging from
   configuration conflict and route withdrawal to service interruption.

3.2.  Case2:RIB overflow fault caused by relaxed import route filter
      policy

   Maintainers relaxed the import routing filtering strategy on the
   boundary router, resulting in a large number of additional prefixes
   continuously entering the RIB.  At that time, there were no alarms,
   and the change was considered to have been completed normally.
   Several months later, the number of RIB entries exceeded the hardware
   TCAM limit, FIB programming failed, BGP sessions trembled, and
   business was interrupted.  Operations personnel cannot trace back
   which operation caused it, and can only search through historical
   change records one by one, which takes a long time to locate.  If BMP
   messages carry configuration change messages, they can automatically
   associate historical change operations when abnormal RIB growth is
   detected, quickly narrowing down the scope of investigation.

4.  BMP Extended TLVs

4.1.  Configure message TLV

   This TLV follows the TLV encoding format specified in BMP v4:
   Extended TLV Support for BGP Monitoring Protocol (BMP), with the
   following structure:

Gao, et al.              Expires 31 January 2027                [Page 3]
Internet-Draft            BMP Config Change TLV                July 2026

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |E|      Type (15 bits)         |         Length (2 octets)     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |     Configuration session ID  |      Configuration source     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    ~                     Reserved                                  ~
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                      Figure 1:Configure message TLV

   *  E bit (1 bit): Enterprise Extension bit, following the definition
      of BMP v4: Extended TLV Support for BGP Monitoring Protocol (BMP).
      The E bit of this TLV must be set to 0.

   *  Type (15 bits): The value is TBD1 (to be allocated by IANA later).

   *  Length (2 bytes): The total byte length of the value field.

   *  Configuration session ID (2 bytes): Represents the unique
      identifier of the configuration management session.

   *  Configuration source (2 bytes): Operator ID or equipment/system
      identification.

   *  Reserved field (variable length): Used to extend other relevant
      information about the configuration.For example, configuration
      commands that directly cause changes in routing status.

4.2.  Configure effective timestamp TLV

   BMP v4: Extended TLV Support for BGP Monitoring Protocol (BMP)
   defines the Timestamp TLV, which is used to carry various types of
   time information related to BMP events.  This document introduces new
   subtypes for this TLV, specifically designed to carry configuration-
   related time information.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |              Type             |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |G|            Index            | Timestmp Type |               ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~           Timestamp (seconds)                 |               ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~           Timestamp (microseconds)            ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                           Figure 2: Timestamp TLV

Gao, et al.              Expires 31 January 2027                [Page 4]
Internet-Draft            BMP Config Change TLV                July 2026

   *  Configure effective timestamp sub-type Time stamp type value: TBD2
      (allocated by IANA in the BMP timestamp TLV subtype registry)
      Name: Configuration Effective Timestamp Description: The time when
      the submitted configuration is officially put into operation.

5.  Scope of application of BMP message type

5.1.  Peer Up Notification

   If the establishment of a BGP neighbor session is directly triggered
   by configuration changes (such as adding new BGP neighbors or
   modifying neighbor parameters leading to session reestablishment), it
   is recommended to include the configuration message TLV and the
   configuration submission timestamp TLV in the message.

5.2.  Peer Down Notification

   If the interruption of a neighbor session is caused by a
   configuration change (such as the deletion of a BGP neighbor or a
   configuration change triggering session reset), it is recommended to
   include the Configuration Message TLV and the Configuration
   Submission Timestamp TLV in the message.

5.3.  Route Monitoring Messages

   If the route update (publish/revoke) is triggered by a local
   configuration change, the route monitoring message can carry a
   configuration message TLV and a configuration submission timestamp
   TLV.  Specific scenarios may include:

   *  Modify routing policies to trigger route recalculation, route
      withdrawal, or re-advertisement;

   *  Adding or deleting BGP network announcements directly leads to the
      publication or withdrawal of routes;

   *  Modify the next hop, MED, and other attributes to affect existing
      route advertisements;

   *  Adjust the route redistribution strategy, triggering route
      additions and deletions.

Gao, et al.              Expires 31 January 2027                [Page 5]
Internet-Draft            BMP Config Change TLV                July 2026

5.4.  Routing Event Logging (REL) Messages

   The configuration session ID and timestamp sub-types defined in this
   document are fully applicable to the routing event log (REL) messages
   specified in draft-ietf-grow-bmp-rel-06.  When the log action TLV
   (Type 6, Encoding 1 = Configuration Event) in the REL message
   indicates that the event is triggered by a configuration statement,
   it is recommended to also include the configuration message TLV.

6.  Safety considerations

   TBD

7.  IANA Considerations

7.1.  BMP TLV type registration: configuring message TLVs

   Request IANA to add the following entry to the "BMP TLV Type"
   registry:

   +------+----------------------------+-------------------+
   | Type |         Name               |     Reference     |
   +------+----------------------------+-------------------+
   | TBD1 |  configuring message TLV   |    Section 4.1    |
   +------+----------------------------+-------------------+

7.2.  Registration of BMP Timestamp TLV Subtype

   Request IANA to add the following entry in the "BMP Timestamp TLV
   Subtype" registry:

   +------+-------------------------+------------------+
   | Type |         Name            |      Reference   |
   +------+-------------------------+------------------+
   | TBD2 |  Configure effective    |                  |
   |      |   timestamp TLV         |   Section 4.2    |
   +------+-------------------------+------------------+

8.  Informative References

   [I-D.ietf-grow-bmp-rel]
              Lucente, P. and C. Cardona, "Logging of routing events in
              BGP Monitoring Protocol (BMP)", Work in Progress,
              Internet-Draft, draft-ietf-grow-bmp-rel-06, 21 July 2026,
              <https://datatracker.ietf.org/doc/html/draft-ietf-grow-
              bmp-rel-06>.

Gao, et al.              Expires 31 January 2027                [Page 6]
Internet-Draft            BMP Config Change TLV                July 2026

   [I-D.ietf-grow-bmp-tlv]
              Lucente, P., Gu, Y., Younsi, M., and P. Francois, "BMP v4:
              Extended TLV Support for BGP Monitoring Protocol (BMP)",
              Work in Progress, Internet-Draft, draft-ietf-grow-bmp-tlv-
              21, 21 July 2026, <https://datatracker.ietf.org/doc/html/
              draft-ietf-grow-bmp-tlv-21>.

Authors' Addresses

   Xing Gao
   China Unicom
   Beijing
   China
   Email: gaox60@chinaunicom.cn

   Jing Zhao
   China Unicom
   Beijing
   China
   Email: zhaoj501@chinaunicom.cn

   Zhiyuan Wang
   Huawei
   Beijing
   China
   Email: wangzhiyuan51@huawei.com

   Tian Tong
   China Unicom
   Beijing
   China
   Email: tongt5@chinaunicom.cn

Gao, et al.              Expires 31 January 2027                [Page 7]