Technical Summary
RFC 7854, BMP, uses different message types for different purposes.
Most of these are Type, Length, Value (TLV) structured. One message
type, the Peer Up message, lacks a set of TLVs defined for its use,
instead sharing a namespace with the Initiation message. Subsequent
experience has shown that this namespace sharing was a mistake, as it
hampers the extension of the protocol.
This document updates RFC 7854 by creating an independent namespace
for the Peer Up message. It also updates RFC 8671 and RFC 9069 by
moving the defined codepoints in the newly introduced registry. The
changes in this document are formal only, compliant implementations
of RFC 7854, RFC 8671 and RFC 9069 also comply with this
specification.
Working Group Summary
A few people spoke in favor of publication, no objections were raised.
This is really not surprising for this sort of document - it's a process / registration type document.
Document Quality
The document is clear, readable and short.
It contains an Implementation Status section, 2 open source
implementations exist: FRRouting & pmacct.
Personnel
Job Snijders is DS.
Warren "Ace" Kumari is RAD!!!!