home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
ietf
/
dlswmib
/
dlswmib-minutes-94dec.txt
< prev
Wrap
Text File
|
1995-06-01
|
6KB
|
154 lines
Data Link Switching MIB BOF (DLSWMIB)
Reported by Deirdre Kostick/Bellcore
The DLSWMIB BOF met on 6 December to gauge community interest in
development of a common, standard MIB for Data Link Switching (DLSw).
DLSw Overview
Wayne Clark presented an overview of Data Link Switching. Data Link
Switching is a method for encapsulating SNA traffic in TCP/IP. DLSw
provides an internetworking solution for multi-protocol networks.
The specification for DLSw is being developed at the APPN Implementors
Workshop (AIW); Version 1 of the specification for DLSw is to be
completed this year.
Several companies offer DLSw-capable products.
DLSw MIB Background
Work on a common DLSw MIB began at the AIW in parallel with the work on
the DLSw specification. A MIB proposal based on existing
enterprise-specific MIBs has been developed. Since the goal of the AIW
effort was to produce a common, standard SNMP MIB, there was interest in
forming an IETF working group.
DLSw MIB MIB Proposal Review
Peter Gayek walked through the current proposal draft. Key
points/issues resulting from that walkthrough are summarized below.
(These notes are based on ``draft-aiw-dlswnm-mib-02.txt'' posted at
networking.raleigh.ibm.com.)
Issues/Recommendations Summary
o Work on the conformance statements should be handled later, after
the content of the main body of the MIB is more stable.
o Retain the MIB summary in the introduction section; it is very
useful to the MIB reader.
o Need to add a list of port number pairs in the MIB. Identify which
are used for SNA/NetBIOS. Also identify priority (e.g., high/low).
o Remove dlswName (use sysName); remove dlswDescr (use sysDescr).
o DLSw Code Capability
- Remove dlswSnaSupport, dlswNMSupport. Information is available
via the SAP list.
- A given node acts in send/receive mode all the time. There are
several problems with the current definition of the object.
Need to represent multiple capabilities; and identify
send/receive mode separately.
- Create two objects (send/receive) and use an enumerated list to
identify capabilities. Action Item: Ravi Periasamy will post
a proposed enumerated list.
o dlswAdminVirtualSegment - remove text describing when the value
takes effect.
o dlswAdminVirtualSegmentMTU - change from *MTU to *LF.
- Check SRB enumerated list (who had this item?).
- Change to INTEGER.
o dlswAdminFlowCntlMode - revise description.
o dlswInitRecvWndwSize - change to INTEGER 0..65.
Identify expected reasonable values.
o dlswStatus - change to Admin/Oper objects. Include text describing
relation to sysUpTime.
o DLSw Circuit Table - Need to clarify what the S1/S2 identifiers
indicate (e.g., S1 is local, S2 is remote).
o dlswCircuitState - need to use standard establishment states. Need
to add an admin object. The management application can de-activate
circuits, but cannot activate circuits. The admin object should
only allow writes, not creates.
o Delete Flow Control Statistics objects; they are too detailed. Add
eight objects to transport connection level. Add:
- total FCI S/R
- independent FCI S/R
- halves window received
- reset send
- reset received
- high water mark
o Delete dlswCircuitStateDownTime, dlswCircuitS1SenseCode,
dlswCircuitLastS2SenseCode. Add dlswCircuitSenseCode with an
enumerated list (e.g., (1) halt DL, (2) halt no-ack, (3) tcp
failed). This would help determine why a circuit went down.
o Revise index of dlswSdlcLinkStateTable to Local MAC Local SAP.
Action Item: Wayne Clark will send out mail requesting feedback on
how table is used.
o Decided to remove partner configuration objects.
o Traps - add trap enabled/disabled object. need to verify that the
four conditions are sufficient.
Goals and Milestones
12/31/94 Post proprietary MIBS
1/15/95 Post first Internet-Draft of the DLSw MIB
3/15/95 Post second Internet-Draft of DLSw MIB
4/3/95 Meet at IETF to review MIB (if necessary)
5/15/95 Post final Internet-Draft of DLSw MIB and submit to AD
6/95 Proposed Standard
Draft Charter Discussion
A proposed draft charter was discussed and agreed to.
Description of the working group:
The DLSw MIB Working Group is chartered to define a set of
managed objects for devices that support Data Link Switching
(DLSw) version 1. DLSw is a method for encapsulating SNA
(System Network Architecture) or NetBIOS (Network Basic Input
Output Services) traffic in TCP/IP. DLSw is intended to aid in
the transport of SNA and NetBIOS traffic across WANs. The
objects will be the minimum necessary to provide the ability to
monitor and control DLSw devices, supporting fault isolation,
configuration and performance management. The set of objects
will be consistent with the SNMP framework and existing SNMP
standards.
The working group will consider existing enterprise-specific
MIB modules that define objects which support management of
these devices.
The working group recognizes that managed objects for later
versions of DLSw may need to be identified in the future.
These objects are out of scope for the current (i.e., 1995)
charter; however, once the working group completes its charter,
a new charter identifying some or all of these components may
be considered.