Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
Sensor Measurement Lists (SenML)
draft-ietf-core-senml-16
Approval announcement
Draft of message to be sent after approval:
Announcement
From: The IESG <iesg-secretary@ietf.org >
To: IETF-Announce <ietf-announce@ietf.org >
Cc: The IESG <iesg@ietf.org >, jaime.jimenez@ericsson.com , core-chairs@ietf.org , draft-ietf-core-senml@ietf.org , Jaime Jimenez <jaime.jimenez@ericsson.com >, core@ietf.org , alexey.melnikov@isode.com , rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Sensor Measurement Lists (SenML)' to Proposed Standard (draft-ietf-core-senml-16.txt )
The IESG has approved the following document:
- 'Sensor Measurement Lists (SenML)'
(draft-ietf-core-senml-16.txt ) as Proposed Standard
This document is the product of the Constrained RESTful Environments Working
Group.
The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.
A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-senml/
Ballot Text
Technical Summary
This specification defines media types for representing simple sensor
measurements and device parameters in the Sensor Measurement Lists
(SenML). Representations are defined in JavaScript Object Notation
(JSON), Concise Binary Object Representation (CBOR), eXtensible
Markup Language (XML), and Efficient XML Interchange (EXI), which
share the common SenML data model. A simple sensor, such as a
temperature sensor, could use this media type in protocols such as
HTTP or CoAP to transport the measurements of the sensor or to be
configured.
Working Group Summary
The document has gone through multiple expert reviews and
has been discussed on multiple IETF meetings.
The document was not controversial.
Document Quality
There are several existing implementations of the formats described in this document.
Personnel
Document Shepherd: Jaime Jiménez,
Area Director: Alexey Melnikov,
RFC Editor Note
RFC Editor Note
Please add the following sentence to the end of 1st paragraph of Section 13:
Malicious use of SenML to change system state could have severe consequences,
potentially including violation of physical security, property damage, and even
loss of life.