Subject: [netmod] Protocol Action: 'JSON Encoding of Data Modeled with YANG' to Proposed Standard (draft-ietf-netmod-yang-json-10.txt)

From: The IESG <[email-masked]>
Date: Mon, 28 Mar 2016 09:26:02 -0700

The IESG has approved the following document:
- 'JSON Encoding of Data Modeled with YANG'
  (draft-ietf-netmod-yang-json-10.txt) as Proposed Standard

This document is the product of the NETCONF Data Modeling Language
Working Group.

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-json/

Technical Summary

   This document defines encoding rules for representing configuration,
    state data, RPC operation or action input and output parameters, and
    notifications defined using YANG as JavaScript Object Notation (JSON)
    text.

Working Group Summary

   The JSON encoding is one of the two media types supported by the
   RESTCONF protocol [draft-ietf-netconf-restconf]. This document was discussed
   multiple times during the RESTCONF specification process. The main issue has been
   around the encoding of the "anyxml" type, which YANG 1.1 no longer recommends using.  The 
   document went through 3 WG last calls, and there is broad consensus on the final version.

Document Quality

   There are several existing RESTCONF implementations, and some others being 
   worked on, that either support both XML and JSON encoding, or are JSON-only, 
   for example:
      * YumaWork’s YumaPro platform's SDK
      * Linux Foundation’s OpenDaylight platform 
      * Juniper’s Contrail Service Orchestration platform

   Other tools and libraries also support the JSON encoding defined
   in this document, including:
     * The popular `pyang` utility
     * The libyang library

Personnel

   The Shepherd is Kent Watsen.  The AD is Benoit Claise.