idnits 2.17.1 draft-pti-pen-registration-05.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 26, 2019) is 1673 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Cotton 3 Internet-Draft A. Baber 4 Intended status: Informational PTI 5 Expires: March 29, 2020 P. Hoffman 6 ICANN 7 September 26, 2019 9 Registration Procedures for Private Enterprise Numbers (PENs) 10 draft-pti-pen-registration-05 12 Abstract 14 This document describes how Private Enterprise Numbers (PENs) are 15 registered by IANA. It shows how to request a new PEN and how to 16 request an update to a current PEN. It also gives a brief overview 17 of PEN uses. 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 29, 2020. 36 Copyright Notice 38 Copyright (c) 2019 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 1.1. Uses of PENs . . . . . . . . . . . . . . . . . . . . . . 2 55 2. PEN Assignment . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. Requesting a PEN Assignment . . . . . . . . . . . . . . . 3 57 2.2. Modifying an Existing Record . . . . . . . . . . . . . . 4 58 2.3. Deleting a PEN Record . . . . . . . . . . . . . . . . . . 4 59 3. PEN Registry Specifics . . . . . . . . . . . . . . . . . . . 4 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 62 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 63 7. Informative References . . . . . . . . . . . . . . . . . . . 5 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 Private Enterprise Numbers (PENs) are identifiers that can be used 69 anywhere that an ASN.1 object identifier (OID) [ASN1] can be used. 70 Originally, PENs were developed so that organizations that needed to 71 identify themselves in Simple Network Management Protocol (SNMP) 72 [RFC3411] Management Information Base (MIB) configurations could do 73 so easily. PENs are also useful in any application or configuration 74 language that needs OIDs to identify organizations. 76 The IANA Functions Operator, referred to in this document as "IANA", 77 manages and maintains the PEN registry in consultation with the IESG. 78 PENs are issued from an OID prefix that was assigned to IANA. That 79 OID prefix is 1.3.6.1.4.1. Using the (now archaic) notation of 80 ownership names in the OID tree, that corresponds to: 82 1 3 6 1 4 1 83 iso.org.dod.internet.private.enterprise 85 A PEN is an OID that begins with the PEN prefix. Thus, the OID 86 1.3.6.1.4.1.32473 is a PEN. 88 1.1. Uses of PENs 90 Once a PEN has been assigned to an organization, individual, or other 91 entity, that assignee can use the PEN by itself (possibly to 92 represent the assignee) or as the root of other OIDs associated with 93 the assignee. For example, if an assignee is assigned the PEN 94 1.3.6.1.4.1.32473, it might use 1.3.6.1.4.1.32473.7 to identify a 95 protocol extension and use 1.3.6.1.4.1.32473.12.3 to identify a set 96 of algorithms that it supports in a protocol. 98 Neither IANA nor the IETF can control how an assignee uses its PEN. 99 In fact, no one can exert such control: that is the meaning of 100 "private" in "private enterprise number". Similarly, no one can 101 prevent an assignee that is not the registered owner of a PEN from 102 using that PEN, or any PEN, however they want. 104 A very common use of PENs is to give unique identifiers in IETF 105 protocols. SNMP MIB configuration files use PENs for identifying the 106 origin of values. Some protocols that use PENs as identifiers of 107 extension mechanisms include RADIUS [RFC2865], DIAMETER [RFC3588], 108 Syslog [RFC5424], RSVP [RFC5284], and vCard [RFC6350]. 110 2. PEN Assignment 112 Private Enterprise Numbers (PENs) are assigned by IANA. Requests for 113 new assignments and for the modification of existing assignments can 114 be submitted through the IANA web site. 116 2.1. Requesting a PEN Assignment 118 IANA maintains the PEN registry in accordance with the "First Come 119 First Served" registration policy described in [RFC8126]. Values are 120 generally assigned sequentially. 122 The registry is a list of values and their assignees. The assignee 123 is also considered the registration's "change controller," as 124 described in [RFC8126]. The change controller is effectively the 125 "owner" of the registration and can verify or refuse attempts to 126 modify or delete it. Requests for PEN registration must include 127 contact information that can be used for verification. 129 ASCII text representations are required, but requesters may provide 130 additional non-ASCII representations. 132 Parties may request more than one PEN, but in most cases it is more 133 appropriate to obtain a sub-assignment of the existing registration. 134 Sub-assignments are maintained by the assignee. They are not 135 recorded by IANA. 137 IANA may refuse to process abusive requests. 139 2.2. Modifying an Existing Record 141 Any of the information associated with a registered value can be 142 modified, including the name of the assignee. 144 Modification requests require authorization by the assignee or change 145 controller. Authorization will be validated either with information 146 kept on file with IANA or with other identifying documentation, if 147 necessary. 149 2.3. Deleting a PEN Record 151 Although such requests are rare, an assignee can ask IANA to delete a 152 registration. Values associated with deleted registrations will not 153 become available for re-assignment until all other unassigned values 154 have been exhausted. 156 3. PEN Registry Specifics 158 The range for values after the PEN prefix is 0 to 2**32-1. The 159 values 0 and 4294967295 (2**32-1) are reserved. Note that while the 160 original PEN definition had no upper bound for the value after the 161 PEN prefix, there is now an upper bound due to some IETF protocols 162 limiting the size of that value. For example, DIAMETER [RFC3588] 163 limits the value to 2**32-1. 165 There is a PEN number, 32473, reserved for use as an example in 166 documentation. This reservation is described in [RFC5612]. 168 Values in the registry that have unclear ownership are marked 169 "Reserved". These values will not be reassigned to a new company or 170 individual without consulting the IESG. 172 4. IANA Considerations 174 This entire document consists of considerations for IANA and for its 175 customers who want to apply for, modify, or delete a PEN. 177 Values 2187, 2188, 3513, 4164, 4565,4600, 4913, 4999, 5099, 5144, 178 5201, 5683, 5777, 6260, 6619, 14827, 16739, 26975 and the range from 179 11670 to 11769, which had been missing from the registry, will be 180 listed as "Reserved." As described in [RFC8126], reserved values can 181 be released by the IESG. 183 5. Security Considerations 185 Registering PENs does not introduce any significant security 186 considerations. 188 There is no cryptographic binding of a registrant in the PEN registry 189 and the PEN(s) assigned to them. Thus, the entries in the PEN 190 registry cannot be used to validate the ownership of a PEN in use. 191 For example, if the PEN 1.3.6.1.4.1.32473 is seen in a protocol as 192 indicating the owner of some data, there is no way to securely 193 correlate that use with the name and assignee of the owner listed in 194 the PEN registry. 196 6. Acknowledgements 198 An earlier version of this document was authored by Pearl Liang and 199 Alexey Melnikov. Additional significant contributions have come from 200 Dan Romascanu, Bert Wijnen, David Conrad, and Benoit Claise. 202 7. Informative References 204 [ASN1] ITU-T, "ITU-T X.690: Information technology - ASN.1 205 encoding rules", 2016, . 208 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 209 "Remote Authentication Dial In User Service (RADIUS)", 210 RFC 2865, DOI 10.17487/RFC2865, June 2000, 211 . 213 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 214 Architecture for Describing Simple Network Management 215 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 216 DOI 10.17487/RFC3411, December 2002, 217 . 219 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 220 Arkko, "Diameter Base Protocol", RFC 3588, 221 DOI 10.17487/RFC3588, September 2003, 222 . 224 [RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", 225 RFC 5284, DOI 10.17487/RFC5284, August 2008, 226 . 228 [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, 229 DOI 10.17487/RFC5424, March 2009, 230 . 232 [RFC5612] Eronen, P. and D. Harrington, "Enterprise Number for 233 Documentation Use", RFC 5612, DOI 10.17487/RFC5612, August 234 2009, . 236 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 237 DOI 10.17487/RFC6350, August 2011, 238 . 240 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 241 Writing an IANA Considerations Section in RFCs", BCP 26, 242 RFC 8126, DOI 10.17487/RFC8126, June 2017, 243 . 245 Authors' Addresses 247 Michelle Cotton 248 Public Technical Identifiers, an affiliate of ICANN 250 Email: michelle.cotton@iana.org 252 Amanda Baber 253 Public Technical Identifiers, an affiliate of ICANN 255 Email: amanda.baber@iana.org 257 Paul Hoffman 258 ICANN 260 Email: paul.hoffman@icann.org