[DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-zoneversion-10.txt

["Wessels, Duane" <[e-mail]>]

All,

the changes from draft-ietf-dnsop-zoneversion-09 to -10 address or incorporate the following points recently raised:

- Removed <xref> from abstract (Roman Danyliw)
- RFC 8499 -> RFC 9499 (Roman Danyliw)
- Incorporated Joe Abley's proposed text for "enclosing zone"
- Instruct responders to return FORMERR for invalid ZONEVERSION queries (Mark, Petr, John, et.al.)
- Rephrase "reminders" about certain types of responses (NXDOMAIN, SERVFAIL, etc) to not use uppercase requirements keywords (Murray Kucherawy)
- Move BCP 14 to normative references (Eric Vyncke)

We think that addresses all the outstanding comments at this time.  If we have overlooked something, please let us know.

DW



> Begin forwarded message:
> 
> From: <[e-mail]>
> Subject: [EXTERNAL] New Version Notification for draft-ietf-dnsop-zoneversion-10.txt
> Date: July 8, 2024 at 3:02:18 PM PDT
> To: Duane Wessels <[e-mail]>, Hugo Salgado <[e-mail]>, Mauricio Ereche <[e-mail]>, Mauricio Vergara Ereche <[e-mail]>
> 
> A new version of Internet-Draft draft-ietf-dnsop-zoneversion-10.txt has been
> successfully submitted by Duane Wessels and posted to the
> IETF repository.
> 
> Name:     draft-ietf-dnsop-zoneversion
> Revision: 10
> Title:    The DNS Zone Version (ZONEVERSION) Option
> Date:     2024-07-08
> Group:    dnsop
> Pages:    14
> URL:      https://www.ietf.org/archive/id/draft-ietf-dnsop-zoneversion-10.txt
> Status:   https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/
> HTML:     https://www.ietf.org/archive/id/draft-ietf-dnsop-zoneversion-10.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-zoneversion
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-zoneversion-10
> 
> Abstract:
> 
>   The DNS ZONEVERSION option is a way for DNS clients to request, and
>   for authoritative DNS servers to provide, information regarding the
>   version of the zone from which a response is generated.  The Serial
>   field from the Start Of Authority (SOA) resource record is a good
>   example of a zone's version, and the only one defined by this
>   specification.  Additional version types may be defined by future
>   specifications.
> 
>   Including zone version data in a response simplifies and improves the
>   quality of debugging and diagnostics since the version and the DNS
>   answer are provided atomically.  This can be especially useful for
>   zones and DNS providers that leverage IP anycast or multiple backend
>   systems.  It functions similarly to the DNS Name Server Identifier
>   (NSID) option described in RFC5001.
> 
> 
> 
> The IETF Secretariat
> 
>