Protocol Action: 'Generalized DNS Notifications' to Proposed Standard (draft-ietf-dnsop-generalized-notify-08.txt)

The IESG <iesg-secretary@ietf.org> Mon, 17 March 2025 11:05 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Generalized DNS Notifications' to Proposed Standard (draft-ietf-dnsop-generalized-notify-08.txt)
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <174220951054.141148.1550632077320138446@dt-datatracker-5b9b68c5b6-zxk6z>
Date: Mon, 17 Mar 2025 04:05:10 -0700
Message-ID-Hash: 7XC6WZTCF7IG2SJCTIERVMUICAXMYO2H
CC: The IESG <iesg@ietf.org>, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-generalized-notify@ietf.org, rfc-editor@rfc-editor.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FcsA0dOpHzhOXY201T6DoSc1q9Q>

The IESG has approved the following document:
- 'Generalized DNS Notifications'
(draft-ietf-dnsop-generalized-notify-08.txt) as Proposed Standard

This document is the product of the Domain Name System Operations Working
Group.

The IESG contact persons are Warren Kumari and Mahesh Jethanandani.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-generalized-notify/

Technical Summary

This document extends the use of DNS NOTIFY (RFC 1996) beyond
conventional zone transfer hints, bringing the benefits of ad-hoc
notifications to DNS delegation maintenance in general. Use cases
include DNSSEC bootstrapping and key rollovers hints, and quicker
changes to a delegation's NS record set.

To enable this functionality, a method for discovering the receiver
endpoint for such notification message is introduced, via the new
DSYNC record type.

Working Group Summary

Initially there were two different drafts discussing possible solutions. The
Working Group suggested the authors combine their work into one document, which
they did. Consensus has been very solid.

Document Quality

No DNS protocol changes are introduced by this document. The
mechanism instead makes use of a wider range of DNS messages allowed
by the protocol. Future extension for further use cases (such as
multi-signer key exchange) is possible.

Section 7 lists an example implementation, and the authors have been working
with others to deploy this.

Personnel

Tim Wicinski is DS.
Warren "Ace" Kumari is RAD!!!!!!!!! (and sad that this is the last time he gets to use this joke...)

Protocol Action: 'Generalized DNS Notifications' … The IESG