[jkrey@ISI.EDU: RFCs 1316, 1317, 1318, on Character MIB, RS-232-LIKE MIB, PARALLEL-PRINTER-LIKE-MIB]

Bob Stewart <rlstewart@eng.xyplex.com> Fri, 17 April 1992 14:59 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa01149; 17 Apr 92 10:59 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa19171; 17 Apr 92 11:03 EDT
Received: from inet-gw-1.pa.dec.com by NRI.Reston.VA.US id aa19160; 17 Apr 92 11:03 EDT
Received: by inet-gw-1.pa.dec.com; id AA26699; Fri, 17 Apr 92 08:01:30 -0700
Received: by nsl.pa.dec.com; id AA08305; Fri, 17 Apr 92 07:57:35 -0700
Received: by inet-gw-1.pa.dec.com; id AA26485; Fri, 17 Apr 92 07:57:24 -0700
Received: by xap.xyplex.com id <AA28338@xap.xyplex.com>; Wed, 15 Apr 92 20:59:04 -0500
Date: Wed, 15 Apr 92 20:59:04 -0500
Message-Id: <9204160159.AA28338@xap.xyplex.com>
From: Bob Stewart <rlstewart@eng.xyplex.com>
To: char-mib@pa.dec.com
Subject: [jkrey@ISI.EDU: RFCs 1316, 1317, 1318, on Character MIB, RS-232-LIKE MIB, PARALLEL-PRINTER-LIKE-MIB]

Tah-dah!  Finally.

	Bob

---------- Forwarded Message

From: jkrey@ISI.EDU (Joyce Reynolds)
Date: Thu, 16 Apr 92 09:31:25 PDT
Posted-Date: Thu, 16 Apr 92 09:31:25 PDT
To: ietf@ISI.EDU, rfc-dist@nic.ddn.mil
Subject: RFCs 1316, 1317, 1318, on Character MIB, RS-232-LIKE MIB, PARALLEL-PRINTER-LIKE-MIB
Cc: jkrey@ISI.EDU



New Request for Comments are now available in online RFC libraries:

        RFC 1316:

        Title:      Definitions of Managed Objects
                    for Character Stream Devices
        Author:     B. Stewart, Editor
        Mailbox:    rlstewart@eng.xyplex.com
        Pages:      17
        Characters: 35,143
        Obsoletes/Updates:  none

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets.
In particular it defines objects for the management of character
stream devices.  This document was produced by the Character MIB
Working Group.

This is now a Proposed Standard Protocol.

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


        RFC 1317:

        Title:      Definitions of Managed Objects for
                    RS-232-like Hardware Devices
        Author:     B. Stewart, Editor
        Mailbox:    rlstewart@eng.xyplex.com
        Pages:      17
        Characters: 30,442
        Obsoletes/Updates:  none

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets.
In particular, it defines objects for the management of RS-232-like
devices.  This document was produced by the Character MIB
Working Group.

This is now a Proposed Standard Protocol.

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


        RFC 1318:

        Title:      Definitions of Managed Objects
                    for Parallel-printer-like Hardware Devices
        Author:     B. Stewart, Editor
        Mailbox:    rlstewart@eng.xyplex.com
        Pages:      11
        Characters: 19,570
        Obsoletes/Updates:  none

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets.
In particular, it defines objects for the management of
parallel-printer-like devices.  This document was produced by the
Character MIB Working Group.

This is now a Proposed Standard Protocol.

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

RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, or 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 NIC@NIC.DDN.MIL.  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 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute