|
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 is the YANG module that provides the definition of the management for network interfaces. The ITU-T models augment the IETF interfaces model
|
|
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 "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state. Errata exist.
|
|
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:
|
|
|
Normative References/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group/
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,/
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,/
DOI 10.17487/RFC3688, January 2004,/
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.2", RFC 5246,/
DOI 10.17487/RFC5246, August 2008,/
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for/
the Network Configuration Protocol (NETCONF)", RFC 6020,/
DOI 10.17487/RFC6020, October 2010,/
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,/
and A. Bierman, Ed., "Network Configuration Protocol/
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,/
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure/
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,/
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",/
RFC 6991, DOI 10.17487/RFC6991, July 2013,/
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",/
RFC 7950, DOI 10.17487/RFC7950, August 2016,/
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF/
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,/
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC/
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,/
May 2017, /
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration/
Access Control Model", STD 91, RFC 8341,/
DOI 10.17487/RFC8341, March 2018,/
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,/
and R. Wilton, "Network Management Datastore Architecture/
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,/
Informative References/
[RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",/
RFC 7224, DOI 10.17487/RFC7224, May 2014,/
/
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",/
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 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.
|
|
