SNA NAU Services MIB (snanau) Charter
NOTE: This charter is accurate as of the 31st IETF Meeting in San Jose. It
may now be out-of-date. (Consider this a "snapshot" of the working
group from that meeting.) Up-to-date charters for all active working
groups can be found elsewhere in this Web server.
- Zbigniew Kielczewski <firstname.lastname@example.org>
- Deirdre Kostick <email@example.com>
Network Management Area Director(s):
- Marshall Rose <firstname.lastname@example.org>
- David Perkins <email@example.com>
Mailing List Information
- General Discussion:firstname.lastname@example.org
- To Subscribe: email@example.com
- Archive: thumper.bellcore.com:pub/tob/snanaumib/archive
Description of Working Group
The SNA NAU Services MIB Working Group is chartered to define a
set of managed objects for PU type 2.1 LEN nodes and LU type 6.2
devices for SNA networks. These objects will be the minimum
necessary to provide the ability to monitor and control those
devices, providing fault, configuration, and performance
management, and 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. It will also make sure that its work is aligned with the
SNA DLC Services MIB Working Group, due to the close relationship
between the devices being worked on by the two groups.
The working group recognizes that managed objects for other
components may need to be identified in the future. For example,
APPN end and network nodes are not included. These objects are out
of scope for the current charter; however, once the group
completes its charter, a new charter identifying some or all of
these components may be considered.
Goals and Milestones
- Begin discussion of proprietary MIBS and develop a single proposal.
- Post an Internet-Draft of the SNA NAU Services MIB.
- Submit the SNA NAU Services MIB to the IESG fo consideration as a Proposed Standard.
- Post proprietary MIB modules
- Develop and post a single proposal for structure of the MIB module
- Meet at IETF to review proposed structure/walkthru
- Post Internet-Draft of the APPC MIB
- Post second Internet-Draft of APPC MIB
- Meet at IETF to review MIB (if necessary)
- Achieve concensus on the final I-D
Request for Comments