idnits 2.17.1 draft-pti-pen-registration-04.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 (March 27, 2019) is 1855 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: September 28, 2019 P. Hoffman 6 ICANN 7 March 27, 2019 9 Registration Procedures for Private Enterprise Numbers (PENs) 10 draft-pti-pen-registration-04 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 September 28, 2019. 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, that organization 91 can use the PEN by itself (possibly to represent the organization) or 92 as the root of other OIDs associated with the organization. For 93 example, if an organization is assigned the PEN 1.3.6.1.4.1.32473, it 94 might use 1.3.6.1.4.1.32473.7 to identify a protocol extension and 95 use 1.3.6.1.4.1.32473.12.3 to identify a set of algorithms that it 96 supports in a protocol. 98 Neither IANA nor the IETF can control how an organization uses its 99 PEN. 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 organization that is not the registered owner of a PEN 102 from 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 First Come First Served registries require the identification of a 123 "change controller," as described in [RFC8126]. In this registry, 124 the assignee is understood to be the change controller, unless the 125 requester specifies otherwise. The assignee may be an individual, an 126 organization, a project, or some other entity. In addition, 127 requesters must supply contact information that can be used to verify 128 an attempt to modify or delete the registration. 130 ASCII text representations are required, but requesters may provide 131 additional non-ASCII representations. 133 Parties may request more than one PEN, but in most cases it is more 134 appropriate to obtain a sub-assignment of the existing registration. 135 Sub-assignments are maintained by the assignee. They are not 136 recorded by IANA. 138 IANA may refuse to process abusive requests. 140 2.2. Modifying an Existing Record 142 Assignees can request the modification of any of the information 143 associated with a registered value, including the name of the 144 assignee. 146 Modification requests require authorization by the change controller. 147 Authorization will be validated either with information kept on file 148 with IANA or with other identifying documentation, if necessary. 150 2.3. Deleting a PEN Record 152 Although such requests are rare, an assignee can ask IANA to delete a 153 registration. Values associated with deleted registrations will not 154 become available for re-assignment until all other unassigned values 155 have been exhausted. 157 3. PEN Registry Specifics 159 The range for values after the PEN prefix is 0 to 2**32-1. The 160 values 0 and 4294967295 (2**32-1) are reserved. Note that while the 161 original PEN definition had no upper bound for the value after the 162 PEN prefix, there is now an upper bound due to some IETF protocols 163 limiting the size of that value. For example, DIAMETER [RFC3588] 164 limits the value to 2**32-1. 166 There is a PEN number, 32473, reserved for use as an example in 167 documentation. This reservation is described in [RFC5612]. 169 Values in the registry that have unclear ownership are marked 170 "Reserved". These values will not be reassigned to a new company or 171 individual without consulting the IESG. 173 The PEN registry has some missing assignments. These numbers will be 174 available for assignment, but will only be assigned with the 175 permission of the IESG. At the time of publication of this document, 176 the list of missing assignments is: 2187, 2188, 3513, 4164, 4565, 177 4600, 4913, 4999, 5099, 5144, 5201, 5683, 5777, 6260, 6619, 14827, 178 16739, 26975 and the range from 11670 to 11769. 180 4. IANA Considerations 182 This entire document consists of considerations for IANA and for its 183 customers who want to apply for, modify, or delete a PEN. 185 5. Security Considerations 187 Registering PENs does not introduce any significant security 188 considerations. 190 There is no cryptographic binding of a registrant in the PEN registry 191 and the PEN(s) assigned to them. Thus, the entries in the PEN 192 registry cannot be used to validate the ownership of a PEN in use. 193 For example, if the PEN 1.3.6.1.4.1.32473 is seen in a protocol as 194 indicating the owner of some data, there is no way to securely 195 correlate that use with the name and organization of the owner listed 196 in the PEN registry. 198 6. Acknowledgements 200 An earlier version of this document was authored by Pearl Liang and 201 Alexey Melnikov. Additional significant contributions have come from 202 Dan Romascanu, Bert Wijnen, David Conrad, and Benoit Claise. 204 7. Informative References 206 [ASN1] ITU-T, "ITU-T X.690: Information technology - ASN.1 207 encoding rules", 2016, . 210 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 211 "Remote Authentication Dial In User Service (RADIUS)", 212 RFC 2865, DOI 10.17487/RFC2865, June 2000, 213 . 215 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 216 Architecture for Describing Simple Network Management 217 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 218 DOI 10.17487/RFC3411, December 2002, 219 . 221 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 222 Arkko, "Diameter Base Protocol", RFC 3588, 223 DOI 10.17487/RFC3588, September 2003, 224 . 226 [RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", 227 RFC 5284, DOI 10.17487/RFC5284, August 2008, 228 . 230 [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, 231 DOI 10.17487/RFC5424, March 2009, 232 . 234 [RFC5612] Eronen, P. and D. Harrington, "Enterprise Number for 235 Documentation Use", RFC 5612, DOI 10.17487/RFC5612, August 236 2009, . 238 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 239 DOI 10.17487/RFC6350, August 2011, 240 . 242 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 243 Writing an IANA Considerations Section in RFCs", BCP 26, 244 RFC 8126, DOI 10.17487/RFC8126, June 2017, 245 . 247 Authors' Addresses 249 Michelle Cotton 250 PTI, an affiliate of ICANN 252 Email: michelle.cotton@iana.org 254 Amanda Baber 255 PTI, an affiliate of ICANN 257 Email: amanda.baber@iana.org 259 Paul Hoffman 260 ICANN 262 Email: paul.hoffman@icann.org