BMP v4: Extended TLV Support for BGP Monitoring Protocol (BMP)

BMP v4: Extended TLV Support for BGP Monitoring Protocol (BMP) NTT

Veemweg 23 Barneveld 3771 NL paolo@ntt.net

Huawei

Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China guyunan@huawei.com

INSA-Lyon

France maxence.younsi@insa-lyon.fr

INSA-Lyon

France pierre.francois@insa-lyon.fr

General Global Routing Operations BGP BMP tlv Most of the BGP Monitoring Protocol (BMP) message types make provision for data in Type, Length, Value (TLV) format. However, Route Monitoring messages (which provide a snapshot of the monitored Routing Information Base) Stats Reports (which supply periodical counters) and Peer Down messages (which indicate that a peering session was terminated) do not. Supporting (optional) data in TLV format across all BMP message types provides consistent and extensible structures that would be useful in the various use cases where conveying additional data to a monitoring station is required. This document updates RFC 7854 to support TLV data in all message types and defines some essential TLVs. Additionally, this document introduces support for enterprise-specific TLVs in the BGP Monitoring Protocol by defining an Enterprise Bit (E-bit) that allows usage of per-vendor Type values.

The BGP Monitoring Protocol (BMP) version 3 is defined in RFC 7854. The Route Monitoring message is defined in Section 4.6 of and consists of: Common Header Per-Peer Header BGP Update PDU The Stats Reports message is defined in Section 4.8 of and consists of: Common Header Per-Peer Header Stats Count Stats in TLV format The Peer Down Notification message is defined in Section 4.9 of and consists of: Common Header Per-Peer Header Reason Data (only if Reason code is 1, 2 or 3) TLV (only if Reason code is 6) This means that Route Monitoring, Stats Reports and Peer Down messages have a non-extensible format (except for the specific case of Peer Down Reason Code 6 as specified in Section 5.3 of). In the Route Monitoring case, this prevents the transmission of parsing characteristics of transported NLRIs (e.g. ADD-PATH, Multi Labels, etc.), RIB status of a path (e.g. primary, backup, unused, etc.) or of vendor- specific data. In the Stats Reports and Peer Down case, this prevents matching with TLVs previously sent in other messages, including the Peer Up message. This document: Bumps the BMP version for all message types defined in RFC 7854, allowing receivers to distinguish BMPv4 from BMPv3 and handle it explicitly Changes the structure of Route Monitoring message type so that the BGP Update PDU is enclosed in a TLV. The BGP Message TLV is mandatory Allows all defined BMP message types to make provision for optional TLV data. Also, vendors need the ability to define proprietary Information Elements for reasons such as delivering pre-standard products, this need aligns with Section 4.1 of. The E-bit allows early development phases to interoperate among vendors by defining enterprise-specific TLVs without conflicting with existing IANA allocations. The concept of an E-bit is not new. For example, such mechanism is defined in Section 3.2 of for a very similar purpose.

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 RFC 2119 RFC 8174 when, and only when, they appear in all capitals, as shown here. The document uses the terms defined in RFC 7854.

For an exporter to flag a receiver that it complies with this specification, the Version field of the BMP Common Header, documented in Section 4.4 of, MUST be set to 4. This applies to every BMP message type. If a BMP station does not support the version indicated in the message, it SHOULD close the session and take the procedures described in Error Handling.

The TLV data type (Information TLV) is defined in Section 4.4 of for the Initiation and Peer Up message types. The definition is updated as described in IANA-registered TLV Encoding and further extended by Enterprise-specific TLV Encoding, IANA-registered Indexed TLV Encoding and Enterprise-specific Indexed TLV Encoding.

1 bit to flag an enterprise-specific TLV, set to 0. The TLV Type value MUST have been defined in IANA-BMP 15 bits of TLV Type, 2 octets of TLV Length, and 0 or more octets of TLV Value.

Enterprise-specific TLV encoding is defined as follows: 1 bit to flag an enterprise-specific TLV, set to 1 15 bits of TLV Type, 2 octets of TLV length. This comprises the length of the IANA PEN plus the TLV Value. 4 octets of IANA Private Enterprise Number IANA-PEN 0 or more octets of TLV Value.

Stats Report messages are also encoded in a TLV-like fashion, as documented in Section 4.8 of. the E-bit therefore similarly applies to these messages too, with the most significant bit of Stat Type set to 1 in order to flag the presence of a 4-byte PEN field following Stat Len field and preceding Stat Data field, i.e.:

While the encoding is not per se backward compatible, there is no existing IANA-allocated Type value that makes use of the most significant bit (which is being used in this document to define the E-bit), except the experimental and reserved ones mentioned in Section 10.5 of, Section 10.6 of and Section 10.9 of. Of these, the Experimental values are being suppressed in favor of using the E-bit mechanism described in this document; the Reserved value is instead excluded by the E-bit mechanism such that no PEN will be included as part of the TLV. Future BMPv4 message types MUST make use of the TLV encoding defined in this document.

Route Monitoring messages may require per-NLRI TLVs. That is, there may be a need to map TLVs to NLRIs contained in the BGP Update message, for example, to express additional characteristics of a specific NLRI. For this purpose, TLVs enclosed in a Route Monitoring message MUST be indexed, with the index starting at one (1) to refer to the first NLRI. Index zero (0) specifies that a TLV applies to all NLRIs contained in the BGP Update PDU. TLVs that are message-wide rather than NLRI-specific also use Index zero, as specified in their respective definitions. An NLRI Index identifies an NLRI occurrence in the BGP Update PDU. NLRIs are numbered sequentially, starting at one (1), in the order in which they occur in the BGP Update PDU, as follows:

Each NLRI in the Withdrawn Routes field, in encoded order.
For each Path Attribute that carries NLRIs, in the order in which the Path Attributes appear in the UPDATE, each NLRI carried by that attribute, in encoded order. This includes NLRIs in MP_UNREACH_NLRI and MP_REACH_NLRI attributes.
Each NLRI in the trailing IPv4-unicast NLRI field, in encoded order, if present.

Each occurrence of an NLRI is indexed independently. In particular, if the same prefix appears more than once in the BGP Update PDU, including with different Path Identifiers when ADD-PATH is in use, each occurrence receives a distinct NLRI Index. Withdrawn NLRIs and advertised NLRIs share the same NLRI Index space. The Index field is 2 bytes long, of which the top-most bit, G-bit, is used to flag a Group Index (more in ). TLVs of the same type and with the same index can be repeated as part of the same message, unless specified otherwise by the definition of the specific TLV. Indexed TLVs are encoded as in the following figure:

The reported length in indexed TLVs refers to the total encoded TLV value (i.e., with the length of the index field excluded). A monitoring station can properly match indexed TLVs to the corresponding NLRI only if - or as long as - NLRIs are decoded successfully. In case of any parsing or error condition that prevents full decoding of the BGP PDU, the station MUST stop matching indexed TLVs to NLRIs. Of the BMP message types defined so far, indexed TLVs apply only to Route Monitoring messages. For example, they do not apply to Route Mirroring messages because a sender may not be aware of the payload of the transported BGP Update message.

For completeness, following is an illustration of the structure of an Enterprise-specific Indexed TLV.

While the structure of the Common Header remains unaltered, the following two definitions are changed compared to : Version: Indicates the BMP version. This is set to '4' for all message types defined in RFC 7854. Message Length: Total length of the message in bytes (including headers, encapsulated BGP Message TLV and optional TLV data).

For consistency with the Route Mirroring type defined in , this document extends the encoding of the Route Monitoring message type where the Per-Peer Header is followed by mandatory and optional TLVs. The BGP Update PDU () is encoded itself as part of a BGP Message TLV with code point &IANA_RM_CODE_BGP_PDU; and index set to 0. A Route Monitoring message MUST contain one BGP Message TLV which may be preceded or followed by other optional TLV data. Consequently, the BGP Update PDU is not encoded as part of the message as was the case for BMPv3 (RFC 7854) but it is rather enclosed in a TLV.

In a Route Monitoring message where a BGP Update PDU carries N NLRIs, indexed TLVs allow handling of the cases of 1:1 and N:1 relationship among TLVs and NLRIs (i.e., one TLV applies to one NLRI, N TLVs apply to one same NLRI). The cases of 1:N and M:N relationships (i.e., one TLV applies to N NLRIs and M TLVs apply to N NLRIs) can benefit from grouping. For that purpose, a Group TLV is defined with the aim to limit both verbosity and repetitions. The 2-byte index defines a new Group Index and the top-most bit (G-bit) MUST be set to 1. The full 2-byte value, that is including the G-bit, MUST be unique to the message. The value carries two or more 2-byte NLRI indexes whose values MUST be less than or equal to the number of NLRIs packed in the BGP Update PDU. An NLRI index can be listed as part of multiple Group TLVs within the same message. NLRI indexes within a Group TLV SHOULD be sorted by the sender. A Group Index MUST NOT reference an NLRI index 0. A Group TLV MUST NOT include its own or another Group Index. Multiple non-Group TLVs MAY point to the same Group Index, i.e., a group can be reused within the same Route Monitoring message. The Group TLV type is &IANA_RM_CODE_GROUP;. It is RECOMMENDED that this TLV is encoded first in order to ease parsing of the Route Monitoring message at the BMP station side.

The Value field contains a UTF-8 string whose value MUST be equal to the value of the VRF or table name (i.e., RD instance name) being conveyed. The string size MUST be within the range of 1 to 255 bytes. This is in line with . The VRF/Table Name TLV type is &IANA_RM_CODE_VRF;.

Stateless parsing helps scaling the number of Route Monitoring messages that can be processed at collection time, avoiding having to correlate them to BGP capabilities received as part of the Peer Up message, for example. Some BGP capabilities are not per AFI/SAFI, like 4-byte ASN RFC 6793, and hence these can potentially be part of the BMP Peer flags of a Route Monitoring message. Those that are, instead, per AFI/SAFI require finer granularity and hence the need to use an indexed TLV. To maintain the consistency between BGP Capabilities, they are all carried in Stateless Parsing TLVs, regardless of their type. The encoding of BGP Capabilities is already generically defined in Section 4 of . It includes every information needed for its understanding, including AFI/SAFI codes. This encoding can be reused in the Stateless Parsing TLV, leveraging already existing BGP encoders and decoders for implementers. The Stateless Parsing TLV type is &IANA_RM_CODE_SP; and its Value is the BGP Capability encoded as exactly as it would be in the BGP OPEN of the session. It is thus made of all three Capability Code, Capability Length, and Capability Value fields defined in . For example, an ADD-PATH capability, as defined by RFC 7911, for IP/Unicast with value Send/Receive would be encoded as a BGP Capability as: Capability Code, 1 byte, value=69 Capability Length, 1 byte, value=4 AFI, 2 bytes, value=1 SAFI, 1 byte, value=1 Value, 1 byte, value=3 The index of the Stateless Parsing TLV MUST be set to 0. If no Stateless Parsing TLV is present in a Route Monitoring message, the receiver MUST fall back to use capabilities present in the BGP Open PDU contained in the relevant BMP Peer Up message in order to properly parse BGP Update PDUs. Each BGP capability MUST be encoded in a separate Stateless Parsing TLV. It is RECOMMENDED that the Stateless Parsing TLV is encoded preceding the BGP Message TLV in order to ease parsing of the Route Monitoring message at the BMP station side.

The Peer Down Notification message type () is extended following a consistent approach with the Peer Up type (). That is, the message is extended so that optional TLVs are placed at the end of the message. This means for Reason codes 1 or 3, a BGP Notification PDU follows; the PDU MAY be further followed by TLV data. For Reason code 2, a 2-byte field follows to provide additional Finite State Machine (FSM) info; this field MAY be followed by TLV data. For all other Reason codes, TLV data MAY follow the Reason field.

The Stats Reports message is extended so that the Stats Count and stats data as defined in Section 4.8 of are all enclosed inside a Stats TLV with code point &IANA_SR_CODE_STATS;. The Stats TLV is mandatory and can be followed by optional TLV data. While the Stats Count field could be used to discriminate among stats data and trailing optional TLV data, it is felt that enclosing Stats Count and stats data inside a container TLV is cleaner by embracing a fully TLV'd body.

All other message types defined in RFC 7854 do already provision for TLV data. It is RECOMMENDED that all future BMPv4 message types provide optional TLV data, consistently with existing message types.

In this section some TLVs are introduced that apply to all existing BMP message types and as such will need a code point reserved in all TLV registries, namely: BMP Initiation Information TLVs, BMP Termination Message TLVs, BMP Route Mirroring TLVs along with registries defined in this document BMP Route Monitoring TLVs, BMP Peer Up and Peer Down TLVs and BMP Stats Reports TLVs. We thus request IANA to allocate, for each TLV, the same codepoint value in every TLV codepoint registry of this document, as detailed in their respective sections.

The Timestamp TLV carries one of several timestamp types for a BMP message. For each TLV registry seeded in this document, the code point of the Timestamp TLV is &IANA_RM_CODE_TSTAMP;. The value of the TLV is the Timestamp Type code, defined in followed by a 4-byte "Timestamp Seconds" field representing the number of seconds since midnight (zero hour), January 1, 1970 (UTC). The Timestamp TLV also optionally supports microseconds precision. If available, the subsecond microseconds of the timestamp follow the "Timestamp Seconds" as a 4-byte field called "Timestamp Microseconds". When using microseconds precision, the encoding of the timestamp is identical to existing BMP documents , , and . The timestamp MUST NOT be set to zero to indicate unavailability. For the timestamp field in the Per-Peer Header this means that it MUST always be populated. The Timestamp TLV is optional; a timestamp MUST NOT be included if it is not available. The value of the Length field is 5 bytes (1 byte for the Timestamp Type field plus the length of the 4-byte "Timestamp Seconds" field). The value of the Length field is 9 bytes when microseconds are included as the "Timestamp Microseconds" field. The Index field is not included in the length. The TLV structure including the index, i.e., suitable for the Route Monitoring message type, is illustrated in .

Timestamp TLV 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) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |G| Index (2 octets) | Timestamp Type| ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Timestamp Seconds | ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Timestamp Microseconds (optional) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ defines the list of currently defined Timestamp Types.

defines the list of timestamp types that can be carried in the Timestamp TLV. Each timestamp type is described in the section associated with its name and code in the table.

Code	Name	Section
&IANA_TIMESTAMP_CODE_TRIGGER;	Trigger Time
&IANA_TIMESTAMP_CODE_EXPORT;	Message Export Time
&IANA_TIMESTAMP_CODE_ADJINPRE;	Adj-RIB-In Pre-Policy Time
&IANA_TIMESTAMP_CODE_ADJINPOST;	Adj-RIB-In Post-Policy Time
&IANA_TIMESTAMP_CODE_LOCRIB;	Local-RIB Time
&IANA_TIMESTAMP_CODE_ADJOUTPRE;	Adj-RIB-Out Pre-Policy Time
&IANA_TIMESTAMP_CODE_ADJOUTPOST;	Adj-RIB-Out Post-Policy Time

The Trigger Time is the timestamp of the event which triggered BMP to report the event. This might be a received message, a BGP peering or a BMP session going down or up, etc. This type applies to all BMP messages and is unique within a BMP message. In message types that require indexing the index field MUST be included and set to zero.

The Message Export Time is the time at which BMP generates the BMP message. This type applies to all BMP messages and is unique within a BMP message. In message types that require indexing the index field must be included and set to zero.

The Adj-RIB-In Pre-Policy and Adj-RIB-In Post-Policy Times are the times at which the route has been installed in the Adj-RIB-In Pre-Policy and Post-Policy, as per . This type is per NLRI and hence applies only to message types supporting indexing. If the timestamp applies to all NLRIs in a BGP PDU, index MUST be zero.

The Local-RIB Time is the time at which the route has been installed in the Local-RIB, as per . This type is per NLRI and hence applies only to message types supporting indexing. If the timestamp applies to all NLRIs in a BGP PDU, index must be zero.

The Adj-RIB-Out Pre-Policy and Adj-RIB-Out Post-Policy Times are the times at which the route has been installed in the Adj-RIB-Out Pre-Policy and Post-Policy, as per . This type is per NLRI and hence applies only to message types supporting indexing. If the timestamp applies to all NLRIs in a BGP PDU, index MUST be zero.

The Sequence Number TLV carries the sequence number of a message in a BMP session. For each TLV registry seeded in this document, the code point of the Sequence Number TLV is &IANA_RM_CODE_SEQ;. In BMP message types that require indexing, for example Route Monitoring, the index field MUST be included and set to zero. This TLV MUST NOT be repeated within the same message. Ordering of BMP messages based on timestamp becomes complicated when timestamps have conflicting meanings or when they are simply unavailable. A Sequence Number on a per BMP session basis allows the operator to easily and uniquely identify BMP messages on a BMP session. The value of the TLV is the sequence number of the BMP message in the BMP session, starting at 0, and encoded as an 8-byte integer. If the sequence number would overflow, the BMP session MUST be reset. The value of the Length field is 8. The Index field is not included in the length. The TLV structure including the index, i.e., suitable for the Route Monitoring message type, is illustrated in .

Sequence Number TLV 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) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |G| Index (2 octets) | ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + ~ Sequence Number (8 octets) ~ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Extended Flags TLV carries the Flags field usually present in the Per-Peer Header, while extending the length of the field. This allows for a larger range of flags to be allocated in the future. For each TLV registry seeded in this document, the code point of the Extended Flags TLV is &IANA_RM_CODE_EXT_FLAGS;. In BMP message types that require indexing, for example Route Monitoring, the index field MUST be included and set to zero. This TLV MUST NOT be repeated within the same message. The value of the TLV is a sequence of bytes of variable size. The minimum size of the sequence is one byte, to fit at least the already existing flags. The flags carried in this TLV are defined in the BMP Extended Peer Flags IANA registry defined by this document. The first byte of the sequence carries all flags defined prior to this document, that is Flags V, L, A, O, and F as defined in Section 10.3 of, Section 9.1 of and Section 4.2 of. The value of the Length field is the number of bytes in the sequence. The Index field is not included in the length. The TLV structure including the index, i.e., suitable for the Route Monitoring message type, is illustrated in .

Extended Flags TLV 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) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |G| Index (2 octets) | Flags (Variable) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When this TLV is included in a BMP message, the rightmost bit (X Flag) of the Per-Peer Header Flags MUST be set to 1 to indicate that the flags to consider are carried in this TLV. The flags in the Per-Peer Header are still set according to the current specification, allowing collectors that do not understand the X Flag and Extended Flags TLV to still function. Unused bits of the first byte are declared as reserved, newly allocated bits will be carried in the following byte(s) of the sequence and counting of the bits will always start at bit zero of the first byte (i.e., first bit of the second byte will be 8).

RFC 8654 permits BGP Update and other messages to grow to a length of 65535 octets. This may cause a BMP PDU that attempts to encapsulate such long messages to overflow. A BMP exporter and a BMP station may not support the same version of the protocol. Because BMP is unidirectional, with data flowing only from the exporter to the station, the station SHOULD close the BMP session and log the condition as a warning; the exporter SHOULD retry connecting with a non-aggressive timer. A BMP station may not support some of the TLVs encoded by the exporter; the station MUST ignore unsupported TLV types; additionally, in case of indexed TLVs, if the index is invalid (i.e. out of bounds), the TLV MUST be ignored. A Group TLV or an indexed TLV that references an undefined Group Index MUST also be ignored. The station SHOULD log the condition as a warning.

It is not believed that this document adds any additional security considerations compared to RFC 7854.

In Route Monitoring messages, the number of TLVs can be bound to the number of NLRIs carried in the BGP Update message. This may degrade the packing of information in such messages and have specific impacts on the memory and CPU used in a BMP implementation. As a result of that it SHOULD always be possible to disable such features to mitigate their impact. Multiple TLVs of the same type can be repeated as part of the same message; it is left to the specific use cases whether all, any, the first or the last TLV should be considered as well as whether ordering matters and repeating is allowed. It is RECOMMENDED that implementers making use of the Enterprise Bit extension have a well-defined internal registry for privately assigned code points that is also exposed to the public.

Minimum compliance when upgrading a BMP exporter from BMPv3 to BMPv4:

Version change from 3 to 4 in the Common Header
The Per-Peer Header timestamp MUST NOT be zero
BGP Message TLV in Route Monitoring message
Stats TLV container in Stats Report message

This document asks IANA to rename, create, change registration procedures and available values for, and add assignments to registries.

IANA is requested to create a new registry "BMP Route Monitoring TLVs" which is to be seeded with the following new TLV types (): Type = &IANA_RM_CODE_SEQ;: Sequence Number TLV. The value field is defined in . Type = &IANA_RM_CODE_EXT_FLAGS;: Extended Flags TLV. The value field is defined in . Type = &IANA_RM_CODE_TSTAMP;: Timestamp TLV. The value field is defined in . Type = &IANA_RM_CODE_GROUP;: Group TLV. The value field is defined in . Type = &IANA_RM_CODE_VRF;: VRF/Table Name TLV. The value field is defined in . Type = &IANA_RM_CODE_SP;: Stateless Parsing TLV. The value field is defined in . Type = &IANA_RM_CODE_BGP_PDU;: BGP Message TLV. The value field is defined in . Values 0 through 16383 of the "BMP Route Monitoring TLVs" registry MUST be assigned using the Standards Action policy as defined in Section 4.9 of; values 16384 through 32767 MUST be assigned using the First Come First Served policy as defined in Section 4.4 of. The upper bound of the registry is 65535. Values 32768 through 65534 are enterprise-specific as identified by the E-bit and therefore not IANA-assigned. Value 65535 is Reserved.

IANA is requested to create a new registry "BMP Stats Reports TLVs" seeded with the following new TLV types (): Type = &IANA_SR_CODE_STATS;: Stats TLV. It encloses Stats Count and stats data. The value field is defined in . Type = &IANA_RM_CODE_SEQ;: Sequence Number TLV. The value field is defined in . Type = &IANA_RM_CODE_EXT_FLAGS;: Extended Flags TLV. The value field is defined in . Type = &IANA_RM_CODE_TSTAMP;: Timestamp TLV. The value field is defined in . Values 0 through 16383 of the "BMP Stats Reports TLVs" registry MUST be assigned using the Standards Action policy as defined in Section 4.9 of; values 16384 through 32767 MUST be assigned using the First Come First Served policy as defined in Section 4.4 of. The upper bound of the registry is 65535. Values 32768 through 65534 are enterprise-specific as identified by the E-bit and therefore not IANA-assigned. Value 65535 is Reserved.

The "BMP Peer Up Message TLVs" registry defined by BMP Peer Up Message Namespace is to be renamed "BMP Peer Up and Peer Down TLVs". For BMP Initiation Information TLVs, BMP Termination Message TLVs, BMP Peer Up and Peer Down TLVs and BMP Route Mirroring TLVs registries it is requested to make the range 0-16383 as Standards Action (down from current 0-32767); it also asks to make the range 16384-32767 as First Come First Served (in place of current 32768-65530). Values 32768 through 65534 are enterprise-specific as identified by the E-bit and therefore not IANA-assigned. This document also requests to remove the Experimental allocation from the same registries, the code points now flagged Experimental will become Unassigned. The high-order, or leftmost, bit of each registry will be assigned to the E-bit, hence reducing the Unassigned pool: the maximum available value for assignment for the registries will be 32767 (i.e., as opposed to current 65530). For the same registries, this document requests IANA to allocate the code points for Timestamp TLV (&IANA_ALL_CODE_TSTAMP;), Sequence Number TLV (&IANA_ALL_CODE_SEQ;) and Extended Flags TLV (&IANA_ALL_CODE_EXT_FLAGS;). IANA is requested to assign the code points consistently to "BMP Route Monitoring TLVs" and "BMP Stats Reports TLVs" registries seeded in this document (i.e., Timestamp TLV = &IANA_RM_CODE_TSTAMP;, etc.). This document requests that IANA assign the following new code points to the "BMP Peer Flags for Peer Types 0 through 2" and the "BMP Peer Flags for Loc-RIB Instance Peer Type" registries:

Flag 5: Reserved
Flag 6: Reserved
Flag 7: X flag (Extended Flags). Set if the Flags are carried in the Extended Flags TLV instead of the Per-Peer Header.

This document also requests the definition of a "BMP Extended Peer Flags" registry which allocates flags contained in the Extended Flags TLV. The size of this registry is TBD. The registration policy for this registry is Standards Action as defined in . The registry is seeded as follows:

Flag 0: V flag
Flag 1: L flag
Flag 2: A flag
Flag 3: O flag
Flag 4: F flag
Flag 5: Reserved
Flag 6: Reserved
Flag 7: X flag defined in this document

This document also requests the definition of a "BMP Timestamp Types" registry. This registry contains code points for the type of timestamp carried by the Timestamp TLV. The size of the registry matches the size of the Timestamp Type field defined in which is 1 byte. The registration policy for this registry is Expert Review as defined in . The registry is seeded as follows:

Type = 0: Reserved.
Type = &IANA_TIMESTAMP_CODE_TRIGGER;: Trigger Time. The timestamp corresponds to the event that triggered BMP to report the route or state, such as receiving a message or a session transition.
Type = &IANA_TIMESTAMP_CODE_EXPORT;: Message Export Time. The timestamp corresponds to the time when the BMP message was generated for export.
Type = &IANA_TIMESTAMP_CODE_ADJINPRE;: Adj-RIB-In Pre-Policy Time. The timestamp corresponds to when the route was installed in the Adj-RIB-In Pre-Policy, as per .
Type = &IANA_TIMESTAMP_CODE_ADJINPOST;: Adj-RIB-In Post-Policy Time. The timestamp corresponds to when the route was installed in the Adj-RIB-In Post-Policy, as per .
Type = &IANA_TIMESTAMP_CODE_LOCRIB;: Local-RIB Time. The timestamp corresponds to when the route was installed in the Local-RIB, as per .
Type = &IANA_TIMESTAMP_CODE_ADJOUTPRE;: Adj-RIB-Out Pre-Policy Time. The timestamp corresponds to when the route was installed in the Adj-RIB-Out Pre-Policy, as per .
Type = &IANA_TIMESTAMP_CODE_ADJOUTPOST;: Adj-RIB-Out Post-Policy Time. The timestamp corresponds to when the route was installed in the Adj-RIB-Out Post-Policy, as per .

The TLV Type values used by BMP are managed by IANA as are the Private Enterprise Numbers used by enterprise-specific Type values IANA-PEN.

&RFC2119; &RFC8174; BGP Monitoring Protocol (BMP) Parameters IANA BMP Peer Flags IANA Private Enterprise Numbers IANA

The diagram in shows an example of a Route Monitoring message carrying a BGP UPDATE containing 10 NLRIs. The message contains the following TLVs: a Group TLV with index 0x800b, pointing to NLRI 1, 2, 3 and 10 a Group TLV with index 0x800c, pointing to NLRI 4, 5 and 6 a Stateless Parsing TLV with index 0x0000, stating that the Add-Path Capability is set to Both (Snd/Rcv) for the IPv4 Unicast address family in the BGP UPDATE. a TLV pertaining to NLRI 7 a TLV pertaining to the NLRIs listed in the Group TLV defined in 1 a TLV pertaining to the NLRIs listed in the Group TLV defined in 2

The authors would like to thank Jeff Haas, Camilo Cardona, Thomas Graf, Pierre Francois, Ben Maddison, Tim Evens, Luuk Hendriks, Maxence Younsi, Ahmed Elhassany, Colin Petrie, Dhananjay Pakti and Shunwan Zhuang for their valuable input. The authors would also like to thank Greg Skinner, Zongpeng Du and Mohamed Boucadair for their review.