Skip to main content

Shepherd writeup

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 is solid.

2. Was there controversy about particular points, or were there decisions where
the consensus was particularly rough?

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
  Yes. At least two implementations existed. 

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.
  No. The contents of this document have no closely interact with technologies 
in other IETF WG or external organizations. 

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.
  No formal review required. 

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.
  Thrift compilers have successfully generated automatic code from the 
Information Elements Schema defined in Appendix B, which are used in two 
interoperable implementations.

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?
  This document is ready for publication.  The document shepherd has done a 
complete and general review of the Document. All issues that were raised in the 
working group have been addressed. A new version (-17) with nits modification 
is going to be published. This document is ready to be submitted to IESG.

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
  The IETF Areas’ comments have been addressed.

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?
  The intended status is Proposed Standards. It is indicated in the header.
It matches with the content of the Document which defines protocol procedures. 
All Datatracker state attributes correctly reflect this intent.

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. All Authors and Contributors have made a statement regarding their 
knowledge of IPR which would relate to this Document. Six IPR disclosures 
have been made against this Document. The WG did not raise any issue with 
the existence of these IPR.

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.
  The number of authors exceeds five. The sixth co-author Jordan Head is the 
main editor of version 16. He did great job to improve the draft. 

14. Document any remaining I-D nits in this document. Simply running the idnits
tool is not enough; please review the "Content Guidelines" on (Also note that the current idnits tool generates
some incorrect warnings; a rewrite is underway.)
  Some idnits noise exist, but only editorial changes needed.

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
  The community has sufficient access to review such normative references.

17. Are there any normative downward references (see RFC 3967 and BCP
97) that are not already listed in the DOWNREF registry? If so,
list them.

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).
  There was a long thread with the AD about registry naming/structure. 
Aligned with his suggestions, the document lists IANA registries to be created, 
with reasonable names, detailed specification of initial contents and procedures 
for future allocations (expert review).

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.
  Tony Przygienda, Bruno Rijsman and Pascal Thubert are suggested as the 
IANA Experts for the new registries.