Re: [Netconf] netconf-binary-encoding comments

On Fri, Jul 6, 2018 at 2:17 AM, Robert Wilton <rwilton@cisco.com> wrote:

>
>
> On 05/07/2018 17:07, Andy Bierman wrote:
>
> Hi,
>
> I think the first-order issue is for the WG to decide if there is a
> problem to be
> solved by this WG, and if so, what is the problem scope.
>
> +1.
>
> I actually wonder whether extending RESTCONF wouldn't be a more efficient
> path here.  Adding support for CBOR to RESTCONF looks like it would be much
> easier than adding it to NETCONF.
>

of course, because HTTP already supports content-type negotiation.
There is nothing to add to RESTCONF.
You can use other media types than XML or JSON now.

> But then, it is unclear to me what the long term relationship between
> NETCONF and RESTCONF is meant to be.
>
>
Maybe "let the market decide" and not worry about it too much in the IETF

> Thanks,
> Rob
>
>

Andy

>
>
> Details like the SID assignments for rpc, rpc-reply, etc do not really
> impact that decision.
>
> When I brought up this issue 5 years ago there was zero interest in
> improving the
> efficiency of NETCONF. Maybe YANG Push will change that POV.
>
> https://tools.ietf.org/html/draft-bierman-netconf-efficiency-extensions-00
>
> I think this draft should focus on the protocol mechanisms and not define
> any media types. Definitions of GPB and other formats are not trivial and
> need
> their own RFCs.
>
>
> Andy
>
>
> On Thu, Jul 5, 2018 at 8:07 AM, Balazs Lengyel <
> balazs.lengyel@ericsson.com> wrote:
>
>> Hello,
>> Is this applicable for Restconf? Would a Restconf binary encoding be
>> interesting?
>>
>> Chapter 2)
>>
>> - A more detailed explanation of which parts are encoded would be good.
>> What is the top XML element that will be encoded? <rpc>, <RPC-reply>,
>> <RPC-error>, <notification> ? Just referencing a figure in another draft is
>> not enough.
>>
>> - SHOULD, SHALL or SHALL NOT a client server declare support for the XML
>> encoding? Is that always implicit? State it.
>>
>> 4.2) Shouldn't we also have a JSON encoding here?
>>
>> I would think that all encodings need some official reference, defining
>> how they are used with YANG: RFC, web link
>>
>> Is the Thrift and gpb encoding trivial or is it described somewhere or do
>> we need an RFC about it? Please state whichever is the case.
>>
>> regards Balazs
>>
>>
>>
>>
>>
>> --
>> Balazs Lengyel                       Ericsson Hungary Ltd.
>> Senior Specialist
>> Mobile: +36-70-330-7909              email: Balazs..Lengyel@ericsson.com
>> <Balazs.Lengyel@ericsson.com>
>>
>> _______________________________________________
>> Netconf mailing list
>> Netconf@ietf.org
>> https://www.ietf.org/mailman/listinfo/netconf
>>
>
>
>
> _______________________________________________
> Netconf mailing listNetconf@ietf.orghttps://www.ietf.org/mailman/listinfo/netconf
>
>
>