Re: [core] Ben Campbell's Discuss on draft-ietf-core-senml-14: (with DISCUSS and COMMENT)

[Carsten Bormann <[e-mail]>]

Here is my knee-jerk reaction to the other Ben’s review.

> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Hopefully this is easy to address:
> 
> §4.7  talks about how SenML can also be used to configure parameters and
> controlling actuators. That capability has some rather significant security
> implications, but I failed to find mention of it in the security
> considerations. That needs to be explicitly discussed.

Indeed.
TBD.

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Substantive:
> 
> §4.4: "If this value is a version number larger than the version which the
>   system understands, the system SHOULD NOT use this object."
> 
> Why not MUST NOT? Are there situations where an implementation might reasonably
> use an object with a higher version number than the implementation understands?

Not really.
Fair point.

> Editorial/Nits:
> 
> The title is misleading. It makes it sound like the document is just
> registering media types; in fact it defines SenML.

Right, it is defining the media types.
(Hmm, if “media types” means “media type names and their registrations”, maybe we do need to change the title.)

> §1, first paragraph: "This format was defined...": The antecedent of "this" is
> unclear, since the fact the document defines SenML has not yet been mentioned.

s/This format/The format established by these media types/

> §4.3, table 1: What do the asterisks mean?

(See my knee-jerk comments on Adam’s COMMENTS.)

> §5.1.2, paragraph starting with "Note that...": I'm surprised to find normative
> requirements buried in a note in an example.

We should decide the whole stream pile before fixing this (which is just a symptom of the less-than-well-definedness of streams).

> §10, first paragraph: “ the an integrated sum...": competing articles.

s/the an/an/

> §14: “Sensor data can range from information with almost no security
> considerations..."
> s/security/privacy

Yep.

Grüße, Carsten