'resource-type': A required field used to indicate the resource type of the topic-data resource for the topic. It encodes the resource type as a CBOR text string. The value should be "core.ps.conf".¶
'media-type': An optional field used to indicate the media type of the topic-data resource for the topic. It encodes the media type as a this information as the integer identifier of the CoAP content format (e.g., value is "50" for "application/json").¶
+'media-type': An optional field used to indicate the media type of the topic-data resource for the topic. It encodes the media type as a this information as the integer identifier of the CoAP content-format (e.g., value is "50" for "application/json").¶
'topic-type': An optional field used to indicate the attribute or property of the topic-data resource for the topic. It encodes the attribute as a CBOR text string. Example attributes include "temperature".¶
@@ -2149,7 +2149,7 @@A topic-configuration with a topic-data resource must have been created in order to publish data to it (See Section 2.4.3) and be in the half-created or fully-created state in order to the publish operation to work (see Section 3.1).¶
A client can publish data to a topic by submitting the data in a PUT request to the topic-data URI as indicated in its topic resource property. Please note that the topic-data URI is not the same as the topic-configuration URI used for configuring the topic (see Section 2.2).¶
On success, the server returns a 2.04 (Updated) response. However, when data is published to the topic for the first time, the server instead MUST return a 2.01 (Created) response and set the topic in the fully-created state (see Section 3.1).¶
-If the request does not have an acceptable content format, the server returns a 4.15 (Unsupported Content Format) response.¶
+If the request does not have an acceptable content-format, the server returns a 4.15 (Unsupported Content-Format) response.¶
If the client is sending publications too fast, the server returns a 4.29 (Too Many Requests) response [RFC8516].¶
Example of first publication:¶
@@ -2338,18 +2338,18 @@-+-----------------+-----------+--------------+------------+ -| Name | CBOR Key | CBOR Type | Reference | -|-----------------|-----------|--------------|------------| -| topic-name | TBD1 | tstr | [RFC-XXXX] | -| topic-data | TBD2 | tstr | [RFC-XXXX] | -| resource-type | TBD3 | tstr | [RFC-XXXX] | -| media-type | TBD4 | uint (opt) | [RFC-XXXX] | -| topic-type | TBD5 | tstr (opt) | [RFC-XXXX] | -| expiration-date | TBD6 | tstr (opt) | [RFC-XXXX] | -| max-subscribers | TBD7 | uint (opt) | [RFC-XXXX] | -| observer-check | TBD8 | uint (opt) | [RFC-XXXX] | -+-----------------+-----------+--------------+------------+ ++-----------------+-----------+-----------+------------+ +| Name | CBOR Key | CBOR Type | Reference | +|-----------------|-----------|-----------|------------| +| topic-name | TBD1 | tstr | [RFC-XXXX] | +| topic-data | TBD2 | tstr | [RFC-XXXX] | +| resource-type | TBD3 | tstr | [RFC-XXXX] | +| media-type | TBD4 | uint | [RFC-XXXX] | +| topic-type | TBD5 | tstr | [RFC-XXXX] | +| expiration-date | TBD6 | tstr | [RFC-XXXX] | +| max-subscribers | TBD7 | uint | [RFC-XXXX] | +| observer-check | TBD8 | uint | [RFC-XXXX] | ++-----------------+-----------+-----------+------------+
Clients and servers in the Internet of Things¶
+This type is used by clients that create, retrieve, and update topic configurations at servers acting as a pub-sub broker.¶
The syntax and semantics of fragment identifiers is as specified for -"application/cbor". (At publication of RFC XXXX, there is no -fragment identification syntax defined for "application/cbor".)¶
+N/A¶
IANA has added the following Content-Formats to the "CoAP Content-Formats" @@ -2506,7 +2504,7 @@
TBD9 is to be assigned from the space 256..999.¶
-In the registry the column "Content-Type" is called "Media type" and the -column "Content Coding" is called "Encoding". This paragraph to be removed by RFC editor.¶
IANA is asked to register the following entries in the subregistry of the "Constrained RESTful Environments (CoRE) Parameters" registry group.¶
-The registry is initially populated with the entries in Figure 5 of Section 4.¶
+This specification establishes the "Pubsub Topic Configuration Parameters" IANA registry within the "Constrained RESTful Environments (CoRE) +Parameters" registry group.¶
+The columns of this registry are:¶
+Name: This is a descriptive name that enables easier reference to the item. The name MUST be unique. It is not used in the encoding.¶
+CBOR Key: This is the value used as CBOR key of the item. These values MUST be unique. The value can be a positive integer, a negative integer, or a text string. Different ranges of values use different registration policies [RFC8126]. Integer values from -256 to 255 as well as text strings of length 1 are designated as "Standards Action With Expert Review". Integer values from -65536 to -257 and from 256 to 65535, as well as text strings of length 2 are designated as "Specification Required". Integer values greater than 65535 as well as text strings of length greater than 2 are designated as "Expert Review". Integer values less than -65536 are marked as "Private Use".¶
+CBOR Type: This contains the CBOR type of the item, or a pointer to the registry that defines its type, when that depends on another item.¶
+Reference: This contains a pointer to the public specification for the item.¶
+The registry is initially populated with the entries in Figure 5 of Section 4.¶
Marco provided thorough reviews and guidance on the last versions of this document.¶
+Marco provided very thorough reviews and guidance on the last versions of this document.¶