Re: Proposal to do away with netconf attributes in data model payloads

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Wed, Mar 31, 2004 at 03:54:49PM -0800, Andy Bierman wrote:
 
> Look at this encoding:
>   
> <modify>
>   <target xmlns="http://example.com/xsd/foo.1";>
>    /chassis/slots/slot[@instance-id='3']/ports/port[@instance-id='7']/duplex-mode
>   </target>
>   <value>auto</value>
> </modify>
> <create>
>  <target xmlns="http://example.com/xsd/foo.1";>
>   /chassis/slots/slot[@instance-id='3']/ports/port[@instance-id='7']/filters/ip-filters/ip-filter[@instance-id='1']
>   </target>
>   <value>
>     <action>permit</action>
>     <direction>both</direction>
>     <address>
>       <addr-type>ipv4</addr-type>
>       <addr>192.168.1.1</addr>
>     </address>
>   </value>
> </create>

This is more or less what I have in mind and what I prefer to do. Note
that this approach does not dictate how naming is actually done (as
long as you can express it in xpath).
 
> I think this was suggested already on the mailing list.
> IMO, if Xpath is supported, it's a much more efficient encoding
> than what we have now.  But I don't want to make Xpath mandatory.

I believe that the main market for initial netconf deployment are 
operator networks and they run boxes that should be capable to do 
xpath processing. Once netconf is successful in this market and 
operators/administrators like it, smaller boxes will start to 
support it because there is a customer demand. If netconf does 
not take off in this market, then we have failed anyway and the
whole issue becomes a mood point.

/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/>