|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
This RFC provides a format for displaying information about YANG data models.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?draft=&rfc=8531&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of the referred RFC, is "Best Current Practice".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Best Current Practice" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFC are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Informative References/
/
[OSPF-YANG]/
Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem,/
"Yang Data Model for OSPF Protocol", Work in Progress,/
draft-ietf-ospf-yang-10, March 2018./
/
[PYANG] "pyang", February 2018,/
https://github.com/mbj4668/pyang./
/
[RFC7407] Bjorklund, M. and J. Schoenwaelder, "A YANG Data Model for/
SNMP Configuration", RFC 7407, DOI 10.17487/RFC7407,/
December 2014, https://www.rfc-editor.org/info/rfc7407./
/
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",/
RFC 7950, DOI 10.17487/RFC7950, August 2016,/
https://www.rfc-editor.org/info/rfc7950./
/
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF/
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,/
https://www.rfc-editor.org/info/rfc8040./
/
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface/
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,/
https://www.rfc-editor.org/info/rfc8343./
/
[SCHEMA-MOUNT]/
Bjorklund, M. and L. Lhotka, "YANG Schema Mount", Work in/
Progress, draft-ietf-netmod-schema-mount-08, October 2017./
/
[YANG-NIs] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X./
Liu, "YANG Model for Network Instances", Work in/
Progress, draft-ietf-rtgwg-ni-model-11, March 2018./
/
[YANG-Routing]/
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for/
Routing Management (NMDA Version)", Work in Progress,/
draft-ietf-netmod-rfc8022bis-11, January 2018.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
Reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or to IETF RFCs categorized as Historic or Experimental. Normative references must only be made to IETF RFCs that are Standards Track or to Informational RFCs that have IETF consensus.
|
|
