<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.3.8) --><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-core-cf-reg-update-09" number="9876" category="std" consensus="true" submissionType="IETF" updates="7252" obsoletes="" tocInclude="true" sortRefs="true" symRefs="true"version="3"> <!-- xml2rfc v2v3 conversion 3.28.1 -->version="3" xml:lang="en"> <front> <title abbrev="CoAP Content-FormatRegistrations Update">UpdateRegistration Procedure Updates">Updates to the IANACoAP Content-FormatsRegistrationProcedures</title>Procedures for Constrained Application Protocol (CoAP) Content-Formats</title> <seriesInfoname="Internet-Draft" value="draft-ietf-core-cf-reg-update-09"/>name="RFC" value="9876"/> <author fullname="Thomas Fossati"> <organization>Linaro</organization> <address> <email>thomas.fossati@linaro.org</email> </address> </author> <author fullname="Esko Dijk"> <organization>IoTconsultancy.nl</organization> <address> <email>esko.dijk@iotconsultancy.nl</email> </address> </author> <date year="2025"month="May" day="10"/> <area>Web and Internet Transport</area> <workgroup>Constrained RESTful Environments</workgroup>month="September"/> <area>WIT</area> <workgroup>core</workgroup> <keyword>IANA</keyword> <keyword>registration</keyword> <keyword>update</keyword> <keyword>CoAP</keyword> <keyword>Content-Format</keyword> <abstract><?line 56?><t>This document updatesRFC7252 regardingRFC 7252 by modifying the registration procedures for the "CoAP Content-Formats" IANA registry, within the "Constrained RESTful Environments (CoRE) Parameters" registry group. This document also introduces a new column, "Media Type", to the registry. Furthermore, this document reserves Content-Format identifiers 64998 and 64999 for use in documentation.</t> </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 target="mailto:core@ietf.org"/>), which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/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> <middle><?line 62?><section anchor="introduction"> <name>Introduction</name> <t><xref section="12.3" sectionFormat="of" target="RFC7252"/> describes the registration procedures for the "CoAP Content-Formats" IANA registry within the "Constrained RESTful Environments (CoRE) Parameters" registry group <xreftarget="IANA.core-parameters"/>.target="IANA.core-params"/>. (Note that the columns of this registry have been revised according to <xref target="Err4954"/>.) In particular, it defines the rules for obtainingCoAPConstrained Application Protocol (CoAP) Content-Format identifiers from the "IETF Review with Expert Review or IESGApproval"Approval with Expert Review" range of the registry (256-9999) as well as from theFirst"First Come FirstServedServed" (FCFS) range of the registry (10000-64999). For the FCFS range, these rules do not involve theDesignated Expert (DE)designated expert and are managed solely by IANA personnel to finalize the registration.</t> <t>Unfortunately, the rules do not explicitly require checking that the combination of Content-Type (i.e., Media Type with optional parameters) and Content Coding associated with the requested CoAP Content-Format is semantically valid. This task is generally non-trivial, requires knowledge from multiple documents and technologies, and should not be solely demanded from the registrar. This lack of guidance may engender confusion in both the registering party and the registrar, and it has already led to erroneous registrations.</t> <t>This document updates <xref target="RFC7252"/> by modifying the registration 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 procedure to be performed for most ranges of the registry, and allow the registration of temporary Content-Format identifiers. This document also introduces a new column, "Media Type", to the registry. Furthermore, this document reserves Content-Format identifiers 64998 and 64999 for use in documentation.</t> </section> <section anchor="conventions-and-definitions"> <name>Conventions and Definitions</name><t>The<t> The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t> <?line -18?>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"/>. In this document, those terms are fully capitalized.</t> </section> <section anchor="security-considerations"> <name>Security Considerations</name> <t>This documenthardensupdates the registration procedures of CoAP Content-Formatsin ways thatto reduce the chances of malicious manipulation of the associated registry.</t><t>Other than that,<t>Otherwise, it does not change the Security Considerations of <xref target="RFC7252"/>.</t> </section> <section anchor="iana-considerations"> <name>IANA Considerations</name> <t>This document updates the IANA procedures defined in <xref target="RFC7252"/> for registering CoAP Content-Formats as described in <xref target="iana"/>. It alsoremoves a note that was added to the registry as a temporary patch (<xref target="temp-note-removal"/>),adds a new note concerning temporary registrations (<xref target="new-note-add"/>) and reserves Content-Format IDs 64998 and 64999 for documentation (<xref target="reserve-64999"/>).</t> <section anchor="iana"> <name>CoAP Content-Formats Registry</name> <t>This section and its subsections replace <xref section="12.3" sectionFormat="of" target="RFC7252"/>.</t><t><cref anchor="replace-self">RFC Editor: in this section, please replace 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"/>. 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 Internet Media Types to be used in CoAP and assigned each, in combination with a Content Coding, a numeric identifier. The name of the registry is "CoAP Content-Formats", within the"CoRE"Constrained RESTful Environments (CoRE) Parameters" registry group.</t> <t>Each entry in the registry must include the Content Type, the Content Coding (if any), the Media Type registered with IANA, the numeric identifier in the range 0-65535 to be used for that Media Type in CoAP,the Content Coding associated with this identifier,and a reference to a document describing what a payload with that Media Type means semantically.</t> <t>CoAP does not include a separate way to convey Content Coding information with a request orresponse, andresponse; for thatreasonreason, the Content Coding (if any) is also specified for eachidentifier (if any).identifier. If multiple Content Codings will be used with a Media Type, then a separate Content-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> <t>The registration procedures for CoAP Content-Formats are described in <xref target="tbl-new-cf-proc"/>.</t> <table anchor="tbl-new-cf-proc"><name>CoAP Content-Formats: Registration Procedures</name><name>Registration Procedures for CoAP Content-Formats</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> <thalign="left">Notes</th>align="left">Note</th> </tr> </thead> <tbody> <tr> <td align="left">0-255</td> <td align="left">Expert Review</td> <td align="left">Review procedure described inRFCthis,RFC 9876, <xref target="checks"/>.</td> </tr> <tr> <td align="left">256-9999</td> <td align="left">IETF Review with Expert Review or IESG Approval with Expert Review</td> <td align="left">Review procedure described inRFCthis,RFC 9876, <xref target="checks"/></td> </tr> <tr> <td align="left">10000-19999</td> <td align="left">Expert Review</td> <td align="left">Review procedure described inRFCthis,RFC 9876, <xref target="checks"/>.</td> </tr> <tr> <td align="left">20000-32999</td> <td align="left">First Come FirstServed (FCFS)</td>Served</td> <tdalign="left">FCFSalign="left"><t>FCFS is allowed if theregistration: <br/> *registration has no parameters,and <br/> *the registration has an empty Content Coding,and <br/> *the Media Type is not yet used in this registry, and<br/> *the Media Type is registered (or approved for registration) in the "Media Types" registry <xreftarget="IANA.media-types"/>.</td>target="IANA.media-types"/>.</t> </td> </tr> <tr> <td align="left">33000-64997</td> <td align="left">Expert Review</td> <td align="left">Review procedure described inRFCthis,RFC 9876, <xref target="checks"/>.</td> </tr> <tr> <td align="left">64998-64999</td> <tdalign="left">-</td> <tdalign="left">Reserved for Documentation</td> <td align="left"></td> </tr> <tr> <td align="left">65000-65535</td> <td align="left">Experimental Use</td> <td align="left">No operational use</td> </tr> </tbody> </table> <t>Because the namespace of single-byte identifiers is so small, the IANA policy for additions in the range 0-255 inclusive to the registry is "Expert Review" as described in Section <xref section="4.5"sectionFormat="of" target="BCP26"/>.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> <t>The 256-9999 range has registration procedures requiring "IETF Review with Expert Review" or "IESG Approval with ExpertReview."Review". In particular:</t> <ul spacing="normal"> <li> <t>All assignments according to "IETF Review with Expert Review" are made on an "IETF Review" basis per Section <xref section="4.8"sectionFormat="of" target="BCP26"/>sectionFormat="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref> with "Expert Review" additionally required per Section <xref section="4.5"sectionFormat="of" target="BCP26"/>.sectionFormat="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref>. </t> <t> The procedure for early IANA allocation of"standards trackStandards Track codepoints"points defined in <xref target="RFC7120"/> also applies. When such a procedure is used, IANA will ask theDesignated Expert(s)designated expert(s) to approve the early allocation before registration. In addition, working group chairs are encouraged to consult theExpert(s)expert(s) early during the process outlined in <xref section="3.1" sectionFormat="of" target="RFC7120"/>.</t> </li> <li> <t>All assignments according to "IESG Approval with Expert Review" are made on an "IESG Approval" basis per Section <xref section="4.10"sectionFormat="of" target="BCP26"/>sectionFormat="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref> with "Expert Review" additionally required per Section <xref section="4.5"sectionFormat="of" target="BCP26"/>.</t>sectionFormat="bare" target="RFC8126"/> of <xref target="BCP26">RFC 8126</xref>.</t> </li> </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 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 Coding", 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 requiresExpert Review)"Expert Review") can be requested.</t> <t>The identifiers between 65000 and 65535 inclusive are reserved for experiments. They are not meant for vendor-specific use of any kind and <bcp14>MUST NOT</bcp14> be used in operational deployments.</t> <t>In machine-to-machine (M2M) applications, it is not expected that generic Internet Media Types such as text/plain,application/xmlapplication/xml, or application/octet-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 parse 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+cbor.</t> <section anchor="temporary-content-format-registrations"> <name>Temporary Content-Format Registrations</name> <t>This section clarifies that the "CoAP Content-Formats" registry allows temporary registrations within the0-649980-64997 range.</t> <t>A temporary registration may becreatedcreated, forexampleexample, by an IANA early allocation action <xref target="RFC7120"/>. If the referenced Media Type is provisional (that is, included in theIANA"Provisional Standard MediaType" registryType Registry" <xreftarget="IANA.provisional-standard-media-types"/>)target="IANA.prov-media-types"/>), then a created registration is always temporary.</t> <t>A temporary registration is marked as such by IANA in the corresponding registry entry. Once the required registration procedure (defined in <xref target="tbl-new-cf-proc"/>) for the temporary ID has successfully completed, and the referenced Media Type is included in theIANA Media Types"Media Types" registry <xref target="IANA.media-types"/>, IANA must remove any indication about the temporary nature of the registration so that the entry becomes permanent.</t> <t>If a temporary registration does not successfully complete the registration procedure, IANA must remove the entry and set the Content-Format ID value back to "Unassigned". This mayhappenhappen, forexampleexample, when an Internet-Draft requesting a Content-Format ID is abandoned. If a temporary registration (in any range) refers to a provisional Media Type that is abandoned, IANA must remove the entry and set the Content-Format ID value back to "Unassigned".</t> <t>Note that in the10000-64998 range10000-64997 range, the abandonment of a document requesting a Content-Format ID does not cause an entry to be removed. That is because the required registration procedure for this range does not require completion of any standards process, nor does it require a registering document.</t> <t anchor="expert-review-7120-exemptions">Temporary registrations within 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. Instead, theDesignated Expertsdesignated experts direct IANA to carry out this task.</t> </section> <section anchor="adding-the-media-type-column-to-the-registry"><name>Adding<name>Addition of the Media Type Column to the Registry</name> <t>To assist users of the "CoAP Content-Formats" registry in finding detailed information about the Media Type associated with each CoAP Content-Format, and to ensure that a Media Type exists before a new entry can be registered, IANAis requested to add ahas added the new column "Media Type" to the registry. This new column is placeddirectlyto the right of the existing "Content Type" column.</t> <t>The "Media Type" field for each entry lists the (base) Media Type name 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 theIANA"Provisional Standard MediaType" registryType Registry" <xreftarget="IANA.provisional-standard-media-types"/>.target="IANA.prov-media-types"/>. If a provisional Media Type becomes a permanent Media Type, IANA must update the "Media Type" field in the associated registry entries to ensure the hyperlink directs to the registration information for that Media Type.</t><t>Note that the<t>In a registrationrequest procedure remains unchanged. Arequest, the requester does not need to fill out the "Media Type" field separately, as the necessary information is already provided in the "Content Type" field of the request.</t> </section> <section anchor="checks"> <name>Expert Review Procedure</name> <t>TheDesignated Expert (DE)designated expert is instructed to perform theExpert Review,"Expert Review", as described by the following checklist:</t> <ol spacing="normal" type="1"><li> <t>The combination of Content-Type and Content Coding for which the registration is requested must not be already present in the "CoAP Content-Formats"registry;</t>registry.</t> </li> <li> <t>The Media Type associated with the requested Content-Format musteitherbe either registered in the "Media Types" registry <xref target="IANA.media-types"/> or approved for registration. Alternatively, it may be listed in the "Provisional Standard MediaType" registryType Registry" <xreftarget="IANA.provisional-standard-media-types"/>.target="IANA.prov-media-types"/>. The use of provisional standard Media Types is only permitted for Content-Format identifiers within the ranges of 0-255 and256-9999;</t>256-9999.</t> </li> <li> <t>The optional parameter names must have been defined in association with the Media Type, and any parameter values associated with such parameter names must be aspermitted;</t>permitted.</t> </li> <li> <t>The Content Type must be in the preferred format defined in <xreftarget="preferred-format"/>;</t>target="preferred-format"/>.</t> </li> <li> <t>If a Content Coding is specified, it must exist (or must have been approved for registration) in the "HTTP ContentCoding" registry ofCoding Registry" within the "Hypertext Transfer Protocol (HTTP) Parameters" registry group <xreftarget="IANA.http-parameters"/>.</t>target="IANA.http-params"/>.</t> </li> </ol> <t>For the 0-255 range, in addition to the checks described above, theDEdesignated expert is instructed to also evaluate the requestedcodepointcode point concerning the limited availability of the 1-bytecodepointcode point space. For the ranges 256-9999, 10000-19999, and 33000-64997, a similar criterion may also apply where combinations of Media Type parameters and Content Coding choices consume considerablecodepointcode point space.</t> </section> <section anchor="preferred-format"> <name>Preferred Format for the Content Type Field</name> <t>This section defines the preferred string format for including a requested Content Typeintoin the "CoAP Content-Formats" registry. During the review process, theDesignated Expert(s)designated expert(s) or IANA may rewrite a requested 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> <ol spacing="normal" type="1"><li> <t>For any case-insensitive elements, lowercase characters are used.</t> </li> <li> <t>Parameter values are only quoted if the value is such that it requires 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> </li> <li> <t>A single semicolon character without any adjacent whitespace characters is used as the separator between the Media Type and parameters.</t> </li> </ol> </section> <section anchor="examples-for-invalid-registration-requests"> <name>Examplesforof Invalid Registration Requests</name> <t>This section provides examples of registration requests for the "CoAP Content-Formats"Registryregistry that are invalid but would be approved under the procedure defined in <xref section="12.3" sectionFormat="of" target="RFC7252"/>. The checklist defined in <xref target="checks"/> should prevent any of these attempts from succeeding. These examples serve as a representative, but not exhaustive, sample to train theDE'sdesignated expert's eye on invalid registration attempts.</t> <t>All the example registration requests use two CoAP Content-Format identifiers: 64998 and 64999.</t><t>For<!-- [rfced] Please confirm that "IETF Review or IESG Approval" is correct here. Does this apply to all ranges that require "Expert Review"? 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.Likewise, such registrations must not be allowed to succeed.</t>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"> <name>The Media Type is Unknown</name> <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 Type</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/unknown+cbor</td> <td align="left">-</td> <td align="left">64999</td><td>application/unknown+cbor</td> <td>-</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="the-media-type-parameter-is-unknown"> <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><table align="left"><table> <name>Attempt at Registering Content-Format for a Media Type with an Unknown Parameter</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/cose;unknown-parameter=1</td> <td align="left">-</td> <td align="left">64999</td><td>application/cose;unknown-parameter=1</td> <td>-</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="the-media-type-parameter-value-is-invalid"> <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><table align="left"><table> <name>Attempt at Registering Content-Format for a Media Type with an Invalid Parameter Value</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/cose;cose-type=invalid</td> <td align="left">-</td> <td align="left">64999</td><td>application/cose;cose-type=invalid</td> <td>-</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="the-content-coding-is-unknown"> <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><table align="left"><table> <name>Attempt at Registering Content-Format with Unknown Content Coding</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/senml+cbor</td> <td align="left">inflate</td> <td align="left">64999</td><td>application/senml+cbor</td> <td>inflate</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="duplicate-entry-with-default-media-type-parameters"> <name>Duplicate Entry with Default Media Type Parameters</name> <t>The registrant requests an FCFS Content-Format ID for a Media Type that includes a parameter set to its default value, while a (hypothetical) Content-Format ID 64998 is already registered for this Media Type without that parameter. 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 Different Content-Format ID (1)</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/my</td> <td align="left">-</td> <td align="left">64998</td><td>application/my</td> <td>-</td> <td>64998</td> </tr> <tr><td align="left">application/my;parameter=default</td> <td align="left">-</td> <td align="left">64999</td><td>application/my;parameter=default</td> <td>-</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="duplicate-entry-with-default-content-coding"> <name>Duplicate Entry with Default Content Coding</name> <t>The registrant requests an FCFS Content-Format ID for the "identity" Content Coding, which is the default coding. If accepted, this request would duplicate an entry with (hypothetical) 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 Different Content-Format ID (2)</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/my</td> <td align="left">-</td> <td align="left">64998</td><td>application/my</td> <td>-</td> <td>64998</td> </tr> <tr><td align="left">application/my</td> <td align="left">identity</td> <td align="left">64999</td><td>application/my</td> <td>identity</td> <td>64999</td> </tr> </tbody> </table> </section> <section anchor="duplicate-entry-with-equivalent-parameter"> <name>Duplicate Entry with Equivalent Parameter</name> <t>The registrant requests an FCFS Content-Format ID for a Media Type that includes a parameter. The value of this parameter appears distinct from that of a (hypothetical) previously registered Content-Format ID 64998 that also includes this parameter. However, the semantics of the parameter value are identical to the existing registration.</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"/>. Sincefor URNs,the Namespace Identifier(<tt>example</tt>(see <tt>example</tt> in this example) for URNs is 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 Different Content-Format ID (3)</name> <thead> <tr><th align="left">Content<th>Content Type</th><th align="left">Content<th>Content Coding</th><th align="left">ID</th><th>ID</th> </tr> </thead> <tbody> <tr><td align="left">application/eat+cwt;eat_profile="urn:example:1"</td> <td align="left">-</td> <td align="left">64998</td><td>application/eat+cwt;eat_profile="urn:example:1"</td> <td>-</td> <td>64998</td> </tr> <tr><td align="left">application/eat+cwt;eat_profile="urn:EXAMPLE:1"</td> <td align="left">-</td> <td align="left">64999</td><td>application/eat+cwt;eat_profile="urn:EXAMPLE:1"</td> <td>-</td> <td>64999</td> </tr> </tbody> </table> </section> </section> </section> <sectionanchor="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 document is approved for publication. RFC-Editor: please remove this section once the note has been removed.</t> </section> <sectionanchor="new-note-add"> <name>New NoteAddition</name> <t><cref anchor="replace-self_1">RFC Editor: in this section, please replace RFCthis with the RFC number assigned to this documentandremove this note.</cref></t>Reference Additions</name> <t>IANAis instructed to addhas added the following note to the registry:</t><ul empty="true"> <li> <t>"Note:<blockquote><t>Note: As perRFCthis,RFC 9876, temporary registrations within the 0-255 range are approved byDesignated Experts.designated experts. These registrations are not subject to the formal<xref target="RFC7120"/>renewalprocess."</t> </li> </ul>process in <xref target="RFC7120"/>.</t></blockquote> <t> IANA has also listed this document as an additional reference for the registry. </t> </section> <section anchor="reserve-64999"> <name>Reserving Content-Format Identifiers 64998 and 64999 for Documentation</name> <t>IANAis instructed to reservehas reserved Content-Format identifiers 64998 and 64999 for use in documentation.</t> </section> </section> </middle> <back> <references anchor="sec-combined-references"> <name>References</name> <references anchor="sec-normative-references"> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7120.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7252.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9193.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.0026.xml"/> <referenceanchor="RFC7120"> <front> <title>Early IANA Allocation of Standards Track Code Points</title> <author fullname="M. Cotton" initials="M." surname="Cotton"/> <date month="January" year="2014"/> <abstract> <t>This memo describes the process for early allocation of code points by IANA from registries for which "Specification Required", "RFC Required", "IETF Review", or "Standards Action" policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC, which would normally trigger code point allocation. The procedures in this 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 web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless 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-machine (M2M) applications such as smart energy and building automation.</t> <t>CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity 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="Reschke"/> <date month="June" year="2022"/> <abstract> <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, 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, 7232, 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 Value 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 multiple types of values, from numbers to text strings and arbitrary binary Data Values. In order to facilitate processing of binary Data Values, this document specifies 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 any 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 constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations 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 describing the conditions under which new values should be assigned, as well as when 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 Considerations 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 5226.</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"anchor="IANA.core-params" target="https://www.iana.org/assignments/core-parameters"> <front> <title>Constrained RESTful Environments (CoRE) Parameters</title> <author> <organization>IANA</organization> </author> </front> </reference> <reference anchor="IANA.media-types" target="https://www.iana.org/assignments/media-types"> <front> <title>Media Types</title> <author> <organization>IANA</organization> </author> </front> </reference> <referenceanchor="IANA.http-parameters"anchor="IANA.http-params" target="https://www.iana.org/assignments/http-parameters"> <front> <title>Hypertext Transfer Protocol (HTTP) Parameters</title> <author> <organization>IANA</organization> </author> </front> </reference> <referenceanchor="IANA.provisional-standard-media-types"anchor="IANA.prov-media-types" target="https://www.iana.org/assignments/provisional-standard-media-types"> <front> <title>Provisional Standard Media Type Registry</title> <author> <organization>IANA</organization> </author> </front> </reference><reference anchor="RFC2119"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <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 signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, 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</title> <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 protocol 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><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> </references> <references anchor="sec-informative-references"> <name>Informative References</name> <reference anchor="Err4954"target="https://www.rfc-editor.org/errata/eid4954" quoteTitle="false">quote-title="false" target="https://www.rfc-editor.org/errata/eid4954"> <front><title>RFC Errata Report<title>Erratum ID 4954</title> <author><organization/><organization>RFC Errata</organization> </author><date/> </front> <seriesInfo name="RFC" value="7252"/> </reference> <reference anchor="RFC2046"> <front> <title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title> <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 resource identifier. With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance. With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and it describes procedures for registering 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"/><refcontent>RFC 7252</refcontent> </reference> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2046.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml"/> </references> </references><?line 336?><section numbered="false" anchor="acknowledgments"> <name>Acknowledgments</name> <t>Thank youAmanda Baber, Carsten Bormann, Christer Holmberg, Éric Vyncke, Francesca Palombini, Ketan Talaulikar, Marco Tiloca, Mohamed Boucadair, Paul Wouters, Renzo Navas, and Rich Salz<contact fullname="Amanda Baber"/>, <contact fullname="Carsten Bormann"/>, <contact fullname="Christer Holmberg"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Francesca Palombini"/>, <contact fullname="Ketan Talaulikar"/>, <contact fullname="Marco Tiloca"/>, <contact fullname="Mohamed Boucadair"/>, <contact fullname="Paul Wouters"/>, <contact fullname="Renzo Navas"/>, and <contact fullname="Rich Salz"/> for your reviews, comments, suggestions, and fixes.</t> </section> </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>