BMP Peer Up Message Namespace

defines a number of different BMP message types. With the exception of the Route Monitoring message type, these messages are TLV-structured. Most message types have distinct namespaces and IANA registries. However, the namespace of the Peer Up message overlaps that of the Initiation message. As the BMP protocol has been extended, this oversight has become problematic. In this document, we create a distinct namespace for the Peer Up message to eliminate this overlap, and create the corresponding missing registry. The changes in this document are formal only, compliant implementations of , and also comply with this specification.

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 when, and only when, they appear in all capitals, as shown here.

A string TLV is a free-form sequence of UTF-8 characters whose length in bytes is given by the TLV's Length field. There is no requirement to terminate the string with a null (or any other particular) character -- the Length field gives its termination.

We update as follows: The "Information TLV" of section 4.4, that was shared between the Initiation and Peer Up message types, is renamed as the "Initiation Information TLV", and is only relevant to the Initiation message type. A "Peer Up Information TLV" is defined, and is relevant to the Peer Up message type. A "BMP Peer Up Information TLVs" registry is is created, seeded with the Peer Up Information TLV. Other than as summarized above, and detailed below, there are no other changes.

The Information TLV defined in section 4.4 of is renamed "Initiation Information TLV". It is used only by the Initiation message, not by the Peer Up message. The definition of Type = 0 is revised to be: Type = 0: String. The Information field contains a string. The value is administratively assigned. If multiple strings are included, their ordering MUST be preserved when they are reported. Type = 1: sysDescr. The Information field contains an ASCII string whose value MUST be set to be equal to the value of the sysDescr MIB-II object. Type = 2: sysName. The Information field contains an ASCII string whose value MUST be set to be equal to the value of the sysName MIB-II object.

The final paragraph of section 4.10 of references the Information TLV (which is revised above). That paragraph is replaced by the following: Information: Information about the peer, using the Peer Up Information TLV format defined below. The String type may be repeated. Inclusion of the Information field is OPTIONAL. Its presence or absence can be inferred by inspection of the Message Length in the common header.

The Peer Up Information TLV is used by the Peer Up message.

Information Type (2 bytes): Type of information provided. Defined types are: Type = 0: String. The Information field contains a string. The value is administratively assigned. If multiple strings are included, their ordering MUST be preserved when they are reported. Type = 3: VRF/Table Name. The Information field contains a UTF-8 string whose value MUST be equal to the value of the VRF or table name (e.g., RD instance name) being conveyed. The string size MUST be within the range of 1 to 255 bytes. Type = 4: Admin Label. The Information field contains a free-form UTF-8 string whose byte length is given by the Information Length field. The value is administratively assigned. There is no requirement to terminate the string with null or any other character. Information Length (2 bytes): The length of the following Information field, in bytes. Information (variable): Information about the monitored router, according to the type.

IANA is requested to create a registry within the BMP group, named "BMP Peer Up Message TLVs", reference this document. Registration procedures for this registry are: Range Registration Procedures 0, 3-32767 Standards Action 32768-65530 First Come, First Served 65531-65534 Experimental 1-2, 65535 Reserved Initial values for this registry are: Type Description Reference 0 String this document 1 Reserved this document 2 Reserved this document 3 VRF/Table Name this document 4 Admin Label this document 65535 Reserved this document IANA is also requested to rename the existing "BMP Initiation and Peer Up Information TLVs" registry to "BMP Initiation Information TLVs" and seed it with the following values: Type Description Reference 0 String this document 1 sysDescr this document 2 sysName this document 3 Reserved this document 4 Reserved this document 65535 Reserved this document

This rearrangement of deck chairs does not change the underlying security issues inherent in the existing .

This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. As of today these vendors have produced an implementation of the BMP Peer Up Namespace: FRRouting pmacct

The authors would like to thank Maxence Younsi for his review.