idnits 2.17.1 draft-ietf-ifmib-ssr-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (23 October 1994) is 10771 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '5' is defined on line 389, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1443 (ref. '5') (Obsoleted by RFC 1903) ** Obsolete normative reference: RFC 1231 (ref. '6') (Obsoleted by RFC 1743, RFC 1748) ** Downref: Normative reference to an Historic RFC: RFC 1525 (ref. '7') -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' Summary: 17 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Draft 802.5 Station Source Routing MIB October 1994 4 IEEE 802.5 Station Source Routing MIB 6 23 October 1994 8 Keith McCloghrie 9 cisco Systems, Inc. 11 Fred Baker 12 cisco Systems, Inc. 14 Eric B. Decker 15 cisco Systems, Inc. 17 Status of this Memo 19 This document is an Internet Draft. Internet Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its 21 Areas, and its Working Groups. Note that other groups may also 22 distribute working documents as Internet Drafts. 24 Internet Drafts are valid for a maximum of six months and may be 25 updated, replaced, or obsoleted by other documents at any time. 26 It is inappropriate to use Internet Drafts as reference material 27 or to cite them other than as a "work in progress". 29 Draft 802.5 Station Source Routing MIB October 1994 31 1. Introduction 33 This memo defines a portion of the Management Information Base 34 (MIB) for use with network management protocols in the Internet 35 community. In particular, it describes managed objects used by 36 IEEE 802.5 end-stations for managing source routes on a Token Ring 37 network where IEEE source-routing is in use. IEEE source-routing 38 is described in 802.5 Token Ring Access Method and Physical Layer 39 Specifications [8] and related ISO publications [9, 10, 11]. 41 This memo is an incremental update to RFC XXXX [6]. It is 42 documented separately from the RFC XXXX solely due to the latter's 43 maturity within the Internet standardization process. 45 Draft 802.5 Station Source Routing MIB October 1994 47 2. The SNMPv2 Network Management Framework 49 The SNMPv2 Network Management Framework consists of four major 50 components. They are: 52 o RFC 1442 [1] which defines the SMI, the mechanisms used for 53 describing and naming objects for the purpose of management. 55 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 56 objects for the Internet suite of protocols. 58 o RFC 1445 [3] which defines the administrative and other 59 architectural aspects of the framework. 61 o RFC 1448 [4] which defines the protocol used for network 62 access to managed objects. 64 The Framework permits new objects to be defined for the purpose of 65 experimentation and evaluation. 67 2.1. Object Definitions 69 Managed objects are accessed via a virtual information store, 70 termed the Management Information Base or MIB. Objects in the MIB 71 are defined using the subset of Abstract Syntax Notation One 72 (ASN.1) defined in the SMI. In particular, each object type is 73 named by an OBJECT IDENTIFIER, an administratively assigned name. 74 The object type together with an object instance serves to 75 uniquely identify a specific instantiation of the object. For 76 human convenience, we often use a textual string, termed the 77 descriptor, to refer to the object type. 79 Draft 802.5 Station Source Routing MIB October 1994 81 3. Overview 83 This memo defines a single table: the 802.5 Station Source Routing 84 Table, which contains the source routes known by a end-station on 85 an IEEE 802.5 Token Ring network in which IEEE source-routing is 86 in use. 88 3.1. Source Routing 90 Source routing extends the 802.5 protocol [8] by assigning a 91 unique ring number to each ring within the extended LAN, and a 92 bridge number to each source routing bridge's connection to a 93 ring. A Routing Information Field (RIF) must be included in 94 frames which need to traverse multiple rings. The format of the 95 RIF is: 97 octets octets octets octets 98 1&2 3&4 5&6 17&18 99 +------+------+------+-------+------+ 100 | RC | RD | RD | ... | RD | 101 +------+------+------+-------+------+ 102 <---- 0 to 8 RD fields ----> 104 The format of the Routing Control (RC) field is: 106 octet 1 octet 2 107 +---------------+---------------+ 108 |b b b l l l l l|d f f f 0 0 0 0| 109 +---------------+---------------+ 110 ^ ^ ^ ^ 111 | | | | 112 Explorer indicator --+ | | +-- Max frame length* 113 Length of RIF field --+ +-- Direction to use RDs 115 * Note that the length of the Maximum frame length subfield 116 has recently been extended to 6 bits. 118 Draft 802.5 Station Source Routing MIB October 1994 120 The format of each Routing Descriptor (RD) field is: 122 octet 1 octet 2 123 +---------------+---------------+ 124 |r r r r r r r r r r r r i i i i| 125 +---------------+---------------+ 126 <---- ring number ----> <-----> 127 ^ 128 | 129 bridge number --+ 131 3.2. Relationship to RFC XXXX 133 RFC XXXX [6], the IEEE 802.5 MIB, defines managed objects used for 134 interfaces to IEEE 802.5 Token Ring subnetworks. This memo is an 135 incremental update to RFC XXXX, and is documented independently 136 solely due to the maturity of the definitions contained within RFC 137 XXXX. 139 3.3. Relationship to RFC 1525 141 RFC 1525 [7] defines the MIB objects specific to source-routing 142 for source-routing and SRT bridges. This memo defines the MIB 143 objects specific to source-routing for source-routing end- 144 stations. 146 3.4. Static Source Routes 148 It is unclear how many, if any, existing systems allow the 149 creation or deletion of "static" 802.5 source routes by network 150 management. However, SNMPv2 SMI defines that the MAX-ACCESS 151 clause as specifying the maximal level of access which makes 152 "protocol sense". Thus, this memo provides support for static 153 source routes through the dot5SrRouteStatus object, but the 154 conformance statements allow for stations which do not support 155 static source routes, by requiring that compliant agents only need 156 provide read-access to dot5SrRouteStatus. 158 Draft 802.5 Station Source Routing MIB October 1994 160 3.5. Destinations on the Local Ring 162 Entries should be included in the dot5SrRouteTable for destination 163 MAC addresses which are on the same ring as the instrumented 802.5 164 interface. For such entries, dot5SrRouteDescr has the value of 165 the zero-length string, and dot5SrRouteControl has the 166 corresponding value. 168 Draft 802.5 Station Source Routing MIB October 1994 170 4. Definitions 172 TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN 174 IMPORTS 175 MODULE-IDENTITY, OBJECT-TYPE, 176 experimental -- to be removed by IANA 177 FROM SNMPv2-SMI 178 TEXTUAL-CONVENTION, RowStatus, MacAddress 179 FROM SNMPv2-TC 180 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 181 mib-2, ifIndex FROM RFC1213-MIB; 183 dot5SrMIB MODULE-IDENTITY 184 LAST-UPDATED "9410231620Z" 185 ORGANIZATION "IETF Interfaces MIB Working Group" 186 CONTACT-INFO 187 " Keith McCloghrie 188 Postal: Cisco Systems, Inc. 189 170 West Tasman Drive, 190 San Jose CA 95134-1706. 192 Phone: (408) 526-5260 193 Email: kzm@cisco.com" 194 DESCRIPTION 195 "The MIB module for managing source routes in 196 end-stations on IEEE 802.5 Token Ring networks." 197 ::= { experimental 58 } -- to be assigned as { mib-2 xx } by IANA 199 dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 } 201 RouteDescriptor ::= TEXTUAL-CONVENTION 202 DISPLAY-HINT "1x:" 203 STATUS current 204 DESCRIPTION 205 "Represents a Routing Descriptor (RD) as used 206 by 802.5 Source Routing." 207 REFERENCE "Annex C of ISO/IEC 10038: 1993, 208 [ANSI/IEEE Std 802.1D, 1993]" 209 SYNTAX OCTET STRING (SIZE(0..30)) 211 Draft 802.5 Station Source Routing MIB October 1994 213 -- The 802.5 Station Source Route Table 214 -- 216 dot5SrRouteTable OBJECT-TYPE 217 SYNTAX SEQUENCE OF Dot5SrRouteEntry 218 MAX-ACCESS not-accessible 219 STATUS current 220 DESCRIPTION 221 "The table of source-routing routes. 222 This represents the 802.5 RIF database." 223 ::= { dot5SrMIBObjects 1 } 225 dot5SrRouteEntry OBJECT-TYPE 226 SYNTAX Dot5SrRouteEntry 227 MAX-ACCESS not-accessible 228 STATUS current 229 DESCRIPTION 230 "Information on a specific route. 232 An entry is created whenever a 'Single Path 233 Explorer' or an 'All Paths Explorer' discovers 234 a route to a neighbor not currently in the table, 235 or whenever an 'All Paths Explorer' discovers a 236 better (shorter) route than the route currently 237 stored in the table. This is done on behalf of 238 any network layer client. 240 The ifIndex value in the INDEX clause refers to 241 the value of MIB-II's ifIndex object for the 242 interface on which the route is in effect." 243 INDEX { ifIndex, dot5SrRouteDestination } 244 ::= { dot5SrRouteTable 1 } 246 Dot5SrRouteEntry ::= SEQUENCE { 247 dot5SrRouteDestination MacAddress, 248 dot5SrRouteControl OCTET STRING, 249 dot5SrRouteDescr RouteDescriptor, 250 dot5SrRouteStatus RowStatus 251 } 253 dot5SrRouteDestination OBJECT-TYPE 254 SYNTAX MacAddress 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 259 Draft 802.5 Station Source Routing MIB October 1994 261 "The destination of this route." 262 ::= { dot5SrRouteEntry 2 } 264 dot5SrRouteControl OBJECT-TYPE 265 SYNTAX OCTET STRING (SIZE(2)) 266 MAX-ACCESS read-create 267 STATUS current 268 DESCRIPTION 269 "The value of Routing Control field for this 270 route." 271 REFERENCE "Annex C of ISO/IEC 10038: 1993, 272 [ANSI/IEEE Std 802.1D, 1993]" 273 ::= { dot5SrRouteEntry 3 } 275 dot5SrRouteDescr OBJECT-TYPE 276 SYNTAX RouteDescriptor 277 MAX-ACCESS read-create 278 STATUS current 279 DESCRIPTION 280 "The Routing Descriptor, containing an 281 embedded sequence of bridge and ring ID's, 282 for this route. For destinations on the 283 local ring, the value of this object is 284 the zero-length string." 285 REFERENCE "Annex C of ISO/IEC 10038: 1993, 286 [ANSI/IEEE Std 802.1D, 1993]" 287 ::= { dot5SrRouteEntry 4 } 289 dot5SrRouteStatus OBJECT-TYPE 290 SYNTAX RowStatus 291 MAX-ACCESS read-create 292 STATUS current 293 DESCRIPTION 294 "The status of this row. Values of the instances 295 of dot5SrRouteControl and dot5SrRouteDescr can be 296 modified while the row's status is 'active." 297 ::= { dot5SrRouteEntry 5 } 299 Draft 802.5 Station Source Routing MIB October 1994 301 -- conformance information 303 dot5SrConformance OBJECT IDENTIFIER ::= { dot5SrMIB 2 } 305 dot5SrGroups OBJECT IDENTIFIER ::= { dot5SrConformance 1 } 306 dot5SrCompliances OBJECT IDENTIFIER ::= { dot5SrConformance 2 } 308 -- compliance statements 310 dot5SrCompliance MODULE-COMPLIANCE 311 STATUS current 312 DESCRIPTION 313 "The compliance statement for SNMPv2 entities 314 which implement the IEEE 802.5 Station Source Route 315 MIB." 317 MODULE -- this module 318 MANDATORY-GROUPS { dot5SrRouteGroup } 320 OBJECT dot5SrRouteStatus 321 SYNTAX INTEGER { active(1) } -- subset of values 322 MIN-ACCESS read-only 323 DESCRIPTION 324 "Write access is not required, and only the 'active' 325 value need be supported." 327 OBJECT dot5SrRouteControl 328 MIN-ACCESS read-only 329 DESCRIPTION 330 "Write access is not required." 332 OBJECT dot5SrRouteDescr 333 MIN-ACCESS read-only 334 DESCRIPTION 335 "Write access is not required." 337 ::= { dot5SrCompliances 1 } 339 Draft 802.5 Station Source Routing MIB October 1994 341 -- units of conformance 343 dot5SrRouteGroup OBJECT-GROUP 344 OBJECTS { dot5SrRouteControl, 345 dot5SrRouteDescr, 346 dot5SrRouteStatus 347 } 348 STATUS current 349 DESCRIPTION 350 "A collection of objects providing for the management of 351 source routes in stations on IEEE 802.5 source-routing 352 networks." 353 ::= { dot5SrGroups 1 } 355 END 356 Draft 802.5 Station Source Routing MIB October 1994 358 5. Acknowledgements 360 The need for this MIB module was agreed upon by the members of the 361 IETF Interfaces Working Group, and the definitions were derived 362 from experience with enterprise-specific MIBs presented to the 363 Working Group. 365 6. References 367 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 368 "Structure of Management Information for version 2 of the 369 Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP 370 Research,Inc., Hughes LAN Systems, Dover Beach Consulting, 371 Inc., Carnegie Mellon University, April 1993. 373 [2] McCloghrie, K., and M. Rose, Editors, "Management Information 374 Base for Network Management of TCP/IP-based internets: MIB- 375 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 376 Systems International, March 1991. 378 [3] Galvin, J., and K. McCloghrie, "Administrative Model for 379 version 2 of the Simple Network Management Protocol 380 (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN 381 Systems, April 1993. 383 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 384 "Protocol Operations for version 2 of the Simple Network 385 Management Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., 386 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie 387 Mellon University, April 1993. 389 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 390 "Textual Conventions for version 2 of the Simple Network 391 Management Protocol (SNMPv2)", RFC 1443, SNMP Research Inc., 392 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie 393 Mellon University, April 1993. 395 [6] McCloghrie, K., and E. B. Decker, "IEEE 802.5 Token Ring 396 MIB", RFC XXXX (update to RFC 1231 in preparation), cisco 397 Systems, Inc., October 1994. 399 [7] McCloghrie, K., E. B. Decker, P. Langville, and A. 400 Rijsinghani, "Definitions of Managed Objects for Source 401 Routing Bridges", RFC 1525, Hughes LAN Systems, cisco 403 Draft 802.5 Station Source Routing MIB October 1994 405 Systems, Inc., Digital Equipment Corporation, September 1993. 407 [8] "Token Ring Access Method and Physical Layer Specifications", 408 IEEE Standard 802.5-1989, 1989. 410 [9] "Information technology - Local and metropolitan area 411 networks - Part 5: Token ring access method and physical 412 layer specifications", ISO/IEC 8802-5, 1992. 414 [10] "Information technology - Telecommunications and information 415 exchange between systems - Local area networks - Media access 416 control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std 417 802.1D, 1993 Edition]. 419 [11] "Source Routing Operation by End Systems", ISO/IEC 8802-2 420 PDAM5.3 (6N7721). 422 Draft 802.5 Station Source Routing MIB October 1994 424 7. Security Considerations 426 Security issues are not discussed in this memo. 428 8. Authors Addresses 430 Keith McCloghrie 431 cisco Systems, Inc. 432 170 West Tasman Drive, 433 San Jose CA 95134-1706. 434 Phone: (408) 526-5260 435 EMail: kzm@cisco.com 437 Fred Baker 438 cisco Systems, Inc. 439 519 Lado Drive 440 Santa Barbara, CA 93111 441 Phone: (805) 681-0115 442 EMail: fred@cisco.com 444 Eric B. Decker 445 cisco Systems, Inc. 446 1525 O'Brien Dr. 447 Menlo Park, California 94025 448 Phone: (415) 688-8241 449 EMail: cire@cisco.com 451 Draft 802.5 Station Source Routing MIB October 1994 453 Table of Contents 455 1 Introduction .............................................. 2 456 2 The SNMPv2 Network Management Framework ................... 3 457 2.1 Object Definitions ...................................... 3 458 3 Overview .................................................. 4 459 3.1 Source Routing .......................................... 4 460 3.2 Relationship to RFC XXXX ................................ 5 461 3.3 Relationship to RFC 1525 ................................ 5 462 3.4 Static Source Routes .................................... 5 463 3.5 Destinations on the Local Ring .......................... 6 464 4 Definitions ............................................... 7 465 5 Acknowledgements .......................................... 12 466 6 References ................................................ 12 467 7 Security Considerations ................................... 14 468 8 Authors Addresses ......................................... 14