RFC 7951: JSON Encoding of Data Modeled with YANG
In plain English — editorial summary, not part of the RFC
This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.
Document record
- Document ID
- RFC7951
- Published
- August 2016
- Authors
- L. Lhotka
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7895YANG Module LibraryObsoleted
June 2016
- RFC 8022A YANG Data Model for Routing ManagementObsoleted
November 2016
- RFC 8072YANG Patch Media TypeCurrent
February 2017
- RFC 8309Service Models ExplainedCurrent
January 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 8349A YANG Data Model for Routing Management (NMDA Version)Current
March 2018
- RFC 8407Guidelines for Authors and Reviewers of Documents Containing YANG Data ModelsObsoleted
October 2018
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?