Diff: rfc9371xml2.original.xml

	rfc9371xml2.original.xml	rfc9371.xml

	<?xml version="1.0" encoding="US-ASCII"?>	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
	<!ENTITY RFC2865 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.2865.xml">
	<!ENTITY RFC3411 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.3411.xml">
	<!ENTITY RFC5284 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5284.xml">
	<!ENTITY RFC5424 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5424.xml">
	<!ENTITY RFC5612 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.5612.xml">
	<!ENTITY RFC6350 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.6350.xml">
	<!ENTITY RFC6733 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.6733.xml">
	<!ENTITY RFC8126 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
	.8126.xml">


		<!DOCTYPE rfc [
		<!ENTITY nbsp " ">
		<!ENTITY zwsp "">
		<!ENTITY nbhy "‑">
		<!ENTITY wj "⁠">
	]>	]>

	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<?rfc strict="yes" ?>
	<?rfc toc="yes"?>
	<?rfc tocdepth="4"?>
	<?rfc symrefs="yes"?>
	<?rfc sortrefs="yes" ?>
	<?rfc compact="yes" ?>
	<?rfc subcompact="no" ?>
	<rfc category="info" docName="draft-pti-pen-registration-10"
	ipr="trust200902">
	<front>
	<title abbrev="PEN registration">Registration Procedures for Private Enterprise
	Numbers (PENs)</title>

	<author initials="A." surname="Baber" fullname="Amanda Baber">
	<organization abbrev="IANA">Internet Assigned Numbers Authority</organization>
	<address>
	<postal>
	<street>PTI/ICANN</street>
	<street>12025 Waterfront Drive</street>
	<city>Los Angeles</city>
	<code>90094</code>
	<country>United States of America</country>
	</postal>
	<email>amanda.baber@iana.org</email>
	</address>
	</author>


	<author fullname="Paul Hoffman" initials="P" surname="Hoffman">	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="
	<organization>ICANN</organization>	info" consensus="true" docName="draft-pti-pen-registration-10" number="9371" ipr
	<address>	="trust200902" obsoletes="" updates="" xml:lang="en" tocInclude="true" tocDepth=
	<postal>	"4" symRefs="true" sortRefs="true" version="3">
	<street>12025 Waterfront Drive</street>
	<city>Los Angeles</city>
	<code>90094</code>
	<country>United States of America</country>
	</postal>
	<email>paul.hoffman@icann.org</email>
	</address>
	</author>


	<date />	<!-- xml2rfc v2v3 conversion 3.15.3 -->
		<front>


	<abstract>	<title abbrev="PEN Registration">Registration Procedures for Private Enterpr
		ise Numbers (PENs)</title>
		<seriesInfo name="RFC" value="9371"/>
		<author initials="A." surname="Baber" fullname="Amanda Baber">
		<organization abbrev="IANA">Internet Assigned Numbers Authority</organizat
		ion>
		<address>
		<postal>
		<extaddr>PTI/ICANN</extaddr>
		<street>12025 Waterfront Drive</street>
		<city>Los Angeles</city>
		<code>90094</code>
		<country>United States of America</country>
		</postal>
		<email>amanda.baber@iana.org</email>
		</address>
		</author>
		<author fullname="Paul Hoffman" initials="P" surname="Hoffman">
		<organization>ICANN</organization>
		<address>
		<postal>
		<street>12025 Waterfront Drive</street>
		<city>Los Angeles</city>
		<code>90094</code>
		<country>United States of America</country>
		</postal>
		<email>paul.hoffman@icann.org</email>
		</address>
		</author>
		<date year="2023" month="February" />


	<t>	<abstract>
		<t>
	This document describes how Private Enterprise Numbers (PENs) are registered by IANA. It	This document describes how Private Enterprise Numbers (PENs) are registered by IANA. It

	shows how to request a new PEN and how to request an update to a current PEN. It also gives	shows how to request a new PEN and how to modify a current PEN. It also gives
	a brief overview of PEN uses.	a brief overview of PEN uses.
	</t>	</t>

		</abstract>
	</abstract>	</front>
		<middle>
	</front>	<section numbered="true" toc="default">
		<name>Introduction</name>
	<middle>	<t>

	<section title="Introduction">

	<t>
	Private Enterprise Numbers (PENs) are identifiers that can be used anywhere that an ASN.1	Private Enterprise Numbers (PENs) are identifiers that can be used anywhere that an ASN.1

	object identifier (OID) <xref target="ASN1"/> can be used. Originally, PENs were developed	object identifier (OID) <xref target="ASN1" format="default"/> can be used. Orig inally, PENs were developed
	so that organizations that needed to identify themselves in Simple Network Manag ement	so that organizations that needed to identify themselves in Simple Network Manag ement

	Protocol (SNMP) <xref target="RFC3411"/> Management Information Base (MIB) confi gurations	Protocol (SNMP) <xref target="RFC3411" format="default"/> Management Information Base (MIB) configurations
	could do so easily. PENs are also useful in any application or configuration lan guage that	could do so easily. PENs are also useful in any application or configuration lan guage that
	needs OIDs to identify organizations.	needs OIDs to identify organizations.
	</t>	</t>

	<t>	<t>
	The IANA Functions Operator, referred to in this document as "IANA",	The IANA Functions Operator, referred to in this document as "IANA",
	manages and maintains the PEN registry in consultation with the IESG.	manages and maintains the PEN registry in consultation with the IESG.
	PENs are issued from an OID prefix that was assigned to IANA. That OID	PENs are issued from an OID prefix that was assigned to IANA. That OID
	prefix is 1.3.6.1.4.1. Using the (now archaic) notation of ownership names in th e OID	prefix is 1.3.6.1.4.1. Using the (now archaic) notation of ownership names in th e OID
	tree, that corresponds to:	tree, that corresponds to:
	</t>	</t>

		<artwork name="" type="" align="left" alt=""><![CDATA[
	<figure><artwork><![CDATA[
	1 3 6 1 4 1	1 3 6 1 4 1
	iso.org.dod.internet.private.enterprise	iso.org.dod.internet.private.enterprise

	]]></artwork></figure>	]]></artwork>
		<t>
	<t>
	A PEN is an OID that begins with the PEN prefix. Thus, the OID 1.3.6.1.4.1.32473 is a	A PEN is an OID that begins with the PEN prefix. Thus, the OID 1.3.6.1.4.1.32473 is a
	PEN.	PEN.
	</t>	</t>

		<section numbered="true" toc="default">
	<section title="Uses of PENs">	<name>Uses of PENs</name>
		<t>
	<t>
	Once a PEN has been assigned to an organization, individual, or other entity, th at assignee can use the	Once a PEN has been assigned to an organization, individual, or other entity, th at assignee can use the
	PEN by itself (possibly to represent the assignee) or as the root of other OIDs	PEN by itself (possibly to represent the assignee) or as the root of other OIDs
	associated with the assignee. For example, if an assignee is assigned the PEN	associated with the assignee. For example, if an assignee is assigned the PEN
	1.3.6.1.4.1.32473, it might use 1.3.6.1.4.1.32473.7 to identify a protocol exten sion	1.3.6.1.4.1.32473, it might use 1.3.6.1.4.1.32473.7 to identify a protocol exten sion
	and use 1.3.6.1.4.1.32473.12.3 to identify a set of algorithms that it supports in a	and use 1.3.6.1.4.1.32473.12.3 to identify a set of algorithms that it supports in a
	protocol.	protocol.
	</t>	</t>

		<t>
	<t>
	Neither IANA nor the IETF can control how an assignee uses	Neither IANA nor the IETF can control how an assignee uses
	its PEN. In fact, no one can exert such control: that is the meaning of "private "	its PEN. In fact, no one can exert such control: that is the meaning of "private "
	in "private enterprise number". Similarly, no one can prevent an assignee that	in "private enterprise number". Similarly, no one can prevent an assignee that
	is not the registered owner of a PEN from using that PEN, or any PEN, however th ey want.	is not the registered owner of a PEN from using that PEN, or any PEN, however th ey want.
	</t>	</t>

		<t>
	<t>
	A very common use of PENs is to give unique identifiers in IETF protocols. SNMP MIB	A very common use of PENs is to give unique identifiers in IETF protocols. SNMP MIB

	configuration files use PENs for identifying the origin of values. Some protocol s that use	configuration files use PENs for identifying the origin of values. Protocols tha t use
	PENs as identifiers of extension mechanisms include	PENs as identifiers of extension mechanisms include

	RADIUS <xref target="RFC2865"/>,	RADIUS <xref target="RFC2865" format="default"/>,
	Diameter <xref target="RFC6733"/>,	Diameter <xref target="RFC6733" format="default"/>,
	Syslog <xref target="RFC5424"/>,	Syslog <xref target="RFC5424" format="default"/>,
	RSVP <xref target="RFC5284"/>,	RSVP <xref target="RFC5284" format="default"/>,
	and vCard <xref target="RFC6350"/>.	and vCard <xref target="RFC6350" format="default"/>.
	</t>	</t>

		</section>
		</section>
		<section numbered="true" toc="default">
		<name>PEN Assignment</name>


	</section>	<t>
		PENs are assigned by IANA. The registry is located at
	</section>	<eref target="https://www.iana.org/assignments/enterprise-numbers" brackets="ang
		le"/>, and requests for new assignments
	<section title="PEN Assignment">

	<t>
	Private Enterprise Numbers (PENs) are assigned by IANA. The registry is located
	at
	https://www.iana.org/assignments/enterprise-numbers, and requests for new assign
	ments
	or the modification of existing assignments can also be submitted at that URL.	or the modification of existing assignments can also be submitted at that URL.
	</t>	</t>

		<t>
	<t>
	IANA maintains the PEN registry in accordance with the "First Come First	IANA maintains the PEN registry in accordance with the "First Come First

	Served" registration policy described in <xref target="RFC8126"/>. Values are	Served" registration policy described in <xref target="RFC8126" format="default" />. Values are
	assigned sequentially.	assigned sequentially.
	</t>	</t>

		<section numbered="true" toc="default">
	<section title="Requesting a PEN Assignment">	<name>Requesting a PEN Assignment</name>
		<t>
	<t>
	Requests for assignment must provide the name of the assignee, the name of a	Requests for assignment must provide the name of the assignee, the name of a
	public contact who can respond to questions about the assignment, and contact	public contact who can respond to questions about the assignment, and contact
	information that can be used to verify change requests. The contact's name and	information that can be used to verify change requests. The contact's name and
	email address will be included in the public registry.	email address will be included in the public registry.
	</t>	</t>

	<t>	<t>

	A proposed assignee may request multiple PENs, but obtaining one PEN and making	A prospective assignee may request multiple PENs, but obtaining one PEN and maki ng
	internal sub-assignments is typically more appropriate. (Sub-assignments	internal sub-assignments is typically more appropriate. (Sub-assignments
	should not be reported to IANA.)	should not be reported to IANA.)
	</t>	</t>

	<t>	<t>
	IANA may refuse to process abusive requests.	IANA may refuse to process abusive requests.
	</t>	</t>

		</section>
	</section>	<section numbered="true" toc="default">
		<name>Modifying an Existing Record</name>
	<section title="Modifying an Existing Record">	<t>

	<t>
	Any of the information associated	Any of the information associated
	with a registered value can be modified, including the name of the assignee.	with a registered value can be modified, including the name of the assignee.
	</t>	</t>

		<t>
	<t>
	Modification requests require authorization by a representative of the	Modification requests require authorization by a representative of the
	assignee. Authorization will be validated either with information kept on	assignee. Authorization will be validated either with information kept on
	file with IANA or with other identifying documentation, if necessary.	file with IANA or with other identifying documentation, if necessary.
	</t>	</t>

		</section>
	</section>	<section numbered="true" toc="default">
		<name>Deleting a PEN Record</name>
	<section title="Deleting a PEN Record">	<t>

	<t>
	Although such requests are rare, registrations can be deleted. When a	Although such requests are rare, registrations can be deleted. When a
	registration is deleted, all identifying information is removed from the	registration is deleted, all identifying information is removed from the
	registry, and the value is marked as "returned." Returned values will not be	registry, and the value is marked as "returned." Returned values will not be

	made available for re-assignment until all other unassigned values have been	made available for reassignment until all other unassigned values have been
	exhausted; as can be seen in <xref target="specifics"/>, the unassigned values	exhausted; as can be seen in <xref target="specifics" format="default"/>, the un
		assigned values
	are unlikely to ever run out.	are unlikely to ever run out.
	</t>	</t>

		</section>
	</section>	</section>
		<section anchor="specifics" numbered="true" toc="default">
	</section>	<name>PEN Registry Specifics</name>

	<section title="PEN Registry Specifics" anchor="specifics">

	<t>	<t>
	The range for values after the PEN prefix is 0 to 2**32-1. The values 0 and 4294 967295	The range for values after the PEN prefix is 0 to 2**32-1. The values 0 and 4294 967295
	(2**32-1) are reserved. Note that while the original PEN definition had no upper bound for	(2**32-1) are reserved. Note that while the original PEN definition had no upper bound for
	the value after the PEN prefix, there is now an upper bound due to some IETF	the value after the PEN prefix, there is now an upper bound due to some IETF

	protocols limiting the size of that value. For example, Diameter <xref target="R FC6733"/>	protocols limiting the size of that value. For example, Diameter <xref target="R FC6733" format="default"/>
	limits the value to 2**32-1.	limits the value to 2**32-1.
	</t>	</t>

		<t>
	<t>
	There is a PEN number, 32473, reserved for use as an example in documentation. T his	There is a PEN number, 32473, reserved for use as an example in documentation. T his

	reservation is described in <xref target="RFC5612"/>.	reservation is described in <xref target="RFC5612" format="default"/>.
	</t>	</t>

		<t>
	<t>
	Values in the registry that have unclear ownership are marked "Reserved". These values	Values in the registry that have unclear ownership are marked "Reserved". These values
	will not be reassigned to a new company or individual without consulting the IES G.	will not be reassigned to a new company or individual without consulting the IES G.
	</t>	</t>

		</section>
		<section anchor="IANA" numbered="true" toc="default">


	</section>	<name>IANA Considerations</name>
		<t>
	<section anchor="IANA" title="IANA Considerations">	Per this document, IANA has made the following changes to the PEN registry:

	<t>
	This document requires two changes to the PEN registry.
	</t>	</t>

		<ul spacing="normal">
	<t>	<li>Values 2187, 2188, 3513, 4164, 4565, 4600, 4913, 4999, 5099, 5144, 5201,
	Values 2187, 2188, 3513, 4164, 4565, 4600, 4913, 4999, 5099, 5144, 5201,	5683, 5777, 6260, 6619, 14827, 16739, 26975, and the range from 11670 to
	5683, 5777, 6260, 6619, 14827, 16739, 26975 and the range from 11670 to	11769, which had been missing from the registry, have been listed as
	11769, which had been missing from the registry, will be listed as	"Reserved." As described in <xref target="RFC8126" format="default"/>, reserved
	"Reserved." As described in <xref target="RFC8126"/>, reserved values can be	values can be
	released by the IESG.	released by the IESG.

	</t>	</li>
		<li>
	<t>	This document has been listed in the registry's "Reference" field.
	In addition, this document will be listed in the registry's "Reference" field.	</li>
	</t>	<li>
		"First Come First Served" has been listed as its registration procedure.
	</section>	</li>
		</ul>
	<section anchor="Security" title="Security Considerations">	</section>
		<section anchor="Security" numbered="true" toc="default">
	<t>	<name>Security Considerations</name>
		<t>
	Registering PENs does not introduce any significant security considerations.	Registering PENs does not introduce any significant security considerations.
	</t>	</t>

		<t>
	<t>
	There is no cryptographic binding of a registrant in the PEN registry and the PE N(s)	There is no cryptographic binding of a registrant in the PEN registry and the PE N(s)
	assigned to them. Thus, the entries in the PEN registry cannot be used to valida te the	assigned to them. Thus, the entries in the PEN registry cannot be used to valida te the
	ownership of a PEN in use. For example, if the PEN 1.3.6.1.4.1.32473 is seen in a protocol	ownership of a PEN in use. For example, if the PEN 1.3.6.1.4.1.32473 is seen in a protocol
	as indicating the owner of some data, there is no way to securely correlate that use with	as indicating the owner of some data, there is no way to securely correlate that use with
	the name and assignee of the owner listed in the PEN registry.	the name and assignee of the owner listed in the PEN registry.
	</t>	</t>

		</section>
		</middle>
		<back>
		<references>
		<name>References</name>
		<references>
		<name>Normative References</name>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
		126.xml"/>
		</references>
		<references>
		<name>Informative References</name>


	</section>	<reference anchor="ASN1" target="https://www.itu.int/rec/T-REC-X.690/en"
		>
	<section title="Acknowledgements">	<front>
		<title>Information technology - ASN.1 encoding rules: Specification
	<t>	of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished
	An earlier version of this document was authored by Pearl Liang and	Encoding Rules (DER)</title>
	Alexey Melnikov. Additional significant contributions have come from	<author>
	Dan Romascanu, Bert Wijnen, David Conrad, Michelle Cotton, and Benoit Claise.	<organization>ITU-T</organization>
		</author>
		<date month="February" year="2021"/>
		</front>
		<seriesInfo name='ITU-T Recommendation' value='X.690' />
		</reference>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
		865.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
		411.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
		733.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
		284.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
		424.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
		612.xml"/>
		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6
		350.xml"/>
		</references>
		</references>
		<section numbered="false" toc="default">
		<name>Acknowledgements</name>
		<t>
		An earlier draft version of this document was authored by <contact fullname="Pea
		rl Liang"/> and
		<contact fullname="Alexey Melnikov"/>. Additional significant contributions have
		come from
		<contact fullname="Dan Romascanu"/>, <contact fullname="Bert Wijnen"/>, <contact
		fullname="David Conrad"/>, <contact fullname="Michelle Cotton"/>, and <contact
		fullname="Benoit Claise"/>.
	</t>	</t>

		</section>
	</section>	</back>

	</middle>

	<back>

	<references title="Normative References">

	&RFC8126;

	</references>

	<references title="Informative References">

	<reference anchor="ASN1" target="https://www.itu.int/itu-t/recommendations/rec.a
	spx?rec=x.690">
	<front>
	<title>ITU-T X.690: Information technology - ASN.1 encoding rules</title>
	<author>
	<organization>ITU-T</organization>
	</author>
	<date year="2016"/>
	</front>
	</reference>

	&RFC2865;
	&RFC3411;
	&RFC6733;
	&RFC5284;
	&RFC5424;
	&RFC5612;
	&RFC6350;
	</references>

	</back>

	</rfc>	</rfc>

End of changes. 41 change blocks.
	210 lines changed or deleted	178 lines changed or added
This html diff was produced by rfcdiff 1.48.