Re: Thoughts on NetConf Requirements

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Hunkins, Andrew" <ahunkins@unimax.com>
> To: "Andy Bierman" <abierman@cisco.com>
> Cc: <netconf@ops.ietf.org>
> Sent: Thursday, June 12, 2003 1:40 PM
> Subject: RE: Thoughts on NetConf Requirements
...
> 3. My definition of the management & sync layer is a *programmable*
> layer that is tuned to fit the business rules of a particular site.  It
> includes complex scheduling procedures and semantic relations across
> multiple devices of disparate purposes.  xmlconf has none of this.  It
> sounds like these are clearly placed in the hands of an xmlconf client
> application.  Am I missing something?
...

Such programmability is tied to the choice of an information model,
at least for defining how one sets up schedules and rules, and how
one names the objects to be manipulated.  The snmpconf and disman
WGs have covered some of this functionality for SNMP.

However,
I haven't seen any substantive discussion on either WG's mailing
list of the prospects for doing netconf-supportive work.  As disman
WG chair, I'd welcome such a discussion, but am not trying to
stake any "turf" here, and am open-minded regarding the question
of what existing (or new) WG might be an appropriate forum
for actually doing such work.

Randy



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