draft-ietf-core-senml-etch-07.txt   rfc8790.txt 
Network Working Group A. Keranen Internet Engineering Task Force (IETF) A. Keränen
Internet-Draft Ericsson Request for Comments: 8790 Ericsson
Intended status: Standards Track M. Mohajer Category: Standards Track M. Mohajer
Expires: September 10, 2020 March 9, 2020 ISSN: 2070-1721 June 2020
FETCH & PATCH with Sensor Measurement Lists (SenML) FETCH and PATCH with Sensor Measurement Lists (SenML)
draft-ietf-core-senml-etch-07
Abstract Abstract
The Sensor Measurement Lists (SenML) media type and data model can be The Sensor Measurement Lists (SenML) media type and data model can be
used to send collections of resources, such as batches of sensor data used to send collections of resources, such as batches of sensor data
or configuration parameters. The CoAP FETCH, PATCH, and iPATCH or configuration parameters. The Constrained Application Protocol
methods enable accessing and updating parts of a resource or multiple (CoAP) FETCH, PATCH, and iPATCH methods enable accessing and updating
resources with one request. This document defines new media types parts of a resource or multiple resources with one request. This
for the CoAP FETCH, PATCH, and iPATCH methods for resources document defines new media types for the CoAP FETCH, PATCH, and
represented with the SenML data model. iPATCH methods for resources represented using the SenML data model.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on September 10, 2020. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8790.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology
3. Using FETCH and (i)PATCH with SenML . . . . . . . . . . . . . 3 3. Using FETCH and (i)PATCH with SenML
3.1. SenML FETCH . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. SenML FETCH
3.2. SenML (i)PATCH . . . . . . . . . . . . . . . . . . . . . 5 3.2. SenML (i)PATCH
4. Fragment Identification . . . . . . . . . . . . . . . . . . . 7 4. Fragment Identification
5. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Extensibility
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations
7.1. CoAP Content-Format Registration . . . . . . . . . . . . 8 7.1. CoAP Content-Format Registration
7.2. senml-etch+json Media Type . . . . . . . . . . . . . . . 8 7.2. senml-etch+json Media Type
7.3. senml-etch+cbor Media Type . . . . . . . . . . . . . . . 9 7.3. senml-etch+cbor Media Type
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 8. References
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References
9.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.2. Informative References
9.2. Informative References . . . . . . . . . . . . . . . . . 11 Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses
1. Introduction 1. Introduction
The Sensor Measurement Lists (SenML) media type [RFC8428] and data The Sensor Measurement Lists (SenML) media type [RFC8428] and data
model can be used to transmit collections of resources, such as model can be used to transmit collections of resources, such as
batches of sensor data or configuration parameters. batches of sensor data or configuration parameters.
An example of a SenML collection is shown below: An example of a SenML collection is shown below:
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true}, {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true},
{"n":"5851", "v":42}, {"n":"5851", "v":42},
{"n":"5750", "vs":"Ceiling light"} {"n":"5750", "vs":"Ceiling light"}
] ]
Here three resources "3311/0/5850", "3311/0/5851", and "3311/0/5750", Here, three resources, "3311/0/5850", "3311/0/5851", and
of an IPSO dimmable light smart object [IPSO] are represented using a "3311/0/5750", of a dimmable light smart object [IPSO] are
single SenML Pack with three SenML Records. All resources share the represented using a single SenML Pack with three SenML Records. All
same base name "2001:db8::2/3311/0/", hence full names for resources resources share the same base name "2001:db8::2/3311/0/"; hence, full
are "2001:db8::2/3311/0/5850", etc. names for the resources are "2001:db8::2/3311/0/5850", etc.
The CoAP [RFC7252] FETCH, PATCH, and iPATCH methods [RFC8132] enable The CoAP [RFC7252] FETCH, PATCH, and iPATCH methods [RFC8132] enable
accessing and updating parts of a resource or multiple resources with accessing and updating parts of a resource or multiple resources with
one request. one request.
This document defines two new media types, one using the JavaScript This document defines two new media types, one using the JavaScript
Object Notation (JSON) [RFC8259] and one using the Concise Binary Object Notation (JSON) [RFC8259] and one using the Concise Binary
Object Representation (CBOR) [RFC7049], which can be used with the Object Representation (CBOR) [RFC7049], which can be used with the
CoAP FETCH, PATCH, and iPATCH methods for resources represented with CoAP FETCH, PATCH, and iPATCH methods for resources represented using
the SenML data model (i.e., for both SenML and Sensor Streaming the SenML data model (i.e., for both SenML and Sensor Streaming
Measurement Lists (SenSML) data). The rest of the document uses term Measurement Lists (SenSML) data). The rest of the document uses the
"(i)PATCH" when referring to both methods as the semantics of the new term "(i)PATCH" when referring to both methods as the semantics of
media types are the same for the CoAP PATCH and iPATCH methods. the new media types are the same for the CoAP PATCH and iPATCH
methods.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Readers should also be familiar with the terms and concepts discussed Readers should also be familiar with the terms and concepts discussed
in [RFC8132] and [RFC8428]. The following additional terms are used in [RFC8132] and [RFC8428]. The following additional terms are used
in this document: in this document:
Fetch Record: One set of parameters that is used to match SenML Fetch Record: One set of parameters that is used to match SenML
Record(s). Record(s).
Fetch Pack: One or more Fetch Records in an array structure. Fetch Pack: One or more Fetch Records in an array structure.
skipping to change at page 3, line 44 skipping to change at line 132
Patch Pack: One or more Patch Records in an array structure. Patch Pack: One or more Patch Records in an array structure.
Target Record: A Record in a SenML Pack that matches the selection Target Record: A Record in a SenML Pack that matches the selection
criteria of a Fetch or Patch Record and hence is a target for a criteria of a Fetch or Patch Record and hence is a target for a
Fetch or Patch operation. Fetch or Patch operation.
Target Pack: A SenML Pack that is a target for a Fetch or Patch Target Pack: A SenML Pack that is a target for a Fetch or Patch
operation. operation.
(i)PATCH: A term that refers to both CoAP "PATCH" and "iPATCH" (i)PATCH: A term that refers to both CoAP "PATCH" and "iPATCH"
methods when there is no difference in this specification in which methods when there is no difference in this specification as to
one is used. which one is used.
3. Using FETCH and (i)PATCH with SenML 3. Using FETCH and (i)PATCH with SenML
The FETCH/(i)PATCH media types for SenML are modeled as extensions to The FETCH/(i)PATCH media types for SenML are modeled as extensions to
the SenML media type to enable re-use of existing SenML parsers and the SenML media type to enable reuse of existing SenML parsers and
generators, in particular on constrained devices. Unless mentioned generators, in particular on constrained devices. Unless mentioned
otherwise, FETCH and PATCH Packs are constructed with the same rules otherwise, FETCH and PATCH Packs are constructed with the same rules
and constraints as SenML Packs. and constraints as SenML Packs.
The key differences to the SenML media type are allowing the use of a The key differences from the SenML media type are allowing the use of
"null" value for removing records with the (i)PATCH method and lack a "null" value for removing Records with the (i)PATCH method and the
of value fields in Fetch Records. Also the Fetch and Patch Records lack of value fields in Fetch Records. Also, the Fetch and Patch
do not have default time or base version when the fields are omitted. Records do not have a default time or base version when the fields
are omitted.
3.1. SenML FETCH 3.1. SenML FETCH
The FETCH method can be used to select and return a subset of The FETCH method can be used to select and return a subset of
records, in sequence, of one or more SenML Packs. The SenML Records Records, in sequence, of one or more SenML Packs. The SenML Records
are selected by giving a set of names that, when resolved, match are selected by giving a set of names that, when resolved, match
resolved names in a Target SenML Pack. The names for a Fetch Pack resolved names in a Target SenML Pack. The names for a Fetch Pack
are given using the SenML "name" and/or "base name" fields. The are given using the SenML "name" and/or "base name" fields. The
names are resolved by concatenating the base name with the name field names are resolved by concatenating the base name with the name field
as defined in [RFC8428]. as defined in [RFC8428].
A Fetch Pack MUST contain at least one Fetch Record. A Fetch Record A Fetch Pack MUST contain at least one Fetch Record. A Fetch Record
MUST contain a name and/or a base name field. MUST contain a name and/or base name field.
For example, to select the IPSO resources "5850" and "5851" from the For example, to select the resources "5850" and "5851" from the
example in Section 1, the following Fetch Pack can be used: example in Section 1, the following Fetch Pack can be used:
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850"}, {"bn":"2001:db8::2/3311/0/", "n":"5850"},
{"n":"5851"} {"n":"5851"}
] ]
The result to a FETCH request with the example above would be: The result of a FETCH request with the example above would be:
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true}, {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":true},
{"n":"5851", "v":42}, {"n":"5851", "v":42},
] ]
The SenML time and unit fields can be used in a Fetch Record to The SenML time and unit fields can be used in a Fetch Record to
further narrow the selection of matched SenML Records. When no time further narrow the selection of matched SenML Records. When no time
or unit is given in a Fetch Record, all SenML Records with the given or unit is given in a Fetch Record, all SenML Records with the given
name are matched (i.e., unlike with SenML Records, lack of time field name are matched (i.e., unlike with SenML Records, the lack of time
in a Fetch Record does not imply time value zero). When time is field in a Fetch Record does not imply a time value of zero). When
given in the Fetch Record, only the SenML Records (if any) with equal time is given in the Fetch Record, a Target Record is matched only
resolved time value and name are matched. Similarly, when unit is when its resolved time value and name are equal to those of the Fetch
given, only the SenML Records with equal resolved unit and name are Record. Similarly, when unit is given, a Target Record is matched
matched. If both time and unit are given in the Fetch Record, both only when its resolved unit and name are equal to those of the Fetch
MUST to match for the SenML Record to match. Each Target Record MUST Record. If both the time and unit are given in the Fetch Record, a
be included in the response at most once, even if multiple Fetch Target Record is matched only when both are equal to those of the
Records match with the same Target Record. Fetch Record. Each Target Record MUST be included in the response at
most once, even if multiple Fetch Records match with the same Target
Record.
For example, if the IPSO resource "5850" would have multiple sensor For example, if the resource "5850" had multiple sensor readings
readings (SenML Records) with different time values, the following (SenML Records) with different time values, the following Fetch Pack
Fetch Pack can be used to retrieve the Record with time can be used to retrieve the Record with time "1.276020091e+09":
"1.276020091e+09":
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850", "t":1.276020091e+09} {"bn":"2001:db8::2/3311/0/", "n":"5850", "t":1.276020091e+09}
] ]
The resolved form of records (Section 4.6 of [RFC8428]) is used when The resolved form of Records (Section 4.6 of [RFC8428]) is used when
comparing the names, times, and units of the Target and Fetch Records comparing the names, times, and units of the Target and Fetch Records
to accommodate for differences in use of the base values. In to accommodate differences in the use of the base values. In the
resolved form the SenML name in the example above becomes resolved form, the SenML name in the example above becomes
"2001:db8::2/3311/0/5850". Since there is no base time in the Pack, "2001:db8::2/3311/0/5850". Since there is no base time in the Pack,
the time in resolved form is equal to the time in the example. the time in resolved form is equal to the time in the example.
If no SenML Records match, empty SenML Pack (i.e., array with no If no SenML Records match, an empty SenML Pack (i.e., array with no
elements) is returned as a response. elements) is returned as a response.
Fetch Records MUST NOT contain other fields than name, base name, Fetch Records MUST NOT contain other fields than name, base name,
time, base time, unit, and base unit. Implementations MUST reject time, base time, unit, and base unit. Implementations MUST reject
and generate an error for a Fetch Pack with other fields. [RFC8132] and generate an error for a Fetch Pack with other fields. [RFC8132],
Section 2.2 provides guidance for FETCH request error handling, e.g., Section 2.2 provides guidance for FETCH request error handling, e.g.,
using the 4.22 (Unprocessable Entity) CoAP error response code. using the 4.22 (Unprocessable Entity) CoAP error response code.
3.2. SenML (i)PATCH 3.2. SenML (i)PATCH
The (i)PATCH method can be used to change the fields of SenML The (i)PATCH method can be used to change the fields of SenML
Records, to add new Records, and to remove existing Records. The Records, to add new Records, and to remove existing Records. The
names, times, and units of the Patch Records are given and matched in names, times, and units of the Patch Records are given and matched in
same way as for the Fetch Records, except each Patch Record MUST the same way as for the Fetch Records, except each Patch Record MUST
match at most one Target Record. A Patch Record matching more than match at most one Target Record. A Patch Record matching more than
one Target Record is considered invalid (patching multiple Target one Target Record is considered invalid (patching multiple Target
Records with one Patch Record would result in multiple copies of the Records with one Patch Record would result in multiple copies of the
same record). Patch Packs can also include new values and other same Record). Patch Packs can also include new values and other
SenML fields for the Records. Application of Patch Packs is SenML fields for the Records. Application of Patch Packs is
idempotent; hence PATCH and iPATCH methods for SenML Packs are idempotent; hence, the PATCH and iPATCH methods for SenML Packs are
equivalent. equivalent.
When the name in a Patch Record matches with the name in an existing When the name in a Patch Record matches with the name in an existing
Record, the resolved time values and units (if any) are compared. If Record, the resolved time values and units (if any) are compared. If
the time values and units either do not exist in both Records or are the time values and units either do not exist in both Records or are
equal, the Target Record is replaced with the contents of the Patch equal, the Target Record is replaced with the contents of the Patch
Record. All Patch Records MUST contain at least a SenML Value or Sum Record. All Patch Records MUST contain at least a SenML Value or Sum
field. field.
If a Patch Record contains a name, or combination of a time value, If a Patch Record contains a name, or the combination of a time
unit, and a name, that do not exist in any existing Record in the value, unit, and name, that does not exist in any existing Record in
Pack, the given Record, with all the fields it contains, is added to the Pack, the given Record, with all the fields it contains, is added
the Pack. to the Pack.
If a Patch Record has a value ("v") field with value null, it MUST If a Patch Record has a value ("v") field with a null value, it MUST
NOT be added but the matched Record (if any) is removed from the NOT be added, but the matched Record (if any) is removed from the
Target Pack. Target Pack.
The Patch Records MUST be applied in the same sequence they are in The Patch Records MUST be applied in the same sequence as they are in
the Patch Pack. If multiple Patch Packs are being processed at the the Patch Pack. If multiple Patch Packs are being processed at the
same time, the result MUST be equivalent to applying them in one same time, the result MUST be equivalent to applying them in one
sequence. sequence.
Implementations MUST reject and generate an error for Patch Packs Implementations MUST reject and generate an error for Patch Packs
with invalid Records. If a Patch Pack is rejected, the state of the with invalid Records. If a Patch Pack is rejected, the state of the
Target Pack is not changed, i.e., either all or none of the Patch Target Pack is not changed, i.e., either all or none of the Patch
Records are applied. [RFC8132] Section 3.4 provides guidance for Records are applied. [RFC8132], Section 3.4 provides guidance for
error handling with PATCH and iPATCH requests, e.g., using the 4.22 error handling with PATCH and iPATCH requests, e.g., using the 4.22
(Unprocessable Entity) and 4.09 (Conflict) CoAP error response codes. (Unprocessable Entity) and 4.09 (Conflict) CoAP error response codes.
For example, the following document could be given as an (i)PATCH For example, the following document could be given as an (i)PATCH
payload to change/set values of two SenML Records for the example in payload to change/set the values of two SenML Records for the example
Section 1: in Section 1:
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":false}, {"bn":"2001:db8::2/3311/0/", "n":"5850", "vb":false},
{"n":"5851", "v":10} {"n":"5851", "v":10}
] ]
If the request is successful, the resulting representation of the If the request is successful, the resulting representation of the
example SenML Pack would be as follows: example SenML Pack would be as follows:
[ [
skipping to change at page 7, line 9 skipping to change at line 288
[ [
{"bn":"2001:db8::2/3311/0/", "n":"5850", "v":null}, {"bn":"2001:db8::2/3311/0/", "n":"5850", "v":null},
{"n":"5851", "v":null} {"n":"5851", "v":null}
] ]
4. Fragment Identification 4. Fragment Identification
Fragment identification for Records of Fetch and Patch Packs uses the Fragment identification for Records of Fetch and Patch Packs uses the
same mechanism as SenML JSON/CBOR fragment identification (see same mechanism as SenML JSON/CBOR fragment identification (see
Section 9 of [RFC8428]), i.e., "rec" scheme followed by a comma- Section 9 of [RFC8428]), i.e., the "rec" scheme followed by a comma-
separated list of Record positions or range(s) of Records. For separated list of Record positions or range(s) of Records. For
example, to select the 3rd and 5th Record of a Fetch or Patch Pack, a example, to select the 3rd and 5th Record of a Fetch or Patch Pack, a
fragment identifier "rec=3,5" can be used in the URI of the Fetch or fragment identifier "rec=3,5" can be used in the URI of the Fetch or
Patch Pack resource. Patch Pack resource.
5. Extensibility 5. Extensibility
The SenML mandatory to understand fields extensibility mechanism (see The SenML mandatory-to-understand field extensibility mechanism (see
section 4.4 in [RFC8428]) does not apply to Patch Packs, i.e., Section 4.4 of [RFC8428]) does not apply to Patch Packs, i.e.,
unknown fields MUST NOT generate an error but such fields are treated unknown fields MUST NOT generate an error, but such fields are
like any other field (e.g., added to Patch target records where treated like any other field (e.g., added to Patch target Records
applicable). where applicable).
This specification allows only a small subset of SenML fields in This specification allows only a small subset of SenML fields in
Fetch Records but future specifications may enable new fields for Fetch Records, but future specifications may enable new fields for
Fetch Records and possibly also new fields for selecting targets for Fetch Records and possibly also new fields for selecting targets for
Patch Records. Patch Records.
6. Security Considerations 6. Security Considerations
The security and privacy considerations of SenML apply also with the The security and privacy considerations of SenML also apply to the
FETCH and (i)PATCH methods. CoAP's security mechanisms are used to FETCH and (i)PATCH methods. CoAP's security mechanisms are used to
provide security for the FETCH and (i)PATCH methods. provide security for the FETCH and (i)PATCH methods.
In FETCH and (i)PATCH requests, the client can pass arbitrary names In FETCH and (i)PATCH requests, the client can pass arbitrary names
to the target resource for manipulation. The resource implementer to the target resource for manipulation. The resource implementer
must take care to only allow access to names that are actually part must take care to only allow access to names that are actually part
of (or accessible through) the target resource. In particular the of (or accessible through) the target resource. In particular, the
receiver needs to ensure that any input does not lead to uncontrolled receiver needs to ensure that any input does not lead to uncontrolled
special interpretation by the system. special interpretation by the system.
If the client is not allowed to do a GET or PUT on the full target If the client is not allowed to do a GET or PUT on the full target
resource (and thus all the names accessible through it), access resource (and thus all the names accessible through it), access
control rules must be evaluated for each record in the pack. control rules must be evaluated for each Record in the Pack.
7. IANA Considerations 7. IANA Considerations
This document registers two new media types and CoAP Content-Format This document registers two new media types and CoAP Content-Format
IDs for both media types. IDs for both media types.
Note to RFC Editor: Please replace all occurrences of "RFC-AAAA" with
the RFC number of this document.
7.1. CoAP Content-Format Registration 7.1. CoAP Content-Format Registration
IANA is requested to assign CoAP Content-Format IDs for the SenML IANA has assigned CoAP Content-Format IDs for the SenML PATCH and
PATCH and FETCH media types in the "CoAP Content-Formats" sub- FETCH media types in the "CoAP Content-Formats" subregistry, within
registry, within the "CoRE Parameters" registry [RFC7252]. The the "Constrained RESTful Environments (CoRE) Parameters" registry
assigned IDs are shown in Table 1. [RFC7252]. The assigned IDs are shown in Table 1.
+-----------------------------+----------+---------+ +=============================+==========+=====+
| Media type | Encoding | ID | | Media Type | Encoding | ID |
+-----------------------------+----------+---------+ +=============================+==========+=====+
| application/senml-etch+json | - | TBD-320 | | application/senml-etch+json | - | 320 |
| | | | +-----------------------------+----------+-----+
| application/senml-etch+cbor | - | TBD-322 | | application/senml-etch+cbor | - | 322 |
+-----------------------------+----------+---------+ +-----------------------------+----------+-----+
Table 1: CoAP Content-Format IDs Table 1: CoAP Content-Format IDs
7.2. senml-etch+json Media Type 7.2. senml-etch+json Media Type
Type name: application Type name: application
Subtype name: senml-etch+json Subtype name: senml-etch+json
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: binary Encoding considerations: binary
Security considerations: See Section 6 of RFC-AAAA. Security considerations: See Section 6 of RFC 8790.
Interoperability considerations: N/A Interoperability considerations: N/A
Published specification: RFC-AAAA Published specification: RFC 8790
Applications that use this media type: Applications that use the Applications that use this media type: Applications that use the
SenML media type for resource representation. SenML media type for resource representation.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml-etch+json is supported by using fragment application/senml-etch+json is supported by using fragment
identifiers as specified by RFC AAAA. identifiers as specified by Section 4 of RFC 8790.
Additional information: Additional information:
Deprecated alias names for this type: N/A Deprecated alias names for this type: N/A
Magic number(s): N/A Magic number(s): N/A
File extension(s): senml-etchj
Windows Clipboard Name: "SenML FETCH/PATCH format" File extension(s): senml-etchj
Macintosh file type code(s): N/A Windows Clipboard Name: "SenML FETCH/PATCH format"
Macintosh Universal Type Identifier code: org.ietf.senml-etch-json Macintosh file type code(s): N/A
conforms to public.text
Person & email address to contact for further information: Ari Macintosh Universal Type Identifier code:
Keranen ari.keranen@ericsson.com org.ietf.senml-etch-json conforms to public.text
Intended usage: COMMON Person & email address to contact for further information:
Ari Keränen <ari.keranen@ericsson.com>
Restrictions on usage: N/A Intended usage: COMMON
Author: Ari Keranen ari.keranen@ericsson.com Restrictions on usage: N/A
Change controller: IESG Author: Ari Keränen <ari.keranen@ericsson.com>
Change controller: IESG
7.3. senml-etch+cbor Media Type 7.3. senml-etch+cbor Media Type
Type name: application Type name: application
Subtype name: senml-etch+cbor Subtype name: senml-etch+cbor
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: binary Encoding considerations: binary
Security considerations: See Section 6 of RFC-AAAA. Security considerations: See Section 6 of RFC 8790.
Interoperability considerations: N/A Interoperability considerations: N/A
Published specification: RFC-AAAA Published specification: RFC 8790
Applications that use this media type: Applications that use the Applications that use this media type: Applications that use the
SenML media type for resource representation. SenML media type for resource representation.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml-etch+cbor is supported by using fragment application/senml-etch+cbor is supported by using fragment
identifiers as specified by RFC AAAA. identifiers as specified by Section 4 of RFC 8790.
Additional information: Additional information:
Deprecated alias names for this type: N/A Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): senml-etchc
Macintosh file type code(s): N/A Magic number(s): N/A
Macintosh Universal Type Identifier code: org.ietf.senml-etch-cbor File extension(s): senml-etchc
conforms to public.data
Person & email address to contact for further information: Ari Macintosh file type code(s): N/A
Keranen ari.keranen@ericsson.com
Intended usage: COMMON Macintosh Universal Type Identifier code:
org.ietf.senml-etch-cbor conforms to public.data
Restrictions on usage: N/A Person & email address to contact for further information:
Ari Keränen <ari.keranen@ericsson.com>
Author: Ari Keranen ari.keranen@ericsson.com Intended usage: COMMON
Change controller: IESG Restrictions on usage: N/A
8. Acknowledgements Author: Ari Keränen <ari.keranen@ericsson.com>
The use of FETCH and (i)PATCH methods with SenML was first introduced Change controller: IESG
by the OMA SpecWorks LwM2M v1.1 specification. This document
generalizes the use to any SenML representation. The authors would
like to thank Carsten Bormann, Christian Amsuess, Jaime Jimenez,
Klaus Hartke, Michael Richardson, and other participants from the
IETF CoRE and OMA SpecWorks DMSE working groups who have contributed
ideas and reviews.
9. References 8. References
9.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object
Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049,
October 2013, <https://www.rfc-editor.org/info/rfc7049>. October 2013, <https://www.rfc-editor.org/info/rfc7049>.
skipping to change at page 11, line 24 skipping to change at line 483
[RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", STD 90, RFC 8259, Interchange Format", STD 90, RFC 8259,
DOI 10.17487/RFC8259, December 2017, DOI 10.17487/RFC8259, December 2017,
<https://www.rfc-editor.org/info/rfc8259>. <https://www.rfc-editor.org/info/rfc8259>.
[RFC8428] Jennings, C., Shelby, Z., Arkko, J., Keranen, A., and C. [RFC8428] Jennings, C., Shelby, Z., Arkko, J., Keranen, A., and C.
Bormann, "Sensor Measurement Lists (SenML)", RFC 8428, Bormann, "Sensor Measurement Lists (SenML)", RFC 8428,
DOI 10.17487/RFC8428, August 2018, DOI 10.17487/RFC8428, August 2018,
<https://www.rfc-editor.org/info/rfc8428>. <https://www.rfc-editor.org/info/rfc8428>.
9.2. Informative References 8.2. Informative References
[IPSO] IPSO, "IPSO Light Control Smart Object", 2018, [IPSO] IPSO, "IPSO Light Control Smart Object", 2019,
<http://www.openmobilealliance.org/tech/profiles/ <http://www.openmobilealliance.org/tech/profiles/
lwm2m/3311.xml>. lwm2m/3311.xml>.
Acknowledgements
The use of the FETCH and (i)PATCH methods with SenML was first
introduced by the OMA SpecWorks Lightweight Machine to Machine
(LwM2M) v1.1 specification. This document generalizes the use to any
SenML representation. The authors would like to thank Carsten
Bormann, Christian Amsüss, Jaime Jiménez, Klaus Hartke, Michael
Richardson, and other participants from the IETF CoRE and OMA
SpecWorks DMSE working groups who have contributed ideas and reviews.
Authors' Addresses Authors' Addresses
Ari Keranen Ari Keränen
Ericsson Ericsson
FI-02420 Jorvas
Finland
Email: ari.keranen@ericsson.com Email: ari.keranen@ericsson.com
Mojan Mohajer Mojan Mohajer
Email: mojanm@hotmail.com Email: mojanm@hotmail.com
 End of changes. 88 change blocks. 
182 lines changed or deleted 182 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/