[DNSOP] Re: AD review of draft-ietf-dnsop-rfc8624-bis-05

2025-02-18 Thread Warren Kumari
On Tue, Feb 18, 2025 at 6:55 AM, Eric Vyncke < evyncke=40cisco@dmarc.ietf.org> wrote: > > > Dear all, > > > > Thanks for your patience as I was on vacations when the publication of > this I-D was requested. > No worries, and thanks. Apologies for my mail client having renumbered the ordered l

[DNSOP] Re: AD review of draft-ietf-dnsop-must-not-ecc-gost-02

2025-02-18 Thread Warren Kumari
On Mon, Feb 17, 2025 at 11:15 AM, Eric Vyncke < evyncke=40cisco@dmarc.ietf.org> wrote: > Dear all, > > > > Thanks for your patience as I was on vacations when the publication of > this I-D was requested. As the DNSOP responsible AD is also an author, I > was selected as the acting responsible

[DNSOP] I-D Action: draft-ietf-dnsop-rfc8624-bis-06.txt

2025-02-18 Thread internet-drafts
Internet-Draft draft-ietf-dnsop-rfc8624-bis-06.txt is now available. It is a work item of the Domain Name System Operations (DNSOP) WG of the IETF. Title: DNSSEC Cryptographic Algorithm Recommendation Update Process Authors: Wes Hardaker Warren Kumari Name:draft-ietf-dns

[DNSOP] Re: AD review of draft-ietf-dnsop-rfc8624-bis-05

2025-02-18 Thread Eric Vyncke (evyncke)
Hello Warren, Thanks for the quick reply and revised I-D. We agree on all points, and I will proceed shortly with the IETF Last Call, some more comments below as EV> Regards -éric From: Warren Kumari Date: Tuesday, 18 February 2025 at 23:35 To: Eric Vyncke (evyncke) Cc: dnsop@ietf.org Subje

[DNSOP] Re: AD review of draft-ietf-dnsop-must-not-sha1-02

2025-02-18 Thread Warren Kumari
On Mon, Feb 17, 2025 at 10:01 AM, Eric Vyncke < evyncke=40cisco@dmarc.ietf.org> wrote: > Dear all, > > > > Thanks for your patience as I was on vacations when the publication of > this I-D was requested. > Thanks, an no worries… As the DNSOP responsible AD is also an author, I was selected

[DNSOP] I-D Action: draft-ietf-dnsop-must-not-sha1-03.txt

2025-02-18 Thread internet-drafts
Internet-Draft draft-ietf-dnsop-must-not-sha1-03.txt is now available. It is a work item of the Domain Name System Operations (DNSOP) WG of the IETF. Title: Deprecating the use of SHA-1 in DNSSEC signature algorithms Authors: Wes Hardaker Warren Kumari Name:draft-ietf-dn

[DNSOP] I-D Action: draft-ietf-dnsop-must-not-ecc-gost-03.txt

2025-02-18 Thread internet-drafts
Internet-Draft draft-ietf-dnsop-must-not-ecc-gost-03.txt is now available. It is a work item of the Domain Name System Operations (DNSOP) WG of the IETF. Title: Deprecate usage of ECC-GOST within DNSSEC Authors: Wes Hardaker Warren Kumari Name:draft-ietf-dnsop-must-not-e

[DNSOP] Re: AD review of draft-ietf-dnsop-must-not-ecc-gost-02

2025-02-18 Thread Eric Vyncke (evyncke)
Thank you, Warren, for your replies on the 3 related I-Ds, I will proceed shortly with the IETF Last Call. About deprecating an already historic RFC, I am unsure as well as those 2 terms are not really well defined. Let’s see what the IESG/RFC Editor say indeed, smart idea to add this note in

[DNSOP] Re: Reminder: (in 2 HOURS) DNSOP Virtual Interim Meeting 17 February 2025

2025-02-18 Thread Michael De Roover
On Monday, February 17, 2025 1:54:34 PM CET Suzanne Woolf wrote: > Good morning/afternoon/evening. We’re resending this announcement to get it > to the top of everyone’s Monday mailbox. DNSOP interim starts in 2 hours, > at 20:00 UTC. Agenda and Meetecho link below. > > See you there, > Suzanne, T

[DNSOP] AD review of draft-ietf-dnsop-rfc8624-bis-05

2025-02-18 Thread Eric Vyncke (evyncke)
Dear all, Thanks for your patience as I was on vacations when the publication of this I-D was requested. As the DNSOP responsible AD is also an author, I was selected as the acting responsible AD for this I-D. Hence, here are some comments that I want to be addressed (either by replying to me o

[DNSOP] Re: RFC for web3 wallet mapping using DNS

2025-02-18 Thread Shay C
I have made a new draft https://datatracker.ietf.org/doc/draft-chins-dnsop-web3-wallet-mapping/ - Separated the forward mapping and reverse mapping. Will propose a ID for reverse mapping separately. - Removed DEFAULT record because it had the potential to return incorrect records Che