I support this. And found a nit, the document says:
The most confusing element of the above equation comes from the "3 * (DNSKEY RRSIG Signature Validity) / 2" but the formula just before doesn't include "3 *" anywhere in it. Cheers, Ondrej -- Ondřej Surý -- Technical Fellow -------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Milesovska 5, 130 00 Praha 3, Czech Republic mailto:ondrej.s...@nic.cz https://nic.cz/ -------------------------------------------- ----- Original Message ----- > From: "tjw ietf" <tjw.i...@gmail.com> > To: "dnsop" <dnsop@ietf.org> > Sent: Thursday, 16 March, 2017 08:16:50 > Subject: [DNSOP] DNSOP Call for Adoption: > draft-hardaker-rfc5011-security-considerations > All > > We've had a lot of WG discussion on this, and it seems relevant to do a formal > call for adoption. If there are outstanding issues raised during the CfA, time > in Chicago will be set aside to have those discussions. > > > This starts a Call for Adoption for: > draft-hardaker-rfc5011-security-considerations > > The draft is available here: > [ > https://datatracker.ietf.org/doc/draft-hardaker-rfc5011-security-considerations/ > | > https://datatracker.ietf.org/doc/draft-hardaker-rfc5011-security-considerations/ > ] > > Please review this draft to see if you think it is suitable for adoption by > DNSOP, and comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > If there are > > This call for adoption ends: 30 March 2017 > > Thanks, > tim wicinski > DNSOP co-chair > > _______________________________________________ > 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
