Hi all, I'd like to understand better what the purpose/aspiration of this draft is, in particular as it's Standards Track.
What normative protocol specification does it actually make? To me, the descriptions in the document mainly appear to be a number of observations how to apply RFC 6781 / 7583 considerations to scenarios where there are multiple signers. While perhaps useful to spell out explicitly, it seems that the mechanisms described are "by implication" of current (DNSKEY and RRSIG presence) requirements rather than "by originality" of something new. As such, I would have expected this to be Informational (as are RFC 6781 / 7583). But I might be entirely misunderstanding, hence the question! Best, Peter On 2/6/25 14:46, Suzanne Woolf wrote:
Dear colleagues, This initiates the Working Group Last Call (WGLC) for draft-ietf-dnsop-dnssec-automation, "DNSSEC automation". The draft can be reviewed here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-automation <https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-automation/>/ <https://datatracker.ietf.org/doc/draft-ietf-dnsop-structured-dns-error/> Intended Status: Proposed Standard Document Shepherd: Suzanne Woolf The Working Group adopted draft-ietf-dnsop-dnssec-automation in May 2022. Since then, the draft has undergone multiple revisions following Working Group presentations and feedback. Both the Security Directorate and DNS Directorate have completed their reviews, and their suggestions have been incorporated into the latest version. Additionally, a proof-of-concept implementation is available, as referenced in the draft. Based on the reviews and incorporated feedback from both the Working Group and directorates, the authors and Working Group chairs believe that the draft is ready to proceed to Working Group Last Call. Please take the time to review this draft and share any relevant comments. For the WGLC to be effective, we need both positive support and constructive feedback; a simple lack of objection isn’t enough. If you believe this draft is ready for publication as an RFC, please state your support. Conversely, if you feel the document isn’t ready for publication, please provide your concerns and reasoning. This starts a two-week Working Group Last Call process, concluding on February 20, 2025. Thank you, Suzanne, Tim, and Benno _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
-- Like our community service? 💛 Please consider donating at https://desec.io/ deSEC e.V. Möckernstraße 74 10965 Berlin Germany Vorstandsvorsitz: Nils Wisiol Registergericht: AG Berlin (Charlottenburg) VR 37525 _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
