Hi Donald, Thanks for the suggestions. We’ve implemented all your suggested changes in the source document. We’ll wait a few days for any more changes and then publish a new revision.
DW > On May 12, 2024, at 1:30 AM, Donald Eastlake <d3e...@gmail.com> wrote: > > Caution: This email originated from outside the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > > Hi, > > I support this draft but have the following comments: > > I would assume this has been discussed before but, presumably, the purpose of > this document is to see that the zoneversion option will interoperate between > different implementations. So, why isn't it Standards Track? > > NSID should be expanded on first use and a reference to RFC 5001 added. > > Section 2: The first line is sort of run-on at the end of the line. Suggest > some more parentheses; > OLD > This document specifies a new EDNS(0) Section 6.1.2 of [RFC6891] > NEW > This document specifies a new EDNS(0) (Section 6.1.2 of [RFC6891]) > > Section 6: "In special for"? Maybe "In gratitude for"? or probably better yet > "Special thanks for" > > Section 8: There are other ways to obtain trustworthiness. Suggest the > following: > OLD > be necessary to use an encrypted and authenticated DNS transport. > NEW > be necessary to use an encrypted and authenticated DNS transport, TSIG > [RFC8946], or SIG(0) [RFC2931]. > > Very minor: The RFC Editor understands "[this document]" and "TBD". All the > current RFC Editor instructions in this draft are superfluous and could be > deleted. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 2386 Panoramic Circle, Apopka, FL 32703 USA > d3e...@gmail.com > > > On Tue, May 7, 2024 at 10:25 PM Suzanne Woolf > <swoolf=40pir....@dmarc.ietf.org> wrote: > Colleagues, > > > Back in October 2023, the WG requested publication of "The DNS Zone Version > (ZONEVERSION) Option" > (https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/). > > When our AD reviewed it before taking it to IETF Last Call, he felt there > were some issues that needed to be addressed, and returned it to the WG. At > the time, the chairs asked the authors to address the comments, and told the > WG we'd run another WGLC before requesting publication again. > > The authors have addressed Warren's comments, so we're opening a 1-week WGLC > on the revised zoneversion document. Please review the new version and speak > up on the list to support advancing it or tell us where you think it still > needs work. > > We'll close the WGLC in one week, May 15. > > Current version: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/ > Warren's AD review: > https://mailarchive.ietf.org/arch/browse/dnsop/?q=%22AD%20Review%3A%20draft-ietf-dnsop-zoneversion%22 > Diff : > https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-zoneversion-05 > > > Thanks, > Suzanne (for the chairs) > > _______________________________________________ > DNSOP mailing list -- dnsop@ietf.org > To unsubscribe send an email to dnsop-le...@ietf.org > _______________________________________________ > DNSOP mailing list -- dnsop@ietf.org > To unsubscribe send an email to dnsop-le...@ietf.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
