# 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][1]) reviewers, and your
diligence in completing it is appreciated. The full role of the shepherd is
further described in [RFC 4858][2]. 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. WG has consensus eventually.
2. There was controvesry when the document was first proposed. There was
issues raise such as nationalistic cryptography, or algorithms.
Issues were also raised that initially the document was Proposed Standards,
which was needed to update the IANA registry. However, during working
group discussions, it was discovered that RFC6014 which updated the registries
to not always require Standards Track documents missed an IANA registry.
RFC9157 was published to address this issue. Once that was completed
the document could proceed as Infomational.
3. No appeals threatened
4. There are implementations of this algorithm.
## Additional Reviews
5. Other reviews such as security would be useful
6. No formal expert reviews needed
7. No Yang
8. No automated checks
## Document Shepherd Checks
9. Shepherd feels document is clearly written and ready to be handed off.
10. All outside issues addressed
11. RFC is being requested as Informational, and this is the correct RFC type.
Datatracker attributes are correct.
12. All authors reminded of IPR.
13. All authors are listed willingly.
14. No current nits
15. All references are accurate
16. All references freely available
17. No downward normative references
18. All normatives references have been published
19. This document will Obsolete RFC5933, and Update RFC8624. This is relected
in the abstract and discussed in the introduction.
20. IANA considerations section is consistent with document.
21. No new IANA registries