Re: A few potential requirements

[Eliot Lear <lear@cisco.com>]

Hi,

I've been quiet in this discussion up till now, but August approaches.  As
a vendor, I've got some questions that I hope will be answered in the
requirements:

1.  How shall information be aggregated and represented?
	1a.  Do people want to change the fundamental way they configure
interfaces, BGP, ACLs, etc., or are you happy?  If you're happy we can go
home.

2.  If you want to standardize how to configure interfaces and functions,
how should this differ from SNMP MIBs and the process to create them (for
instance)?

3.  What aspects of configuration should be covered?  Do we need to cover
all "show commands"?  If so, do we shelve SNMP?

4.  Do you want a state description or do you want scripting?  While the
latter may be more powerful, it is a whole lot of rope that makes support
more difficult.  Do you need a scripting capability on the box, or is on
the NMS good enough?

I understand the these questions are contentious.  Perhaps capturing
positives and negatives might be useful, where we bring boxing gloves and
sell tickets to resolve differences in London.

thanks
--
Eliot Lear
lear@cisco.com