# Document Shepherd Write-Up for Group Documents
*This version is dated 4 July 2022.*
Thank you for your service as a document shepherd. Among the responsibilities is
answering the questions in this write-up to give helpful context to Last Call
and Internet Engineering Steering Group ([IESG]) reviewers, and your
diligence in completing it is appreciated. The full role of the shepherd is
further described in [RFC 4858]. You will need the cooperation of the authors
and editors to complete these checks.
Note that some numbered items contain multiple related questions; please be sure
to answer all of them.
## Document History
1. Does the working group (WG) consensus represent the strong concurrence of a
few individuals, with others being silent, or did it reach broad agreement?
The WG consensus on the merits of the .alt proposal is reasonably
strong. It deals with a fairly esoteric subject, so many participants
in DNSOP didn't have strong views. No one thinkks it's a perfect
solution to the problem it describes. However, there's consensus that
it's likely to help future protocol designers, potentially including
some in the IETF and some outside.
2. Was there controversy about particular points, or were there decisions where
the consensus was particularly rough?
Yes. Some participants felt it would not be appropriate for the IETF
to consider a proposal that they believed was properly in the remit
of ICANN as maintainer of the public DNS root zone. However, this was
eventually solved by being appropriately restricted about the scope of
the draft and the WG's job. The proposal relates only to protocols
that are not the DNS, but use domain names; and there is a liaison
relationship in place between the IETF and ICANN to handle any needed
clarifications. The WG was only obligated to consider the proposal on
3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
so, please summarize the areas of conflict in separate email messages to the
responsible Area Director. (It should be in a separate email because this
questionnaire is publicly available.)
4. For protocol documents, are there existing implementations of the contents of
the document? Have a significant number of potential implementers indicated
plans to implement? Are any existing implementations reported somewhere,
either in the document itself (as [RFC 7942] recommends) or elsewhere
N/A; this draft documents an IANA registry entry and some
considerations for DNS operators and protocol designers.
## Additional Reviews
5. Do the contents of this document closely interact with technologies in other
IETF working groups or external organizations, and would it therefore benefit
from their review? Have those reviews occurred? If yes, describe which
reviews took place.
This draft closely interacts with the responsibilities of ICANN, and is the
subject of a liaison discussion and liaison statement draft.
6. Describe how the document meets any required formal expert review criteria,
such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
7. If the document contains a YANG module, has the final version of the module
been checked with any of the [recommended validation tools] for syntax and
formatting validation? If there are any resulting errors or warnings, what is
the justification for not fixing them at this time? Does the YANG module
comply with the Network Management Datastore Architecture (NMDA) as specified
in [RFC 8342]?
8. Describe reviews and automated checks performed to validate sections of the
final version of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, CBOR's CDDL, etc.
## Document Shepherd Checks
9. Based on the shepherd's review of the document, is it their opinion that this
document is needed, clearly written, complete, correctly designed, and ready
to be handed off to the responsible Area Director?
10. Several IETF Areas have assembled [lists of common issues that their
reviewers encounter]. For which areas have such issues been identified
and addressed? For which does this still need to happen in subsequent
11. What type of RFC publication is being requested on the IETF stream ([Best
Current Practice], [Proposed Standard, Internet Standard],
[Informational, Experimental or Historic])? Why is this the proper type
of RFC? Do all Datatracker state attributes correctly reflect this intent?
This document is intended as a Proposed Standard. The reasoning is
that the registry it seeks to update requires Standards Action or IESG
Approval, and Proposed Standard seems more appropriate for a naming
convention intended to be widely adopted, inside or outside the IETF.
12. Have reasonable efforts been made to remind all authors of the intellectual
property rights (IPR) disclosure obligations described in [BCP 79]? To
the best of your knowledge, have all required disclosures been filed? If
not, explain why. If yes, summarize any relevant discussion, including links
to publicly-available messages when applicable.
Yes. Nothing relevant has been identified, and the authors have been
reminded to disclose any such thing that they know of.
13. Has each author, editor, and contributor shown their willingness to be
listed as such? If the total number of authors and editors on the front page
is greater than five, please provide a justification.
14. Document any remaining I-D nits in this document. Simply running the [idnits
tool] is not enough; please review the ["Content Guidelines" on
authors.ietf.org]. (Also note that the current idnits tool generates
some incorrect warnings; a rewrite is underway.)
The draft has been through quite a lot of review, and conforms to the
suggested guidelines. The only idnits warning is a flippant reference
in the changelog.
15. Should any informative references be normative or vice-versa? See the [IESG
Statement on Normative and Informative References].
16. List any normative references that are not freely available to anyone. Did
the community have sufficient access to review any such normative
17. Are there any normative downward references (see [RFC 3967] and [BCP
97]) that are not already listed in the [DOWNREF registry]? If so,
18. Are there normative references to documents that are not ready to be
submitted to the IESG for publication or are otherwise in an unclear state?
If so, what is the plan for their completion?
19. Will publication of this document change the status of any existing RFCs? If
so, does the Datatracker metadata correctly reflect this and are those RFCs
listed on the title page, in the abstract, and discussed in the
introduction? If not, explain why and point to the part of the document
where the relationship of this document to these other RFCs is discussed.
20. Describe the document shepherd's review of the IANA considerations section,
especially with regard to its consistency with the body of the document.
Confirm that all aspects of the document requiring IANA assignments are
associated with the appropriate reservations in IANA registries. Confirm
that any referenced IANA registries have been clearly identified. Confirm
that each newly created IANA registry specifies its initial contents,
allocations procedures, and a reasonable name (see [RFC 8126]).
This document allocates one new entry in a single registry,
Its intended status is consistent with that registry's policy, and the required
documentation for a proposed registry entry laid out in RFC 6761 is included.
21. List any new IANA registries that require Designated Expert Review for
future allocations. Are the instructions to the Designated Expert clear?
Please include suggestions of designated experts, if appropriate.