subelements

[Johan Rydberg <johan.rydberg@edgeware.tv>]

While working on my data model I encountered a small design problem, and
decided to look what NETCONF normally do in these situations.  This made
me think about a thing that I've always thought was odd:

Why are configurations named with an subelements of <source> or <target>
and not text payload of the element?  This should make it impossible to
have a configuration named "config", for example.

What is the standard way of refering to units in NETCONF? via named
subelements, via reference elements (<store-ref name="running"/>) or via
text?  What was the idea and reason behind using named subelements for
the wire protocol?

Or is the idea that if you want more configurations than those the RFC
mention (running, startup, candidate) you must implement the URL
capability?



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>