IETF NM Area Report

[Deirdre Kostick <[e-mail]>]

IETF NETWORK MANAGEMENT AREA REPORT (June, 1995)

This report provides a status of current activities 
in the IETF Network Management Area, 
including a summary of current working group (WG) policy 
and NM Area Director disclosure information.

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: 		none
This is a new WG chartered to develop a set of managed 
objects for IEEE802.12 network interfaces and repeaters. 
Needs to coordinate modelling efforts with the hubmib WG 802.3 
repeater MIB efforts .

AToM MIB (atommib)
	Chair: 		Kaj Tesink ([e-mail])
	Consultant:	Keith McCloghrie ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1695 (proposed standard)
The WG re-activated in 4/95.

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.

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)

The WG is eligible to re-activate.

Data Link Switching  MIB (dlswmib)
	Chair: 		Shannon Nix ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none

The WG started in 3/95; chartered to identify managed 
objects for Data Link Switching.

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

WG is eligible to reactivate.

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)
The WG is scheduled to re-activate after Stockholm. 
Needs to coordinate with output of Interfaces MIB modelling effort.

Host Resources MIB (hostmib)
	Chair: 		Steven Waldbusser (tbd)
	Mailing List:	[e-mail]
	To Join::	[e-mail]
	RFC: 		RFC1514 (proposed standard)
The WG is eligible to reactivate.

IEEE 802.3 Hub MIB (hubmib)
	Chair: 		Donna McMaster ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1516 (draft standard)
The WG has reactivated; 
the Chair is soliciting implementation experience.
The WG will expand its scope to include 100BaseT and MAU modelling.

Interfaces MIB (ifmib)
	Chair: 		Ted Brunner ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1573 (proposed standard)
			RFC1748-9
The WG recently re-activated to review RFC1573. 
Chair soliciting implementation experience.
Meeting at Stockholm IETF.

ISDN MIB (isdnmib)
	Chair: 		Ed Alcoff ([e-mail])
	Consultant:	Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		none
The WG is newly chartered to identify managed objects for 
ISDN type interfaces. Meeting at Stockholm IETF.

Mail and Directory Management MIB (madman)
	Chair: 		Steve Kille (S. [e-mail])
	Consultant:	Marshall Rose ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail] 
                        (body: subscribe ietf-madman)
	RFC: 		RFC1565-1567 (proposed standard)
The WG is eligible to reactivate.

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

Printer MIB (printmib)
	Chair: 		Joel Gyllenskog ([e-mail])
	Consultant:	Steven Waldbusser (tbd)
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1759 (proposed standard)
The WG is considering clarification of some objects 
in the recently published RFC.

RDBMS MIB (rdbmsmib)
	Chair: 		Robert Purvey ([e-mail])
	Consultant:	Marshall Rose ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1697 (proposed standard)
The WG is eligible to reactivate.

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


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

The WG is completing an APPC MIB.

SNMPv2 (snmpv2)
	Chair: 		Bob Stewart ([e-mail])
	Mailing List:	[e-mail]
	Mailing List:	[e-mail]
	RFC: 		SNMPv2 series (proposed standard)
The WG is evaluating the recently completed set of SNMPv2 IDs.

Trunk MIB (trunkmib)
	Chair: 		Fred Baker ([e-mail])
	Mailing List:	[e-mail]
	Mailing List:	[e-mail]
	RFC: 		RFC1406, 1407 (proposed standard)
The WG is re-activated and will meet in Stockholm.
The DS1/DS3 mib design needs to reflect the revised RFC1573 work 
(see interfaces mib).
SONET MIB also eligible for review.

Uninterruptible Power Supply MIB (upsmib)
	Chair: 		Jeff Case ([e-mail])
	Mailing List:	[e-mail]
	To Join:	[e-mail]
	RFC: 		RFC1628 (proposed standard)
The WG is currently reviewing RFC1628 via email discussion.

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

Open WG Requests
-----------------

o  Distributed Management MIB (distman): 
   Formation of working group okayed pending 
   conclusion of SNMPv2 work and identification of workable 
   scope and model. Mailing list to be announced.

o  Entity MIB : BOF scheduled for Stockholm IETF. 
   Contact is Keith McCloghrie ([e-mail])

o  RAID MIB: Current Status: No advisor currently available.

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 the mailing list, 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. 
Current consultants are the members of the NM Area Directorate. 
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 theres 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 is 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 final call on formation 
of Working Groups. 
 
NM AREA DIRECTORATE
-------------------

Membership:

	Fred Baker (cisco.com)
	Ted Brunner ([e-mail])
	Jeff Case ([e-mail])
	Keith McCloghrie ([e-mail])
	Donna McMaster ([e-mail])
	Marshall Rose ([e-mail])
	Bob Stewart ([e-mail])
	Kaj Tesink ([e-mail])
	Steve Waldbusser (need new addr)

STATEMENT OF DISCLOSURE
-----------------------

On May 1, 1995 I joined AT&T Bell Labs. I have a few shares of 
Pacific Bell and Bell Atlantic, & expect to be buying some AT&T stock. 
I receive a tiny, tiny royalty for writing a few pages in 
a book on internetworking.


Deirdre C. Kostick
IETF NM Area Director