Extension for BMP Peer Header

When BGP establishes a peer relationship using a Link-Local address or unnumbered address, the local outgoing interface must be specified for the relationship to be established successfully. In other words, BGP Link-Local or unnumbered peers may only be distinguished by interface information. However, the per-peer information in a BMP message does not include interface information, making it impossible to distinguish which BGP Link-Local peer or unnumbered peer the reported BMP message originated from. This document defines new BMP peer types that allows the per-peer header to carry its corresponding peer interface information.

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.

This section defines new BMP peer types for reporting the BMP messages that need to be distinguished through peer interface intormation. The peer types are defined as follows:

Peer Type = TBD1 (RECOMMENDED value 4): Global Instance Interface Peer.
Peer Type = TBD2 (RECOMMENDED value 5): RD Instance Interface Peer.

BMP messages using the peer types defined in this document MUST include peer interface information.

For new BMP peer types defined in this document, this section defines a interface per-peer header. It is defined according to per-peer header of , as shown below:

Compared with per-peer header of , the Peer Interface Index is added to indicate the interface used to establish BGP peers. Other fields are defined in Section 4.2 of and Section 4 of .

TBD