Extension for BMP Peer Header
draft-lin-grow-bmp-peer-interface-00
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.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
|
|
|---|---|---|---|
| Authors | Changwang Lin , Yisong Liu , Mukul Kumar Srivastava | ||
| Last updated | 2026-02-27 | ||
| RFC stream | (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-lin-grow-bmp-peer-interface-00
GROW C. Lin
Internet-Draft New H3C Technologies
Intended status: Standards Track Y. Liu
Expires: 31 August 2026 China Mobile
M. Srivastava
Hewlett Packard Enterprise
27 February 2026
Extension for BMP Peer Header
draft-lin-grow-bmp-peer-interface-00
Abstract
This document defines new BMP peer types that allows the per-peer
header to carry its corresponding interface information, especially
in order to distinguish BGP peers established based on interfaces.
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 August 2026.
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
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.
Lin, et al. Expires 31 August 2026 [Page 1]
Internet-Draft BMP Peer Interface February 2026
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. New BMP Peer Types . . . . . . . . . . . . . . . . . . . . . 2
3.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 2
3.2. Format . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Operational Considerations . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
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.
2. Terminology
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.
3. New BMP Peer Types
3.1. Definition
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:
Lin, et al. Expires 31 August 2026 [Page 2]
Internet-Draft BMP Peer Interface February 2026
* 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.
3.2. Format
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 [RFC7854], as shown below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type | Peer Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Distinguisher (present based on peer type) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Address (16 bytes) |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Interface Index (present based on peer type) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer BGP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp (seconds) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp (microseconds) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Compared with per-peer header of [RFC7854], the Peer Interface Index
is added to indicate the interface used to establish BGP peers.
Other fields are defined in Section 4.2 of [RFC7854] and Section 4 of
[RFC8671].
4. Operational Considerations
TBD
Lin, et al. Expires 31 August 2026 [Page 3]
Internet-Draft BMP Peer Interface February 2026
5. Security Considerations
TBD
6. IANA Considerations
TBD
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[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/info/rfc7854>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8671] Evens, T., Bayraktar, S., Lucente, P., Mi, P., and S.
Zhuang, "Support for Adj-RIB-Out in the BGP Monitoring
Protocol (BMP)", RFC 8671, DOI 10.17487/RFC8671, November
2019, <https://www.rfc-editor.org/info/rfc8671>.
Authors' Addresses
Changwang Lin
New H3C Technologies
Beijing
China
Email: linchangwang.04414@h3c.com
Yisong Liu
China Mobile
32 Xuanwumen West Street
Beijing
Xicheng District, 100053
China
Email: liuyisong@chinamobile.com
Lin, et al. Expires 31 August 2026 [Page 4]
Internet-Draft BMP Peer Interface February 2026
Mukul Srivastava
Hewlett Packard Enterprise
Email: mukul.srivastava@hpe.com
Lin, et al. Expires 31 August 2026 [Page 5]