[DNSOP] Re: Fwd: New Version Notification for draft-pels-d nsop-axfr-notify-01.txt

Stefan Ubbink <[email protected]> Wed, 26 Aug 2026 13:35:55 +0200
Newsgroups	gmane.ietf.dnsop
Organization	SIDN
Message-ID	<[email protected]>
On Mon, 10 Aug 2026 10:03:01 +0200
Martin Pels <[email protected]> wrote:

> Hi,

Hello Martin (and Florian),

> 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.

I have read the 01 version of the document and have a few remarks.

# 1. Introduction

I like the use of the word 'incidentally' in "or an operator incidentally 
wanting to propagate changes to a zone without updating the SOA record."
because I think in normal operation changes to a zone should include an
increase of the SOA SERIAL.

# 3.2. Secondary server behaviour

It seems to me that the 'SHOULD' in "The AXFR query SHOULD contain an empty
ZONEVERSION option in the EDNS(0) OPT pseudo-RR." has to be a 'MUST', because
if a secondary doesn't add this, it will not receive the information it needs.

"Replace the locally stored ZONETIMESTAMP value with the ZONETIMESTAMP value
from the AXFR response If the secondary" technically, you can not replace
something that is not available, so maybe the text could be "Store the
ZONETIMESTAMP value from the AXFR response, overwriting any previous value
if available."

I hope this helps.


> 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]



-- 
Stefan Ubbink
DNS & Systems Engineer
Present: Mon, Tue, Wed, Fri
SIDN | Meander 501 | 6825 MD | Arnhem | The Netherlands
T +31 (0)26 352 55 00
https://www.sidn.nl

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
signature.asc (application/pgp-signature, 833 B)