idnits 2.17.1 draft-scudder-grow-bmp-registries-change-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 20, 2018) is 2037 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1997' is defined on line 120, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Scudder 3 Internet-Draft Juniper Networks 4 Updates: 7854 (if approved) September 20, 2018 5 Intended status: Standards Track 6 Expires: March 24, 2019 8 Revision to Registration Procedures for Multiple BMP Registries 9 draft-scudder-grow-bmp-registries-change-00.txt 11 Abstract 13 This document updates RFC 7854, BGP Monitoring Protocol (BMP) by 14 making a change to the registration procedures for several 15 registries. Specifically, any BMP registry with a range of 16 32768-65530 designated "Specification Required" has that range re- 17 designated as "First Come First Served". 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 24, 2019. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 57 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 59 5.2. Informative References . . . . . . . . . . . . . . . . . 3 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1. Introduction 64 [RFC7854] creates a number of IANA registries that include a range of 65 32768-65530 designated "Specification Required". Each such registry 66 also has a large range designated "Standards Action". Subsequent 67 experience has shown two things. First, there is less difference 68 between these two policies in practice than there is in theory 69 (consider that [RFC8126] explains that for Specification Required, 70 "Publication of an RFC is an ideal means of achieving this 71 requirement"). Second, it's desirable to have a very low bar to 72 registration, to avoid the risk of conflicts introduced by use of 73 unregistered code points (so-called "code point squatting"). 75 Accordingly, this document revises the registration procedures, as 76 given in Section 2. 78 2. IANA Considerations 80 IANA is requested to revise the following registries within the BMP 81 group: 83 o BMP Statistics Types 84 o BMP Initiation Message TLVs 85 o BMP Termination Message TLVs 86 o BMP Termination Message Reason Codes 87 o BMP Peer Down Reason Codes 88 o BMP Route Mirroring TLVs 89 o BMP Route Mirroring Information Codes 91 For each of these registries, the ranges 32768-65530 whose 92 registration procedures were "Specification Required" are revised to 93 have the registration procedures "First Come First Served". 95 3. Security Considerations 97 This revision to registration procedures does not change the 98 underlying security issues inherent in the existing [RFC7854]. 100 4. Acknowledgements 102 Thanks to Jeff Haas for review and encouragement. 104 5. References 106 5.1. Normative References 108 [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP 109 Monitoring Protocol (BMP)", RFC 7854, 110 DOI 10.17487/RFC7854, June 2016, 111 . 113 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 114 Writing an IANA Considerations Section in RFCs", BCP 26, 115 RFC 8126, DOI 10.17487/RFC8126, June 2017, 116 . 118 5.2. Informative References 120 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 121 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 122 . 124 Author's Address 126 John Scudder 127 Juniper Networks 128 1194 N. Mathilda Ave 129 Sunnyvale, CA 94089 130 USA 132 Email: jgs@juniper.net