As required by RFC 4858, this is the current template for the Document
Shepherd write up for draft-ietf-dnsop-edns-key-tag
This RFC is being requests as a Standards Track.
This is the correct type of RFC.
This document specifies two different ways for validating DNS resolvers
to signal to a server which DNSSEC keys are referenced in their chain-of-
trust. The data from such signaling allow zone administrators to
monitor the progress of rollovers in a DNSSEC-signed zone. This
document describes two independent methods for validating resolvers
to publish their referenced keys: an EDNS option and a different
Working Group Summary:
The working group was in strong consensus behind this document. One thing
which did emerge was that there was a division over two methods for
publishihng the keys (EDNS option vs a DNS query). It turned out that each
method had its positives and its negatives. The consensus from the working
group was to offer both alternatives, documents the flaws in each.
Document Shepherd: Tim Wicinski
Area Director: Joel Jaeggli
The document shepherd did a deep dive on the document for technical
correctness, as well as an editorial pass for grammar and diction.
The shepherd feels this document is ready for publication.
The document shepherd does not have any concerns about the depth or breath of
No additional reviews needed.
The document shepherd has no concerns about this document for the Area
(7) The authors have confirmed they are not aware of any IPR against this
The working group is in strong consenus for this document.
There has been no extreme discontent.
No Nits found
All references have been identified as normative or informative
There are no normative references in an unclear state
There are no downward normative references
Publication of this document will not change any existing RFCs
The IANA Considerations section requests the assignment of a new
EDNS0 option code. Discussing with the Expert Reviewer of DNS parameters,
this section is correctly structured
No new IANA Registries.