Hi, This version incorporates all feedback we received on the list.
As a loop prevention mechanism we opted for using a new ZONEVERSION subtype. This precludes the inclusion of a version value in the NOTIFY message, which makes the secondary server behaviour a bit inefficient. But it removes the need for defining an entirely new EDE option with almost the same semantics as ZONEVERSION.
Kind regards, Martin and Florian On 10/08/2026 09:36, [email protected] wrote:
A new version of Internet-Draft draft-pels-dnsop-axfr-notify-01.txt has been successfully submitted by Martin Pels and posted to the IETF repository. Name: draft-pels-dnsop-axfr-notify Revision: 01 Title: AXFR message type for DNS NOTIFY Date: 2026-08-10 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-pels-dnsop-axfr-notify-01.txt Status: https://datatracker.ietf.org/doc/draft-pels-dnsop-axfr-notify/ HTML: https://www.ietf.org/archive/id/draft-pels-dnsop-axfr-notify-01.html HTMLized: https://datatracker.ietf.org/doc/html/draft-pels-dnsop-axfr-notify Diff: https://author-tools.ietf.org/iddiff?url2=draft-pels-dnsop-axfr-notify-01 Abstract: This document defines a new AXFR message type for DNS NOTIFY messages, together with an accompanying subtype for the ZONEVERSION EDNS(0) option. The message instructs a secondary server to perform an AXFR zone transfer of a zone. The IETF Secretariat
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
