SNA DLC Services MIB (snadlc)

NOTE: This charter is a snapshot of that in effect at the time of the 38th IETF Meeting in Memphis, Tennessee. It may now be out-of-date.

Chair(s): 

Shannon Nix <snix@cisco.com>

Routing Area Director(s): 

Joel Halpern <jhalpern@newbridge.com>

Area Advisor: 

Ken Key <key@tgv.com>

Mailing Lists: 

General Discussion:snadlcmib@cisco.com
To Subscribe: snadlcmib-request@cisco.com
Archive:

Description of Working Group: 

The SNA DLC Services MIB Working Group is chartered to define a set of managed objects for the SDLC and LLC-2 data link controls 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 that support management of these devices. The group may choose to consider any work done by the IEEE in the area of managed object definition for LLC-2. It will also make sure that its work is aligned with the SNA NAU 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 SNA data link controls and related components (e.g., QLLC, System/370 Channel, Data Link Switching, and ESCON) may need to be identified in the future. 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:

Done 

Mailing list discussion of vendor proprietary MIBs.

Done 

Post an Internet-Draft of the SNA DLC MIB.

Done 

Submit the SNA DLC MIB to the IESG for consideration as a Proposed Standard.

No Current Internet-Drafts

Request For Comments:

RFC 

Status 

Title

RFC1747 

PS 

Definitions of Managed Objects for SNA Data Link Control: SDLC

Current Meeting Report

The Working Group did not meet. 

Slides

None Received 

TOC