rfc9876v2.txt | rfc9876.txt | |||
---|---|---|---|---|
skipping to change at line 78 ¶ | skipping to change at line 78 ¶ | |||
Authors' Addresses | Authors' Addresses | |||
1. Introduction | 1. Introduction | |||
Section 12.3 of [RFC7252] describes the registration procedures for | Section 12.3 of [RFC7252] describes the registration procedures for | |||
the "CoAP Content-Formats" IANA registry within the "Constrained | the "CoAP Content-Formats" IANA registry within the "Constrained | |||
RESTful Environments (CoRE) Parameters" registry group | RESTful Environments (CoRE) Parameters" registry group | |||
[IANA.core-params]. (Note that the columns of this registry have | [IANA.core-params]. (Note that the columns of this registry have | |||
been revised according to [Err4954].) In particular, it defines the | been revised according to [Err4954].) In particular, it defines the | |||
rules for obtaining Constrained Application Protocol (CoAP) Content- | rules for obtaining Constrained Application Protocol (CoAP) Content- | |||
Format identifiers from the "IETF Review with Expert Review or IESG | Format identifiers from the "IETF Review or IESG Approval" range of | |||
Approval with Expert Review" range of the registry (256-9999) as well | the registry (256-9999) as well as from the "First Come First Served" | |||
as from the "First Come First Served" (FCFS) range of the registry | (FCFS) range of the registry (10000-64999). For the FCFS range, | |||
(10000-64999). For the FCFS range, these rules do not involve the | these rules do not involve the designated expert and are managed | |||
designated expert and are managed solely by IANA personnel to | solely by IANA personnel to finalize the registration. | |||
finalize the registration. | ||||
Unfortunately, the rules do not explicitly require checking that the | Unfortunately, the rules do not explicitly require checking that the | |||
combination of Content-Type (i.e., Media Type with optional | combination of Content-Type (i.e., Media Type with optional | |||
parameters) and Content Coding associated with the requested CoAP | parameters) and Content Coding associated with the requested CoAP | |||
Content-Format is semantically valid. This task is generally non- | Content-Format is semantically valid. This task is generally non- | |||
trivial, requires knowledge from multiple documents and technologies, | trivial, requires knowledge from multiple documents and technologies, | |||
and should not be solely demanded from the registrar. This lack of | and should not be solely demanded from the registrar. This lack of | |||
guidance may engender confusion in both the registering party and the | guidance may engender confusion in both the registering party and the | |||
registrar, and it has already led to erroneous registrations. | registrar, and it has already led to erroneous registrations. | |||
skipping to change at line 491 ¶ | skipping to change at line 490 ¶ | |||
The registrant requests an FCFS Content-Format ID for a Media Type | The registrant requests an FCFS Content-Format ID for a Media Type | |||
that includes a parameter. The value of this parameter appears | that includes a parameter. The value of this parameter appears | |||
distinct from that of a (hypothetical) previously registered Content- | distinct from that of a (hypothetical) previously registered Content- | |||
Format ID 64998 that also includes this parameter. However, the | Format ID 64998 that also includes this parameter. However, the | |||
semantics of the parameter value are identical to the existing | semantics of the parameter value are identical to the existing | |||
registration. | registration. | |||
In this example, the eat_profile parameter value (which can be any | In this example, the eat_profile parameter value (which can be any | |||
URI) is set as a Uniform Resource Name (URN) [RFC8141]. Since the | URI) is set as a Uniform Resource Name (URN) [RFC8141]. Since the | |||
Namespace Identifier (see example in this example) for URNs is | Namespace Identifier (example, in this case) for URNs is defined as | |||
defined as case insensitive, the two registrations are semantically | case insensitive, the two registrations are semantically identical. | |||
identical. | ||||
+=====================================+================+=======+ | +=====================================+================+=======+ | |||
| Content Type | Content Coding | ID | | | Content Type | Content Coding | ID | | |||
+=====================================+================+=======+ | +=====================================+================+=======+ | |||
| application/ | - | 64998 | | | application/ | - | 64998 | | |||
| eat+cwt;eat_profile="urn:example:1" | | | | | eat+cwt;eat_profile="urn:example:1" | | | | |||
+-------------------------------------+----------------+-------+ | +-------------------------------------+----------------+-------+ | |||
| application/ | - | 64999 | | | application/ | - | 64999 | | |||
| eat+cwt;eat_profile="urn:EXAMPLE:1" | | | | | eat+cwt;eat_profile="urn:EXAMPLE:1" | | | | |||
+-------------------------------------+----------------+-------+ | +-------------------------------------+----------------+-------+ | |||
End of changes. 2 change blocks. | ||||
9 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |