|
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:
|
|
|
Network Management Datastore Architecture (NMDA) provides an architectural framework for organizing YANG data models. NMDA is used by the data models in the ITU-T that are translated from protocol neutral UML-based Information 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 "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,/
https://www.rfc-editor.org/info/rfc2119./
/
[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,/
https://www.rfc-editor.org/info/rfc6241./
/
[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./
/
[RFC7952] Lhotka, L., "Defining and Using Metadata with YANG",/
RFC 7952, DOI 10.17487/RFC7952, August 2016,/
https://www.rfc-editor.org/info/rfc7952./
/
[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./
/
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in/
RFC 2119 Key Words", BCP 14, RFC 8174,/
DOI 10.17487/RFC8174, May 2017,/
https://www.rfc-editor.org/info/rfc8174./
/
[W3C.REC-xml-20081126]/
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and/
F. Yergeau, "Extensible Markup Language (XML) 1.0/
(Fifth Edition)", World Wide Web Consortium Recommendation/
REC-xml-20081126, November 2008,/
https://www.w3.org/TR/2008/REC-xml-20081126./
/
Informative References/
/
[NETMOD-Operational]/
Bjorklund, M. and L. Lhotka, "Operational Data in NETCONF/
and YANG", Work in Progress, draft-bjorklund-netmod-/
operational-00, October 2012./
/
[OpState-Enhance]/
Watsen, K., Bierman, A., Bjorklund, M., and J./
Schoenwaelder, "Operational State Enhancements for YANG,/
NETCONF, and RESTCONF", Work in Progress, draft-kwatsen-/
netmod-opstate-02, February 2016./
/
[OpState-Modeling]/
Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling/
of Operational State Data in YANG", Work in Progress,/
draft-openconfig-netmod-opstate-01, July 2015./
/
[OpState-Reqs]/
Watsen, K. and T. Nadeau, "Terminology and Requirements/
for Enhanced Handling of Operational State", Work in/
Progress, draft-ietf-netmod-opstate-reqs-04, January 2016./
/
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,/
DOI 10.17487/RFC3688, January 2004,/
https://www.rfc-editor.org/info/rfc3688./
/
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for/
the Network Configuration Protocol (NETCONF)", RFC 6020,/
DOI 10.17487/RFC6020, October 2010,/
https://www.rfc-editor.org/info/rfc6020./
/
[RFC6244] Shafer, P., "An Architecture for Network Management Using/
NETCONF and YANG", RFC 6244, DOI 10.17487/RFC6244,/
June 2011, https://www.rfc-editor.org/info/rfc6244./
/
[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./
/
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",/
RFC 8344, DOI 10.17487/RFC8344, March 2018,/
https://www.rfc-editor.org/info/rfc8344./
/
[With-config-state]/
Wilton, R., ""With-config-state" Capability for/
NETCONF/RESTCONF", Work in Progress, draft-wilton-netmod-/
opstate-yang-02, December 2015./
/
[YANG-SEC] IETF, "YANG Security Guidelines", https://trac.ietf.org//
trac/ops/wiki/yang-security-guidelines.
|
|
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.
|
|
