(1) RFC is Informational, and this is the correct RFC type.
Technical Summary:
The "ZONEVERSION" EDNS option allows a DNS querier to request a DNS
authoritative server to add an EDNS option in the answer of such
query with a token field representing the version of the zone which
contains the answered Resource Record ("RR"), such as the Start Of
Authority ("SOA") serial field in zones when this number corresponds
to the zone version.
Working Group Summary:
WG worked and collaborated on resolving any and all issues. No rough consensus.
Document Quality:
Document is of good quality. There are several implementations that have been
in use for some time now.
Personnel:
Document Shepherd:
Responsible Area Director:
(3) The Document Shepherd did a detailed review of the document
for content as well as simple editorial checks (spelling/grammar).
The shepherd feels the document is ready for publication.
(4) The Document Shepherd has no concerns on the depth or breadth
of the reviews.
(5) There is no need for broader review.
(6) There are no concerns from the document shepherd.
(7) No IPR disclosures
(8) There is no IPR
(9) The WG Consensus on this document is very solid.
(10) There have been no appeals.
(11) The following editorial nits were pointed out to the authors, who will
update their document after hearing from the AD.
Section 2:
s/distingishes/distinguishes/
s/disambiguate such situation/disambiguates such a situation/
Section 8:
s/suited at such task/suited at such a task/
(12) No formal review needed
(13) All references have been identified as normative or informative.
(14) All normative references are in a clear state.
(15) There are no downward normative references
(16) N/A
(17) The document shepherd confirmed the consistency and references of the
IANA Considerations section is accurate.
(18) There is one IANA registry created: "ZONEVERSION" registry, and the IANA
considerations describe the different methods to update the registry.
(19) N/A
(20) No Yang Necessary