Revision to Registration Procedures for Multiple BMP Registries
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale
CA
94089
USA
jgs@juniper.net
General
Network Working Group
IDR
This document updates RFC 7854, BGP Monitoring Protocol (BMP) by making
a change to the registration procedures for several registries.
Specifically, any BMP registry with a range of 32768-65530 designated
"Specification Required" has that range re-designated as "First Come
First Served".
creates a number of IANA registries that
include a range of 32768-65530 designated "Specification Required".
Each such registry also has a large range designated "Standards
Action". Subsequent experience has shown two things. First, there is
less difference between these two policies in practice than there is in
theory (consider that explains that for
Specification Required, "Publication of an RFC is an ideal means of
achieving this requirement"). Second, it's desirable to have a very low
bar to registration, to avoid the risk of conflicts introduced by use
of unregistered code points (so-called "code point squatting").
Accordingly, this document revises the registration procedures, as given
in .
IANA is requested to revise the following registries within the BMP
group:
BMP Statistics Types
BMP Initiation Message TLVs
BMP Termination Message TLVs
BMP Termination Message Reason Codes
BMP Peer Down Reason Codes
BMP Route Mirroring TLVs
BMP Route Mirroring Information Codes
For each of these registries, the ranges 32768-65530 whose registration
procedures were "Specification Required" are revised to have the
registration procedures "First Come First Served".
This revision to registration procedures does not change the
underlying security issues inherent in the existing .
Thanks to Jeff Haas for review and encouragement.