Hi Paul,
Thanks for doing that maintenance.
I'm not sure if draft-ietf-dnsop-generalized-notify should also be added; it's
a DS provisioning document, but also more general. Just bringing it up with no
preference.
I think it would be a good idea to list all those DNSSEC docs in a registry, so
we don't have to replace the document regularly.
Best,
Peter
PS: Diff:
https://author-tools.ietf.org/iddiff?url1=rfc9364&url2=draft-hoffman-rfc9364bis&difftype=--html
On 4/30/25 04:07, Paul Hoffman wrote:
Greetings again. At the meeting in Bangkok, someone said that we should start
thinking about updating RFC 9364, BCP 237, that defines DNSSEC. I've started
this, but we're in no rush to adopt because there are some drafts in the queue
that will be added before we're ready to do a full update. See Appendix A for
the list of things already updated, and what's to come.
--Paul Hoffman
Begin forwarded message:
*From: *<internet-dra...@ietf.org>
*Subject: **[Ext] New Version Notification for draft-hoffman-rfc9364bis-00.txt*
*Date: *April 29, 2025 at 19:02:32 PDT
*To: *Paul Hoffman <paul.hoff...@icann.org>
A new version of Internet-Draft draft-hoffman-rfc9364bis-00.txt has been
successfully submitted by Paul Hoffman and posted to the
IETF repository.
Name: draft-hoffman-rfc9364bis
Revision: 00
Title: DNS Security Extensions (DNSSEC)
Date: 2025-04-29
Group: Individual Submission
Pages: 12
URL: https://www.ietf.org/archive/id/draft-hoffman-rfc9364bis-00.txt
Status: https://datatracker.ietf.org/doc/draft-hoffman-rfc9364bis/
HTMLized: https://datatracker.ietf.org/doc/html/draft-hoffman-rfc9364bis
Abstract:
This document describes the DNS Security Extensions (commonly called
"DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as
a handful of others. One purpose is to introduce all of the RFCs in
one place so that the reader can understand the many aspects of
DNSSEC. This document does not update any of those RFCs. A second
purpose is to state that using DNSSEC for origin authentication of
DNS data is the best current practice. A third purpose is to provide
a single reference for other documents that want to refer to DNSSEC.
This document obsoletes RFC 9364.
This document is being tracked at
(https://github.com/paulehoffman/rfc9364bis).
The IETF Secretariat
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
--
Like our community service? 💛
Please consider donating at
https://desec.io/
deSEC e.V.
Möckernstraße 74
10965 Berlin
Germany
Vorstandsvorsitz: Nils Wisiol
Registergericht: AG Berlin (Charlottenburg) VR 37525
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
