NM Area Summary

[Deirdre Kostick <[e-mail]>]

IETF NETWORK MANAGEMENT AREA REPORT (December, 1996)

This report provides a status of current activities in the IETF Network
Management Area; and summary of current working group (WG) policy. As
discussed at the last IETF, the IETF Network Management and Operations
Areas will be merged to form a new Operations and Management Area. The
IESG is working on the assignment of the NM Area WGs to the
appropriate IETF Areas; the re-organization is planned to be effective
by the next IETF meeting in April, 1997.

Working Group Summary
----------------------


100BaseT MIB (see hubmib)

100VG MIB (vgmib)
	Chair: 		Jeff Johnson (jjohnson@cisco. com)
	Consultant:	Kaj Tesink ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC2020 - Proposed Standard 
                        (IEEE 802.12-type Interfaces MIB)

STATUS: Completed Definitions of Managed Objects
for IEEE 802.12 Interfaces. Definitions of Managed Objects
for IEEE 802.12 Repeater Devices in final draft;
ready for submission to Area Director for review.
 

Agent Extensibility (agentx)
	Chair: 		Bob Natale ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none


STATUS: Working group active.  Three work items:
1. platform-independent protocol 
2. MIB to monitor intra-agent communication (opt.)
3. programmatic interface to the services (opt.)


Application MIB (applmib)
	Chairs: 	Cheryl Krupczak ([e-mail])
                        Jon Saperia ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none


STATUS: Working group active. Final draft of the
System Application MIB under NM Area review. The next work
items are: the Application Management MIB and the WWW MIB.



AToM MIB (atommib)
	Chair: 		Kaj Tesink ([e-mail])
	Consultant:	Keith McCloghrie ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1695 (ATM MIB - proposed standard)
                        RFC1595 (SONET MIB -proposed standard)

Current work items:

1. Definitions of Supplemental managed Objects for ATM
   Management (open)
2. Definitions of Textual Conventions and OBJECT-IDENTITIES
   for ATM Management (changes to current I-D, expect to wrap
   up in 2/97). 
3. Definitions of Tests for ATM Management. 
   Extension in ifmib and ATM-specific objects. New draft pending, no
technical
   open issues. Candidate for Proposed.
4. Managed Objects for Controlling the Collection and
   Storage of Accounting Information for Connection-Oriented
   Networks. No open technical issues, final draft pending.
5. Definitions of Managed Objects for ATM Management 
   (RFC1695 update), final I-D pending -- to be forwarded for NM Area
review in
   1/97.
6. Definitions of Managed Objects for SONET/SDH Interface Type.
7. Accounting Information for ATM Networks.No open technical 
   issues, final draft pending.
8. Managed Objects for Recording ATM Performance History
   Data Based on 15 minute intervals (open)
9. Textual Conventions for MIB Modules Using Performance 
   History - under NM Area review

STATUS: Active


Bridge MIB (bridge)
	Chair: 		Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1493 (draft standard)
			RFC1525 (proposed standard)

Chair soliciting implementation experience and feedback.

STATUS: Still pending implementation experience. Drafts have
expired.


Character MIB (charmib)
	Chair: 		Bob Stewart ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1658 (draft standard)
			RFC1659 (draft standard)
			RFC1660 (draft standard)

STATUS: The WG is eligible to re-activate.


DECnet Phase IV  MIB (decnetiv)
	Chair: 		Jon Saperia ([e-mail])
	Mailing List:	[e-mail] 
	To Join :	[e-mail]
	RFC: 		RFC1559 (draft standard)
STATUS: The WG is eligible to re-activate.

Distributed Management (disman)
	Chair: 		Maria Greene ([e-mail])
	To Join :	[e-mail]
	RFC: 		none

STATUS: Active. Documents under development are:
1. Threshold Monitoring MIB
2. Script MIB
3. Distributed Management Framework Descriptions and MIB



DLSw MIB (dlswmib)
	Chair: 		Shannon Nix ([e-mail])
	To Join :	[e-mail]
	RFC: 		RFC2024 (Proposed Standard)

STATUS: Inactive.



Entity MIB (entity)
	Chair: 		Keith McCloghrie ([e-mail])
	Mailing List:	[e-mail]
	To Join :	[e-mail]
	RFC: 		RFC2037 (Proposed Standard)


STATUS: Inactive.

	
FDDI MIB (fddimib)
	Chair: 		Anil Rijsinghani ([e-mail]) 
	Mailing List:	[e-mail] 
	To Join:	[e-mail]
	RFC:		RFC1285 (proposed standard)
			RFC1512 (proposed standard)

STATUS: ID under review for Draft status.


Frame Relay Service MIB (frnetmib)
	Chair: 		James Watt ([e-mail])
	Consultant:	Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1604 (proposed standard)

STATUS: Active. Work in progress includes:
1. Review of RFC1604 for consideration for progression to
Draft Standard. Inputs include implementation experience,
changes to IFMIB, DS1, DS3, FR-DTE, DS0 and DS0-bundle groups.
2. Definition of managed objects for FR DTE SVCs.
3. Definition of managed objects to provide instrumentation
required to manage connections that terminate a mixture of
ATM and FR interfaces (also called the Interworking MIB).
4. Definition of a small number of managed objects for 
recent FR Forum Implementation Agreements for DTEs.



Host Resources MIB (hostmib)
	Chair: 		Steven Waldbusser ([e-mail])
	Mailing List:	[e-mail]
	To Join::	[e-mail]
	RFC: 		RFC1514 (proposed standard)

STATUS: The WG is eligible to reactivate.


IEEE 802.3 Hub MIB (hubmib)
	Chair: 		Dan Romanescu ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1516 (draft standard)
                        RFC1515 (proposed standard)

STATUS: 2 MIBs under review; hubmib approved. Set includes:
1. Definitions of objects for IEEE 802.3 MAUs
2. Definitions of objects for IEEE 802.3 Repeater devices
3. Definitions of objects for Ethernet-like Interface Types


Interfaces MIB (ifmib)
	Chair: 		Ted Brunner ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1573 Evolution of Interfaces Group
                                (proposed standard)
                        RFC1623 Ethernet-like Interfaces
                        RFC1643 Ethernet-like Interfaces - v2
                        RFC1694 SMDS
			RFC1743 IEEE 802.5 MIB -v2
                        RFC1748 IEEE 802.5 MIB -v2
                        RFC1749 IEEE 802.5 Station Source Routing
                        

STATUS: Interfaces Group I-D finalized.


ISDN MIB (isdnmib)
	Chair: 		Ed Alcoff ([e-mail])
	Consultant:	Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none

STATUS: I-Ds under 2nd last call. Work includes:
1. ISDN Management Information Base
2. Dial Control Management Information Base


Mail and Directory Management MIB (madman)
	Chair: 		Steve Kille ([e-mail])
	Consultant:	Jon Saperia ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail] (body: subscribe ietf-madman”)
	RFC: 		RFC1565-1567 (proposed standard)

STATUS: Moved to Applications Area.

Modem Management (modemmgt)
	Chair: 		Mark S. Lewis ([e-mail])
	Consultant:	Steven Waldbusser 
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1696 (proposed standard)
The WG is eligible to reactivate.

Physical Topology MIB (ptopomib)
        Chair:          Ken Jones ([e-mail])
	Consultant:	Andy Bierman
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none

STATUS: New. Goals are to:
1. Agree on and document the common framework/model for
discussing physical topology.
2. Identify a set of managed objects providing phyical topology
3. Media-specific mechanisms to communicate topology information


Printer MIB (printmib)
	Chairs: 	Chris Wellens ([e-mail])
                        Lloyd Young ([e-mail])
	Consultant:	
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1759 (proposed standard)

STATUS: Re-activated. May add job monitoring to the scope.

RDBMS MIB (rdbmsmib)
	Chair: 		Robert Purvey ([e-mail])
	Consultant:	
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1697 (proposed standard)

The WG is eligible to reactivate.
STATUS: The WG is eligible to reactivate.

RMON MIB (rmonmib)
	Chair: 		Andy Bierman ([e-mail])
	Consultant:	Steve Waldbusser
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1271
                        RFC1757
                        RMON2 MIB (proposed standard)


STATUS:ACTIVE


SNA DLC Services MIB (snadlcmib)
	Chair: 		Shannon Nix ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1747 (proposed standard)

STATUS: Active. Working on LLC MIB.


SNA NAU Services MIB (snanaumib)
	Chair: 		Bill Kwan ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1666 SNA NAU MIB (proposed standard)
                        RFC2051  APPC MIB (proposed standard)

STATUS: Active. Working on: APPN, DLUR, and HPR MIBs.


SNMPng (Formerly snmpv2)
	Chair: 		Russ Mundy ([e-mail])
	Mailing List:	[e-mail]
	Mailing List:	[e-mail]
	RFC: 		SNMPv2 series (draft standard)

STATUS: Eligible to reactivate. New draft charter due end of 1/97.


Trunk MIB (trunkmib)
	Chair: 		Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	Mailing List:	[e-mail]
	RFC: 		RFC1406, 1407 (proposed standard)

STATUS: WG Chair soliticing implementation experience. Needs feedback
on the far-end tables for DS1 & DS3 MIBs. DS0 MIBS have been reviewed. 


Uninterruptible Power Supply MIB (upsmib)
	Chair: 		Jeff Case ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1628 (proposed standard)

STATUS: Active.


X.25 MIB (x25mib)
	Chair: 		Dean Throop ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1461 (proposed standard)

STATUS: Eligible to reactivate


Open WG Requests

IPv6 MIB -- need to assign directorate review to get recommendation;
need
stable IPv6 address format. Private MIB posted.

Web-based Management -- need to articulate scope. 
Internet-drafts posted.

General WG Policy

A working group meeting is NOT required when a MIB document is up for
review processing 
through the standards cycle. If changes are minor & implementation
experience input can be 
solicited via mailing list discussion, working group reactivation should
only be via the mailing list.

For formation of a new working group:

1. Check whether or not an existing WG is working with that technology.
If not, then you will 
need to have an advisor/consultant. Consultants are experienced members
of the NM Area 
NM Area. Request the list from the Area Director.
2. Find a directorate member who is willing to advise you during the
initial stages (e.g., setting up 
a BOF). If no directorate member is available, then no WG is formed.
Else continue.
3. Work with your advisor to understand what is invovled in setting up a
working group. For 
example, you need the following:  a chair that preferably has some
experience in IETF, a 
document editor, a mailing list, an archive site, and a community of
interested participants. 
Work with your advisor to determine if there is an initial sufficient
support and commitment to 
continue. If there is, ask your advisor to confer with the AD about
proceeding (Issues the AD 
will consider include available resources.)
4. If you, the Advisor, and the AD determine that there is sufficient
interest, set up the new 
mailing list. (It can be announced on the general SNMP list.)
5. If there’s sufficient interest expressed via the mail list, request a
BOF via your Advisor. You’ll 
need someone to chair the BOF, work out an agenda, etc. This person does
not necessarily 
have to be the Chair of the working group. Report results to the Advisor
and Area Director.
6. If there’s sufficient interest, you need to develop a Charter. Ask
your Advisor for a sample. 
This will be forwarded to the AD for review and then to the IESG for
approval. The IESG, not 
the AD, makes the call on formation of Working Groups. (Also see
RFC1602.)
 
NM AREA DIRECTORATE/REVIEWERS

Membership:

	Fred Baker 
	Ted Brunner 
	Jeff Case 
        Kathy deGraaf
        Maria Greene
        Cheryl Krupczak
        Jeff Johnson
	Keith McCloghrie 
        Marshall Rose
        Jon Saperia
	Bob Stewart 
	Kaj Tesink 
	Steve Waldbusser
        James Watt
        Bert Wijnen
        Chris Wellens



Deirdre C. Kostick
IETF NM Area Director