home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_q_t
/
draft-ietf-snanau-appcmib-06.txt
< prev
next >
Wrap
Text File
|
1996-10-31
|
2KB
|
66 lines
A new Request for Comments is now available in online RFC libraries.
RFC 2051:
Title: Definitions of Managed Objects for APPC using
SMIv2
Author: M. Allen, B. Clouston, Z. Kielczewski, W. Kwan,
B. Moore
Date: October 1996
Mailbox: mallen@hq.walldata.com, clouston@cisco.com,
zbig@cisco.com, billk@jti.com,
remoore@ralvm6.vnet.ibm.com
Pages: 124
Characters: 239,359
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2051.txt
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 controlling of network devices with APPC (Advanced
Program-to-Program Communications) capabilities. This memo identifies
managed objects for the SNA LU6.2 protocols. This RFC is a product of
the SNA NAU 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-DIST-REQUEST@ISI.EDU.
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 and Mary Kennedy
USC/Information Sciences Institute