On Mon, Nov 02, 2015 at 09:03:46AM +0900, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Thu, Oct 29, 2015 at 01:17:56PM +0100, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > > > Hi,
> > > >
> > > > the issues Y09 and Y57 were declared dead after intense discussions of
> > > > various solution proposals. It later appeared to me that there is a
> > > > solution that we have not considered. The requirement to have a key
> > > > for every list and unique values in a leaf-list for config nodes is
> > > > essentially there to allow edits on individual elements using
> > > > edit-config. The solution not considered so far is simply to give up
> > > > the ability to edit invidual elements, that is, a config list without
> > > > a key can only be modified as whole and similarily a leaf-list that
> > > > allows non-unique values can only be modified as a whole (with
> > > > edit-config). Comments?
> > >
> > > How would this look in edit-config? There are quite a few details to
> > > think through in order to support this.
> > >
> >
> > Why would that be complicated for edit-config? This key-less list
> > would essentially be anyxml with a known structure. You likely do not
> > allow edit-config specific attributes on all of them.
>
> For anyxml/anydata, there is a surrounding container that contains the
> "blob":
>
> anydata foo;
>
> <foo>
> <blah>
> <blaha>goo</blaha>
> </blah>
> </foo>
>
> but with a list, the entries are encoded w/o any surrounding tag:
>
> list foo { ... }
>
> <foo>
> // entry 1
> </foo>
> <foo>
> // entry 2
> </foo>
>
And the consequence of this is?
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
