[DNSOP] Re: [TLS] Re: Re: Re: Re: AD review draft-ietf-tls-svcb-ech

2024-10-16 Thread Ben Schwartz
OK. Erik, Mike, Paul: Let me know if you have any further comments on #18. --Ben From: Sean Turner Sent: Wednesday, October 16, 2024 3:06 PM To: draft-ietf-tls-svcb-ech.auth...@ietf.org Cc: dnsop@ietf.org WG ; TLS List Subject: Re: [TLS] [DNSOP] Re: Re: Re: Re

[DNSOP] Re: [TLS] Re: Re: Re: Re: AD review draft-ietf-tls-svcb-ech

2024-10-16 Thread Sean Turner
Authors (Ben, Mike, and Eric), Thank for the PR with some examples: https://github.com/tlswg/draft-ietf-tls-svcb-ech/pull/18 Once you’ve settled the debate (hopefully before Monday), please go ahead and merge so that Paul can get the IETF LC started. Cheers, spot > On Oct 9, 2024, at 09:38, Se

[DNSOP] Re: [Ext] [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread Dave Lawrence
Warren Kumari writes: > Robert, if you'd like to propose standardizing SHA-512 for use in DS > records please propose this in an Internet Draft — there is a > helpful page here: > https://authors.ietf.org/en/home And if you do, note that next unassigned algorithm value is 7, not 5. 5 is GOST R 34

[DNSOP] Re: [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread Paul Wouters
Ondřej Surý wrote: I am quite confused as SHA-512 is not standardized for use in DS records: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml I believe this change should be rejected until (and if) SHA-512 is standardized to use in DS records. Indeed it should be rejected, bu

[DNSOP] Re: [Drip] Re: Fwd: Re: I-D Action: draft-ietf-drip-registries-18.txt

2024-10-16 Thread Daniel Migault
Hi, Thanks for the feedbacks. The Working Group Last Call is finished and authors will update the document with the received feed backs and publish a new version. Yours, Daniel On Tue, Oct 1, 2024 at 1:23 PM Robert Moskowitz wrote: > CAA should be expanded on first use. > > DRIP expansion (in

[DNSOP] Re: [Ext] [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread Warren Kumari
Yup, I agree. While what is being proposed may be the right thing to do, the Errata process is not the appropriate way to accomplish this. >From "IESG Processing of RFC Errata for the IETF Stream" ( https://datatracker.ietf.org/doc/statement-iesg-iesg-processing-of-rfc-errata-for-the-ietf-stream-

[DNSOP] Re: [Ext] [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread Paul Hoffman
This is a purposely technical change to the document, and thus should be rejected. It is not an errata at all. The correct way to ask for a technical change such as this is to first ask the DNSOP WG, then possibly write a draft. ___ DNSOP mailing list

[DNSOP] Note deadlines for IETF 121

2024-10-16 Thread Suzanne Woolf
Hi, Just a gentle reminder that the draft cutoff for Dublin is next Monday at midnight UTC, and draft WG agendas are due a week from today, also at midnight UTC. If you have a draft or a request for agenda time in DNSOP, please get those submitted. Much thanks, Suzanne, Tim, and Benno ___

[DNSOP] Re: [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread Ondřej Surý
Hi, I am quite confused as SHA-512 is not standardized for use in DS records: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml I believe this change should be rejected until (and if) SHA-512 is standardized to use in DS records. Ondrej -- Ondřej Surý — ISC (He/Him) My working ho

[DNSOP] [Technical Errata Reported] RFC8624 (8144)

2024-10-16 Thread RFC Errata System
The following errata report has been submitted for RFC8624, "Algorithm Implementation Requirements and Usage Guidance for DNSSEC". -- You may review the report below and at: https://www.rfc-editor.org/errata/eid8144 -- Type:

[DNSOP] Re: [EXTERNAL] Call for Adoption: draft-huque-dnsop-grease

2024-10-16 Thread Suzanne Woolf
Dear colleagues, This call for adoption is now closed. The chairs have reviewed the comments and we see enough support for this draft to adopt it. Thanks to everyone who commented. Several of you seemed to feel it’s a sound framework but it might need substantial work— please continue the disc