Re: Separation of protocol and information model

[Phil Shafer <phil@juniper.net>]

"Chen, Weijing" writes:
>In the everyday life of operating
>network, making the correct change of configuration is much harder than
>shipping the change to device. 

Right, so we're doing the simple problem first, then the hard problem(s)
later.  The immediate need it to make a robust Expect-free mechanism
for manipulating configuration data on a device.  The data model for
the contents of that configuration come later.

Thanks,
 Phil

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