CURRENT_MEETING_REPORT_

Reported by Deirdre Kostick/Bellcore

Minutes of the SNA NAU Services MIB Working Group (SNANAU)

The SNANAU Working Group met on July 14 to review the proposed SNA NAU
MIB draft distributed to the mailing list on June 30.



Changes To MIB Draft

There was a lack of feedback on the MIB draft via the mailing list.
This, as well as the need to get feedback, was discussed.

1) Removal of the snaGate group.

Defining objects for management of an SNA Gateway is outside the initial 
scope of the working group's charter. The snaGate group will be removed 
from the current mib draft. The working group will be polled to determine 
the interest in and need for a snaGate mib module.

2) Downstream PU group.

It was recommended that the downstream PU objects be removed from the 
current draft since these objects are more applicable to an SNA Gateway. 
These objects are candidates for inclusion in an snaGate module.

3) Response Time Monitoring objects.

These objects represent the statistics used to monitor terminal session 
response time characteristics.  The RTM objects will be moved from the snaLU
group and moved to a new group, snaMgtTools.  The intent of the snaMgtTools 
group is to provide objects to support currently used LU/PU management 
applications/tools.

Working group input is needed to identify additional functions should be 
supported in this new group.

4) snaLUState Table

The snaLuStateUser*  and 
snaPuStateUser* objects (UserName, UserState, and UserMacAddress) will be 
deleted. These objects are candidates for a snaGateway mib module.

5) snaLuStateLastDataExchange and 
snalPuStateLastDataExchange objects

These objects will be removed since the information is available in the 
snaLuStats and snaPuStats tables.

6) Timeticks/sysUpTime

The wording for objects reflecting counts measured from agent startup time 
will be changed/clarified to indicate the use of sysUpTime.

7) OID Branch

There was discussion on the need for an experimental branch number assignment 
for the snanaumib.  (Dave Perkins will follow-up.)

8) Row Creation

The current draft of the mib supports the capability to create PU and LU 
instances via SNMP Set-Requests. There is a concern that the capability to 
dynamically create PU/LUs is not generally supported.

Two alternatives were discussed:

a) remove the Row-Status objects, supporting a read-only capability,
b) specifying the Read/Write access as an optional, not mandatory capability. 
   Exactly how we can specify alternative "b" needs to be investigated.
   (Dave Perkins will follow-up on this.)

9) sna802dot2..snaQllc...

The objects which refer to underlying link protocols
are subject to change pending on the structures of the
DLC MIB.


Interim Meeting

An interim meeting may be scheduled to coincide with the APPN
Implementor's Workshop (AIW) in September.  The purpose of the interim
meeting will be to review the planned Internet-Draft and to increase
exposure of the MIB to encourage more feedback from the SNA community.



Action Item Summary


   o The working group will be polled to determine if there is interest
     in having an interim meeting.

   o The working group will be polled to gather feedback on the items
     listed in these minutes.

   o The draft will be updated to reflect changes discussed during the
     meeting.

   o Questions on mandatory/optional for the write capability and the
     experimental branch assignment will be investigated, and results
     reported back to the working group.

   o An Internet-Draft will be posted by July 30 based on the MIB draft
     plus the changes discussed at the IETF meeting.



Attendees

Zbigniew Kielczewski     zbig@eicon.qc.ca
Deirdre Kostick          dck2@mail.bellcore.com
David O'Leary            doleary@cisco.com
David Perkins            dperkins@synoptics.com
Kitty Shih               kmshih@novell.com
Ed Stern                 els@proteon.com