Dear DNSOP, Thank you for the very helpful feedback provided by several people on the -00 revision back in November.
Johan and I made changes to the document that incorporate the insights from the crowd, and resolved some other issues. The result is -01, attached below. If you are interested, please take a read. We're looking forward to further feedback here and/or at IETF 116. Thanks! Best, Peter -------- Forwarded Message -------- Subject: New Version Notification for draft-thomassen-dnsop-generalized-dns-notify-01.txt Date: Fri, 10 Feb 2023 08:25:23 -0800 From: internet-dra...@ietf.org To: Johan Stenstam <johan.stens...@internetstiftelsen.se>, Peter Thomassen <pe...@desec.io> A new version of I-D, draft-thomassen-dnsop-generalized-dns-notify-01.txt has been successfully submitted by Peter Thomassen and posted to the IETF repository. Name: draft-thomassen-dnsop-generalized-dns-notify Revision: 01 Title: Generalized DNS Notifications Document date: 2023-02-10 Group: Individual Submission Pages: 16 URL: https://www.ietf.org/archive/id/draft-thomassen-dnsop-generalized-dns-notify-01.txt Status: https://datatracker.ietf.org/doc/draft-thomassen-dnsop-generalized-dns-notify/ Html: https://www.ietf.org/archive/id/draft-thomassen-dnsop-generalized-dns-notify-01.html Htmlized: https://datatracker.ietf.org/doc/html/draft-thomassen-dnsop-generalized-dns-notify Diff: https://author-tools.ietf.org/iddiff?url2=draft-thomassen-dnsop-generalized-dns-notify-01 Abstract: Changes in CDS/CDNSKEY, CSYNC, and other records related to delegation maintenance are usually detected through scheduled scans run by the consuming party (e.g. top-level domain registry), incurring an uncomfortable trade-off between scanning cost and update latency. A similar problem exists when scheduling zone transfers, and has been solved using the well-known DNS NOTIFY mechanism ([RFC1996]). This mechanism enables a primary nameserver to proactively inform secondaries about zone changes, allowing the secondary to initiate an ad-hoc transfer independently of when the next SOA check would be due. This document extends the use of DNS NOTIFY beyond conventional zone transfer hints, bringing the benefits of ad-hoc notifications to DNS delegation maintenance in general. Use cases include DNSSEC key rollovers hints via NOTIFY(CDS) and NOTIFY(DNSKEY) messages, and quicker changes to a delegation's NS record set via NOTIFY(CSYNC) messages. Furthermore, this document proposes a new DNS record type, tentatively referred to as "NOTIFY record", which is used to publish details about where generalized notifications should be sent. TO BE REMOVED: This document is being collaborated on in Github at: https://github.com/peterthomassen/draft-thomassen-dnsop-generalized- dns-notify (https://github.com/peterthomassen/draft-thomassen-dnsop- generalized-dns-notify). The most recent working version of the document, open issues, etc. should all be available there. The authors (gratefully) accept pull requests.
The IETF Secretariat _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
