draft-ietf-ifmib-ssr-mib-00.txt   draft-ietf-ifmib-ssr-mib-01.txt 
IEEE 802.5 Station Source Routing MIB IEEE 802.5 Station Source Routing MIB
26 August 1994 23 October 1994
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
Fred Baker Fred Baker
Advanced Computer Communications, Inc. cisco Systems, Inc.
Eric B. Decker Eric B. Decker
cisco Systems, Inc. cisco Systems, Inc.
<draft-ietf-ifmib-ssr-mib-00.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its documents of the Internet Engineering Task Force (IETF), its
Areas, and its Working Groups. Note that other groups may also Areas, and its Working Groups. Note that other groups may also
distribute working documents as Internet Drafts. distribute working documents as Internet Drafts.
Internet Drafts are valid for a maximum of six months and may be Internet Drafts are valid for a maximum of six months and may be
updated, replaced, or obsoleted by other documents at any time. updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet Drafts as reference material It is inappropriate to use Internet Drafts as reference material
skipping to change at page 4, line 21 skipping to change at page 4, line 21
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 ring number to each ring within the extended LAN, and a unique ring number to each ring within the extended LAN, and a
bridge number to each source routing bridge's connection to a bridge number to each source routing bridge's connection to a
ring. A Routing Information Field (RIF) must be included in ring. A Routing Information Field (RIF) must be included in
frames which need to traverse multiple rings. The format of the frames which need to traverse multiple rings. The format of the
RIF is: RIF is:
octets octets octets octets
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
+---------------+---------------+ +---------------+---------------+
|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.
The format of each Routing Descriptor (RD) field is: The format of each Routing Descriptor (RD) field is:
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 XXXX
RFC XXXX [6], the IEEE 802.5 MIB, defines managed objects used for RFC XXXX [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 XXXX, 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. XXXX.
3.3. Relationship to RFC 1525 3.3. Relationship to RFC 1525
skipping to change at page 6, line 10 skipping to change at page 7, line 10
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 zero-length string, and dot5SrRouteControl has the the zero-length string, and dot5SrRouteControl has the
corresponding value. corresponding value.
4. Definitions 4. Definitions
TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, MODULE-IDENTITY, OBJECT-TYPE,
experimental FROM SNMPv2-SMI experimental -- to be removed by IANA
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;
dot5SrMIB MODULE-IDENTITY dot5SrMIB MODULE-IDENTITY
LAST-UPDATED "9408260220Z" LAST-UPDATED "9410231620Z"
ORGANIZATION "IETF Interfaces MIB Working Group" ORGANIZATION "IETF Interfaces MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Keith McCloghrie "Keith McCloghrie
cisco Systems, Inc. Postal: Cisco Systems, Inc.
1525 O'Brien Dr. 170 West Tasman Drive,
Menlo Park, California 94025 San Jose CA 95134-1706.
Phone: (415) 324-5260 Phone: (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 } ::= { experimental 58 } -- to be assigned as { mib-2 xx } by IANA
dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 } dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 }
RouteDescriptor ::= TEXTUAL-CONVENTION RouteDescriptor ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Routing Descriptor (RD) as used "Represents a Routing Descriptor (RD) as used
by 802.5 Source Routing." 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))
-- The 802.5 Station Source Route Table -- The 802.5 Station Source Route Table
-- --
-- This Source Route Table represents the 802.5 RIF database.
-- Entries are created whenever an Single Path Explorer or an
-- All Paths Explorer discovers a route to a neighbor not
-- currently in the table, or whenever an All Paths Explorer
-- discovers a better (shorter) route than the route currently
-- stored in the table. This is done on behalf of any network
-- layer client.
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."
::= { dot5SrMIBObjects 1 } ::= { dot5SrMIBObjects 1 }
dot5SrRouteEntry OBJECT-TYPE dot5SrRouteEntry OBJECT-TYPE
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.
INDEX { dot5SrRouteIfIndex, dot5SrRouteDestination }
An entry is created whenever a 'Single Path
Explorer' or an 'All Paths Explorer' discovers
a route to a neighbor not currently in the table,
or whenever an 'All Paths Explorer' discovers a
better (shorter) route than the route currently
stored in the table. This is done on behalf of
any network layer client.
The ifIndex value in the INDEX clause refers to
the value of MIB-II's ifIndex object for the
interface on which the route is in effect."
INDEX { ifIndex, dot5SrRouteDestination }
::= { dot5SrRouteTable 1 } ::= { dot5SrRouteTable 1 }
Dot5SrRouteEntry ::= SEQUENCE { Dot5SrRouteEntry ::= SEQUENCE {
dot5SrRouteIfIndex Integer32,
dot5SrRouteDestination MacAddress, dot5SrRouteDestination MacAddress,
dot5SrRouteControl OCTET STRING, dot5SrRouteControl OCTET STRING,
dot5SrRouteDescr RouteDescriptor, dot5SrRouteDescr RouteDescriptor,
dot5SrRouteStatus RowStatus dot5SrRouteStatus RowStatus
} }
dot5SrRouteIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of MIB-II's ifIndex object for the
interface on which this route is in effect."
::= { dot5SrRouteEntry 1 }
dot5SrRouteDestination OBJECT-TYPE dot5SrRouteDestination OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 RouteDescriptor
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Routing Descriptor, containing an "The Routing Descriptor, containing an
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." "The status of this row. Values of the instances
of dot5SrRouteControl and dot5SrRouteDescr can be
modified while the row's status is 'active."
::= { dot5SrRouteEntry 5 } ::= { dot5SrRouteEntry 5 }
-- 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 9, line 30 skipping to change at page 10, line 31
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot5SrRouteGroup } MANDATORY-GROUPS { dot5SrRouteGroup }
OBJECT dot5SrRouteStatus OBJECT dot5SrRouteStatus
SYNTAX INTEGER { active(1) } -- subset of values SYNTAX INTEGER { active(1) } -- subset of values
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only the 'active' "Write access is not required, and only the 'active'
value need be supported." value need be supported."
OBJECT dot5SrRouteControl
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT dot5SrRouteDescr
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { dot5SrCompliances 1 } ::= { dot5SrCompliances 1 }
-- units of conformance -- units of conformance
dot5SrRouteGroup OBJECT-GROUP dot5SrRouteGroup OBJECT-GROUP
OBJECTS { dot5SrRouteControl, OBJECTS { dot5SrRouteControl,
dot5SrRouteDescr, dot5SrRouteDescr,
dot5SrRouteStatus dot5SrRouteStatus
} }
STATUS current STATUS current
skipping to change at page 10, line 43 skipping to change at page 12, line 44
Mellon University, April 1993. Mellon University, April 1993.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for version 2 of the Simple Network "Textual Conventions for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1443, SNMP Research Inc., Management Protocol (SNMPv2)", RFC 1443, SNMP Research Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie
Mellon University, April 1993. Mellon University, April 1993.
[6] McCloghrie, K., and E. B. Decker, "IEEE 802.5 Token Ring [6] McCloghrie, K., and E. B. Decker, "IEEE 802.5 Token Ring
MIB", RFC XXXX (update to RFC 1231 in preparation), cisco MIB", RFC XXXX (update to RFC 1231 in preparation), cisco
Systems, Inc., July 1994. Systems, Inc., October 1994.
[7] McCloghrie, K., E. B. Decker, P. Langville, and A. [7] McCloghrie, K., E. B. Decker, P. Langville, and A.
Rijsinghani, "Definitions of Managed Objects for Source Rijsinghani, "Definitions of Managed Objects for Source
Routing Bridges", RFC 1525, Hughes LAN Systems, cisco Routing Bridges", RFC 1525, Hughes LAN Systems, cisco
Systems, Inc., Digital Equipment Corporation, September 1993. Systems, Inc., Digital Equipment Corporation, September 1993.
[8] "Token Ring Access Method and Physical Layer Specifications", [8] "Token Ring Access Method and Physical Layer Specifications",
IEEE Standard 802.5-1989, 1989. IEEE Standard 802.5-1989, 1989.
[9] "Information technology - Local and metropolitan area [9] "Information technology - Local and metropolitan area
skipping to change at page 11, line 25 skipping to change at page 14, line 9
control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std
802.1D, 1993 Edition]. 802.1D, 1993 Edition].
[11] "Source Routing Operation by End Systems", ISO/IEC 8802-2 [11] "Source Routing Operation by End Systems", ISO/IEC 8802-2
PDAM5.3 (6N7721). 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. Author's Address 8. Authors Addresses
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
1525 O'Brien Dr. 170 West Tasman Drive,
Menlo Park, California 94025 San Jose CA 95134-1706.
Phone: (408) 526-5260
EMail: kzm@cisco.com EMail: kzm@cisco.com
Fred Baker Fred Baker
Advanced Computer Communications cisco Systems, Inc.
315 Bollay Drive 519 Lado Drive
Santa Barbara, California 93117 Santa Barbara, CA 93111
EMail: fbaker@acc.com Phone: (805) 681-0115
EMail: fred@cisco.com
Eric B. Decker Eric B. Decker
cisco Systems, Inc. cisco Systems, Inc.
1525 O'Brien Dr. 1525 O'Brien Dr.
Menlo Park, California 94025 Menlo Park, California 94025
Phone: (415) 688-8241 Phone: (415) 688-8241
EMail: cire@cisco.com EMail: cire@cisco.com
Table of Contents Table of Contents
1 Introduction .............................................. 2 1 Introduction .............................................. 2
2 The SNMPv2 Network Management Framework ................... 3 2 The SNMPv2 Network Management Framework ................... 3
2.1 Object Definitions ...................................... 3 2.1 Object Definitions ...................................... 3
3 Overview .................................................. 4 3 Overview .................................................. 4
3.1 Source Routing .......................................... 4 3.1 Source Routing .......................................... 4
3.2 Relationship to RFC XXXX ................................ 5 3.2 Relationship to RFC XXXX ................................ 5
3.3 Relationship to RFC 1525 ................................ 5 3.3 Relationship to RFC 1525 ................................ 5
3.4 Static Source Routes .................................... 5 3.4 Static Source Routes .................................... 5
skipping to change at page 12, line 14 skipping to change at page 15, line 15
Table of Contents Table of Contents
1 Introduction .............................................. 2 1 Introduction .............................................. 2
2 The SNMPv2 Network Management Framework ................... 3 2 The SNMPv2 Network Management Framework ................... 3
2.1 Object Definitions ...................................... 3 2.1 Object Definitions ...................................... 3
3 Overview .................................................. 4 3 Overview .................................................. 4
3.1 Source Routing .......................................... 4 3.1 Source Routing .......................................... 4
3.2 Relationship to RFC XXXX ................................ 5 3.2 Relationship to RFC XXXX ................................ 5
3.3 Relationship to RFC 1525 ................................ 5 3.3 Relationship to RFC 1525 ................................ 5
3.4 Static Source Routes .................................... 5 3.4 Static Source Routes .................................... 5
3.5 Destinations on the Local Ring .......................... 5 3.5 Destinations on the Local Ring .......................... 6
4 Definitions ............................................... 6 4 Definitions ............................................... 7
5 Acknowledgements .......................................... 10 5 Acknowledgements .......................................... 12
6 References ................................................ 10 6 References ................................................ 12
7 Security Considerations ................................... 11 7 Security Considerations ................................... 14
8 Author's Address .......................................... 11 8 Authors Addresses ......................................... 14
 End of changes. 31 change blocks. 
46 lines changed or deleted 64 lines changed or added

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