[DNSOP] Re: [Ext] Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Shumon Huque
On Mon, Jan 13, 2025 at 5:11 PM Paul Wouters wrote: > On Jan 13, 2025, at 16:38, Warren Kumari wrote: > > On Tue, Jan 07, 2025 at 1:44 PM, Paul Wouters wrote: > >> On Tue, 7 Jan 2025, Paul Hoffman wrote: >> >> draft-ietf-dnsop-must-not-sha1 >> >> This document is fine as-is, with one minor nit:

[DNSOP] Re: [Ext] Algorithm requirements for Section 2 of draft-ietf-dnsop-rfc8624-bis

2025-01-13 Thread Paul Hoffman
I would like to see more discussion of this topic before the document is finished WG Last Call. ___ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org

[DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Warren Kumari
Hi all. [ Meta-comment / email ] Thank you all for your comments. Wes and I have addressed many of these comments, and posted new (editor) versions in git so you can review the changes, see how they look, confirm we addressed your concerns, etc. [0] DNSSEC Cryptographic Algorithm Recommendation

[DNSOP] Re: [Ext] Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Warren Kumari
On Tue, Jan 07, 2025 at 12:17 PM, Paul Hoffman wrote: > This set of drafts is a useful addition to the DNSSEC cannon and should be > published as RFCs. > Thank you for your review and feedback. We have addressed these most of these below, and posted new versions in Github. --Paul Hoffman > > =

[DNSOP] Re: [Ext] Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Warren Kumari
On Tue, Jan 07, 2025 at 1:44 PM, Paul Wouters wrote: > On Tue, 7 Jan 2025, Paul Hoffman wrote: > > draft-ietf-dnsop-must-not-sha1 > > This document is fine as-is, with one minor nit: Appendix C should be > marked for removal by the RFC Editor, similar to Appendix B. > > I think the Title and Abst

[DNSOP] Re: Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Warren Kumari
On Wed, Jan 08, 2025 at 7:07 AM, Stefan Ubbink < Stefan.Ubbink=40sidn...@dmarc.ietf.org> wrote: > On Mon, 6 Jan 2025 21:02:52 -0500 > Tim Wicinski wrote: > > All > > Hello, > > Welcome back from holidays, those who have returned. Discussions with the > working group and authors and we feel these

[DNSOP] Re: [Ext] Working Group Last Call for draft-ietf-dnsop-rfc8624-bis draft-ietf-dnsop-must-not-ecc-gost draft-ietf-dnsop-must-not-sha1

2025-01-13 Thread Paul Wouters
On Jan 13, 2025, at 16:38, Warren Kumari wrote:On Tue, Jan 07, 2025 at 1:44 PM, Paul Wouters wrote:On Tue, 7 Jan 2025, Paul Hoffman wrote: draft-ietf-dnsop-must-not-sha1 This document is fine as-is, with one minor nit: Appendix C should be marked for removal by the RFC Editor, si

[DNSOP] Re: Moving forward on domain validation

2025-01-13 Thread Shumon Huque
Hi Paul, Thanks for your comments. At the last DNSOP meeting in Dublin, I already made some remarks at the mic that the draft is in need of some cleanup and reorganization. A lot of the content has grown by accretion in response to various feedback and it is probably indeed time to do a cleanup p

[DNSOP] Re: [Ext] Moving forward on domain validation

2025-01-13 Thread Paul Hoffman
On Jan 13, 2025, at 06:55, Shumon Huque wrote: > > Thanks for your comments. > > At the last DNSOP meeting in Dublin, I already made some remarks at the mic > that the draft is in need of some cleanup and reorganization. A lot of the > content has grown by accretion in response to various feed