Generic Event Notification (GEN) for BGP Monitoring Protocol (BMP)
draft-sp-grow-bmp-gen-01
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Tarek Saad , Narasimha Prasad | ||
| Last updated | 2025-11-03 | ||
| Replaces | draft-spd-grow-bmp-purge | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-sp-grow-bmp-gen-01
GROW T. Saad
Internet-Draft P. Narasimha
Intended status: Standards Track Cisco Systems, Inc.
Expires: 7 May 2026 3 November 2025
Generic Event Notification (GEN) for BGP Monitoring Protocol (BMP)
draft-sp-grow-bmp-gen-01
Abstract
This document defines a new BMP message type: the Generic Event
Notification (GEN). The BMP GEN message provides a flexible
mechanism for reporting a wide variety of events related to BGP at
different levels of hierarchy, such as routing instance, AFI/SAFI, or
peer level. The BMP GEN message enables operators and automated
systems to receive detailed context for operational events, such as
policy triggers, administrative interventions, and state management
notifications (e.g., RIB view unmonitor events).
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 7 May 2026.
Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
Saad & Narasimha Expires 7 May 2026 [Page 1]
Internet-Draft GEN Message for BMP November 2025
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 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The BMP GEN Message Format . . . . . . . . . . . . . . . . . 3
4.1. The BMP Message Common Header . . . . . . . . . . . . . . 4
4.2. The BMP GEN Message Body . . . . . . . . . . . . . . . . 4
4.3. The BMP GEN Message Fields . . . . . . . . . . . . . . . 5
4.3.1. Example Event Types . . . . . . . . . . . . . . . . . 5
4.3.2. Event Sub-TLVs . . . . . . . . . . . . . . . . . . . 5
4.3.3. RIB View Event Sub-TLV . . . . . . . . . . . . . . . 6
4.3.4. Reason String Event Sub-TLV . . . . . . . . . . . . . 7
4.3.5. Reason Code Event Sub-TLV . . . . . . . . . . . . . . 8
4.3.6. Route Distinguisher Sub-TLV . . . . . . . . . . . . . 9
4.3.7. Peer Address Event Sub-TLV . . . . . . . . . . . . . 9
4.4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4.1. Example Scenario: RIB View Unmonitor . . . . . . . . 10
4.4.2. Example Scenario: Route Import Complete . . . . . . . 11
4.4.3. Example Scenario: Peer Configured is Down . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. BMP Message Type . . . . . . . . . . . . . . . . . . . . 13
6.2. BMP GEN Event Types . . . . . . . . . . . . . . . . . . . 13
6.3. BMP GEN Event Sub-TLV Types . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The BGP Monitoring Protocol (BMP) [RFC7854] provides network
operators with visibility into BGP message exchanges. Recent
extensions, such as [I-D.ietf-grow-bmp-rel], increase the range of
observable BGP-related events. However, there is a need for a more
generic, extensible message type capable of reporting diverse
operational events, including policy triggers, automated network
Saad & Narasimha Expires 7 May 2026 [Page 2]
Internet-Draft GEN Message for BMP November 2025
adjustments, administrative interventions, and notifications for
collector state management, such as route table purges.
This document introduces the BMP Generic Event Notification (GEN)
message, designed to flexibly report on such events with enough
context to allow the collector to take the appropriate action.
The BMP GEN message can be used to deliver a variety of
notifications, including a RIB View notification, which allows a BMP
sender to request that the BMP collector purge the state associated
with specific peers and RIB views.
2. Terminology
* GEN: Generic Event Notification
* BMP: BGP Monitoring Protocol
* BGP: Border Gateway Protocol
* TLV: Type-Length-Value
* RIB: Routing Information Base
3. Motivation
The current BMP message types focus primarily on peer session events
and per-route updates. Network operators and automated systems often
require notification of a broader class of events, such as:
* RIB state management, such as notifying the collector when a RIB
view is no longer being monitored.
* Administrative resets, disables, or maintenance windows
* Notifications about the status of various internal FSM router
states (e.g., Import Completed, Export Completed, etc.)
* Detection of anomalous behavior or threshold crossings
The BMP GEN message provides structured reporting of such events,
including a clear indication of the event type and related context.
4. The BMP GEN Message Format
The BMP GEN message is a new BMP message type.
Saad & Narasimha Expires 7 May 2026 [Page 3]
Internet-Draft GEN Message for BMP November 2025
4.1. The BMP Message Common Header
The BMP GEN message uses the BMP message common header as defined in
[RFC7854]:
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
+-+-+-+-+-+-+-+-+
| Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg. Type |
+---------------+
Figure 1: The BMP message common header
where a new Message Type = TBD1 is assigned to the BMP GEN message
type.
4.2. The BMP GEN Message Body
The BMP GEN message body is formatted as follows:
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
+---------------------------------------------------------------+
| Event Type (2 octets) | Flags (2 octets) |
+---------------------------------------------------------------+
| Timestamp (seconds) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp (microseconds) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sub-TLVs (variable) |
+---------------------------------------------------------------+
Figure 2: The BMP GEN message contents
The BMP GEN message is extensible for future event types. It is
meant to supplement, but not replace, existing BMP message types.
Event Type:
Identifies the event class (see Section 4.3.1 for example Event
Types).
Flags:
Reserved for future use.
Saad & Narasimha Expires 7 May 2026 [Page 4]
Internet-Draft GEN Message for BMP November 2025
Timestamp:
The time when the event occurred, expressed as seconds and
microseconds since midnight (00:00), January 1, 1970 (UTC). If
both are zero, the time is unavailable. Precision of the
timestamp is implementation-dependent.
Event Sub-TLVs:
Optional Sub-TLVs for additional context for the event that
occurred (see Section 4.3.2 for example Sub-TLVs).
4.3. The BMP GEN Message Fields
The following fields are defined for BMP GEN messages.
4.3.1. Example Event Types
The following Event Types are defined:
* Type=0 : RIB View Unmonitor Event sent when a particular RIB-view
is no longer monitored on the Router (Eg: Globally at router level
or for a given AFI/SAFI or for a set of BGP peers).
* Type=1 : Route Import Complete Event sent when import of Routes is
completed (Eg: Globally at router level or for a given Table).
* Type=2 : Peer Configured is Down Event sent when configured
monitored BGP peer on the router has never come up.
4.3.2. Event Sub-TLVs
The Event Sub-TLVs are encoded as a list of optional Sub-TLVs. They
add context to the associated event, either by providing the reason
or act as a set of filters.
All Event Sub-TLVs use a 2-octet Type field and a 2-octet Length
field. The Event Sub-TLV is defined as follows:
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 (2 octets) | Length (2 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\\ Value \\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: BMP GEN message optional Event Sub-TLVs
Saad & Narasimha Expires 7 May 2026 [Page 5]
Internet-Draft GEN Message for BMP November 2025
The following are BMP GEN message Event Sub-TLV Types that are
defined in this document:
+======+=================+=====================+===================+
| Type | Length (octets) | Description | Value Format |
+======+=================+=====================+===================+
| 0 | Variable | Reason String | UTF-8 string |
+------+-----------------+---------------------+-------------------+
| 1 | 1 | Reason Code | see Section 4.3.5 |
+------+-----------------+---------------------+-------------------+
| 2 | 2 | RIB View (Filter) | see Section 4.3.3 |
+------+-----------------+---------------------+-------------------+
| 3 | 8 | Route Distinguisher | see Section 4.3.6 |
| | | (Filter) | |
+------+-----------------+---------------------+-------------------+
| 4 | 4 or 16 | Peer Address | see Section 4.3.7 |
| | | (Filter) | |
+------+-----------------+---------------------+-------------------+
Table 1: Event Sub-TLVs Types defined in this document
4.3.3. RIB View Event Sub-TLV
The RIB View Event Sub-TLV identifies one or more RIB views that are
relevant to the event. The encoding of the RIB View Event Sub-TLV is
shown in Figure 4.
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=2 | Length=2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RIB View |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: The RIB View Event Sub-TLV encoding
Type=2:
Identifies the RIB View Event Sub-TLV Type.
Length=2:
2-bytes.
RIB View:
The RIB View value. This value encoded as shown in Figure 5.
Saad & Narasimha Expires 7 May 2026 [Page 6]
Internet-Draft GEN Message for BMP November 2025
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|J|O|P|L| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: RIB View value encoding
* When I flag is set, it indicates that the Event reflects the Pre-
Policy Adj-RIB-In view
* When J flag is set, it indicates that the Event reflects the Post-
Policy Adj-RIB-In view
* When O flag is set, it indicates that the Event reflects the Pre-
Policy Adj-RIB-Out view
* When P flag is set, it indicates that the Event reflects the Post-
Policy Adj-RIB-Out view
* When L flag is set, it indicates that the Event reflects the
Local-RIB view
The remaining bits are reserved for future use. They MUST be
transmitted as 0 and their values MUST be ignored on receipt.
NOTE: Above is an extension to RIB-view value encoding defined in
[I-D.patki-grow-bmp-common-updates]
4.3.4. Reason String Event Sub-TLV
The Reason String Event Sub-TLV provides a UTF-8 encoded string
describing the event in human-readable form. This Sub-TLV is
intended to assist operators or automated systems in interpreting the
context or rationale for the event, such as "Adj-RIB-Out export
stopped by operator" or "Peer remains in down state".
The encoding of the Reason String Event Sub-TLV is shown in Figure 6.
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=0 | Length (Variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\\ Reason String \\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: The Reason String Event Sub-TLV encoding
Saad & Narasimha Expires 7 May 2026 [Page 7]
Internet-Draft GEN Message for BMP November 2025
Type=0:
Identifies the Reason String Event Sub-TLV Type.
Length (Variable):
The length of the string in bytes.
Reason String:
The UTF-8 string not null-terminated.
4.3.5. Reason Code Event Sub-TLV
The Reason Code Event Sub-TLV provides a 1-octet code indicating the
reason for the event. The encoding of the Reason Code Event Sub-TLV
is shown in Figure 7:
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=1 | Length=1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason Code |
+-+-+-+-+-+-+-+-+
Figure 7: The Reason Code Event Sub-TLV encoding
Type=1:
Identifies the Reason Code Event Sub-TLV Type.
Length=1:
1-byte.
Reason Code:
The Reason Code Value. The following Reason Code values are
defined in this document:
- Value=0: Administrative (e.g., operator action or configuration
change)
- Value=1: Periodic (e.g., scheduled or timer-based)
- Value=2: Error (e.g., protocol error, failure detected)
Additional values may be defined in future documents.
Saad & Narasimha Expires 7 May 2026 [Page 8]
Internet-Draft GEN Message for BMP November 2025
4.3.6. Route Distinguisher Sub-TLV
The Route Distinguisher Event Sub-TLV allows identification of a
particular VPN routing context. When present in the BMP GEN list of
Event Sub-TLVs, the IP address that directly follows the Route
Distinguisher Event Sub-TLV MUST be interpreted within the context of
the routing instance associated with the Route Distinguisher.
The encoding of the Route Distinguisher Event Sub-TLV is shown in
Figure 8:
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=3 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Route Distinguisher |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: The Route Distinguisher Event Sub-TLV encoding
Type=3:
Identifies the Route Distinguisher Event Sub-TLV Type.
Length=8:
The length in bytes of the Route Distinguisher field (always 8
bytes).
Route Distinguisher:
The Route Distinguisher value as per [RFC4364].
4.3.7. Peer Address Event Sub-TLV
The Peer Address Event Sub-TLV identifies a BGP peer that is relevant
to the event. If more than one peer is relevant to the event,
multiple Peer Address Sub-TLVs MAY be included.
The encoding of the Peer Address Event Sub-TLV is shown in Figure 9:
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=4 | Length=(4 or 16) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Address (4 or 16 bytes) |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Saad & Narasimha Expires 7 May 2026 [Page 9]
Internet-Draft GEN Message for BMP November 2025
Figure 9: The Peer Address Event Sub-TLV encoding
Type=4:
Identifies the Peer Address Event Sub-TLV Type.
Length=(4 or 16):
The length in bytes of the Peer Address. This is 4 bytes for IPv4
address and 16-bytes for IPv6 address.
Peer Address:
The BGP Peer IPv4 or IPv6 address.
4.4. Use Cases
4.4.1. Example Scenario: RIB View Unmonitor
Description:
A BMP sender can stop exporting a RIB view to a BMP collector at
any time after its initial export. Without a notification from
the BMP sender, the collector may maintain stale state.
A RIB View Unmonitor event notifies the BMP collector that the
specific RIB view is no longer being monitored on the BMP sender
and updates for that RIB view will no longer be sent. The BMP
collector, in this case, SHOULD purge any data associated with
that RIB view that was previously received.
Scenario:
Adj-RIB-Out Export Stopped Due to Configuration Change
Background:
A network operator decides to stop exporting the Adj-RIB-Out view
for a particular peer (e.g., to reduce monitoring overhead or due
to a policy change).
Event:
The halt of Adj-RIB-Out export for all peers to the BMP collector.
Example BMP GEN Message:
The router sends a BMP GEN message to the BMP collector to notify
that the Adj-RIB-Out view export is stopped for all peers and that
any associated state should be purged.
Saad & Narasimha Expires 7 May 2026 [Page 10]
Internet-Draft GEN Message for BMP November 2025
{
"eventType": 0, // RIB View Unmonitor
"eventTimestampSeconds": 1712959200, // Seconds
"eventTimestampMicroseconds": 123, // Microseconds
"eventSubTLVs": [
{ "type": 0, "value": "Operator triggered for maintenance" },
// Reason String
{ "type": 2, "value": [0, 0, 1, 0, 0, 0, 0, 0] }
// RIB View (bitmap for Adj-RIB-Out Pre)
]
}
4.4.2. Example Scenario: Route Import Complete
Description:
Router has completed the route import activity. The trigger could
be the configuration of VPN AFI/SAFI or the relevant neighbors
coming up, among other events.
This event can be for:
- all routing instances (VRFs),
- a given routing instance, or
- a given AFI/SAFI.
Scenario:
A router has completed route import from VPN AFI/SAFI to all local
routing instances (VRFs).
Event:
The completion of a full walk of VPN AFI/SAFI and route import
activity.
Example BMP GEN Message:
The router sends a BMP GEN message to the BMP collector to notify
that import activity has completed.
{
"eventType": 1, // Route Import Complete
"eventTimestampSeconds": 1712959200, // Seconds
"eventTimestampMicroseconds": 123 // Microseconds
}
Saad & Narasimha Expires 7 May 2026 [Page 11]
Internet-Draft GEN Message for BMP November 2025
4.4.3. Example Scenario: Peer Configured is Down
Description:
The router has peers configured that are not administratively shut
down but are not operationally up. The duration for which they
are down SHOULD be a configurable value on the router.
This event can be for:
- a given peer, or
- a set of peers.
Scenario:
The operator configures a BGP peer (198.51.100.2) under the
routing instance identified by Type=1 RD (198.51.100.1:10). The
BGP peer remains in DOWN state after the configured 10-minute
interval.
Event:
The BGP peer (RD=198.51.100.1:10, 198.51.100.2) does not come up
after 10 minutes elapse from when it is configured.
Example BMP GEN Message:
The router sends a BMP GEN message to the BMP collector to notify
that the BGP peer (RD=198.51.100.1:10, 198.51.100.2) is in DOWN
state.
Note: The Route Distinguisher is encoded as an 8-octet value per
[RFC4364]. The value shown is a hexadecimal representation for
illustration.
{
"eventType": 2, // Peer in Down
"eventTimestampSeconds": 1712959200, // Seconds
"eventTimestampMicroseconds": 123, // Microseconds
"eventSubTLVs": [
{ "type": 0, "value": "Peer remains in down state" },
// Reason String
{ "type": 3, "value": [0, 1, 198, 51, 100, 1, 0, 10] },
// Route Distinguisher (8-octet value per RFC4364,
// example: 198.51.100.1:10)
{ "type": 4, "value": "198.51.100.2" } // Peer Address
]
}
Saad & Narasimha Expires 7 May 2026 [Page 12]
Internet-Draft GEN Message for BMP November 2025
5. Security Considerations
The BMP GEN messages may carry sensitive operational context.
Implementations SHOULD ensure integrity and authenticity, for example
by using transport security as recommended in [RFC7854]. Purge
notifications can affect collector state and SHOULD only be accepted
from authorized BMP senders.
6. IANA Considerations
IANA is requested to assign the following from the "BGP Monitoring
Protocol (BMP) Parameters" registry
(https://www.iana.org/assignments/bmp-parameters/).
6.1. BMP Message Type
A new BMP Message Type value (TBD1) is to be assigned for the BMP GEN
message.
6.2. BMP GEN Event Types
IANA is requested to create a new registry for BMP GEN Event Types.
The following Event Types that are defined in this document (see
Section 4.3.1):
- Type=0 : RIB View Unmonitor
- Type=1 : Route Import Complete
- Type=2 : Peer Configured is Down
6.3. BMP GEN Event Sub-TLV Types
IANA is requested to create a new registry for BMP GEN Event Sub-TLV
Types. The Event Sub-TLV Types described in Table 1 are defined in
this document.
7. Acknowledgements
The authors would like to thank Dhananjay Patki for his detailed
review and feedback. Additional thanks are extended to Jeff Haas,
Luuk Hendriks, and Ben Maddison for their valuable comments and
suggestions. Their insights greatly improved the quality and clarity
of this document.
8. References
8.1. Normative References
Saad & Narasimha Expires 7 May 2026 [Page 13]
Internet-Draft GEN Message for BMP November 2025
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/rfc/rfc4364>.
[RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP
Monitoring Protocol (BMP)", RFC 7854,
DOI 10.17487/RFC7854, June 2016,
<https://www.rfc-editor.org/rfc/rfc7854>.
8.2. 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-04, 3 September
2025, <https://datatracker.ietf.org/doc/html/draft-ietf-
grow-bmp-rel-04>.
[I-D.patki-grow-bmp-common-updates]
Patki, D. and N. Prasad, "Common BMP Route-Monitoring
Messages for Routes Unchanged by Policy", Work in
Progress, Internet-Draft, draft-patki-grow-bmp-common-
updates-02, 20 October 2025,
<https://datatracker.ietf.org/doc/html/draft-patki-grow-
bmp-common-updates-02>.
Authors' Addresses
Tarek Saad
Cisco Systems, Inc.
Canada
Email: tsaad@cisco.com
Prasad S. Narasimha
Cisco Systems, Inc.
India
Email: snprasad@cisco.com
Saad & Narasimha Expires 7 May 2026 [Page 14]