home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_i
/
draft-ietf-ifmib-ssr-mib-02.txt
< prev
next >
Wrap
Text File
|
1995-09-16
|
3KB
|
66 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1749:
Title: IEEE 802.5 Station Source Routing MIB using SMIv2
Author: K. McCloghrie, F. Baker & E. Decker
Date: December 1994
Mailbox: kzm@cisco.com, fred@cisco.com, cire@cisco.com
Pages: 10
Characters: 17,563
Updates: 1748
URL: ftp://ds.internic.net/rfc/rfc1749.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 describes managed objects used by IEEE 802.5
end-stations for managing source routes on a Token Ring network where
IEEE source-routing is in use. IEEE source-routing is described in
802.5 Token Ring Access Method and Physical Layer Specifications and
related ISO publications. This memo is an incremental update to RFC
1748. It is documented separately from the RFC 1748 solely due to the
latter's maturity within the Internet standardization process. This
RFC is the product of the Interfaces 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