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


        RFC 1513:

        Title:      Token Ring Extensions to the Remote Network
                    Monitoring MIB
        Author:     S. Waldbusser
        Mailbox:    waldbusser@cmu.edu
        Pages:      55
        Characters: 121,974
        Updates:    1271


This memo defines extensions to the Remote Network Monitoring MIB for
managing 802.5 Token Ring networks.  The Remote Network Monitoring
MIB, RFC 1271, defines a framework for remote monitoring functions
implemented on a network probe.  That MIB defines objects broken down
into nine functional groups.  Some of those functional groups, the
statistics and the history groups, have a view of the data-link layer
that is specific to the media type and require specific objects to be
defined for each media type.  RFC 1271 defined those specific objects
necessary for Ethernet.  This companion memo defines those specific
objects necessary for Token Ring LANs.  This memo is a product of the
Remote LAN Monitoring Working Group of the IETF.

This is now a Proposed Standard Protocol.

This RFC 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" 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 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute