6. IANA Considerations
6.1. Media Type
Media types are registered in the "Media Types" registry [IANA-MEDIA-TYPES]. IANA has registered the media type for CBOR Sequence, application/cbor-seq, as follows:
Type name: application
Subtype name: cbor-seq
Required parameters: N/A
Optional parameters: N/A
Encoding considerations: binary
Security considerations: See RFC 8742, Section 5.
Interoperability considerations: Described herein.
Published specification: RFC 8742.
Applications that use this media type: Data serialization and deserialization.
Fragment identifier considerations: N/A
Additional information:
-
Deprecated alias names for this type: N/A
-
Magic number(s): N/A
-
File extension(s): N/A
-
Macintosh file type code(s): N/A
Person & email address to contact for further information: [email protected]
Intended usage: COMMON
Author: Carsten Bormann ([email protected])
Change controller: IETF
6.2. CoAP Content-Format Registration
IANA has assigned a CoAP Content-Format ID for the media type "application/cbor-seq", within the "CoAP Content-Formats" subregistry of the "Constrained RESTful Environments (CoRE) Parameters" registry [IANA-CORE-PARAMETERS], from the "Expert Review" (0-255) range ([RFC8126]). The assigned ID is shown in Table 1.
| Media type | Encoding | ID | Reference |
|---|---|---|---|
| application/cbor-seq | - | 63 | RFC 8742 |
Table 1: CoAP Content-Format ID
6.3. Structured Syntax Suffix
Structured Syntax Suffixes are registered within the "Structured Syntax Suffix Registry" maintained at [IANA-STRUCTURED-SYNTAX-SUFFIX]. IANA has registered the "+cbor-seq" structured syntax suffix in accordance with [RFC6838] as follows:
Name: CBOR Sequence
+suffix: +cbor-seq
References: RFC 8742
Encoding considerations: binary
Fragment identifier considerations: The syntax and semantics of fragment identifiers specified for +cbor-seq SHOULD be the same as that specified for "application/cbor-seq". (At the time of publication of this document, there is no fragment identification syntax defined for "application/cbor-seq".)
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+cbor-seq" SHOULD be processed as follows:
o For cases defined in +cbor-seq, if the fragment identifier resolves per the +cbor-seq rules, then process as specified in +cbor-seq.
o For cases defined in +cbor-seq, if the fragment identifier does not resolve per the +cbor-seq rules, then process as specified in "xxx/yyy+cbor-seq".
o For cases not defined in +cbor-seq, process as specified in "xxx/yyy+cbor-seq".
Interoperability considerations: n/a
Security considerations: See RFC 8742, Section 5
Contact: CBOR WG mailing list ([email protected]), or any IESG-designated successor.
Author/Change controller: IETF