Wes, What is missing is how validators/validating resolvers should behave when presented with SHA1.
Roy > On 12 Aug 2022, at 16:48, Wes Hardaker <wjh...@hardakers.net> wrote: > > > Because it's time... > > -------------------- Start of forwarded message -------------------- > From: internet-dra...@ietf.org > To: "Wes Hardaker" <i...@hardakers.net> > Subject: New Version Notification for > draft-hardaker-dnsop-must-not-sha1-00.txt > Date: Fri, 12 Aug 2022 08:48:21 -0700 > > > A new version of I-D, draft-hardaker-dnsop-must-not-sha1-00.txt > has been successfully submitted by Wes Hardaker and posted to the > IETF repository. > > Name: draft-hardaker-dnsop-must-not-sha1 > Revision: 00 > Title: Remove SHA-1 from active use within DNSSEC > Document date: 2022-08-12 > Group: Individual Submission > Pages: 5 > URL: > https://www.ietf.org/archive/id/draft-hardaker-dnsop-must-not-sha1-00.txt > Status: > https://datatracker.ietf.org/doc/draft-hardaker-dnsop-must-not-sha1/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-hardaker-dnsop-must-not-sha1 > > > Abstract: > This document retires the use of SHA-1 within DNSSEC > > > > > The IETF Secretariat > > > -------------------- End of forwarded message -------------------- > > -- > Wes Hardaker > USC/ISI > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
