rfc9515.original | rfc9515.txt | |||
---|---|---|---|---|
d | ||||
Network Working Group J. Scudder | Internet Engineering Task Force (IETF) J. Scudder | |||
Internet-Draft Juniper Networks | Request for Comments: 9515 Juniper Networks | |||
Updates: 7854 (if approved) 22 September 2023 | Updates: 7854 December 2023 | |||
Intended status: Standards Track | Category: Standards Track | |||
Expires: 25 March 2024 | ISSN: 2070-1721 | |||
Revision to Registration Procedures for Multiple BMP Registries | Revision to Registration Procedures for Multiple BMP Registries | |||
draft-ietf-grow-bmp-registries-change-04 | ||||
Abstract | Abstract | |||
This document updates RFC 7854, BGP Monitoring Protocol (BMP) by | This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by | |||
making a change to the registration procedures for several | changing the registration procedures for several registries. | |||
registries. Specifically, any BMP registry with a range of | Specifically, any BMP registry with a range of 32768-65530 designated | |||
32768-65530 designated "Specification Required" has that range re- | "Specification Required" has that range redesignated as "First Come | |||
designated as "First Come First Served". | First Served". | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This is an Internet Standards Track document. | |||
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 | This document is a product of the Internet Engineering Task Force | |||
and may be updated, replaced, or obsoleted by other documents at any | (IETF). It represents the consensus of the IETF community. It has | |||
time. It is inappropriate to use Internet-Drafts as reference | received public review and has been approved for publication by the | |||
material or to cite them other than as "work in progress." | Internet Engineering Steering Group (IESG). Further information on | |||
Internet Standards is available in Section 2 of RFC 7841. | ||||
This Internet-Draft will expire on 25 March 2024. | Information about the current status of this document, any errata, | |||
and how to provide feedback on it may be obtained at | ||||
https://www.rfc-editor.org/info/rfc9515. | ||||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2023 IETF Trust and the persons identified as the | Copyright (c) 2023 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents | |||
license-info) in effect on the date of publication of this document. | (https://trustee.ietf.org/license-info) in effect on the date of | |||
Please review these documents carefully, as they describe your rights | publication of this document. Please review these documents | |||
and restrictions with respect to this document. Code Components | carefully, as they describe your rights and restrictions with respect | |||
extracted from this document must include Revised BSD License text as | to this document. Code Components extracted from this document must | |||
described in Section 4.e of the Trust Legal Provisions and are | include Revised BSD License text as described in Section 4.e of the | |||
provided without warranty as described in the Revised BSD License. | Trust Legal Provisions and are provided without warranty as described | |||
in the Revised BSD License. | ||||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction | |||
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 | 2. IANA Considerations | |||
3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 | 3. Security Considerations | |||
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 | 4. Normative References | |||
5. Normative References . . . . . . . . . . . . . . . . . . . . 3 | Acknowledgements | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 | Author's Address | |||
1. Introduction | 1. Introduction | |||
[RFC7854] creates a number of IANA registries that include a range of | [RFC7854] creates a number of IANA registries that include a range of | |||
32768-65530 designated "Specification Required". Each such registry | 32768-65530 designated "Specification Required". Each such registry | |||
also has a large range designated "Standards Action". Subsequent | also has a large range designated "Standards Action". Subsequent | |||
experience has shown two things. First, there is less difference | experience has shown two things. First, there is less difference | |||
between these two policies in practice than there is in theory | between these two policies in practice than there is in theory | |||
(consider that [RFC8126] explains that for Specification Required, | (consider that [RFC8126] explains that for Specification Required, | |||
"Publication of an RFC is an ideal means of achieving this | "Publication of an RFC is an ideal means of achieving this | |||
requirement"). Second, it's desirable to have a very low bar to | requirement"). Second, it's desirable to have a very low bar to | |||
registration, to avoid the risk of conflicts introduced by use of | registration, to avoid the risk of conflicts introduced by use of | |||
unregistered code points (so-called "code point squatting"). | unregistered code points (so-called "code point squatting"). | |||
Accordingly, this document revises the registration procedures, as | Accordingly, this document revises the registration procedures, as | |||
given in Section 2. | given in Section 2. | |||
2. IANA Considerations | 2. IANA Considerations | |||
IANA is requested to revise the following registries within the BMP | IANA has revised the following registries within the BMP group: | |||
group: | ||||
* BMP Statistics Types | * BMP Statistics Types | |||
* BMP Initiation Message TLVs | * BMP Initiation and Peer Up Information TLVs | |||
* BMP Termination Message TLVs | * BMP Termination Message TLVs | |||
* BMP Termination Message Reason Codes | * BMP Termination Message Reason Codes | |||
* BMP Route Mirroring TLVs | * BMP Route Mirroring TLVs | |||
* BMP Route Mirroring Information Codes | * BMP Route Mirroring Information Codes | |||
For each of these registries, the ranges 32768-65530 whose | For each of these registries, the ranges 32768-65530 whose | |||
registration procedures were "Specification Required" are revised to | registration procedures were "Specification Required" are revised to | |||
have the registration procedures "First Come First Served". | have the registration procedures "First Come First Served". | |||
3. Security Considerations | 3. Security Considerations | |||
This revision to registration procedures does not change the | This revision to registration procedures does not change the | |||
underlying security issues inherent in the existing [RFC7854]. | underlying security issues inherent in [RFC7854]. | |||
4. Acknowledgements | ||||
Thanks to Jeff Haas for review and encouragement, and to Tom Petch | ||||
for review. | ||||
5. Normative References | 4. Normative References | |||
[RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP | [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP | |||
Monitoring Protocol (BMP)", RFC 7854, | Monitoring Protocol (BMP)", RFC 7854, | |||
DOI 10.17487/RFC7854, June 2016, | DOI 10.17487/RFC7854, June 2016, | |||
<https://www.rfc-editor.org/info/rfc7854>. | <https://www.rfc-editor.org/info/rfc7854>. | |||
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | |||
Writing an IANA Considerations Section in RFCs", BCP 26, | Writing an IANA Considerations Section in RFCs", BCP 26, | |||
RFC 8126, DOI 10.17487/RFC8126, June 2017, | RFC 8126, DOI 10.17487/RFC8126, June 2017, | |||
<https://www.rfc-editor.org/info/rfc8126>. | <https://www.rfc-editor.org/info/rfc8126>. | |||
Acknowledgements | ||||
Thanks to Jeff Haas for review and encouragement, and to Tom Petch | ||||
for review. | ||||
Author's Address | Author's Address | |||
John Scudder | John Scudder | |||
Juniper Networks | Juniper Networks | |||
1194 N. Mathilda Ave | 1194 N. Mathilda Ave | |||
Sunnyvale, CA 94089 | Sunnyvale, CA 94089 | |||
United States of America | United States of America | |||
Email: jgs@juniper.net | Email: jgs@juniper.net | |||
End of changes. 14 change blocks. | ||||
47 lines changed or deleted | 42 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |