CURRENT_MEETING_REPORT_
Reported by Keith McCloghrie/Hughes LAN Systems
IEEE 802.3 Hub MIB Minutes
Since this was the first meeting of the Hub MIB Working Group, the first
item of business was discussion of the Working Group's charter. The
discussion emphasised that the focus would be on development of a
Repeater MIB. The possibility of writing a MIB to represent a modular
chassis containing multiple repeaters/bridges/terminal-servers/etc. was
seen as a potential future work item, depending on the wishes of the NM
Area Director and the Working-Group members, but any such effort would
take second place to the development of the Repeater MIB.
Donna McMaster then gave an overview of how an initial draft of a
Repeater MIB had been produced as a literal translation from the work of
the IEEE Hub Management Task Force's MIB. This draft and a set of
proposed changes had been distributed on the mailing-list. Some of
these had been accepted, and some had been the subject of questions
and/or differing views. Thus, a new draft had been produced having one
section (section 7) documenting its differences from the IEEE MIB, and
another (section 8) documenting the outstanding issues. This draft had
also been distributed to the mailing-list, and submitted as an Internet
Draft.
After a review of the changes made so far, the Working-Group approved
the consensus reached on the mailing-list in agreeing to these changes.
A suggestion was also made to change the names of SelfTest1 and
SelfTest2 to be more descriptive of their function, i.e., non-disruptive
and disruptive, respectively.
The next item on the agenda was discussion of the outstanding issues.
The discussion began with the most fundamental issue: whether or not
the MIB should explicitly allow for an agent managing multiple
repeaters. Various arguments were made for each side of the argument.
Much of the discussion was intertwined with discussion of how to manage
a chassis containing multiple cards (repeaters, bridges, etc.) and
having multiple (separate) LAN segments on its backplane.
Arguments for defining a MIB to manage just one repeater:
o The simple agent is simpler,
o Multiple repeaters can be managed through multiple MIB views,
through proxy, or through multiple agents.
o A single repeater doesn't necessarily (usually?) correspond to an
individual card.
o For consistency with the Bridge-MIB, which manages only one Bridge.
1
Arguments for defining a MIB with the explicit ability to manage
multiple repeaters:
o An agent which manages multiple repeaters is simpler.
o A single repeater doesn't necessarily correspond to an individual
card.
o Consistent with MIB-II's interfaces group.
After much discussion, a straw poll has called and resulted in a 15-15
tie. Regretfully, the meeting decided that the Working-Group would have
to try to resolve the issue on the mailing-list, and if that failed then
to schedule a meeting in the September/October timeframe, possibly at
Interop.
The issue of optional tables was also discussed, and the consensus was
that the distinction between the basic and monitoring groups should be
maintained.
At this point, the meeting ran out of time, and it was agreed to take up
the discussion of the remaining issues on the mailing-list.
Attendees
Steve Bostock steveb@novell.com
Howard Brown brown@ctron.com
Jeffrey Case case@cs.utk.edu
John Cook cook@chipcom.com
Dave Cullerot cullerot@ctron.com
James Davin jrd@ptt.lcs.mit.edu
Gary Ellis garye@hpspd.spd.hp.com
Mike Erlinger mike@mti.com
Bill Fardy fardy@ctron.com
Jeff Fried jmf@relay.proteon.com
Shawn Gallagher gallagher@quiver.enet.dec.com
Phillip Hasse phasse@honchuca-emh8.army.mil
Mark Hoerth mark_hoerth@hp0400.desk.hp.com
Ron Jacoby rj@sgi.com
Mike Janson mjanson@mot.com
Ken Jones konkord!ksj@uunet.uu.net
Frank Kastenholz kasten@europa.clearpoint.com
Manu Kaycee kaycee@trlian.enet.dec.com
Mark Kerestes att!alux2!hawk@uunet.uu.net
Kenneth Key key@cs.utk.edu
Cheryl Krupczak cheryl@cc.gatech.edu
Chao-Yu Liang cliang@synoptics.com
Keith McCloghrie kzm@hls.com
Evan McGinnis bem@3com.com
Donna McMaster mcmaster@synoptics.com
Lynn Monsanto monsanto@eng.sun.com
David Perkins dperkins@synoptics.com
Jason Perreault perreaul@interlan.interlan.com
John Pickens jrp@3com.com
2
Anil Rijsinghani anil@levers.enet.dec.com
Jonathan Saperia saperia@tcpjon.enet.dec.com
Mark Schaefer schaefer@davidsys.com
Anil Singhal nsinghal@hawk.ulowell.edu
Bob Stewart rlstewart@eng.xyplex.com
Emil Sturniolo emil@dss.com
Bruce Taber taber@interlan.com
Geoffrey Thompson thompson@synoptics.com
Dean Throop throop@dg-rtp.dg.com
Steven Waldbusser waldbusser@andrew.cmu.edu
Philip C. Wang watadn!phil@uunet.uu.net
Drew Wansley dwansley@secola.columbia.ncr.com
David Ward dward@chipcom.com
Joseph Zur fibrontics!zur@uunet.uu.net
3