Re: [YANG] insert and key attributes

Martin Bjorklund wrote:
> Andy Bierman <ietf@andybierman.com> wrote:
>> How is a manager supposed to know that the agent uses the "-00 YANG"
>> version of the NETCONF protocol, vs. the "-01 YANG" version
>> vs. "RFC 4741 NETCONF"?
> 
> If the manager knows the datamodel, then it knows how to manipulate an
> ordered-by user list; it also knows which element(s) are keys, how
> they are encoded to XML etc.
> 

IMO, it is important to separate the data modeling language
from the protocol, and to keep the NETCONF protocol as DML-neutral
as possible.

It doesn't seem like a good idea for interoperability to
have one flavor of NETCONF if the vendor uses YANG data models
and another if the vendor uses XSD or RelaxNG.  Even worse,
what if the vendor publishes some modules as YANG, others
as XSD, and there are different flavors of NETCONF within
the same agent.

Note that error-app-tag and error-message are not extensions
to the protocol at all -- they simply specify values for
fields already defined in <rpc-error>.

But the key and insert attributes change the behavior of
the <edit-config> operation.  It doesn't matter that they
change it for the better, by adding support for user-ordered lists.
What matters is that a standard protocol needs to be changed
by a WG, and should be done in a way that is not specific
to one particular DML.

> 
> /martin
> 
> 

Andy

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