[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposal to do away with netconf attributes in data model payloads
On Tue, Mar 30, 2004 at 01:14:33PM -0800, Andy Bierman wrote:
> Your proposal is essentially the same as above,
> except you removed the <config> container.
> The only reason there aren't any assumptions
> about naming is that there's no naming in your example.
> The data modeling language will have to specify
> how naming is done.
>
> As I pointed out in my previous emails, this approach
> is too simplistic because the agent needs to know the
> specific element sub-tree associated with the edit-action.
> That's why we're using the 'operation' attribute now.
So you are saying naming is defined by the protocol and not by the
data model?
Note that I do not believe that it will be possible to press everything
into a single naming hierarchy. I believe we will see a need for cross
references and hence I would like to filter what I retrieve or select
what I modify not only by specifying a simple path.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>