Network Management Area

Director:


   o Deirdre C. Kostick:  kostick@qsun.att.com


Area Summary reported by Deirdre C. Kostick/AT&T Bell Labs

Six active working groups, one BOF, and an Open Meeting were held in the
Network Management Area during the Stockholm, Sweden IETF meeting.


Network Management Area Open Meeting (NMAREA)

Agenda items for Wednesday's meeting included:


   o IETF Network Management Area Highlights -- Deirdre Kostick, Network
     Management Area Director, reviewed the status of work efforts in
     the Network Management Area, including active working groups,
     working groups eligible to reactivate, and pending working group
     requests.

   o SNMPv2 Working Group Status Report -- Bob Stewart, SNMPv2 Working
     Group chair, reviewed the status of the SNMPv2 Working Group and
     the current schedule.

   o SNMPv2 Working Group Proposal Summaries -- Bert Wijnen, Uri
     Blumenthal, and Keith McCloghrie.  The Network Management Area
     Director had invited SNMPv2 Working Group participants that had
     indicated an intent to make a proposal, to make brief informational
     presentations on their proposals.  Since this was not an SNMPv2
     Working Group meeting and not all participants with proposals were
     available, there was no discussion of the proposals during the
     meeting, per the direction of the Area Director.

   o General SNMP Issues -- David Perkins presented his views on SNMPv2.


Entity MIB BOF (ENTMIB)

Two presentations were made during the Entity MIB BOF: one discussed the
motivation and potential requirements which an Entity MIB would address;
the second discussed a proposed solution in terms of a specific MIB.

The discussions delved into the details of the specific requirements and
the proposed solution.  The conclusion was that there is community
interest in working on standardizing such a MIB, and that the Network
Management Area Director should be requested to establish a working
group with this goal.

Note:  The Area Director approved formation of this working group, and
will forward the request to the IESG upon receipt of a draft charter.



AToM MIB Working Group (ATOMMIB)

The AToM MIB Working Group met to review the current Supplemental ATM
MIB Internet-Draft and resolve open issues.  Also discussed was the ATM
Textual Conventions MIB which has been drafted and posted.  Seven
implementation reports were presented on the current AToM MIB, RFC 1695.
After completion of the supplemental ATM MIB, the working group will use
this implementation feedback towards consideration of elevation of
RFC 1695 to Draft Standard.



DS1/DS3 MIB Working Group (TRUNKMIB)

The Trunk MIB Working Group met to discuss implementation experience
with RFCs 1406/1407, comments on the list, and the applicability of
RFC 1573.  There were 16 small issues, which were dealt with readily.

One large issue dealt with the Totals Table; in proxy situations, there
are conditions where it might not adequately represent the device being
managed.  This will be discussed on the list, and may result in
explanatory text or the deprecation of the table.

Another dealt with the Fractional Table; RFC 1573's Stack Table offers a
replacement that may be more easily understood and dealt with.  Coupled
with needs for circuit (DS0) configuration, James Watt took an action to
talk with several vendors and make a concrete proposal.



IEEE 802.3 Hub MIB Working Group (HUBMIB)

The Working Group reviewed implementation experience for RFC 1516 and
RFC 1514.  The consensus of the participants was that the majority of
the objects were useful for management of 802.3 repeaters; however,
there are problems with the indexation used in RFC 1516.  For example,
participants identified the need to support multiple repeaters and
implementations of repeaters in modular or stackable hubs with several
segments.

Jeff Johnson presented a proposal for a ``Generic/Real Hub'' MIB model
that would correct the indexing problem.  The Working Group decided to
incorporate this work in their modelling efforts.



Interfaces MIB Working Group (IFMIB)

The Interfaces MIB Working Group reviewed implementation experience and
issues related to RFC 1573.



ISDN MIB Working Group (ISDNMIB)

The ISDN MIB Working Group is currently working on an ISDN MIB and a
Call Control (or ``Dial'') MIB. Several issues with the application of
the Interfaces MIB, RFC 1573, for modelling the stack/layering for ISDN
interfaces were resolved.  The PRI-related objects of the ISDN MIB will
be coordinated with the DS1 MIB (RFC 1406) objects.



Remote Network Monitoring Working Group (RMONMIB)

The RMON Working Group met to finalize details to the RMON-2 MIB
specification under development.  Several open issues were identified
and discussed.  The set of RMON-2 deliverables will consist of two
documents:


   o RMON-2 MIB -- RMON-1 additions, RMON-2 objects, RMON Probe
     Configuration; will be structured as 3 MIBs within one document.

   o Protocol Directory Identifiers -- protocolDirID octet string
     values; also contains other protocolDirectory fields for
     `well-known' protocols.


Discussion topics:


   o Protocol Directory Definition Document
   o Filter and Channel Extensions
   o Textual Conventions fixup
   o Rationale Statements
   o RMON-1 Additions
   o Counting `other' packets
   o DataSource table
   o Performance Metrics table for Application Matrix
   o Conformance statements
   o Switch monitoring
   o alMatrixTopN table broken
   o Conversation buddies in *Matrix tables
   o BOOTP Mode in Config MIB
   o Counting error packets
   o protocolDirectory lastChanged mechanism
   o Agent behavior when control entries deleted
   o TimeFilter TC clarification