|
Thanks for partially addressing my DISCUSS point about using only RFC 2119 by using correctly BCP14. But, BCP14 is incorrectly cited in the informative references while it should be in the normative ones. Yet, another easy fix ;-) Regards -éric
On 02/07/2024, 17:48, "iesg-secretary@xxxxxxxx" <iesg-secretary@xxxxxxxx> wrote: The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@xxxxxxxx mailing lists by 2024-07-16. Exceptionally, comments may be sent to
iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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 [RFC5001]. The file can be obtained via No IPR declarations have been submitted directly on this I-D. |
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
