Re: [Netconf] Fwd: I-D Action: draft-bierman-netconf-restconf-03.txt

On 6 January 2014 12:49, Andy Bierman <andy@yumaworks.com> wrote:
>
>
>
> On Mon, Jan 6, 2014 at 3:33 AM, Wojciech Dec <wdec.ietf@gmail.com> wrote:
>>
>> Hi Andy, all,
>>
>> are the issues leading to this draft  documented somewhere? The IETF
>> 88 minutes only talk about the yang patch aspect.
>>
>> Anyway, I took a read through the latest document and the change to
>> have all Yang data-nodes be resources. Am I correct in interpreting it
>> that now  every leaf node  effectively becomes a resource with a
>> separate URI? Could the authors provide some more insight regarding
>> this change?
>>
>
>
>
> Since YANG Patch is now optional, there is no way to delete an optional leaf
> or leaf-list otherwise, except to copy the entire resource, and then replace
> the entire resource (minus the optional leaf).

I am still not able to get the full rationale for the change.  Can the
authors or chairs provide that?

Anyway, it now appears that every single data leaf is a resource,
instead of an attribute, and the spec doesn't specify a distinction
between handling parent resources and its sub-resources, e.g. At the
very least POST/PUT operations to sub resources need to be constrained
by their parent resource, and leaving that up to the implementation is
kind of a step backwards for the spec as a whole besides being IMO a
major complication for client or server, and likely both e.g how
should a change to a sub-resource that doesn't meet some condition of
the parent be handled? For a single parent resource, how should
multiple sub-resource changes be coordinated (the parent resource
needs to be consistent)? Etc.

If this current development was driven by questions/problems in the
support of HTTP Patch operation (incl. JSON patch), the solution
appears to be possibly worse than the supposed problem. That's why it
would be good to understand the rationale some more.

>
>
>>
>>
>>
>> An unfortunate characteristic, introduced in -02, that still persists
>> in -03 is the configuration and operational split. But we discussed
>> that on a separate thread....
>
>
> The split is removed. The content query parameter is used to pick
> config, non-config or both.
>
>
Ah, yes, see that now. Glad that email discussion helped.

Thanks.

>>
>>
>> Regards,
>> Wojciech.
>
>
> Andy
>
>>
>>
>> On 21 December 2013 21:26, Andy Bierman <andy@yumaworks.com> wrote:
>> > FYI,
>> >
>> > This version of RESTCONF addresses many of the issues raised at the last
>> > IETF.
>> > See the change log for details.
>> >
>> >
>> > Andy
>> >
>> >
>> > ---------- Forwarded message ----------
>> > From: <internet-drafts@ietf.org>
>> > Date: Sat, Dec 21, 2013 at 12:23 PM
>> > Subject: I-D Action: draft-bierman-netconf-restconf-03.txt
>> > To: i-d-announce@ietf.org
>> >
>> >
>> >
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> > directories.
>> >
>> >
>> >         Title           : RESTCONF Protocol
>> >         Authors         : Andy Bierman
>> >                           Martin Bjorklund
>> >                           Kent Watsen
>> >                           Rex Fernando
>> >         Filename        : draft-bierman-netconf-restconf-03.txt
>> >         Pages           : 95
>> >         Date            : 2013-12-21
>> >
>> > Abstract:
>> >    This document describes a RESTful protocol that provides a
>> >    programmatic interface over HTTP for accessing data defined in YANG,
>> >    using the datastores defined in NETCONF.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-bierman-netconf-restconf/
>> >
>> > There's also a htmlized version available at:
>> > http://tools.ietf.org/html/draft-bierman-netconf-restconf-03
>> >
>> > A diff from the previous version is available at:
>> > http://www.ietf.org/rfcdiff?url2=draft-bierman-netconf-restconf-03
>> >
>> >
>> > Please note that it may take a couple of minutes from the time of
>> > submission
>> > until the htmlized version and diff are available at tools.ietf.org.
>> >
>> > Internet-Drafts are also available by anonymous FTP at:
>> > ftp://ftp.ietf.org/internet-drafts/
>> >
>> > _______________________________________________
>> > I-D-Announce mailing list
>> > I-D-Announce@ietf.org
>> > https://www.ietf.org/mailman/listinfo/i-d-announce
>> > Internet-Draft directories: http://www.ietf.org/shadow.html
>> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> >
>> >
>> > _______________________________________________
>> > Netconf mailing list
>> > Netconf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/netconf
>> >
>
>