draft-ietf-ifmib-ssr-mib-01.txt   rfc1749.txt 
Draft 802.5 Station Source Routing MIB October 1994 Network Working Group K. McCloghrie
Request for Comments: 1749 F. Baker
IEEE 802.5 Station Source Routing MIB Updates: 1748 E. Decker
Category: Standards Track cisco Systems, Inc.
23 October 1994 December 1994
Keith McCloghrie
cisco Systems, Inc.
Fred Baker
cisco Systems, Inc.
Eric B. Decker IEEE 802.5 Station Source Routing MIB using SMIv2
cisco Systems, Inc.
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its Internet community, and requests discussion and suggestions for
Areas, and its Working Groups. Note that other groups may also improvements. Please refer to the current edition of the "Internet
distribute working documents as Internet Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet Drafts are valid for a maximum of six months and may be Table of Contents
updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet Drafts as reference material
or to cite them other than as a "work in progress".
Draft 802.5 Station Source Routing MIB October 1994 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 1. Introduction
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base (MIB)
(MIB) for use with network management protocols in the Internet for use with network management protocols in the Internet community.
community. In particular, it describes managed objects used by In particular, it describes managed objects used by IEEE 802.5 end-
IEEE 802.5 end-stations for managing source routes on a Token Ring stations for managing source routes on a Token Ring network where
network where IEEE source-routing is in use. IEEE source-routing IEEE source-routing is in use. IEEE source-routing is described in
is described in 802.5 Token Ring Access Method and Physical Layer 802.5 Token Ring Access Method and Physical Layer Specifications [8]
Specifications [8] and related ISO publications [9, 10, 11]. and related ISO publications [9, 10, 11].
This memo is an incremental update to RFC XXXX [6]. It is
documented separately from the RFC XXXX solely due to the latter's
maturity within the Internet standardization process.
Draft 802.5 Station Source Routing MIB October 1994 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.
2. The SNMPv2 Network Management Framework 2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv2 Network Management Framework consists of four major
components. They are: components. They are:
o RFC 1442 [1] which defines the SMI, the mechanisms used for o RFC 1442 [1] which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
objects for the Internet suite of protocols. objects for the Internet suite of protocols.
o RFC 1445 [3] which defines the administrative and other o RFC 1445 [3] which defines the administrative and other
architectural aspects of the framework. architectural aspects of the framework.
o RFC 1448 [4] which defines the protocol used for network o RFC 1448 [4] which defines the protocol used for network
access to managed objects. access to managed objects.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
2.1. Object Definitions 2.1. Object Definitions
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store, termed
termed the Management Information Base or MIB. Objects in the MIB the Management Information Base or MIB. Objects in the MIB are
are defined using the subset of Abstract Syntax Notation One defined using the subset of Abstract Syntax Notation One (ASN.1)
(ASN.1) defined in the SMI. In particular, each object type is defined in the SMI. In particular, each object type is named by an
named by an OBJECT IDENTIFIER, an administratively assigned name. OBJECT IDENTIFIER, an administratively assigned name. The object
The object type together with an object instance serves to type together with an object instance serves to uniquely identify a
uniquely identify a specific instantiation of the object. For specific instantiation of the object. For human convenience, we
human convenience, we often use a textual string, termed the often use a textual string, termed the descriptor, to refer to the
descriptor, to refer to the object type. object type.
Draft 802.5 Station Source Routing MIB October 1994
3. Overview 3. Overview
This memo defines a single table: the 802.5 Station Source Routing This memo defines a single table: the 802.5 Station Source Routing
Table, which contains the source routes known by a end-station on Table, which contains the source routes known by a end-station on an
an IEEE 802.5 Token Ring network in which IEEE source-routing is IEEE 802.5 Token Ring network in which IEEE source-routing is in use.
in use.
3.1. Source Routing 3.1. Source Routing
Source routing extends the 802.5 protocol [8] by assigning a Source routing extends the 802.5 protocol [8] by assigning a unique
unique ring number to each ring within the extended LAN, and a ring number to each ring within the extended LAN, and a bridge number
bridge number to each source routing bridge's connection to a to each source routing bridge's connection to a ring. A Routing
ring. A Routing Information Field (RIF) must be included in Information Field (RIF) must be included in frames which need to
frames which need to traverse multiple rings. The format of the traverse multiple rings. The format of the RIF is:
RIF is:
octets octets octets octets octets octets octets octets
1&2 3&4 5&6 17&18 1&2 3&4 5&6 17&18
+------+------+------+-------+------+ +------+------+------+-------+------+
| RC | RD | RD | ... | RD | | RC | RD | RD | ... | RD |
+------+------+------+-------+------+ +------+------+------+-------+------+
<---- 0 to 8 RD fields ----> <---- 0 to 8 RD fields ---->
The format of the Routing Control (RC) field is: The format of the Routing Control (RC) field is:
octet 1 octet 2 octet 1 octet 2
+---------------+---------------+ +---------------+---------------+
|b b b l l l l l|d f f f 0 0 0 0| |b b b l l l l l|d f f f 0 0 0 0|
+---------------+---------------+ +---------------+---------------+
^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | |
Explorer indicator --+ | | +-- Max frame length* Explorer indicator --+ | | +-- Max frame length*
Length of RIF field --+ +-- Direction to use RDs Length of RIF field --+ +-- Direction to use RDs
* Note that the length of the Maximum frame length subfield * Note that the length of the Maximum frame length subfield
has recently been extended to 6 bits. has recently been extended to 6 bits.
Draft 802.5 Station Source Routing MIB October 1994 The format of each Routing Descriptor (RD) field is:
The format of each Routing Descriptor (RD) field is:
octet 1 octet 2 octet 1 octet 2
+---------------+---------------+ +---------------+---------------+
|r r r r r r r r r r r r i i i i| |r r r r r r r r r r r r i i i i|
+---------------+---------------+ +---------------+---------------+
<---- ring number ----> <-----> <---- ring number ----> <----->
^ ^
| |
bridge number --+ bridge number --+
3.2. Relationship to RFC XXXX 3.2. Relationship to RFC 1748
RFC XXXX [6], the IEEE 802.5 MIB, defines managed objects used for RFC 1748 [6], the IEEE 802.5 MIB, defines managed objects used for
interfaces to IEEE 802.5 Token Ring subnetworks. This memo is an interfaces to IEEE 802.5 Token Ring subnetworks. This memo is an
incremental update to RFC XXXX, and is documented independently incremental update to RFC 1748, and is documented independently
solely due to the maturity of the definitions contained within RFC solely due to the maturity of the definitions contained within RFC
XXXX. 1748.
3.3. Relationship to RFC 1525 3.3. Relationship to RFC 1525
RFC 1525 [7] defines the MIB objects specific to source-routing RFC 1525 [7] defines the MIB objects specific to source-routing for
for source-routing and SRT bridges. This memo defines the MIB source-routing and SRT bridges. This memo defines the MIB objects
objects specific to source-routing for source-routing end- specific to source-routing for source-routing end-stations.
stations.
3.4. Static Source Routes 3.4. Static Source Routes
It is unclear how many, if any, existing systems allow the It is unclear how many, if any, existing systems allow the creation
creation or deletion of "static" 802.5 source routes by network or deletion of "static" 802.5 source routes by network management.
management. However, SNMPv2 SMI defines that the MAX-ACCESS However, SNMPv2 SMI defines that the MAX-ACCESS clause as specifying
clause as specifying the maximal level of access which makes the maximal level of access which makes "protocol sense". Thus, this
"protocol sense". Thus, this memo provides support for static memo provides support for static source routes through the
source routes through the dot5SrRouteStatus object, but the dot5SrRouteStatus object, but the conformance statements allow for
conformance statements allow for stations which do not support stations which do not support static source routes, by requiring that
static source routes, by requiring that compliant agents only need compliant agents only need provide read-access to dot5SrRouteStatus.
provide read-access to dot5SrRouteStatus.
Draft 802.5 Station Source Routing MIB October 1994
3.5. Destinations on the Local Ring 3.5. Destinations on the Local Ring
Entries should be included in the dot5SrRouteTable for destination Entries should be included in the dot5SrRouteTable for destination
MAC addresses which are on the same ring as the instrumented 802.5 MAC addresses which are on the same ring as the instrumented 802.5
interface. For such entries, dot5SrRouteDescr has the value of interface. For such entries, dot5SrRouteDescr has the value of the
the zero-length string, and dot5SrRouteControl has the zero-length string, and dot5SrRouteControl has the corresponding
corresponding value. value.
Draft 802.5 Station Source Routing MIB October 1994
4. Definitions 4. Definitions
TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE
experimental -- to be removed by IANA
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, MacAddress TEXTUAL-CONVENTION, RowStatus, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
mib-2, ifIndex FROM RFC1213-MIB; mib-2, ifIndex FROM RFC1213-MIB;
dot5SrMIB MODULE-IDENTITY dot5SrMIB MODULE-IDENTITY
LAST-UPDATED "9410231620Z" LAST-UPDATED "9412161000Z"
ORGANIZATION "IETF Interfaces MIB Working Group" ORGANIZATION "IETF Interfaces MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Keith McCloghrie
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive
San Jose CA 95134-1706. San Jose, CA 95134-1706
US
Phone: (408) 526-5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for managing source routes in "The MIB module for managing source routes in
end-stations on IEEE 802.5 Token Ring networks." end-stations on IEEE 802.5 Token Ring networks."
::= { experimental 58 } -- to be assigned as { mib-2 xx } by IANA ::= { mib-2 42 }
dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 } dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 }
RouteDescriptor ::= TEXTUAL-CONVENTION SourceRoute ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Routing Descriptor (RD) as used "Represents a Source Route, containing an
by 802.5 Source Routing." embedded sequence of bridge and ring ID's,
as used by 802.5 Source Routing."
REFERENCE "Annex C of ISO/IEC 10038: 1993, REFERENCE "Annex C of ISO/IEC 10038: 1993,
[ANSI/IEEE Std 802.1D, 1993]" [ANSI/IEEE Std 802.1D, 1993]"
SYNTAX OCTET STRING (SIZE(0..30)) SYNTAX OCTET STRING (SIZE(0..30))
Draft 802.5 Station Source Routing MIB October 1994
-- The 802.5 Station Source Route Table -- The 802.5 Station Source Route Table
-- --
dot5SrRouteTable OBJECT-TYPE dot5SrRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot5SrRouteEntry SYNTAX SEQUENCE OF Dot5SrRouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of source-routing routes. "The table of source-routing routes.
This represents the 802.5 RIF database." This represents the 802.5 RIF database."
skipping to change at page 8, line 30 skipping to change at page 5, line 41
SYNTAX Dot5SrRouteEntry SYNTAX Dot5SrRouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a specific route. "Information on a specific route.
An entry is created whenever a 'Single Path An entry is created whenever a 'Single Path
Explorer' or an 'All Paths Explorer' discovers Explorer' or an 'All Paths Explorer' discovers
a route to a neighbor not currently in the table, a route to a neighbor not currently in the table,
or whenever an 'All Paths Explorer' discovers a or whenever an 'All Paths Explorer' discovers a
better (shorter) route than the route currently better (e.g., shorter) route than the route currently
stored in the table. This is done on behalf of stored in the table. This is done on behalf of
any network layer client. any network layer client.
The ifIndex value in the INDEX clause refers to The ifIndex value in the INDEX clause refers to
the value of MIB-II's ifIndex object for the the value of MIB-II's ifIndex object for the
interface on which the route is in effect." interface on which the route is in effect."
INDEX { ifIndex, dot5SrRouteDestination } INDEX { ifIndex, dot5SrRouteDestination }
::= { dot5SrRouteTable 1 } ::= { dot5SrRouteTable 1 }
Dot5SrRouteEntry ::= SEQUENCE { Dot5SrRouteEntry ::= SEQUENCE {
dot5SrRouteDestination MacAddress, dot5SrRouteDestination MacAddress,
dot5SrRouteControl OCTET STRING, dot5SrRouteControl OCTET STRING,
dot5SrRouteDescr RouteDescriptor, dot5SrRouteDescr SourceRoute,
dot5SrRouteStatus RowStatus dot5SrRouteStatus RowStatus
} }
dot5SrRouteDestination OBJECT-TYPE dot5SrRouteDestination OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft 802.5 Station Source Routing MIB October 1994
"The destination of this route." "The destination of this route."
::= { dot5SrRouteEntry 2 } ::= { dot5SrRouteEntry 2 }
dot5SrRouteControl OBJECT-TYPE dot5SrRouteControl OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2)) SYNTAX OCTET STRING (SIZE(2))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of Routing Control field for this "The value of Routing Control field for this
route." route."
REFERENCE "Annex C of ISO/IEC 10038: 1993, REFERENCE "Annex C of ISO/IEC 10038: 1993,
[ANSI/IEEE Std 802.1D, 1993]" [ANSI/IEEE Std 802.1D, 1993]"
::= { dot5SrRouteEntry 3 } ::= { dot5SrRouteEntry 3 }
dot5SrRouteDescr OBJECT-TYPE dot5SrRouteDescr OBJECT-TYPE
SYNTAX RouteDescriptor SYNTAX SourceRoute
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Routing Descriptor, containing an "The embedded sequence of bridge and ring ID's
embedded sequence of bridge and ring ID's,
for this route. For destinations on the for this route. For destinations on the
local ring, the value of this object is local ring, the value of this object is
the zero-length string." the zero-length string."
REFERENCE "Annex C of ISO/IEC 10038: 1993, REFERENCE "Annex C of ISO/IEC 10038: 1993,
[ANSI/IEEE Std 802.1D, 1993]" [ANSI/IEEE Std 802.1D, 1993]"
::= { dot5SrRouteEntry 4 } ::= { dot5SrRouteEntry 4 }
dot5SrRouteStatus OBJECT-TYPE dot5SrRouteStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row. Values of the instances "The status of this row. Values of the instances
of dot5SrRouteControl and dot5SrRouteDescr can be of dot5SrRouteControl and dot5SrRouteDescr can be
modified while the row's status is 'active." modified while the row's status is 'active."
::= { dot5SrRouteEntry 5 } ::= { dot5SrRouteEntry 5 }
Draft 802.5 Station Source Routing MIB October 1994
-- conformance information -- conformance information
dot5SrConformance OBJECT IDENTIFIER ::= { dot5SrMIB 2 } dot5SrConformance OBJECT IDENTIFIER ::= { dot5SrMIB 2 }
dot5SrGroups OBJECT IDENTIFIER ::= { dot5SrConformance 1 } dot5SrGroups OBJECT IDENTIFIER ::= { dot5SrConformance 1 }
dot5SrCompliances OBJECT IDENTIFIER ::= { dot5SrConformance 2 } dot5SrCompliances OBJECT IDENTIFIER ::= { dot5SrConformance 2 }
-- compliance statements -- compliance statements
dot5SrCompliance MODULE-COMPLIANCE dot5SrCompliance MODULE-COMPLIANCE
skipping to change at page 11, line 5 skipping to change at page 7, line 43
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot5SrRouteDescr OBJECT dot5SrRouteDescr
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { dot5SrCompliances 1 } ::= { dot5SrCompliances 1 }
Draft 802.5 Station Source Routing MIB October 1994
-- units of conformance -- units of conformance
dot5SrRouteGroup OBJECT-GROUP dot5SrRouteGroup OBJECT-GROUP
OBJECTS { dot5SrRouteControl, OBJECTS { dot5SrRouteControl,
dot5SrRouteDescr, dot5SrRouteDescr,
dot5SrRouteStatus dot5SrRouteStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing for the management of "A collection of objects providing for the management of
source routes in stations on IEEE 802.5 source-routing source routes in stations on IEEE 802.5 source-routing
networks." networks."
::= { dot5SrGroups 1 } ::= { dot5SrGroups 1 }
END END
Draft 802.5 Station Source Routing MIB October 1994
5. Acknowledgements 5. Acknowledgements
The need for this MIB module was agreed upon by the members of the The need for this MIB module was agreed upon by the members of the
IETF Interfaces Working Group, and the definitions were derived IETF Interfaces Working Group, and the definitions were derived from
from experience with enterprise-specific MIBs presented to the experience with enterprise-specific MIBs presented to the Working
Working Group. Group.
6. References 6. References
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
"Structure of Management Information for version 2 of the of Management Information for version 2 of the Simple Network
Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc.,
Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
Inc., Carnegie Mellon University, April 1993. University, April 1993.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-
II", STD 17, RFC 1213, Hughes LAN Systems, Performance
Systems International, March 1991.
[3] Galvin, J., and K. McCloghrie, "Administrative Model for
version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN
Systems, April 1993.
[4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie
Mellon University, April 1993.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [2] McCloghrie, K., and M. Rose, Editors, "Management Information
"Textual Conventions for version 2 of the Simple Network Base for Network Management of TCP/IP-based internets: MIB- II",
Management Protocol (SNMPv2)", RFC 1443, SNMP Research Inc., STD 17, RFC 1213, Hughes LAN Systems, Performance Systems
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie International, March 1991.
Mellon University, April 1993.
[6] McCloghrie, K., and E. B. Decker, "IEEE 802.5 Token Ring [3] Galvin, J., and K. McCloghrie, "Administrative Model for version
MIB", RFC XXXX (update to RFC 1231 in preparation), cisco 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445,
Systems, Inc., October 1994. Trusted Information Systems, Hughes LAN Systems, April 1993.
[7] McCloghrie, K., E. B. Decker, P. Langville, and A. [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Rijsinghani, "Definitions of Managed Objects for Source Operations for version 2 of the Simple Network Management
Routing Bridges", RFC 1525, Hughes LAN Systems, cisco Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN
Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993.
Draft 802.5 Station Source Routing MIB October 1994 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1443, SNMP Research Inc., Hughes LAN
Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993.
Systems, Inc., Digital Equipment Corporation, September 1993. [6] McCloghrie, K., and E. Decker, "IEEE 802.5 Token Ring MIB using
SMIv2", RFC 1748 cisco Systems, Inc., December 1994.
[8] "Token Ring Access Method and Physical Layer Specifications", [7] McCloghrie, K., Decker, E., Langville, P., and A. Rijsinghani,
IEEE Standard 802.5-1989, 1989. "Definitions of Managed Objects for Source Routing Bridges", RFC
1525, Hughes LAN Systems, cisco Systems, Inc., Digital Equipment
Corporation, September 1993.
[9] "Information technology - Local and metropolitan area [8] "Token Ring Access Method and Physical Layer Specifications",
networks - Part 5: Token ring access method and physical IEEE Standard 802.5-1989, 1989.
layer specifications", ISO/IEC 8802-5, 1992.
[10] "Information technology - Telecommunications and information [9] "Information technology - Local and metropolitan area networks -
exchange between systems - Local area networks - Media access Part 5: Token ring access method and physical layer
control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std specifications", ISO/IEC 8802-5, 1992.
802.1D, 1993 Edition].
[11] "Source Routing Operation by End Systems", ISO/IEC 8802-2 [10] "Information technology - Telecommunications and information
PDAM5.3 (6N7721). exchange between systems - Local area networks - Media access
control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std
802.1D, 1993 Edition].
Draft 802.5 Station Source Routing MIB October 1994 [11] "Source Routing Operation by End Systems", ISO/IEC 8802-2 PDAM5.3
(6N7721).
7. Security Considerations 7. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
8. Authors Addresses 8. Authors' Addresses
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: (408) 526-5260
EMail: kzm@cisco.com
Fred Baker Phone: (408) 526-5260
cisco Systems, Inc. EMail: kzm@cisco.com
519 Lado Drive
Santa Barbara, CA 93111
Phone: (805) 681-0115
EMail: fred@cisco.com
Eric B. Decker Fred Baker
cisco Systems, Inc. cisco Systems, Inc.
1525 O'Brien Dr. 519 Lado Drive
Menlo Park, California 94025 Santa Barbara, CA 93111
Phone: (415) 688-8241
EMail: cire@cisco.com
Draft 802.5 Station Source Routing MIB October 1994 Phone: (805) 681-0115
EMail: fred@cisco.com
Table of Contents Eric B. Decker
cisco Systems, Inc.
1525 O'Brien Dr.
Menlo Park, California 94025
1 Introduction .............................................. 2 Phone: (415) 688-8241
2 The SNMPv2 Network Management Framework ................... 3 EMail: cire@cisco.com
2.1 Object Definitions ...................................... 3
3 Overview .................................................. 4
3.1 Source Routing .......................................... 4
3.2 Relationship to RFC XXXX ................................ 5
3.3 Relationship to RFC 1525 ................................ 5
3.4 Static Source Routes .................................... 5
3.5 Destinations on the Local Ring .......................... 6
4 Definitions ............................................... 7
5 Acknowledgements .......................................... 12
6 References ................................................ 12
7 Security Considerations ................................... 14
8 Authors Addresses ......................................... 14
 End of changes. 59 change blocks. 
196 lines changed or deleted 165 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/