On 8/3/2025 14:18, Paul Hoffman wrote:
Please note that this draft is already in the RFC Editor's queue, after having
gone through WG Last Call, IETF Last Call, and IESG review.
Making changes after it has been approved would likely bring the document back
to (at least) the WG for review, which seems like a bad idea. If there are no
technical errors, leaving the document as-is will get it published and
implemented sooner.
The thing is currently in Version Changed - Review Needed state. It
would be useful to add a pointer to where "insecure" is defined as the
generic meaning of "insecure" and the DNSSEC meaning are not identical.
The rest of it, can wait I think.
Mike
Discussion on the list here about what it means is good and useful, possibly
for a later revision. Mukund's questions seem reasonable for the community to
get a better understanding.
--Paul Hoffman
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
