Robert Wilton has entered the following ballot position for
draft-ietf-regext-rfc7483bis-04: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


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



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

Hi,

Thank you for this update to RFC 7483.

A couple of minor comments:

In section 5.2.  The Nameserver Object Class:  It might be helpful to warn the
reader that some lines have been wrapped for display purposes.  E.g. the link
value and href.  Alternative, the approach/tooling from RFC 8792 could be used.

It also wasn't clear to me whether the Appendix "Changes from RFC 7483" was
going to be kept - there is no RFC editor note to suggest that it be removed.

Generally, I think that have a short section explaining how a RFC has changed
from a previously published version is helpful.  But if this is kept, then I
would try and condense this text down to just the list of important changes
from RFC 7483.

Regards,
Rob



_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to