[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Design Team for documenting Requirements for Config Mgmt
- To: brian@hursley.ibm.com, khchan@NortelNetworks.com, saperia@mediaone.net, schoenw@ibr.cs.tu-bs.de, mhugh@xpeditio.cnd.hp.com, remoore@us.ibm.com, markstevens@lucent.com, WWeiss@lucentctc.com, scott.hahn@intel.com, herzog@iphighway.com, kzm@cisco.com, rdonkin@orchestream.com, david.durham@intel.com, jseligso@NortelNetworks.com, yoramb@exchange.microsoft.com, slblake@torrentnet.com, jstrassn@cisco.com, Ellesson@raleigh.ibm.com, sob@harvard.edu, fred@cisco.com, randy@psg.com, mleech@nortel.ca, kmn@cisco.com, andrew@extremenetworks.com, timo@bbn.com, vern@ee.lbl.gov, lsanchez@bbn.com, mfine@cisco.com, FranR@iphighway.com, jjr@cabletron.com
- Subject: Design Team for documenting Requirements for Config Mgmt
- From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
- Date: Wed, 22 Sep 99 13:13:55 DST
- cc: mumble@ops.ietf.org
Hi all,
after a few email back and forth between ADs and DT members, we have
come up with a sort fo charter and milestones that will help us
monitor and achieve the goals we discussed last week.
Attached is that charter.
Pls contribute as much as you can, keep an eye on what is happening
and speak up whenever you feel a need. This will help us identify
any issues soon and trigger us to try and work towards solutions.
Pls note, that YOU all are expected to send in any input you may
have ASAP, but no later than October 1st. It must be sent to
mumble@ops.ietf.org
Thanks,
Bert
---------------------------------------------------------------
Design Team for Requirements for Configuration Management
The design team has the following tasks:
1) Write a document that specifies the requirements for
configuration management. This includes reuirements for a
data model, information model, and protocols. The requirments
should be specified such that current/future proposals
can be evaluated.
2) Evaluate (and document such evaluation) the COPS-PR/SoPI
and SNMP/SMI against these requirements.
This task will produce a document that shows how well the
current COPS-PR/SoPI and SNMP/SMI meet those requirements.
In addition, potential changes will be listed to each of
the 2 packages by which they would meet the requirements.
3) Evaluate implementation and deployment costs.
- Cost of implementation
- Time to implement
- Impact on Deployed systems
- Impact on management staffs
Milestones:
20 Sep 99 - Start.
Attendees of meeting send requirements to the mailing
list: mumble@ops.ietf.org
(to subscribe send email to mumble-request@opts.ietf.org
and put the word subscribe in the body)
The sooner everyone sends in requirements, the better.
01 Oct 99 - No more requirements accepted,
08 Oct 99 - or earlier
Design Team (DT) publishes requirements to mumble
list so everyone can check them and comment
15 Oct 99 - or earlier
Design Team (DT) publishes a first cut of the evaluation
to the mumble list so everyone can check and comment
22 Oct 99 - or earlier
Design Team submits document(s) to I-D repository
under the names of:
draft-ops-mumble-<docname>-00.txt
07 Nov 99 - Documents presented/evaluated at 46th IETF in mumble-BOF
(name of BOF to be determined)
Design Team Members:
Luis Sanchez (ipsp) - lsanchez@bbn.com
Jon Saperia (snmp) - saperia@mediaone.net
Keith McCloghrie (cops) - kzm@cisco.com
Design Team Leader: Luis Sanchez
Notes:
- Would be great if Design Team can create/maintain a web page
listing the submitted requirments.(Juergen may be able to
help, he has done so for quite a few other design teams).
- Mailing list and comments are restricted to attendees/invitees
of the "interim policy/rap/diffserv" meeting so as to be able
to be productive and focused.
- There is no discussion of an SNMPv4. We're documenting a set
of requirements and evaluating 2 tool-sets and we have to have
no rumours about a possible SNMPv4.
- The team members can consult with anybody they like on any
items/issues they want/need help with.
- The ADs (and IESG) will evaluate the situation after the 46th
IETF meeting.
Bert