|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Internet Standards Track document (Standards Track)
|
|
3.
|
Justification for the specific reference:
|
|
|
RFC 7951 defines the rules for encoding data models defined in the YANG language as JSON text — including configuration data, state data, RPC/action parameters and notifications. In this Recommendation, where YANG-modeled device or network data need to be exchanged or captured in JSON form (for streaming telemetry, device configuration, IoT policy objects), referencing RFC 7951 ensures consistent and interoperable JSON encodings aligned to YANG models.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues is available at: https://datetracker.ietf.org/ipr/search/
Specifically: https://datetracker.ietf.org/ipr/search/?rfc=7951
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 7951 builds on the widely-adopted YANG data modelling language (RFC 7950). It has been implemented in many network management and telemetry systems, and supports vendor-agnostic exchange of device state/config in JSON form.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Published in 2016, the document has matured over years of deployment in network management systems. Its core encoding rules remain unchanged
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Extends RFC 7950 (YANG 1.1).
Relies on RFC 7159 / RFC 8259 (JSON syntax) for the underlying JSON format.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
./
/
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234,/
DOI 10.17487/RFC5234, January 2008,/
./
/
[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,/
./
/
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data/
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March/
2014, ./
/
[RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493,/
DOI 10.17487/RFC7493, March 2015,/
.
|
|
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.
|
|
