Diff: rfc9876.original.xml

	rfc9876.original.xml	rfc9876.xml

	<?xml version='1.0' encoding='utf-8'?>	<?xml version='1.0' encoding='UTF-8'?>

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

	<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
	<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.3.	-ietf-core-cf-reg-update-09" number="9876" category="std" consensus="true" submi
	8) -->	ssionType="IETF" updates="7252" obsoletes="" tocInclude="true" sortRefs="true" s
	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft	ymRefs="true" version="3" xml:lang="en">
	-ietf-core-cf-reg-update-09" category="std" consensus="true" submissionType="IET
	F" updates="7252" tocInclude="true" sortRefs="true" symRefs="true" version="3">
	<!-- xml2rfc v2v3 conversion 3.28.1 -->
	<front>	<front>

	<title abbrev="CoAP Content-Format Registrations Update">Update to the IANA	<title abbrev="CoAP Content-Format Registration Procedure Updates">Updates t
	CoAP Content-Formats Registration Procedures</title>	o the IANA Registration Procedures for Constrained Application Protocol (CoAP) C
	<seriesInfo name="Internet-Draft" value="draft-ietf-core-cf-reg-update-09"/>	ontent-Formats</title>
		<seriesInfo name="RFC" value="9876"/>
	<author fullname="Thomas Fossati">	<author fullname="Thomas Fossati">
	<organization>Linaro</organization>	<organization>Linaro</organization>
	<address>	<address>
	<email>thomas.fossati@linaro.org</email>	<email>thomas.fossati@linaro.org</email>
	</address>	</address>
	</author>	</author>
	<author fullname="Esko Dijk">	<author fullname="Esko Dijk">
	<organization>IoTconsultancy.nl</organization>	<organization>IoTconsultancy.nl</organization>
	<address>	<address>
	<email>esko.dijk@iotconsultancy.nl</email>	<email>esko.dijk@iotconsultancy.nl</email>
	</address>	</address>
	</author>	</author>

	<date year="2025" month="May" day="10"/>	<date year="2025" month="September"/>
	<area>Web and Internet Transport</area>	<area>WIT</area>
	<workgroup>Constrained RESTful Environments</workgroup>	<workgroup>core</workgroup>
	<keyword>IANA</keyword>	<keyword>IANA</keyword>
	<keyword>registration</keyword>	<keyword>registration</keyword>
	<keyword>update</keyword>	<keyword>update</keyword>
	<keyword>CoAP</keyword>	<keyword>CoAP</keyword>
	<keyword>Content-Format</keyword>	<keyword>Content-Format</keyword>
	<abstract>	<abstract>

	<?line 56?>	<t>This document updates RFC 7252 by modifying the registration procedures for t
		he "CoAP Content-Formats" IANA registry, within the "Constrained RESTful Environ
	<t>This document updates RFC7252 regarding the registration procedures for the "	ments (CoRE) Parameters" registry group.
	CoAP Content-Formats" IANA registry, within the "Constrained RESTful Environment
	s (CoRE) Parameters" registry group.
	This document also introduces a new column, "Media Type", to the registry.	This document also introduces a new column, "Media Type", to the registry.
	Furthermore, this document reserves Content-Format identifiers 64998 and 64999 f or use in documentation.</t>	Furthermore, this document reserves Content-Format identifiers 64998 and 64999 f or use in documentation.</t>
	</abstract>	</abstract>

	<note removeInRFC="true">
	<name>About This Document</name>
	<t>
	The latest revision of this draft can be found at <eref target="https://
	core-wg.github.io/cf-reg-update/draft-ietf-core-cf-reg-update.html"/>.
	Status information for this document may be found at <eref target="https
	://datatracker.ietf.org/doc/draft-ietf-core-cf-reg-update/"/>.
	</t>
	<t>
	Discussion of this document takes place on the
	Constrained RESTful Environments Working Group mailing list (<eref targe
	t="mailto:core@ietf.org"/>),
	which is archived at <eref target="https://mailarchive.ietf.org/arch/bro
	wse/core/"/>.
	Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/core/"/
	>.
	</t>
	<t>Source for this draft and an issue tracker can be found at
	<eref target="https://github.com/core-wg/cf-reg-update"/>.</t>
	</note>
	</front>	</front>
	<middle>	<middle>

	<?line 62?>	<section anchor="introduction">

	<section anchor="introduction">
	<name>Introduction</name>	<name>Introduction</name>

	<t><xref section="12.3" sectionFormat="of" target="RFC7252"/> describes th	<t><xref section="12.3" sectionFormat="of" target="RFC7252"/> describes th
	e registration procedures for the "CoAP Content-Formats" IANA registry within th	e registration procedures for the "CoAP Content-Formats" IANA registry within th
	e "Constrained RESTful Environments (CoRE) Parameters" registry group <xref targ	e "Constrained RESTful Environments (CoRE) Parameters" registry group <xref targ
	et="IANA.core-parameters"/>.	et="IANA.core-params"/>.
	(Note that the columns of this registry have been revised according to <xref tar	(Note that the columns of this registry have been revised according to <xref tar
	get="Err4954"/>.)	get="Err4954"/>.) In particular, it defines the rules for obtaining Constrained
	In particular, it defines the rules for obtaining CoAP Content-Format identifier	Application Protocol (CoAP) Content-Format identifiers from the "IETF Review wit
	s from the "IETF Review or IESG Approval" range of the registry (256-9999) as we	h Expert Review or IESG Approval with Expert Review" range of the registry (256-
	ll as from the First Come First Served (FCFS) range of the registry (10000-64999	9999) as well as from the "First Come First Served" (FCFS) range of the registry
	).	(10000-64999).
	For the FCFS range, these rules do not involve the Designated Expert (DE) and ar	For the FCFS range, these rules do not involve the designated expert and are man
	e managed solely by IANA personnel to finalize the registration.</t>	aged solely by IANA personnel to finalize the registration.</t>
	<t>Unfortunately, the rules do not explicitly require checking that the co mbination of Content-Type (i.e., Media Type with optional parameters) and Conten t Coding associated with the requested CoAP Content-Format is semantically valid .	<t>Unfortunately, the rules do not explicitly require checking that the co mbination of Content-Type (i.e., Media Type with optional parameters) and Conten t Coding associated with the requested CoAP Content-Format is semantically valid .
	This task is generally non-trivial, requires knowledge from multiple documents a nd technologies, and should not be solely demanded from the registrar.	This task is generally non-trivial, requires knowledge from multiple documents a nd technologies, and should not be solely demanded from the registrar.

	This lack of guidance may engender confusion in both the registering party and t he registrar, and has already led to erroneous registrations.</t>	This lack of guidance may engender confusion in both the registering party and t he registrar, and it has already led to erroneous registrations.</t>
	<t>This document updates <xref target="RFC7252"/> by modifying the registr ation procedures for the "CoAP Content-Formats" registry to mitigate the risk of unintentional or malicious errors.	<t>This document updates <xref target="RFC7252"/> by modifying the registr ation procedures for the "CoAP Content-Formats" registry to mitigate the risk of unintentional or malicious errors.
	These updates amend the different ranges of the registry, introduce a review pro cedure to be performed for most ranges of the registry, and allow the registrati on of temporary Content-Format identifiers.	These updates amend the different ranges of the registry, introduce a review pro cedure to be performed for most ranges of the registry, and allow the registrati on of temporary Content-Format identifiers.
	This document also introduces a new column, "Media Type", to the registry.	This document also introduces a new column, "Media Type", to the registry.
	Furthermore, this document reserves Content-Format identifiers 64998 and 64999 f or use in documentation.</t>	Furthermore, this document reserves Content-Format identifiers 64998 and 64999 f or use in documentation.</t>
	</section>	</section>
	<section anchor="conventions-and-definitions">	<section anchor="conventions-and-definitions">
	<name>Conventions and Definitions</name>	<name>Conventions and Definitions</name>

	<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14	<t>
	>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL	The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
	NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECO	"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
	MMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",	",
	"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be i	"<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
	nterpreted as	"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
	described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and	"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
	only when, they	be
	appear in all capitals, as shown here.</t>	interpreted as described in BCP 14 <xref target="RFC2119"/> <xref
	<?line -18?>	target="RFC8174"/> when, and only when, they appear in all capitals, as
		shown here.
		</t>

	<t>This document uses the terms "Media Type", "Content Coding", "Content-Type", and "Content Format" as defined in <xref section="2" sectionFormat="of" target=" RFC9193"/>.	<t>This document uses the terms "Media Type", "Content Coding", "Content-Type", and "Content Format" as defined in <xref section="2" sectionFormat="of" target=" RFC9193"/>.
	In this document, those terms are fully capitalized.</t>	In this document, those terms are fully capitalized.</t>
	</section>	</section>
	<section anchor="security-considerations">	<section anchor="security-considerations">

	<name>Security Considerations</name>	<name>Security Considerations</name>
	<t>This document hardens the registration procedures of CoAP Content-Forma	<t>This document updates the registration procedures of CoAP Content-Forma
	ts in ways that reduce the chances of malicious manipulation of the associated r	ts to reduce the chances of malicious manipulation of the associated registry.</
	egistry.</t>	t>
	<t>Other than that, it does not change the Security Considerations of <xre	<t>Otherwise, it does not change the Security Considerations of <xref targ
	f target="RFC7252"/>.</t>	et="RFC7252"/>.</t>
	</section>	</section>
	<section anchor="iana-considerations">	<section anchor="iana-considerations">
	<name>IANA Considerations</name>	<name>IANA Considerations</name>

	<t>This document updates the IANA procedures defined in <xref target="RFC7	<t>This document updates the IANA procedures defined in <xref target="RFC7252"/>
	252"/> for registering CoAP Content-Formats as described in <xref target="iana"/	for registering CoAP Content-Formats as described in <xref target="iana"/>. It
	>.	also adds a new note concerning temporary registrations (<xref target="new-note-
	It also removes a note that was added to the registry as a temporary patch (<xre	add"/>) and reserves Content-Format IDs 64998 and 64999 for documentation (<xref
	f target="temp-note-removal"/>), adds a new note concerning temporary registrati	target="reserve-64999"/>).</t>
	ons (<xref target="new-note-add"/>) and reserves Content-Format IDs 64998 and 64
	999 for documentation (<xref target="reserve-64999"/>).</t>
	<section anchor="iana">	<section anchor="iana">
	<name>CoAP Content-Formats Registry</name>	<name>CoAP Content-Formats Registry</name>
	<t>This section and its subsections replace <xref section="12.3" section Format="of" target="RFC7252"/>.</t>	<t>This section and its subsections replace <xref section="12.3" section Format="of" target="RFC7252"/>.</t>

	<t><cref anchor="replace-self">RFC Editor: in this section, please repla ce RFCthis with the RFC number assigned to this document and remove this note.</ cref></t>
	<t>Internet Media Types are identified by a string, such as "application /xml" <xref target="RFC2046"/>.	<t>Internet Media Types are identified by a string, such as "application /xml" <xref target="RFC2046"/>.
	In order to minimize the overhead of using Media Types to indicate the format of payloads, <xref target="RFC7252"/> has defined a registry for a subset of Inter net Media Types to be used in CoAP and assigned each, in combination with a Cont ent Coding, a numeric identifier.	In order to minimize the overhead of using Media Types to indicate the format of payloads, <xref target="RFC7252"/> has defined a registry for a subset of Inter net Media Types to be used in CoAP and assigned each, in combination with a Cont ent Coding, a numeric identifier.

	The name of the registry is "CoAP Content-Formats", within the "CoRE Parameters"	The name of the registry is "CoAP Content-Formats", within the "Constrained REST
	registry group.</t>	ful Environments (CoRE) Parameters" registry group.</t>
	<t>Each entry in the registry must include the Media Type registered wit
	h IANA, the numeric identifier in the range 0-65535 to be used for that Media Ty	<t>Each entry in the registry must include the Content Type, the Content Coding
	pe in CoAP, the Content Coding associated with this identifier, and a reference	(if any), the Media Type registered with IANA, the numeric identifier in the ran
	to a document describing what a payload with that Media Type means semantically.	ge 0-65535 to be used for that Media Type in CoAP, and a reference to a document
	</t>	describing what a payload with that Media Type means semantically.</t>
	<t>CoAP does not include a separate way to convey Content Coding informa	<t>CoAP does not include a separate way to convey Content Coding informa
	tion with a request or response, and for that reason the Content Coding is also	tion with a request or response; for that reason, the Content Coding (if any) is
	specified for each identifier (if any).	also specified for each identifier.
	If multiple Content Codings will be used with a Media Type, then a separate Con tent-Format identifier for each is to be registered.	If multiple Content Codings will be used with a Media Type, then a separate Con tent-Format identifier for each is to be registered.
	Similarly, other parameters related to an Internet Media Type can be defined for a CoAP Content-Format entry.</t>	Similarly, other parameters related to an Internet Media Type can be defined for a CoAP Content-Format entry.</t>

	<t>The registration procedures for CoAP Content-Formats are described in <xref target="tbl-new-cf-proc"/>.</t>	<t>The registration procedures for CoAP Content-Formats are described in <xref t arget="tbl-new-cf-proc"/>.</t>
	<table anchor="tbl-new-cf-proc">	<table anchor="tbl-new-cf-proc">

	<name>CoAP Content-Formats: Registration Procedures</name>	<name>Registration Procedures for CoAP Content-Formats</name>
	<thead>	<thead>
	<tr>	<tr>
	<th align="left">Range</th>	<th align="left">Range</th>
	<th align="left">Registration Procedures</th>	<th align="left">Registration Procedures</th>

	<th align="left">Notes</th>	<th align="left">Note</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>
	<td align="left">0-255</td>	<td align="left">0-255</td>
	<td align="left">Expert Review</td>	<td align="left">Expert Review</td>

	<td align="left">Review procedure described in RFCthis, <xref targ et="checks"/>.</td>	<td align="left">Review procedure described in RFC 9876, <xre f target="checks"/>.</td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">256-9999</td>	<td align="left">256-9999</td>
	<td align="left">IETF Review with Expert Review or IESG Approval w ith Expert Review</td>	<td align="left">IETF Review with Expert Review or IESG Approval w ith Expert Review</td>

	<td align="left">Review procedure described in RFCthis, <xref targ et="checks"/></td>	<td align="left">Review procedure described in RFC 9876, <xre f target="checks"/></td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">10000-19999</td>	<td align="left">10000-19999</td>
	<td align="left">Expert Review</td>	<td align="left">Expert Review</td>

	<td align="left">Review procedure described in RFCthis, <xref targ et="checks"/>.</td>	<td align="left">Review procedure described in RFC 9876, <xre f target="checks"/>.</td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">20000-32999</td>	<td align="left">20000-32999</td>

	<td align="left">First Come First Served (FCFS)</td>	<td align="left">First Come First Served</td>
	<td align="left">FCFS is allowed if the registration: <br/> * has	<td align="left"><t>FCFS is allowed if
	no parameters, and <br/> * has an empty Content Coding, and <br/> * the Media Ty	the registration has no parameters,
	pe is not yet used in this registry, and <br/> * the Media Type is registered (o	the registration has an empty Content Coding,
	r approved for registration) in the "Media Types" registry <xref target="IANA.me	the Media Type is not yet used in this registry, and
	dia-types"/>.</td>	the Media Type is registered (or approved for registration) in th
		e "Media Types" registry <xref target="IANA.media-types"/>.</t>
		</td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">33000-64997</td>	<td align="left">33000-64997</td>
	<td align="left">Expert Review</td>	<td align="left">Expert Review</td>

	<td align="left">Review procedure described in RFCthis, <xref targ et="checks"/>.</td>	<td align="left">Review procedure described in RFC 9876, <xre f target="checks"/>.</td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">64998-64999</td>	<td align="left">64998-64999</td>

	<td align="left">-</td>
	<td align="left">Reserved for Documentation</td>	<td align="left">Reserved for Documentation</td>

		<td align="left"></td>
	</tr>	</tr>
	<tr>	<tr>
	<td align="left">65000-65535</td>	<td align="left">65000-65535</td>
	<td align="left">Experimental Use</td>	<td align="left">Experimental Use</td>
	<td align="left">No operational use</td>	<td align="left">No operational use</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>

	<t>Because the namespace of single-byte identifiers is so small, the IAN A policy for additions in the range 0-255 inclusive to the registry is "Expert R eview" as described in <xref section="4.5" sectionFormat="of" target="BCP26"/>.	<t>Because the namespace of single-byte identifiers is so small, the IAN A policy for additions in the range 0-255 inclusive to the registry is "Expert R eview" as described in Section <xref section="4.5" sectionFormat="bare" target=" RFC8126"/> of <xref target="BCP26">RFC 8126</xref>.
	For the handling of temporary allocations within the 0-255 range, see also <xref target="expert-review-7120-exemptions"/>.</t>	For the handling of temporary allocations within the 0-255 range, see also <xref target="expert-review-7120-exemptions"/>.</t>

	<t>The 256-9999 range has registration procedures requiring "IETF Review with Expert Review" or "IESG Approval with Expert Review." In particular:</t>	<t>The 256-9999 range has registration procedures requiring "IETF Review with Expert Review" or "IESG Approval with Expert Review". In particular:</t>
	<ul spacing="normal">	<ul spacing="normal">
	<li>	<li>

	<t>All assignments according to "IETF Review with Expert Review" are made on an "IETF Review" basis per <xref section="4.8" sectionFormat="of" targe t="BCP26"/> with "Expert Review" additionally required per <xref section="4.5" s ectionFormat="of" target="BCP26"/>. </t>	<t>All assignments according to "IETF Review with Expert Review" are made on an "IETF Review" basis per Section <xref section="4.8" sectionFormat="b are" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref> with "Expert Rev iew" additionally required per Section <xref section="4.5" sectionFormat="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref>. </t>
	<t>	<t>

	The procedure for early IANA allocation of "standards track code points" defined in <xref target="RFC7120"/> also applies. When such a procedure is used, IANA w ill ask the Designated Expert(s) to approve the early allocation before registra tion. In addition, working group chairs are encouraged to consult the Expert(s) early during the process outlined in <xref section="3.1" sectionFormat="of" targ et="RFC7120"/>.</t>	The procedure for early IANA allocation of Standards Track code points defined i n <xref target="RFC7120"/> also applies. When such a procedure is used, IANA wil l ask the designated expert(s) to approve the early allocation before registrati on. In addition, working group chairs are encouraged to consult the expert(s) ea rly during the process outlined in <xref section="3.1" sectionFormat="of" target ="RFC7120"/>.</t>
	</li>	</li>
	<li>	<li>

	<t>All assignments according to "IESG Approval with Expert Review" a re made on an "IESG Approval" basis per <xref section="4.10" sectionFormat="of" target="BCP26"/> with "Expert Review" additionally required per <xref section="4 .5" sectionFormat="of" target="BCP26"/>.</t>	<t>All assignments according to "IESG Approval with Expert Review" a re made on an "IESG Approval" basis per Section <xref section="4.10" sectionForm at="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref> with "Exper t Review" additionally required per Section <xref section="4.5" sectionFormat="b are" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref>.</t>
	</li>	</li>
	</ul>	</ul>
	<t>The registration policy for the 10000-19999 and 33000-64997 ranges is "Expert Review", following the procedure described in <xref target="checks"/>.< /t>	<t>The registration policy for the 10000-19999 and 33000-64997 ranges is "Expert Review", following the procedure described in <xref target="checks"/>.< /t>
	<t>The registration policy for the 20000-32999 range is FCFS.	<t>The registration policy for the 20000-32999 range is FCFS.
	A registration request for this range must consist solely of a registered Media Type name in the "Content Type" field, without any parameter names or "Content C oding", and the Media Type must not have been used in this registry yet.	A registration request for this range must consist solely of a registered Media Type name in the "Content Type" field, without any parameter names or "Content C oding", and the Media Type must not have been used in this registry yet.

	If the criteria do not apply, a registration for a different range (which requir es Expert Review) can be requested.</t>	If the criteria do not apply, a registration for a different range (which requir es "Expert Review") can be requested.</t>
	<t>The identifiers between 65000 and 65535 inclusive are reserved for ex periments.	<t>The identifiers between 65000 and 65535 inclusive are reserved for ex periments.
	They are not meant for vendor-specific use of any kind and <bcp14>MUST NOT</bcp1 4> be used in operational deployments.</t>	They are not meant for vendor-specific use of any kind and <bcp14>MUST NOT</bcp1 4> be used in operational deployments.</t>

	<t>In machine-to-machine applications, it is not expected that generic I nternet Media Types such as text/plain, application/xml or application/octet-str eam are useful for real applications in the long term.	<t>In machine-to-machine (M2M) applications, it is not expected that gen eric Internet Media Types such as text/plain, application/xml, or application/oc tet-stream are useful for real applications in the long term.
	It is recommended that M2M applications making use of CoAP request new Internet Media Types from IANA indicating semantic information about how to create or par se a payload.	It is recommended that M2M applications making use of CoAP request new Internet Media Types from IANA indicating semantic information about how to create or par se a payload.
	For example, a Smart Energy application payload carried as Concise Binary Object Representation (CBOR) might request a more specific type like application/se+cb or.</t>	For example, a Smart Energy application payload carried as Concise Binary Object Representation (CBOR) might request a more specific type like application/se+cb or.</t>
	<section anchor="temporary-content-format-registrations">	<section anchor="temporary-content-format-registrations">
	<name>Temporary Content-Format Registrations</name>	<name>Temporary Content-Format Registrations</name>

	<t>This section clarifies that the "CoAP Content-Formats" registry all	<t>This section clarifies that the "CoAP Content-Formats" registry all
	ows temporary registrations within the 0-64998 range.</t>	ows temporary registrations within the 0-64997 range.</t>
	<t>A temporary registration may be created for example by an IANA earl	<t>A temporary registration may be created, for example, by an IANA ea
	y allocation action <xref target="RFC7120"/>.	rly allocation action <xref target="RFC7120"/>.
	If the referenced Media Type is provisional (that is, included in the IANA "Prov	If the referenced Media Type is provisional (that is, included in the "Provision
	isional Standard Media Type" registry <xref target="IANA.provisional-standard-me	al Standard Media Type Registry" <xref target="IANA.prov-media-types"/>), then a
	dia-types"/>) then a created registration is always temporary.</t>	created registration is always temporary.</t>
	<t>A temporary registration is marked as such by IANA in the correspon ding registry entry.	<t>A temporary registration is marked as such by IANA in the correspon ding registry entry.

	Once the required registration procedure (defined in <xref target="tbl-new-cf-pr	Once the required registration procedure (defined in <xref target="tbl-new-cf-pr
	oc"/>) for the temporary ID has successfully completed, and the referenced Media	oc"/>) for the temporary ID has successfully completed, and the referenced Media
	Type is included in the IANA Media Types registry <xref target="IANA.media-type	Type is included in the "Media Types" registry <xref target="IANA.media-types"/
	s"/>, IANA must remove any indication about the temporary nature of the registra	>, IANA must remove any indication about the temporary nature of the registratio
	tion so that the entry becomes permanent.</t>	n so that the entry becomes permanent.</t>
	<t>If a temporary registration does not successfully complete the regi	<t>If a temporary registration does not successfully complete the registration p
	stration procedure, IANA must remove the entry and set the Content-Format ID val	rocedure, IANA must remove the entry and set the Content-Format ID value back to
	ue back to "Unassigned".	"Unassigned". This may happen, for example, when an Internet-Draft requesting a
	This may happen for example when an Internet-Draft requesting a Content-Format I	Content-Format ID is abandoned.
	D is abandoned.
	If a temporary registration (in any range) refers to a provisional Media Type th at is abandoned, IANA must remove the entry and set the Content-Format ID value back to "Unassigned".</t>	If a temporary registration (in any range) refers to a provisional Media Type th at is abandoned, IANA must remove the entry and set the Content-Format ID value back to "Unassigned".</t>

	<t>Note that in the 10000-64998 range the abandonment of a document re questing a Content-Format ID does not cause an entry to be removed.	<t>Note that in the 10000-64997 range, the abandonment of a document r equesting a Content-Format ID does not cause an entry to be removed.
	That is because the required registration procedure for this range does not requ ire completion of any standards process, nor does it require a registering docum ent.</t>	That is because the required registration procedure for this range does not requ ire completion of any standards process, nor does it require a registering docum ent.</t>
	<t anchor="expert-review-7120-exemptions">Temporary registrations with in the 0-255 range are exempt from the formal renewal process outlined in <xref target="RFC7120"/>.	<t anchor="expert-review-7120-exemptions">Temporary registrations with in the 0-255 range are exempt from the formal renewal process outlined in <xref target="RFC7120"/>.
	Specifically, IANA will not monitor the removal of registrations in this range.	Specifically, IANA will not monitor the removal of registrations in this range.

	Instead, the Designated Experts direct IANA to carry out this task.</t>	Instead, the designated experts direct IANA to carry out this task.</t>
	</section>	</section>
	<section anchor="adding-the-media-type-column-to-the-registry">	<section anchor="adding-the-media-type-column-to-the-registry">

	<name>Adding the Media Type Column to the Registry</name>	<name>Addition of the Media Type Column to the Registry</name>
	<t>To assist users of the "CoAP Content-Formats" registry in finding d	<t>To assist users of the "CoAP Content-Formats" registry in finding d
	etailed information about the Media Type associated with each CoAP Content-Forma	etailed information about the Media Type associated with each CoAP Content-Forma
	t, and to ensure that a Media Type exists before a new entry can be registered,	t, and to ensure that a Media Type exists before a new entry can be registered,
	IANA is requested to add a new column "Media Type" to the registry.	IANA has added the new column "Media Type" to the registry.
	This new column is placed directly to the right of the existing "Content Type" c	This new column is placed to the right of the existing "Content Type" column.</t
	olumn.</t>	>
	<t>The "Media Type" field for each entry lists the (base) Media Type n ame and provides a hyperlink to registration information for that Media Type as recorded by IANA.	<t>The "Media Type" field for each entry lists the (base) Media Type n ame and provides a hyperlink to registration information for that Media Type as recorded by IANA.

	If the Media Type is provisional, the hyperlink points to the IANA "Provisional	If the Media Type is provisional, the hyperlink points to the "Provisional Stand
	Standard Media Type" registry <xref target="IANA.provisional-standard-media-type	ard Media Type Registry" <xref target="IANA.prov-media-types"/>.
	s"/>.	If a provisional Media Type becomes a permanent Media Type, IANA must u
	If a provisional Media Type becomes a permanent Media Type, IANA must update the	pdate the "Media Type" field in the associated registry entries to ensure the hy
	"Media Type" field in the associated registry entries to ensure the hyperlink d	perlink directs to the registration information for that Media Type.</t>
	irects to the registration information for that Media Type.</t>	<t>In a registration request, the requester does not need to fill out
	<t>Note that the registration request procedure remains unchanged. A r	the "Media Type" field separately, as the necessary information is already provi
	equester does not need to fill out the "Media Type" field separately, as the nec	ded in the "Content Type" field of the request.</t>
	essary information is already provided in the "Content Type" field of the reques
	t.</t>
	</section>	</section>
	<section anchor="checks">	<section anchor="checks">
	<name>Expert Review Procedure</name>	<name>Expert Review Procedure</name>

	<t>The Designated Expert (DE) is instructed to perform the Expert Revi ew, as described by the following checklist:</t>	<t>The designated expert is instructed to perform the "Expert Review", as described by the following checklist:</t>
	<ol spacing="normal" type="1"><li>	<ol spacing="normal" type="1"><li>

	<t>The combination of Content-Type and Content Coding for which th e registration is requested must not be already present in the "CoAP Content-For mats" registry;</t>	<t>The combination of Content-Type and Content Coding for which th e registration is requested must not be already present in the "CoAP Content-For mats" registry.</t>
	</li>	</li>
	<li>	<li>

	<t>The Media Type associated with the requested Content-Format mus t either be registered in the "Media Types" registry <xref target="IANA.media-ty pes"/> or approved for registration. Alternatively, it may be listed in the "Pro visional Standard Media Type" registry <xref target="IANA.provisional-standard-m edia-types"/>. The use of provisional standard Media Types is only permitted for Content-Format identifiers within the ranges of 0-255 and 256-9999;</t>	<t>The Media Type associated with the requested Content-Format mus t be either registered in the "Media Types" registry <xref target="IANA.media-ty pes"/> or approved for registration. Alternatively, it may be listed in the "Pro visional Standard Media Type Registry" <xref target="IANA.prov-media-types"/>. T he use of provisional standard Media Types is only permitted for Content-Format identifiers within the ranges of 0-255 and 256-9999.</t>
	</li>	</li>
	<li>	<li>

	<t>The optional parameter names must have been defined in associat ion with the Media Type, and any parameter values associated with such parameter names must be as permitted;</t>	<t>The optional parameter names must have been defined in associat ion with the Media Type, and any parameter values associated with such parameter names must be as permitted.</t>
	</li>	</li>
	<li>	<li>

	<t>The Content Type must be in the preferred format defined in <xr ef target="preferred-format"/>;</t>	<t>The Content Type must be in the preferred format defined in <xr ef target="preferred-format"/>.</t>
	</li>	</li>
	<li>	<li>

	<t>If a Content Coding is specified, it must exist (or must have b een approved for registration) in the "HTTP Content Coding" registry of the "Hyp ertext Transfer Protocol (HTTP) Parameters" <xref target="IANA.http-parameters"/ >.</t>	<t>If a Content Coding is specified, it must exist (or must have b een approved for registration) in the "HTTP Content Coding Registry" within the "Hypertext Transfer Protocol (HTTP) Parameters" registry group <xref target="IAN A.http-params"/>.</t>
	</li>	</li>
	</ol>	</ol>

	<t>For the 0-255 range, in addition to the checks described above, the	<t>For the 0-255 range, in addition to the checks described above, the
	DE is instructed to also evaluate the requested codepoint concerning the limite	designated expert is instructed to also evaluate the requested code point conce
	d availability of the 1-byte codepoint space.	rning the limited availability of the 1-byte code point space.
	For the ranges 256-9999, 10000-19999, and 33000-64997, a similar criterion may a	For the ranges 256-9999, 10000-19999, and 33000-64997, a similar criterion may a
	lso apply where combinations of Media Type parameters and Content Coding choices	lso apply where combinations of Media Type parameters and Content Coding choices
	consume considerable codepoint space.</t>	consume considerable code point space.</t>
	</section>	</section>
	<section anchor="preferred-format">	<section anchor="preferred-format">
	<name>Preferred Format for the Content Type Field</name>	<name>Preferred Format for the Content Type Field</name>

	<t>This section defines the preferred string format for including a re	<t>This section defines the preferred string format for including a re
	quested Content Type into the "CoAP Content-Formats" registry.	quested Content Type in the "CoAP Content-Formats" registry.
	During the review process, the Designated Expert(s) or IANA may rewrite a reques	During the review process, the designated expert(s) or IANA may rewrite a reques
	ted Content Type into this preferred string format before approval.</t>	ted Content Type into this preferred string format before approval.</t>
	<t>The preferred string format is as defined in <xref section="8.3.1" sectionFormat="of" target="RFC9110"/> and follows these rules:</t>	<t>The preferred string format is as defined in <xref section="8.3.1" sectionFormat="of" target="RFC9110"/> and follows these rules:</t>
	<ol spacing="normal" type="1"><li>	<ol spacing="normal" type="1"><li>
	<t>For any case-insensitive elements, lowercase characters are use d.</t>	<t>For any case-insensitive elements, lowercase characters are use d.</t>
	</li>	</li>
	<li>	<li>

	<t>Parameter values are only quoted if the value is such that it r equires use of <tt>quoted-string</tt> per <xref section="5.6.6" sectionFormat="o f" target="RFC9110"/>.	<t>Parameter values are only quoted if the value is such that it r equires use of a <tt>quoted-string</tt> per <xref section="5.6.6" sectionFormat= "of" target="RFC9110"/>.
	Otherwise, a parameter value is included unquoted.</t>	Otherwise, a parameter value is included unquoted.</t>
	</li>	</li>
	<li>	<li>

	<t>A single semicolon character without any adjacent whitespace ch
	aracters is used as the separator between Media Type and parameters.</t>	<t>A single semicolon character without any adjacent whitespace ch
		aracters is used as the separator between the Media Type and parameters.</t>
	</li>	</li>
	</ol>	</ol>
	</section>	</section>
	<section anchor="examples-for-invalid-registration-requests">	<section anchor="examples-for-invalid-registration-requests">

	<name>Examples for Invalid Registration Requests</name>	<name>Examples of Invalid Registration Requests</name>
	<t>This section provides examples of registration requests for the "Co	<t>This section provides examples of registration requests for the "Co
	AP Content-Formats" Registry that are invalid but would be approved under the pr	AP Content-Formats" registry that are invalid but would be approved under the pr
	ocedure defined in <xref section="12.3" sectionFormat="of" target="RFC7252"/>.	ocedure defined in <xref section="12.3" sectionFormat="of" target="RFC7252"/>.
	The checklist defined in <xref target="checks"/> should prevent any of these att empts from succeeding.	The checklist defined in <xref target="checks"/> should prevent any of these att empts from succeeding.

	These examples serve as a representative, but not exhaustive, sample to train th e DE's eye on invalid registration attempts.</t>	These examples serve as a representative, but not exhaustive, sample to train th e designated expert's eye on invalid registration attempts.</t>
	<t>All the example registration requests use two CoAP Content-Format i dentifiers: 64998 and 64999.</t>	<t>All the example registration requests use two CoAP Content-Format i dentifiers: 64998 and 64999.</t>

	<t>For each of the following example registration requests, one can cr
	eate a similar instance where the requested registration is for a CoAP Content-F	<!-- [rfced] Please confirm that "IETF Review or IESG Approval" is correct
	ormat identifier within the "IETF Review or IESG Approval" range.	here. Does this apply to all ranges that require "Expert Review"?
	Likewise, such registrations must not be allowed to succeed.</t>
		Original:
		For each of the following example registration requests, one can
		create a similar instance where the requested registration is for a
		CoAP Content-Format identifier within the "IETF Review or IESG
		Approval" range.

		Perhaps:
		For each of the following example registration requests, one can
		create a similar instance where the requested registration is for a
		CoAP Content-Format identifier within the ranges that require "Expert
		Review".

		[rfced]: AD approval needed for the removal of this text.
		-->

	<section anchor="ex-unknown-mt">	<section anchor="ex-unknown-mt">
	<name>The Media Type is Unknown</name>	<name>The Media Type is Unknown</name>
	<t>The registrant requests an FCFS Content-Format ID for an unknown Media Type:</t>	<t>The registrant requests an FCFS Content-Format ID for an unknown Media Type:</t>

	<table align="left">	<table>
	<name>Attempt at Registering Content-Format for an Unknown Media T ype</name>	<name>Attempt at Registering Content-Format for an Unknown Media T ype</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/unknown+cbor</td>	<td>application/unknown+cbor</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="the-media-type-parameter-is-unknown">	<section anchor="the-media-type-parameter-is-unknown">
	<name>The Media Type Parameter is Unknown</name>	<name>The Media Type Parameter is Unknown</name>
	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an unknown parameter:</t>	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an unknown parameter:</t>

	<table align="left">	<table>
	<name>Attempt at Registering Content-Format for Media Type with Un	<name>Attempt at Registering Content-Format for a Media Type with
	known Parameter</name>	an Unknown Parameter</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/cose;unknown-parameter=1</td>	<td>application/cose;unknown-parameter=1</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="the-media-type-parameter-value-is-invalid">	<section anchor="the-media-type-parameter-value-is-invalid">
	<name>The Media Type Parameter Value is Invalid</name>	<name>The Media Type Parameter Value is Invalid</name>
	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an invalid parameter value:</t>	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an invalid parameter value:</t>

	<table align="left">	<table>
	<name>Attempt at Registering Content-Format for Media Type with In	<name>Attempt at Registering Content-Format for a Media Type with
	valid Parameter Value</name>	an Invalid Parameter Value</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/cose;cose-type=invalid</td>	<td>application/cose;cose-type=invalid</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="the-content-coding-is-unknown">	<section anchor="the-content-coding-is-unknown">
	<name>The Content Coding is Unknown</name>	<name>The Content Coding is Unknown</name>
	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an unknown Content Coding:</t>	<t>The registrant requests an FCFS Content-Format ID for an existing Media Type with an unknown Content Coding:</t>

	<table align="left">	<table>
	<name>Attempt at Registering Content-Format with Unknown Content C oding</name>	<name>Attempt at Registering Content-Format with Unknown Content C oding</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/senml+cbor</td>	<td>application/senml+cbor</td>
	<td align="left">inflate</td>	<td>inflate</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="duplicate-entry-with-default-media-type-parameters">	<section anchor="duplicate-entry-with-default-media-type-parameters">
	<name>Duplicate Entry with Default Media Type Parameters</name>	<name>Duplicate Entry with Default Media Type Parameters</name>
	<t>The registrant requests an FCFS Content-Format ID for a Media Typ e that includes a parameter set to its default value, while	<t>The registrant requests an FCFS Content-Format ID for a Media Typ e that includes a parameter set to its default value, while
	a (hypothetical) Content-Format ID 64998 is already registered for this Media Ty pe without that parameter.	a (hypothetical) Content-Format ID 64998 is already registered for this Media Ty pe without that parameter.
	As a result, this could lead to the creation of two separate Content-Format IDs for the same "logical" entry.</t>	As a result, this could lead to the creation of two separate Content-Format IDs for the same "logical" entry.</t>

	<table align="left">	<table>
	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (1)</name>	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (1)</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/my</td>	<td>application/my</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64998</td>	<td>64998</td>
	</tr>	</tr>
	<tr>	<tr>

	<td align="left">application/my;parameter=default</td>	<td>application/my;parameter=default</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="duplicate-entry-with-default-content-coding">	<section anchor="duplicate-entry-with-default-content-coding">
	<name>Duplicate Entry with Default Content Coding</name>	<name>Duplicate Entry with Default Content Coding</name>
	<t>The registrant requests an FCFS Content-Format ID for the "identi ty" Content Coding, which is the default coding.	<t>The registrant requests an FCFS Content-Format ID for the "identi ty" Content Coding, which is the default coding.
	If accepted, this request would duplicate an entry with (hypothetical)	If accepted, this request would duplicate an entry with (hypothetical)
	Content-Format ID 64998 where the "Content Coding" field is left empty.</t>	Content-Format ID 64998 where the "Content Coding" field is left empty.</t>

	<table align="left">	<table>
	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (2)</name>	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (2)</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/my</td>	<td>application/my</td>
	<td align="left">-</td>	<td>-</td>
	<td align="left">64998</td>	<td>64998</td>
	</tr>	</tr>
	<tr>	<tr>

	<td align="left">application/my</td>	<td>application/my</td>
	<td align="left">identity</td>	<td>identity</td>
	<td align="left">64999</td>	<td>64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section anchor="duplicate-entry-with-equivalent-parameter">	<section anchor="duplicate-entry-with-equivalent-parameter">
	<name>Duplicate Entry with Equivalent Parameter</name>	<name>Duplicate Entry with Equivalent Parameter</name>
	<t>The registrant requests an FCFS Content-Format ID for a Media Typ e that includes a parameter.	<t>The registrant requests an FCFS Content-Format ID for a Media Typ e that includes a parameter.
	The value of this parameter appears distinct from that of a (hypothetical) previ ously registered Content-Format ID 64998 that also includes this parameter.	The value of this parameter appears distinct from that of a (hypothetical) previ ously registered Content-Format ID 64998 that also includes this parameter.
	However, the semantics of the parameter value are identical to the existing regi stration.</t>	However, the semantics of the parameter value are identical to the existing regi stration.</t>
	<t>In this example, the <tt>eat_profile</tt> parameter value (which can be any URI) is set as a Uniform Resource Name (URN) <xref target="RFC8141"/> .	<t>In this example, the <tt>eat_profile</tt> parameter value (which can be any URI) is set as a Uniform Resource Name (URN) <xref target="RFC8141"/> .

	Since for URNs, the Namespace Identifier (<tt>example</tt> in this example) is d	Since the Namespace Identifier (see <tt>example</tt> in this example) for URNs i
	efined as case insensitive, the two registrations are semantically identical.</t	s defined as case insensitive, the two registrations are semantically identical.
	>	</t>
	<table align="left">	<table>
	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (3)</name>	<name>Attempt at Registering an Equivalent Logical Entry with a Di fferent Content-Format ID (3)</name>
	<thead>	<thead>
	<tr>	<tr>

	<th align="left">Content Type</th>	<th>Content Type</th>
	<th align="left">Content Coding</th>	<th>Content Coding</th>
	<th align="left">ID</th>	<th>ID</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td align="left">application/eat+cwt;eat_profile="urn:example:	<td>application/eat+cwt;eat_profile="urn:example:1"</td>
	1"</td>	<td>-</td>
	<td align="left">-</td>	<td>64998</td>
	<td align="left">64998</td>
	</tr>	</tr>
	<tr>	<tr>

	<td align="left">application/eat+cwt;eat_profile="urn:EXAMPLE:	<td>application/eat+cwt;eat_profile="urn:EXAMPLE:1"</td>
	1"</td>	<td>-</td>
	<td align="left">-</td>	<td>64999</td>
	<td align="left">64999</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	</section>	</section>
	</section>	</section>

	<section anchor="temp-note-removal" removeInRFC="true">
	<name>Temporary Note Removal</name>
	<t>The following note has been added to the registry as a temporary fix:
	</t>
	<ul empty="true">
	<li>
	<t>"Note: The validity of the combination of Content Coding, Content
	Type and parameters is checked prior to assignment."</t>
	</li>
	</ul>
	<t>IANA is instructed to remove this note from the registry when this do
	cument is approved for publication.
	RFC-Editor: please remove this section once the note has been removed.</t>
	</section>
	<section anchor="new-note-add">	<section anchor="new-note-add">

	<name>New Note Addition</name>	<name>New Note and Reference Additions</name>
	<t><cref anchor="replace-self_1">RFC Editor: in this section, please rep	<t>IANA has added the following note to the registry:</t>
	lace RFCthis with the RFC number assigned to this document and remove this note.	<blockquote><t>Note: As per RFC 9876, temporary registrations within the
	</cref></t>	0-255 range are approved by designated experts.
	<t>IANA is instructed to add the following note to the registry:</t>	These registrations are not subject to the formal renewal process in <xre
	<ul empty="true">	f target="RFC7120"/>.</t></blockquote>
	<li>	<t>
	<t>"Note: As per RFCthis, temporary registrations within the 0-255 r	IANA has also listed this document as an additional reference for the registry
	ange are approved by Designated Experts.	.
	These registrations are not subject to the formal <xref target="RFC7120"/> renew	</t>
	al process."</t>
	</li>
	</ul>
	</section>	</section>
	<section anchor="reserve-64999">	<section anchor="reserve-64999">
	<name>Reserving Content-Format Identifiers 64998 and 64999 for Documenta tion</name>	<name>Reserving Content-Format Identifiers 64998 and 64999 for Documenta tion</name>

	<t>IANA is instructed to reserve Content-Format identifiers 64998 and 64 999 for use in documentation.</t>	<t>IANA has reserved Content-Format identifiers 64998 and 64999 for use in documentation.</t>
	</section>	</section>
	</section>	</section>
	</middle>	</middle>
	<back>	<back>
	<references anchor="sec-combined-references">	<references anchor="sec-combined-references">
	<name>References</name>	<name>References</name>
	<references anchor="sec-normative-references">	<references anchor="sec-normative-references">
	<name>Normative References</name>	<name>Normative References</name>

	<reference anchor="RFC7120">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
	<front>	120.xml"/>
	<title>Early IANA Allocation of Standards Track Code Points</title>	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
	<author fullname="M. Cotton" initials="M." surname="Cotton"/>	252.xml"/>
	<date month="January" year="2014"/>	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
	<abstract>	110.xml"/>
	<t>This memo describes the process for early allocation of code po	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
	ints by IANA from registries for which "Specification Required", "RFC Required",	193.xml"/>
	"IETF Review", or "Standards Action" policies apply. This process can be used t	<xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.
	o alleviate the problem where code point allocation is needed to facilitate desi	0026.xml"/>
	red or required implementation and deployment experience prior to publication of	<reference anchor="IANA.core-params" target="https://www.iana.org/assign
	an RFC, which would normally trigger code point allocation. The procedures in t	ments/core-parameters">
	his document are intended to apply only to IETF Stream documents.</t>
	</abstract>
	</front>
	<seriesInfo name="BCP" value="100"/>
	<seriesInfo name="RFC" value="7120"/>
	<seriesInfo name="DOI" value="10.17487/RFC7120"/>
	</reference>
	<reference anchor="RFC7252">
	<front>
	<title>The Constrained Application Protocol (CoAP)</title>
	<author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
	<author fullname="K. Hartke" initials="K." surname="Hartke"/>
	<author fullname="C. Bormann" initials="C." surname="Bormann"/>
	<date month="June" year="2014"/>
	<abstract>
	<t>The Constrained Application Protocol (CoAP) is a specialized we
	b transfer protocol for use with constrained nodes and constrained (e.g., low-po
	wer, lossy) networks. The nodes often have 8-bit microcontrollers with small amo
	unts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wire
	less Personal Area Networks (6LoWPANs) often have high packet error rates and a
	typical throughput of 10s of kbit/s. The protocol is designed for machine- to-ma
	chine (M2M) applications such as smart energy and building automation.</t>
	<t>CoAP provides a request/response interaction model between appl
	ication endpoints, supports built-in discovery of services and resources, and in
	cludes key concepts of the Web such as URIs and Internet media types. CoAP is de
	signed to easily interface with HTTP for integration with the Web while meeting
	specialized requirements such as multicast support, very low overhead, and simpl
	icity for constrained environments.</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="7252"/>
	<seriesInfo name="DOI" value="10.17487/RFC7252"/>
	</reference>
	<reference anchor="RFC9110">
	<front>
	<title>HTTP Semantics</title>
	<author fullname="R. Fielding" initials="R." role="editor" surname="
	Fielding"/>
	<author fullname="M. Nottingham" initials="M." role="editor" surname
	="Nottingham"/>
	<author fullname="J. Reschke" initials="J." role="editor" surname="R
	eschke"/>
	<date month="June" year="2022"/>
	<abstract>
	<t>The Hypertext Transfer Protocol (HTTP) is a stateless applicati
	on-level protocol for distributed, collaborative, hypertext information systems.
	This document describes the overall architecture of HTTP, establishes common te
	rminology, and defines aspects of the protocol that are shared by all versions.
	In this definition are core protocol elements, extensibility mechanisms, and the
	"http" and "https" Uniform Resource Identifier (URI) schemes.</t>
	<t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7
	232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
	</abstract>
	</front>
	<seriesInfo name="STD" value="97"/>
	<seriesInfo name="RFC" value="9110"/>
	<seriesInfo name="DOI" value="10.17487/RFC9110"/>
	</reference>
	<reference anchor="RFC9193">
	<front>
	<title>Sensor Measurement Lists (SenML) Fields for Indicating Data V
	alue Content-Format</title>
	<author fullname="A. Keränen" initials="A." surname="Keränen"/>
	<author fullname="C. Bormann" initials="C." surname="Bormann"/>
	<date month="June" year="2022"/>
	<abstract>
	<t>The Sensor Measurement Lists (SenML) media types support multip
	le types of values, from numbers to text strings and arbitrary binary Data Value
	s. In order to facilitate processing of binary Data Values, this document specif
	ies a pair of new SenML fields for indicating the content format of those binary
	Data Values, i.e., their Internet media type, including parameters as well as a
	ny content codings applied.</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="9193"/>
	<seriesInfo name="DOI" value="10.17487/RFC9193"/>
	</reference>
	<reference anchor="BCP26">
	<front>
	<title>Guidelines for Writing an IANA Considerations Section in RFCs
	</title>
	<author fullname="M. Cotton" initials="M." surname="Cotton"/>
	<author fullname="B. Leiba" initials="B." surname="Leiba"/>
	<author fullname="T. Narten" initials="T." surname="Narten"/>
	<date month="June" year="2017"/>
	<abstract>
	<t>Many protocols make use of points of extensibility that use con
	stants to identify various protocol parameters. To ensure that the values in the
	se fields do not have conflicting uses and to promote interoperability, their al
	locations are often coordinated by a central record keeper. For IETF protocols,
	that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
	<t>To make assignments in a given registry prudently, guidance des
	cribing the conditions under which new values should be assigned, as well as whe
	n and how modifications to existing values can be made, is needed. This document
	defines a framework for the documentation of these guidelines by specification
	authors, in order to assure that the provided guidance for the IANA Consideratio
	ns is clear and addresses the various issues that are likely in the operation of
	a registry.</t>
	<t>This is the third edition of this document; it obsoletes RFC 52
	26.</t>
	</abstract>
	</front>
	<seriesInfo name="BCP" value="26"/>
	<seriesInfo name="RFC" value="8126"/>
	<seriesInfo name="DOI" value="10.17487/RFC8126"/>
	</reference>
	<reference anchor="IANA.core-parameters" target="https://www.iana.org/as
	signments/core-parameters">
	<front>	<front>
	<title>Constrained RESTful Environments (CoRE) Parameters</title>	<title>Constrained RESTful Environments (CoRE) Parameters</title>
	<author>	<author>
	<organization>IANA</organization>	<organization>IANA</organization>
	</author>	</author>
	</front>	</front>
	</reference>	</reference>
	<reference anchor="IANA.media-types" target="https://www.iana.org/assign ments/media-types">	<reference anchor="IANA.media-types" target="https://www.iana.org/assign ments/media-types">
	<front>	<front>
	<title>Media Types</title>	<title>Media Types</title>
	<author>	<author>
	<organization>IANA</organization>	<organization>IANA</organization>
	</author>	</author>
	</front>	</front>
	</reference>	</reference>

	<reference anchor="IANA.http-parameters" target="https://www.iana.org/as signments/http-parameters">	<reference anchor="IANA.http-params" target="https://www.iana.org/assign ments/http-parameters">
	<front>	<front>
	<title>Hypertext Transfer Protocol (HTTP) Parameters</title>	<title>Hypertext Transfer Protocol (HTTP) Parameters</title>
	<author>	<author>
	<organization>IANA</organization>	<organization>IANA</organization>
	</author>	</author>
	</front>	</front>
	</reference>	</reference>

	<reference anchor="IANA.provisional-standard-media-types" target="https: //www.iana.org/assignments/provisional-standard-media-types">	<reference anchor="IANA.prov-media-types" target="https://www.iana.org/a ssignments/provisional-standard-media-types">
	<front>	<front>
	<title>Provisional Standard Media Type Registry</title>	<title>Provisional Standard Media Type Registry</title>
	<author>	<author>
	<organization>IANA</organization>	<organization>IANA</organization>
	</author>	</author>
	</front>	</front>
	</reference>	</reference>

	<reference anchor="RFC2119">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
	<front>	119.xml"/>
	<title>Key words for use in RFCs to Indicate Requirement Levels</tit	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
	le>	174.xml"/>
	<author fullname="S. Bradner" initials="S." surname="Bradner"/>
	<date month="March" year="1997"/>
	<abstract>
	<t>In many standards track documents several words are used to sig
	nify the requirements in the specification. These words are often capitalized. T
	his document defines these words as they should be interpreted in IETF documents
	. This document specifies an Internet Best Current Practices for the Internet Co
	mmunity, and requests discussion and suggestions for improvements.</t>
	</abstract>
	</front>
	<seriesInfo name="BCP" value="14"/>
	<seriesInfo name="RFC" value="2119"/>
	<seriesInfo name="DOI" value="10.17487/RFC2119"/>
	</reference>
	<reference anchor="RFC8174">
	<front>
	<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti
	tle>
	<author fullname="B. Leiba" initials="B." surname="Leiba"/>
	<date month="May" year="2017"/>
	<abstract>
	<t>RFC 2119 specifies common key words that may be used in protoco
	l specifications. This document aims to reduce the ambiguity by clarifying that
	only UPPERCASE usage of the key words have the defined special meanings.</t>
	</abstract>
	</front>
	<seriesInfo name="BCP" value="14"/>
	<seriesInfo name="RFC" value="8174"/>
	<seriesInfo name="DOI" value="10.17487/RFC8174"/>
	</reference>
	</references>	</references>
	<references anchor="sec-informative-references">	<references anchor="sec-informative-references">
	<name>Informative References</name>	<name>Informative References</name>

	<reference anchor="Err4954" target="https://www.rfc-editor.org/errata/ei	<reference anchor="Err4954" quote-title="false" target="https://www.rfc-e
	d4954" quoteTitle="false">	ditor.org/errata/eid4954">
	<front>	<front>
	<title>RFC Errata Report 4954</title>	<title>Erratum ID 4954</title>
	<author>	<author>
	<organization/>	<organization>RFC Errata</organization>
	</author>	</author>
	<date/>	</front>
	</front>	<refcontent>RFC 7252</refcontent>
	<seriesInfo name="RFC" value="7252"/>	</reference>
	</reference>
	<reference anchor="RFC2046">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
	<front>	046.xml"/>
	<title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
	Types</title>	141.xml"/>
	<author fullname="N. Freed" initials="N." surname="Freed"/>
	<author fullname="N. Borenstein" initials="N." surname="Borenstein"/
	>
	<date month="November" year="1996"/>
	<abstract>
	<t>This second document defines the general structure of the MIME
	media typing system and defines an initial set of media types. [STANDARDS-TRACK]
	</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="2046"/>
	<seriesInfo name="DOI" value="10.17487/RFC2046"/>
	</reference>
	<reference anchor="RFC8141">
	<front>
	<title>Uniform Resource Names (URNs)</title>
	<author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre
	"/>
	<author fullname="J. Klensin" initials="J." surname="Klensin"/>
	<date month="April" year="2017"/>
	<abstract>
	<t>A Uniform Resource Name (URN) is a Uniform Resource Identifier
	(URI) that is assigned under the "urn" URI scheme and a particular URN namespace
	, with the intent that the URN will be a persistent, location-independent resour
	ce identifier. With regard to URN syntax, this document defines the canonical sy
	ntax for URNs (in a way that is consistent with URI syntax), specifies methods f
	or determining URN-equivalence, and discusses URI conformance. With regard to UR
	N namespaces, this document specifies a method for defining a URN namespace and
	associating it with a namespace identifier, and it describes procedures for regi
	stering namespace identifiers with the Internet Assigned Numbers Authority (IANA
	). This document obsoletes both RFCs 2141 and 3406.</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="8141"/>
	<seriesInfo name="DOI" value="10.17487/RFC8141"/>
	</reference>
	</references>	</references>
	</references>	</references>

	<?line 336?>


	<section numbered="false" anchor="acknowledgments">	<section numbered="false" anchor="acknowledgments">
	<name>Acknowledgments</name>	<name>Acknowledgments</name>

	<t>Thank you	<t>Thank you <contact fullname="Amanda Baber"/>, <contact
	Amanda Baber,	fullname="Carsten Bormann"/>, <contact fullname="Christer Holmberg"/>,
	Carsten Bormann,	<contact fullname="Éric Vyncke"/>, <contact fullname="Francesca
	Christer Holmberg,	Palombini"/>, <contact fullname="Ketan Talaulikar"/>, <contact
	Éric Vyncke,	fullname="Marco Tiloca"/>, <contact fullname="Mohamed Boucadair"/>,
	Francesca Palombini,	<contact fullname="Paul Wouters"/>, <contact fullname="Renzo Navas"/>,
	Ketan Talaulikar,	and <contact fullname="Rich Salz"/> for your reviews, comments,
	Marco Tiloca,	suggestions, and fixes.</t>
	Mohamed Boucadair,
	Paul Wouters,
	Renzo Navas,
	and
	Rich Salz
	for your reviews, comments, suggestions, and fixes.</t>
	</section>	</section>
	</back>	</back>

	<!-- ##markdown-source:
	H4sIAAAAAAAAA9U823LcRnbv+IrOsCohdwcjkbpYole2KZFasVa3kNQ6W1ub
	qAfo4bSJAcZogNSY0gfkL/ItyY/lXLob3RgMqbIlp+JyiSQGffr0ud960jRN
	Gt0Ual+M3i1z2SjRVKKZK3F88PpAPKsO3sI/ZaPKJn1e1QvZGHGizrVpatno
	qhRv6ypTeVsrM0rkdFqrS4A0sCxaZQTvNUoy+Pe8qlf7wjR5kuRVVsoFIJPX
	ctakWjWzNKtqlWaztFbnaUvL0ruPE9NOF9oYANaslrDg+OjseVK2i6mq9xN+
	zeyLb/Ye7CX4+36SwbaqNC08bepWJYDnvUTWSgK+P6qpkGUujgHjulSNOKtl
	aZZV3YySq6q+OK+rdknnKvEIulS5ODk6PZu1hTgqL3VdlQs4KpDgQq1gQb6f
	iJQoiD/r4OT4N2OHvyGd+GdIquRSlS1gLMTn7ysEk2H0I6Cry3PxZ1yKzxdS
	F/AcqfgD0nNS1ef4XNbZHJ7Pm2Zp9u/cwdfwkb5UE/faHXxwZ1pXV0bdQQB3
	cOG5bubt1IJMr87vRLzBNwokfhMAt29OeOlEV/GaOzdyezJvFsUoSWTbzKua
	KAvnL1hOzubVQhrxvDIG6At7C8BblvoXova+eKlLWVf4XDEhGlowmfGCHwr6
	HA8bwz0yF5U41D9drIM8rs5QltqikWW2mpRFAF3BskkOy37QVdN7KymJu0Bg
	ZO3J82ff7O7d3RdaljJVsi5W9imI7L7IKrnkvx/v7sJbSMnUwC7u4eN7oDKq
	XBRp1sCzp8/e7j1EuEKkFiZuTw+e7OOSR7t7D+FPFMoJEXkpazgqCLzZd88X
	KtcyRUnqntHOA+8u6+pSo/7JIjVwyFzWeRoBSHQ5C498VNf3Hz+4b7UyAcHV
	zQo/OD16+RykBZBs5hqEOUnTVMgpijwcLjmDhwIsQ4uybrXHOFKhdsHOKPJo
	tUJdE0tvmwQgQp8PmSYzYmNn167G4grkVJduwc26J7afVSdHO+KtJ9HIQ2IF
	nvROIAtTCV02dZW3GeAmRamugONFuyjHYvQKaSjOgIajsTPGDuAked7W8KBe
	AAfh0wgunFPVlwCwZ3l1jqSeaUBNPLz/+PEjsnX422OiS2sUoOPhEO0mzISF
	zvNCJckWmkbCl4xYcn19quhXsbs3uSeqmUhRYj99ErkyWa2ngMWXYscX5oa4
	vh7SgU+fJsn26wr93xxohpsxRwyejgjt4czlpRJTpUp4BDoAqMgMwLEQVrCB
	lXSAuZMcw8Fl3eisBfs6FroBEs0Af0ugtrDkqKYNHAtBDHnPkIezulowNdDp
	gWO91CA/AOL46PTP4mCJmikLOLcszxVj30mQ2N578DAF1j/eEWA4r1RR4E8P
	87muTQO7L9yvpyhTudh+/uz56c4mmLt34b+URGoHZNRyF5fwChRVkE573LwS
	ZQVnKi+r4lLRq4fK6PMSFDsXRx+Wqm7E9iGwEQUVfDQ4sVKew2emKlSxEtMV
	iwi8aKqyVAWSHYgqC/2LWhM8kOV3aImaFjcoVuOA8hYV9WFZ6AzioBWs/LnV
	sGU2V9kFmxUvD4sp7EGyDBRwHEJNFdt6oiZj0ekuSa2olg1ZSNEJGh/KLoaf
	JDXSmCrTdHxax0f4uQU3qvJhgTAC3QEIRSYLQBs4rnNraRppLvCFc1Wqmj4t
	qzJtan2pZTF2JzTioqyuCpUDQ4n9C3BWelkobwkModqobF5WRXWulRnTEzOv
	2iInwk2V40mO2OSArRclx4PaolXI7AIJd97qHJwicnUlFEgHLKuBuuWsRX+C
	tmhaeSIgDFUjkVCNVoxSCJ1xmoMQywLCuXwl4EwoEKoGq6Cq1kTSYCabPMr1
	tTNiIF8LYMxs9RvdilcQwGahG31O8TXC04ZI0YLC4xIWEgC2kCiHiDNiXxsk
	HSqOwxGEyJ4f0Jupmuw+apjpK+W4czHgYWo2Eh51xAh4BwqELhq5hptXZjM0
	UsWiqK7WCYLvqgWEyxKOutlw/T/1g1sI55KZxBpxiAZc098oS0pA1C8w7DeA
	9bvTs9GYf4rXb+j3k6N/fXd8cnSIv5++OHj50v+S2DdOX7x59/Kw+61b+ezN
	q1dHrw95MTwV0aNk9OrgbyNmzujN27PjN68PXo4EecuI1J7jKG/1slZoV6RJ
	nLvOcQ0Ekf/9X7v3QRH+CaKrvd3dx6AL/Mej3W/AnYmruSp5t6oEnec/gQ+r
	RC6XEMQiFBASkcmlboC/Y/QtYC6uSgHMUkDNP/wdKfOPffGnabbcvf+dfYAH
	jh46mkUPiWbrT9YWMxEHHg1s46kZPe9ROsb34G/R347uwcM/fQ+JhRLp7qPv
	v0vW7I2xzh84sTA9QR/FniF4kto3iNfuLRbtEZKZwwpiZBee7VFs5hIFDHKO
	e7KB/KuMQwYFBbOglWMhONSclAAgtjUE7KgNBlTJWtP+4eYQjEOafaPVJOc5
	UFgAzK/kyrDHrRWZLnK8c3QXtK6zj+Bt9BJiKm+B4MXAjXaWInmDhgKBlgSZ
	Y7AK4KEDQ9jnvM2GEyJw7xqIFLY0chMZnL32lZTg+BGjnMtBAxQ6u0ECEZcD
	hb2+xkyPuGrNaa0W1SXbUh/LXqFrzHN2ilHchh8Epnspm2wutq+v8VGKAFKC
	J4tPn3bGCMMZaQIOHjtTNYWsHYzI1SIseJ1BwXIAQ+K7yUIfHw5b5sgkI1AL
	gCNOgIps2bqxWrUS11tELMspYxUEN9Lwmmmn9hGGC0uIVZTYmOXAdn//d/sW
	KFcx+0eS+NpRp86sTt7t5BhXSAHIAMnGsCMQGzgwAtMJQk1nu/NhAYH79fX3
	aH/v3n9oFRZcC0owBhGlXrgYFxhdzyHgoUDCIBvCrRv0rTnC5bc5Fcd3l3JV
	VDIH49yJ3zwwILITECS+ZNrQ0sFDsmNpDcskMYGCBYMhPTxUMptjNBIF0BTm
	yl4cPEbxAk7XOgu8NcVAAusya4kHMHI49Orn8CdHNyboyRHgCLEowSzjPRat
	wVwlK9qcKRkE+U5jXdyOqs7pxfoxPGAyOJAtPXhw70FIPA4mZUhcR1CGeWvS
	AOTo9rMhG+BIcWJGEYDsTJS1JAjpCneVTjActBiThZJlnHMA2Yj23pY6IoHE
	KEx4QPLAnuO2GUZQq/4BfH2okweb9AiyhmaJNVs+hycOhPiQ8w3RQxu2gWap
	MtY3XITSF3JhW88A4ApMxvGsS3liUEYAPhDGOM5Y5DpqED/K8KAbY80ACacq
	ndRMklPQ5wKrf2NRkZ/qMkV4ryDuIt/KId0DJ10iQKe5rK5D6SKJ9oSj1ZuS
	mWG3U6u+32mmRYqWPZulCIFM4kdxQqL9cVOHAD7BCgv8TD6m9r+BXwDQ3XTv
	wQN43dYCbInjo/ulS2N6aP0zlhI/fULLRvk7lnVwN+GKHgAjLJoQY+NN+nWU
	oXd+FSKEBxdKdi0qX+54BPbeHoO9pYbzkQszpC6QzyHw2Vq8hrFs/Z34A3mG
	sgrEkvUx+BRkENx/01fv6L2e3dRsMFaq8X4jKrHdsjYwu9so8sQqK//hIXac
	zQ1i7ND621JgULV2BL13zxW0vvmSfKLghqMWAJMSKMPMQdwPoziHFjwgPMhV
	WDw0vVGId0aRQolqaaNQeIg57Mfkel9s9TRUUJfvyaC33N/Y0oNo6anKJEJt
	rA82SwyNwBFjxFGodLpqVJRaY3AFRhgi9WIcxL8VxDg2oMhzTp77HhF1nnyI
	0ZdqLVhFXx8xYjQQD7uA7f7kAcVrvhOCFsrVJSHkzwv0GFHhApUhs3FrEDww
	WraKaZRiH3N9rQiVlAsrKfZyUvUB9UDb3cjWervDZ0R12WR+uSyHaI1uNlEj
	tFGj24zUZCSi0vM+5N7igKq9GJfZ+l5Yt751W67EgoOnuDl6fySm0gCH4P2I
	C4/6XGDAa4y0IkHFSlufzNeADbA0EQLJ3Gkie1vwpyx2HVNx7cg1qsAT11iN
	zCo4zbLS2EPt5WVdXw6QJp5TnK7MRPyIvp/D92BnOD3asjFvTPED1mEHq9vb
	Zoe8OhsueoeRDvCdKjhLr5KNLHW0GmPJiSrU3NeATBaMPTEJor2qralizsEX
	9iFpl2573g8wdzVOOomBdLdtivVCwr3Jbkd9S5bJ54jUzVI6JFRRE2NYrHbv
	fm25Wg+UOgOG1AodOfqq0GHYEuq6wRrDcnS5EcmHHIj3GrcjErp+NjKwLzr4
	SXIQL3SxNa9EN0qvU36D54Y3XTEf6CFDLxu4X8rDgnYceXwqTQmw/0XOmRcI
	EUbZXdjAvoMs11qFy5X0w2wDkcIQoeu1DQYKGEJQJE91olpj9US6rg4qLIYS
	MRk4SO6Vz8X21VyDQvveSMS4HRdo+56MZUzo96aquUI8yWVzAYPcdufRJKlz
	4O+V9+dc6F/RK4g6ZlvMqUtV5lWd2qQmIw9fUQojQPlz2shVUMM8PIwKcrUs
	qpXdBwsKC8hHQMfTpkrtryKoQhgqkdkYDXHMKAvB7ItaSoDFYCHAVTQa9aG5
	syykxlpxXNwQHK75RxWAblLgjZILOjygjz1djuQA9RAtJ3ZFRSWnekF1L5KG
	rFpgZ8Sh+WrvVbxyIclSWuJREOTUAetZg8ehRhYZc1tIQQguAY6SVzlFeZ9j
	bwTMLeANIVFFqZxRXV7NAYj6IBeQcaJYni7AO4sjoOj5KkTXJ+KZrGtNhXoM
	2TIN0J7iwMpKvJn+BFwB8VyiQPnK2LOnb052xEKfzxt/PimwSSK8AGGcKwp9
	EbH8jlF/zKZVTYW0LXG2qZ0TTXH1SmkZRBmoC6Zrmd7WF6MExGwsH0ZhGBcG
	SVsBy4MNi6ipOFWWC07NiORUfiuZo2veVvIZeo7fmxZfRMl7qUgwBiO26dwa
	1YcrIbmTWNpz9DZ499RGIgG49cTkthkbrKfaQoQ7b0QLSvG4pO6IdRPpNOpJ
	fcECR8rsGu32GODZuSpD/t1ja4sLb8rMNd+tox0OdcV2FGmtlRJ2vG/r8Dw+
	pNgZkMIYxXYoKuRqgyFX1xTewKZBhoTKfmNOaGM6ckpcYSf768yCtwAxzhDw
	4Wmr9eQaEySvI1x1nKIJUxTpgIGBZ2ioZ1F5PoLgi26DJLmh/TJwlg4L6u6r
	JqyudbV5nDFoQYswcMbY7l3pSrwj29pF3ZtjJ7CM9O6KRLSrYKWHOO/nDBSV
	Mgd2Q+GdAkJVie72JlpsY9cR+EG2YYeFwHC1M1TPQCKsonYbfCWqJN1EkRW8
	blLG2jJuXDEeVJel2CtoZt9IpK6PRUk6lmJKO3BA4QqehMZC+LzTIJm/TUt7
	YaLfyQ/IsKzZ1Arp32VXNpcYw4KaV+puYRdZ4qncSYFY1/tbN2fVydnnOAqf
	r3MuRMu7qRTy2gWsB5uDgzmDWU/PCZxa34lpRJjfUaRWlbqx9sp2y5AeMX4+
	bGXvdVzC6WU+Hk4ODQSnNXp32ggjCggDVoINjB3vsX76IPeTj4F0P6MRCldA
	cQ0w8NYVZWqGim61n/G4zUkD8jPNJj9XjdQFUakf/fRw6DcnqAI+sJG13ZXA
	2eza6kpYagcGAhrGpcPcf2Qh90G5y1Msb7QJhqfQDOR5NFwStdzXR0vIlAVv
	o5fHTl9u+VKs/BoKtCwZCU8q38RZEUOxCUO0M+VLXX+AD1XQaRHgNuS+YM76
	uRfSi8xaTn3eOXxQg+iS9YndecCjod6S5MC5zrkzSW7PxTsbgxyW2W5TLp5E
	lwa+RpxjHcAGc+6cp+zcZ9Ss6Wx7a+84DLPCmpCBMQJijuZmp5fUkA4sGqYn
	TZ/FiMhNrC12YXxnmGscNgej0pY8vJBPxIEX+Loz1KVi8Z+hqXIqOnBq18Oi
	XJlFr1RoFCUpf4e77kbsrADmN1UCusiHULMmK66l+1qzuN6yRQ9WlA0DoRTK
	AW3azOq2nWALilsW9DiuDoOAs/V39RfaDZVtP0l2J1RFvGnAc2BoE1nJVYN1
	jocWyNcypiqgH6VtAfluMsHfOgxvMLD9kdEoUiAUlKYGY2Qxf0WDRNzUcQFR
	LDDIo6F/FCjw+zYjQ1oHG34NI0E0sjl+aCrMOnwqz9EQG5oM3bhc8YaZwSDI
	6IYkOdxA6XClfs+s9eFfWwQjbnSFrSAbckz1HfHYFtuWflRXo/DTrIkDpW+D
	G0/J8vtTe3RDDfZv2vMuKaaumUZIlyiD85+m/OmnTwSULPZ6j96351k4SDLR
	dVIrr0eaz+jsvTg7e9vbJZAdF+K8QEONdSm+2gXooulpKnDOYhtBxFcGrMj1
	7r5QPdY1kaK+kO7K8s4DsDULLBCESZfKhnxH64aMWgwKuemHhL02Y5uCHG00
	c4WVMA1MRNiXeH1rqgscX7Nn3uXWXLeWOnddF8zKsBPbcVjSHvdr2liuMjyq
	4MqsttbiWyM0DlpHVpQ0JLBZwWzDgD3N5pXGMT/qVywU16Rxwm5aDByDnMlb
	L5dWX13lIBLm5+SNrrfW5LRXwAovZnQSz/NaTvBxAy4mcEq2ZnLd3I4Vg1ss
	+yQ57Dow4ZA2Jk8bW0c4o0AhjcRE6Ar5cSsqFMYNn8mF1rbpYkPVTW9rs3Ha
	9NHEtYn8fTVsntH4jq30dddA2O+iNKJByyDWTTVd0dToO4QqFBWsxwJnFGr8
	HFtceCVM2TYXlronCOTtmjXEugsa95/bqukGHDhV17a4xWm5z0uN8xzveVHK
	x37faxc9mDycPOyfcYIX7WjO9ErTxFLfQEc1qLbkHQj3A9tIx8qyBnOEhVR3
	zKiVIvOfQPCBqxBzNLYNHxDEth9dBGeDuqr2fYkwdsAUwuuiD8yoWsNzQMcl
	XSiJBwNOWMD6dV+fjCgHoZf/Osm89b6En9XkLBCbqhaPKRDhim6dTFXnFVq6
	OdLvpA0I5tr85pmz0BiVxGv8vI695gJ6cEkz9KUzrVhoabAW1dgmAdXgFFoE
	d1/Dk4K6PTxoWwfFevQEeCbusMwluD16ZrhihhqLt9yst/gXoO2KOqSOHhF5
	HTJY24VQn5NRBjTMBioBXVW33TTb7w/jWvdH2ar1Ml1AfeOWY0Cex9Vse6Rz
	J+gG6ToQu4/Y8/Wj6s0TbsHEXTj6+RlX5CbJS32hWHHJMMS1mzh854Ep4I/l
	OSvPVj86B1TflXi/CiRqS31IW/4jXTSf4pZuV+KjQSqazFov89GxS2GhBBvt
	49hdZO4/9t3qRwRAE3f2f1gRdn4sUGr/2KEkO6CEc0Qgbeflk1GhZs3IzRAd
	sLwJ3w9yI+sR2hbnd2s441TREM06K95R7zcQy9dj+pfyAkJ6I/gF6JhVRn3r
	+OwBP9n90jTtH8cR2JPvdvr+1bkka+a/EpWdser5wi9Fa/yHUr8nbqOvTGnn
	FHuEjOi9nu/8PpIc7/sFSEx3hpxR0OUMR5G/FHEjue3lbo6Yhy3josRR6W6B
	4807iaNMQ1JtfjWF1ztDHKmZKI6jDlBFl0VyiwaJ8xgDskIlUmzPV0sc4qb5
	+J2B3didBmW0oBDj2y09JnPhDtZ7TCbJAYcTONVlLz9mFKoUeBvE5Z/oZ93d
	KPD1mybV8c6NC8sM1pdHeNU3Q+/ohsZ/qygtVoFmPhLrH3/bmUtH2t+iysDu
	IwjpgTuI5Es+TihGUhz68Z91Lm3v7nyeFMZk+LXiR2EKRy/NarQ2RM0VRs1R
	vaNOVnGwiSUWCEOW1AS3g1FcLuZgOffo+84gnSCW1GSTpHYRWX9oyxXMjUCG
	8Pz37yEpaIssqf7PxGPvFvEIgHvj9HVtE+cznGi6b6voDBdfzcWuInqRzPdC
	pe0198wW5jt4w7KIzNMmEeFMjW9yW8Ti7SfJCwiZL/E+EuelPD/lu4/9RLm7
	ModcscbMe8De9zq4y6x+qApffg+G7z8gwp+BVX6/Bt8O+tneISZ1706Od/j7
	FBpO1N6VmnoKJ8pUbQ2ZyWu0i9vvTl7v2Lt5j3bv71JjWGPigoyCD23F5rUf
	kj8Obh29tyi+971g+4C29lfvDBVCRFAIYaBoweO0BOkUfQOEJ9oX0EOg4B+z
	q+bbgJJPRm1d7luk93dHNyrqxvVH/3bw6u3Lo3j976/C96wKB4Nu1II7sQ38
	6631K7CAIs9T6LKeZTaN69JfuhKLM0pcuP6c+7Yz/QECte/ECPfeF1aHdR4U
	cYdbUt45RFyOqzooVlTKwIHnWld0f7Qb1J6MQHtsszwuRPvxFx4AVWtf6MH3
	/kX8DQMY1ITF+mU7ddIwSUBj0qMcxyT2BUgPSni4iyskVW6ALKaln2JBhr2G
	PJ5YdeDq7ddb0RXjoau5g+fEqYBmnYU9noUMOnCD6P5+z2cNLsbzKJ5K09XA
	6McEduMK0rq287QXD35aLO0wS/+6Qm+4BXkNpOOrRgPh+PEtX4wRX0u63opv
	X2+WI659fblvo8IZK7x/f5C5b66hCjEoJn/xn8qfjGbgiygjO5vL8kKsqjY5
	wC+mkeKphFfGyTNwhYCPeIrolCU8mNdkV8SLqkAo5+Pkf/4TZ5z/uipBe8bJ
	85q+fiCT4M4L0kc9Tv6iGjBCZ7KAeExfSAD8StZZJc40jpTCX9Vc4veqPK3a
	TOZSwwtv4VXxI8TzeIkuOVHlLxU4i0sJfwCCyQm6pVNZ/JIgGQDx2jYEwK/w
	eDOW0Ux7fo7zYDSlTZV1/UGZ9Qvp9J1vwimd8zlW08adFrqb7laku64jLmey
	dje5XSOh+14Ruswf24tJ8r+MKdpgVVIAAA==


	</rfc>	</rfc>

End of changes. 86 change blocks.
	640 lines changed or deleted	282 lines changed or added
This html diff was produced by rfcdiff 1.48.