Bernie, Michael, and Éric, Thank you for your replies, guidance, and clarifications. We have updated the files as requested, recorded AD approval, and noted that all of our queries have been resolved (see AUTH48 status page below).
Please review the files carefully as we do not make changes after publication. The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9915.txt https://www.rfc-editor.org/authors/rfc9915.pdf https://www.rfc-editor.org/authors/rfc9915.html https://www.rfc-editor.org/authors/rfc9915.xml The relevant diff files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9915-diff.html (comprehensive diff) https://www.rfc-editor.org/authors/rfc9915-rfcdiff.html (comprehensive side by side) https://www.rfc-editor.org/authors/rfc9915-auth48diff.html (AUTH48 changes only) https://www.rfc-editor.org/authors/rfc9915-auth48rfcdiff.html (AUTH48 side by side) https://www.rfc-editor.org/authors/rfc9915-lastdiff.html (last version to this) https://www.rfc-editor.org/authors/rfc9915-lastrfcdiff.html (last to this side by side) Please contact us with any further updates/questions/comments you may have. We will await approvals from each of the parties listed on the AUTH48 status page prior to moving forward to publication. The AUTH48 status page for this document is available here: https://www.rfc-editor.org/auth48/rfc9915 Thank you. Megan Ferguson RFC Production Center > On Dec 15, 2025, at 10:15 AM, Michael Richardson <[email protected]> wrote: > > > Eric Vyncke (evyncke) <[email protected]> wrote: >> So,, let's use a "MUST NOT" as we all want all DHCPv6 servers moving to >> RFC 9915, this will be an incentive to implementors to clean up their >> code by removing this function (if they had it). > > I don't think it will push any implementation to change. > I don't care SHOULD NOT vs MUST NOT :-) > It might guide new implementations, but I doubt there will be any. > > > > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
