[core] Robert Wilton's No Objection on draft-ietf-core-sid-23: (with COMMENT)

[Robert Wilton via Datatracker <[e-mail]>]

Robert Wilton has entered the following ballot position for
draft-ietf-core-sid-23: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-core-sid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

You can regard all of these comments as non-blocking (against -23):

1. I think that the security reference to "The security and privacy
considerations in Sections 5 and 6 of [I-D.bormann-t2trg-deref-id] apply." is
somewhat dubious, since it would create a normative reference and block this
doc and we don't know what they will eventually say.  Perhaps change this text
to make this a softer recommendation, i.e., rather than they saying that they
apply, say something like "please also see I-D.bormann-t2trg-deref-id for
further considerations that may be applicable"?  This may then allow it the
reference to bormann-t2trg-deref-id to be informational rather than normative
(but I've not checked other usages).

2. The type-1, type-2, type-3 developers are not referenced very much in the
doc, and I wonder whether referencing by name wouldn't be more helpful for most
readers, e.g., SID-guiding, SID-oblivious, SID-aware).

3. The text in section 6.4.3, seems to be mostly written about drafts that are
creating new YANG modules, and hence allocating new SID files.  There doesn't
appear to be any text about new revisions of existing published YANG modules
that would presumably also need to take into account any previously published
SID file for that module previously published in IANA.

Regards,
Rob