[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Goals for netconf - moving towards the charter description



Ran,

Thank you for the clarification.  According to your opinion that netconf
will not address inventory mgmt nor fault configuration.  But they are
part of the configuration file for the IP device as well (or not? I may
be wrong in assuming what do you mean by an IP device) and how are we
going to address the need to bring up the configuration of an IP device
at reboot time where the fault manipulation by the device requires
re-configuration?  

As for the question regarding diag/testing for the IP device, don't
people use 'ping' or 'traceroute' to do diag/testing all the time?  

-faye

-----Original Message-----
From: RJ Atkinson [mailto:rja@extremenetworks.com] 
Sent: Monday, March 24, 2003 5:41 AM
To: Faye Ly
Cc: Eliot Lear; Andy Bierman; xmlconf@ops.ietf.org
Subject: Re: Goals for netconf - moving towards the charter description


On Sunday, Mar 23, 2003, at 21:12 America/Montreal, Faye Ly wrote:
> 1. Inventory configuration management

Not the focus.

> 2. Fault configuration management (threshold etc)

Not the focus, though might be included (e.g. SNMP Trap collectors
might be configured using proprietary XML moved around by the mechanism
being discussed here).

> 3. Other configuration that involves testing/diagnostic configuration
> and monitoring.

I have no clue what you mean in (3.) above.

And what you've missed is that our focus is on IP-centric devices, IMHO.

Ran
rja@extremenetworks.com


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>