Re: [YANG] insert and key attributes

Andy Bierman writes:
>This is your interpretation of RFC 4741.

Yup, and it's my memory of the WG's repetition of "that's up
to the data modeler".

>The goal of the IETF should be to
>converge on a standard <edit-config> operation, not simply
>codify proprietary CLI with angle brackets.

RFC 4741 did neither of these extremes.  We said explicitly:

5.2.  Data Modeling

   Data modeling and content issues are outside the scope of the NETCONF
   protocol.  An assumption is made that the device's data model is
   well-known to the application and that both parties are aware of
   issues such as the layout, containment, keying, lookup, replacement,
   and management of the data, as well as any other constraints imposed
   by the data model.

   NETCONF carries configuration data inside the <config> element that
   is specific to device's data model.  The protocol treats the contents
   of that element as opaque data.  The device uses capabilities to
   announce the set of data models that the device implements.  The
   capability definition details the operation and constraints imposed
   by data model.

NETCONF gives all power to the data model.  It's an open spec that
allows expandability and evolution.  The goal of the IETF is to
deploy standards that people actually use, and past NM efforts that
have taken this fascist content model have failed due to lack of
flexibility and expressiveness.  NETCONF works hard not to repeat
those mistakes.

The operations in 4741 were not meant to be an exhaustive list that
limits what the DM can do, but to give a normal way to do the few
things that the WG could agree on.  There are many operations that
can only be defined once the data model is known.  YANG defines how
keys are encoded, making it possible to do use "insert" to reorder
lists.  Without lists, keys, and the semantics behind them, you
can't define that operation in any meaningful manner. (Yes, you can
to the "here's a blob to tell you what to move" and "here's a blob
to tell you where to move it", but even these need the data model
to tell you what you can move and where you can move it).

Thanks,
 Phil

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang