Browse Prior Art Database

JSON Encoding of Data Modeled with YANG (RFC7951)

IP.com Disclosure Number: IPCOM000247395D
Original Publication Date: 2016-Aug-01
Included in the Prior Art Database: 2016-Sep-01
Document File: 40 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Lhotka: AUTHOR

Abstract

The Network Configuration Protocol (NETCONF) [RFC6241] uses XML [XML] for encoding data in its Content Layer. Other management protocols might want to use other encodings while still benefiting from using YANG [RFC7950] as the data modeling language.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                         L. Lhotka Request for Comments: 7951                                        CZ.NIC Category: Standards Track                                    August 2016 ISSN: 2070-1721

                 JSON Encoding of Data Modeled with YANG

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7951.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Lhotka                       Standards Track                    [Page 1]
 RFC 7951               JSON Encoding of YANG Data            August 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3

   2.  Terminology and Notation  . . . . . . . . . . . . . . . . . .   3

   3.  Properties of the JSON Encoding . . . . . . . . . . . . . . .   4

   4.  Names and Namespaces  . . . . . . . . . . . . . . . . . . . .   5

   5.  Encoding of YANG Data Node Instances  . . . . . . . . . . . .   7

     5.1.  The "leaf" Data Node  . . . . . . . . . . . . . . . . . .   7

     5.2.  The "container" Data Node . . . . . . . . . . . . . . . .   8

     5.3.  The "leaf-list" Data Node . . . . . . . . . . . . . . . .   8

     5.4.  The "list" Data Node  . . . . . . . . . . . . . . . . . .   9

     5.5.  The "anydata" Data Node . ....