Revision to Registration Procedures for Multiple BMP Registries
draft-ietf-grow-bmp-registries-change-01
Network Working Group J. Scudder
Internet-Draft Juniper Networks
Updates: 7854 (if approved) June 3, 2019
Intended status: Standards Track
Expires: December 5, 2019
Revision to Registration Procedures for Multiple BMP Registries
draft-ietf-grow-bmp-registries-change-01.txt
Abstract
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".
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 December 5, 2019.
Copyright Notice
Copyright (c) 2019 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 Simplified BSD License text as described in Section 4.e of
Scudder Expires December 5, 2019 [Page 1]
Internet-Draft BMP TLV Registration Procedures June 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
[RFC7854] 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 [RFC8126] 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 Section 2.
2. IANA Considerations
IANA is requested to revise the following registries within the BMP
group:
o BMP Statistics Types
o BMP Initiation Message TLVs
o BMP Termination Message TLVs
o BMP Termination Message Reason Codes
o BMP Peer Down Reason Codes
o BMP Route Mirroring TLVs
o 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".
Scudder Expires December 5, 2019 [Page 2]
Internet-Draft BMP TLV Registration Procedures June 2019
3. Security Considerations
This revision to registration procedures does not change the
underlying security issues inherent in the existing [RFC7854].
4. Acknowledgements
Thanks to Jeff Haas for review and encouragement.
5. Normative References
[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>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
Show full document text