RFC1666 on SNANAU MIB

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 11 August 1994 20:30 UTC

Message-Id: <199408112026.AA08193@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1666 on SNANAU MIB
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 11 Aug 1994 13:27:01 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1666:

        Title:      Definitions of Managed Objects
                    for SNA NAUs using SMIv2
        Author:     Z. Kielczewski, D. Kostick & Shih, Editors
        Mailbox:    zbig@eicon.qc.ca, dck2@mail.bellcore.com,
                    kmshih@novell.com
        Pages:      68
        Characters: 134,385
        Obsoletes:  1665


This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing the configuration,
monitoring and control of Physical Units (PUs) and Logical Units (LUs)
in an SNA (Systems Network Architecture) environment.  PUs and LUs are
two types of Network Addressable Units (NAUs) in the logical structure
of an SNA network.  NAUs are the origination or destination points for
SNA data streams.  This memo identifies managed objects for PU Type
1.0, 2.0 and Type 2.1 and LU Type 0, 1, 2, 3, 4, 7.  The generic
objects defined here can also be used to manage LU 6.2 and any LU-LU
session.  This RFC is the product of the SNA NAU Services MIB Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ds.internic.net/rfc/rfc1666.txt"><ftp://ds.internic.net/rfc/rfc1666.txt>

RFC1666 on SNANAU MIB Joyce K. Reynolds