Configuration Management with SNMP (snmpconf)

This Working Group did not meet

NOTE: This charter is a snapshot of the 60th IETF Meeting in San Diego, CA USA. It may now be out-of-date.

Last Modified: 2003-10-21

Chair(s):
Jon Saperia <saperia@jdscons.com>
David Partain <david.partain@ericsson.com>
Operations and Management Area Director(s):
Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Mailing Lists:
General Discussion: snmpconf@snmp.com
To Subscribe: snmpconf-request@snmp.com
In Body: subscribe snmpconf
Archive: snmpconf-request@snmp.com (index snmpconf in body)
Description of Working Group:
The working group will create a Best Current Practices document which outlines the most effective methods for using the SNMP Framework to accomplish configuration management. The scope of the work will include recommendations for device specific as well as network-wide (Policy) configuration. The group is also chartered to write any MIB modules necessary to facilitate configuration management, specifically they will write a MIB module which describes a network entities capabilities and capacities which can be used by management entities making policy decisions at a network level or device specific level.

As a proof of concept, the working group will also write a MIB module which describes management objects for the control of differentiated services policy in coordination with the effort currently taking place in the Differentiated Services Working Group.

Deliverables

1. A Best Current Practices document to provide guidelines on how to best use the existing Internet Standard Management Framework to perform configuration management.

2. A MIB module which describes a network entities capabilities such as support for a particular type of security or a particular queuing method on certain interfaces. The module will also convey the capacity of the device to perform certain work.

3. A MIB module which can be used to concisely convey information about desired network wide Diffserv Based QoS behavior.

4. A document which describes potential future work needed to meet all the Requirements for Configuration Management.

Goals and Milestones:
Done  Announce Working Group and call for Input
Done  Submit Initial Drafts for BCP and MIB Documents
Done  Meet at 47th IETF in Adelaide
Done  Interim Meeting
Done  New Internet Drafts, including a document describing potential future work.
Done  Meet at 48th IETF meeting in Pittsburgh
Done  WG Last Call on remaining Drafts. Submit to AD for consideration as BCP and PS.
Done  Interim Meeting
Done  Revised Drafts for BCP and MIB Documents
Done  Meet at 49th IETF meeting in San Diego
Done  Revised Drafts for BCP and MIB Documents including a document describing potential future work.
Done  Meet at 50th IETF meeting in Minneapolis
Done  WG Last Call Policy MIB Module
Done  WG Last Call Informational Document on SNMP-based Configuration
Done  WG Last Call The Differentiated Services Configuration MIB
Dec 03  Shutdown WG
Internet-Drafts:
  • - draft-ietf-snmpconf-pm-15.txt
  • Request For Comments:
    RFCStatusTitle
    RFC3512 I Configuring Networks and Devices with SNMP
    RFC3747StandardThe Differentiated Services Configuration MIB

    Current Meeting Report

    None received.

    Slides

    None received.