Re: Separation of protocol and information model

[Phil Shafer <phil@juniper.net>]

Bobby Krupczak writes:
>Interesting; however, the vipw program has to use linked code that has
>intimate details of the file structure and code that converts that
>code into an in-memory structure.

I don't follow you here; are you talking about pw_mkdb()? This is
the equivalent of <commit-configuration/> in the netconf case, since
pw_mkdb checks the data and parcels it out to the rest of the system.
In the netconf case, the code invokes a series of RPC to the device.

>It is at this crucial boundary that the protocol, API, and data-model
>become so intertwined and getting them just right is oh so difficult.

Yup, but I think the netconf draft gets it pretty much right.  Dividing
the configuration content from the things one needs to do with that
data is goodness.

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