Subject: Re: [Netconf] yang-push issue: encoding

From: "Eric Voit (evoit)" <[email-masked]>
Date: Fri, 1 Dec 2017 14:47:09 +0000

Agree.  Martin caught this too.  This sentence has been removed in the working copy of the draft.

Eric

From: Netconf [mailto:[email-masked]] On Behalf Of Andy Bierman
Sent: Thursday, November 30, 2017 7:29 PM
To: Netconf <[email-masked]>
Subject: [Netconf] yang-push issue: encoding

Hi,

In yang-push-11:

3.5<https://tools.ietf.org/html/draft-ietf-netconf-yang-push-11#section-3.5>.  Data Encodings

   A publisher MUST support XML encoding and MAY support other encodings

   such as JSON encoding.

I do not think this draft should mention encoding.
It is up to the protocol to specify message encoding rules.
The NETCONF protocol supports XML only.
RESTCONF uses Accept and Content-Type headers to determine the encoding.
CoMI will use CBOR for YANG-encoded data.

Andy