IEEE 802.5 Station Source Routing MIB using SMIv2
RFC 1749

Document Type RFC - Historic (December 1994; No errata)
Updates RFC 1748
Last updated 2013-03-02
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1749 (Historic)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      K. McCloghrie
Request for Comments: 1749                                      F. Baker
Updates: 1748                                                  E. Decker
Category: Standards Track                            cisco Systems, Inc.
                                                           December 1994

           IEEE 802.5 Station Source Routing MIB using SMIv2

Status of this Memo

   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.

Table of Contents

   1. Introduction .............................................    1
   2. The SNMPv2 Network Management Framework ..................    2
   2.1 Object Definitions ......................................    2
   3. Overview .................................................    2
   3.1 Source Routing ..........................................    2
   3.2 Relationship to RFC 1748 ................................    3
   3.3 Relationship to RFC 1525 ................................    3
   3.4 Static Source Routes ....................................    4
   3.5 Destinations on the Local Ring ..........................    4
   4. Definitions ..............................................    4
   5. Acknowledgements .........................................    8
   6. References ...............................................    8
   7. Security Considerations ..................................    9
   8. Authors' Addresses .......................................   10

1.  Introduction

   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 [8]
   and related ISO publications [9, 10, 11].

   This memo is an incremental update to RFC 1748 [6].  It is documented
   separately from the RFC 1748 solely due to the latter's maturity
   within the Internet standardization process.

McCloghrie, Baker & Decker                                      [Page 1]
RFC 1749      802.5 Station Source Routing MIB using SMIv2 December 1994

2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      o    RFC 1442 [1] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

      o    STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
           objects for the Internet suite of protocols.

      o    RFC 1445 [3] which defines the administrative and other
           architectural aspects of the framework.

      o    RFC 1448 [4] which defines the protocol used for network
           access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.

3.  Overview

   This memo defines a single table: the 802.5 Station Source Routing
   Table, which contains the source routes known by a end-station on an
   IEEE 802.5 Token Ring network in which IEEE source-routing is in use.

3.1.  Source Routing

   Source routing extends the 802.5 protocol [8] by assigning a unique
   ring number to each ring within the extended LAN, and a bridge number
   to each source routing bridge's connection to a ring.  A Routing
   Information Field (RIF) must be included in frames which need to
   traverse multiple rings.  The format of the RIF is:

McCloghrie, Baker & Decker                                      [Page 2]
RFC 1749      802.5 Station Source Routing MIB using SMIv2 December 1994

              octets octets octets         octets
               1&2    3&4    5&6            17&18
             +------+------+------+-------+------+
             |  RC  |  RD  |  RD  | ...   |  RD  |
             +------+------+------+-------+------+
                     <---- 0 to 8 RD fields ---->
Show full document text