Re: [core] Lars Eggert's No Objection on draft-ietf-core-senml-versions-03: (with COMMENT)

[Carsten Bormann <[e-mail]>]

Hi Lars,

thank you for these details!

> On 2021-05-26, at 14:33, Lars Eggert via Datatracker <[e-mail]> wrote:
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 7.1, paragraph 4, comment:
>>   [IANA.senml]
>>              IANA, "Sensor Measurement Lists (SenML)",
>>              <http://www.iana.org/assignments/senml>.
> 
> Not sure if a normative reference to an IANA registry page is technically OK; it
> should probably cite the RFC that created that registry instead, and maybe add
> an informative reference to the registry page?

I find dozens of recent RFCs with normative references to IANA registries, and I do believe this practice is both OK and makes a lot of sense (in particular for registries like the present one that have been set up successively over time in multiple RFCs — even if those RFCs are also being references normatively, as they are here).
If you think we should change this practice, I think some guidance by the IESG would be useful.

The nits are fixed in the editor copy; except for the http:// URI — I have written a note to tools-discuss about the generation of http:// URIs in bibxml8.

Grüße, Carsten


> 
> -------------------------------------------------------------------------------
> All comments below are about very minor potential issues that you may choose to
> address in some way - or ignore - as you see fit. Some were flagged by
> automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
> will likely be some false positives. There is no need to let me know what you
> did with these suggestions.
> 
> Section 2.1, paragraph 4, nit:
> -    decimal numbers, e.g. 26 (0b11010, 0x1a) for a version that adds the
> +    decimal numbers, e.g., 26 (0b11010, 0x1a) for a version that adds the
> +                         +
> 
> The text version of this document contains these HTML entities, which might
> indicate issues with its XML source: &nbsp;
> 
> Section 1, paragraph 2, nit:
>> es additional features over time. However in the case of SenML it is expecte
>>                                  ^^^^^^^
> Did you forget a comma after a conjunctive/linking adverb?
> 
> Section 3, paragraph 2, nit:
>> secondary unit names [RFC8798] MAY be be used in the "u" field of SenML Reco
>>                                    ^^^^^
> Possible typo: you repeated a word
> 
> These URLs in the document can probably be converted to HTTPS:
> * http://www.iana.org/assignments/senml
> 
> 
>