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


        RFC 1747:

        Title:      Definitions of Managed Objects for SNA Data Link
                    Control (SDLC) using SMIv2
        Author:     J. Hilgeman, Chair, S. Nix, A. Bartky, 
                    & W. Clark, Editor
        Date:       January 1995
        Mailbox:    jeffh@apertus.com, snix@metaplex.com, 
                    alan@sync.com, wclark@cisco.com
        Pages:      67
        Characters: 147,388
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1747.txt


This specification defines an extension to the Management Information
Base (MIB) for use with SNMP-based network management.  In particular,
it defines objects for managing the configuration, monitoring and
control of data link controls in an SNA environment. This RFC
identifies managed objects for SNA Synchronous Data Link Control
(SDLC) links only.  This RFC is a product of the SNA DLC 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