RE: Thoughts on NetConf Requirements

["Hunkins, Andrew" <ahunkins@unimax.com>]

Okay, that helps.

I've always taken a strict view of the OSI management areas, FCAPS:
Fault, Configuration, Accounting, Performance and Security.  The xmlconf
and netconf led me to believe that the group was going to tackle a
common interface for Configuration.  Much needed!

I know people complain about SNMP, but there are so many efforts to
improve it.  I did not think this was one of them.

Any interest in applying it to configuration and leaving SNMP to support
fault and performance?

-Andrew


> -----Original Message-----
> From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> Sent: Thursday, June 12, 2003 4:01 PM
> To: netconf@ops.ietf.org
> Subject: Re: Thoughts on NetConf Requirements
> 
> 
> 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
> ...
> > 1. The document says multiple requester/consumers are 
> communicating with
> > the device/server.  Terms include: "CLI", "native 
> interface", "SNMP",
> > "expect scripts", "human users" and xmlconf clients themselves.
> > Assuming xmlconf is there, then shouldn't all these 
> non-xmlconf clients
> > be built on top of xmlconf?  (If so, can we eliminate these 
> others and
> > just declare that all clients must use xmlconf?)  If not, 
> why?  If the
> ...
> 
> The working assumption so far seems to be that the set of information
> accessible via xmlconf would intersect the set of information 
> accessible
> via SNMP, but would be neither a subset nor a superset of it.  If this
> assumption remains true, then it doesn't make sense to strictly
> "layer" them, although a particular implementation might do this
> for specific pieces of information.
> 
> 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/>
> 

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