Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
Mark Andrews writes: > If we go ahead with this these two sentences [... snip ...] That seems like a good suggestion considering the direction of the conversation. Both drafts changed accordingly, thanks for the text. -- Wes Hardaker USC/ISI ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
If we go ahead with this these two sentences Validating resolvers MUST treat RRSIG records created from DNSKEY records using these algorithms as insecure. If no other RRSIG records of accepted cryptographic algorithms are available, the validating resolver MUST consider the associated resource records as Bogus. need to be replaced with Validating resolvers MUST treat RRSIG records created from DNSKEY records using these algorithms as an unsupported algorithm. If no other RRSIG records of accepted cryptographic algorithms are available, the validating resolver MUST consider the associated resource records as Insecure. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
On Apr 27, 2024, at 20:39, Tim Wicinski wrote: > > M > > > This starts a Call for Adoption for: > draft-hardaker-dnsop-rfc8624-bis > draft-hardaker-dnsop-must-not-sha1 > draft-hardaker-dnsop-must-not-ecc-gost I support adoption for all three drafts. Willing to help with text and well forced to review them eventually 藍 Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
All These were discussed at the last IETF and the chairs felt there was consensus to request adoption. This starts a Call for Adoption for: draft-hardaker-dnsop-rfc8624-bis draft-hardaker-dnsop-must-not-sha1 draft-hardaker-dnsop-must-not-ecc-gost The drafts are available here: https://datatracker.ietf.org/doc/draft-hardaker-dnsop-rfc8624-bis/ https://datatracker.ietf.org/doc/draft-hardaker-dnsop-must-not-sha1/ https://datatracker.ietf.org/doc/draft-hardaker-dnsop-must-not-ecc-gost/ If adopted, the authors will update these documents to add a note that these documents should move as a group. Please review these drafts to see if you think they are suitable for adoption by DNSOP, and send any comments to the list, clearly stating your view. Please also indicate if you are willing to contribute text, review, etc. This call for adoption ends: May 11 2024 Thanks, For DNSOP co-chairs ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
