idnits 2.17.1 draft-ietf-trunkmib-ds0-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-24) 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 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 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. ** There are 5 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([6], [7], [8]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 1996) is 10296 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: '9' is defined on line 543, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '5') (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 1406 (ref. '6') (Obsoleted by RFC 2495) ** Obsolete normative reference: RFC 1407 (ref. '7') (Obsoleted by RFC 2496) ** Obsolete normative reference: RFC 1595 (ref. '8') (Obsoleted by RFC 2558) -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 18 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT DS0 MIB February 1996 3 Definitions of Managed Objects 4 for the DS0 and DS0 Bundle Interface Type 6 Thu Feb 22 16:14:43 1996 8 draft-ietf-trunkmib-ds0-mib-01.txt 10 David Fowler (editor) 11 Newbridge Networks 12 davef@newbridge.com 14 Status of this Memo 16 This document is an Internet-Draft. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, 18 and its working groups. Note that other groups may also distribute 19 working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as ``work in progress.'' 26 To learn the current status of any Internet-Draft, please check the 27 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 28 Directories on ds.internic.net (US East Coast), nic.nordu.net 29 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 30 Rim). 32 Abstract 34 This memo defines an experimental portion of the Management 35 Information Base (MIB) for use with network management protocols in 36 the Internet community. In particular, it describes objects used for 37 managing DS0 and DS0 Bundle interfaces. This document is a companion 38 document with Definitions of Managed Objects for the DS1/E1/DS2/E2, 39 DS3/E3 and SONET/SDH Interface Types, rfc1406 [6], rfc1407 [7] and 40 rfc1595 [8]. 42 This memo specifies a MIB module in a manner that is both compliant 43 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 44 definitions. 46 This memo does not specify a standard for the Internet community. 48 1. The SNMPv2 Network Management Framework 50 The SNMPv2 Network Management Framework consists of four major 51 components. They are: 53 o the SMI, described in RFC 1902 [1] - the mechanisms used for 54 describing and naming objects for the purpose of management. 56 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 57 objects for the Internet suite of protocols. 59 o the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], - the 60 protocol for accessing managed objects. 62 The Framework permits new objects to be defined for the 63 purpose of experimentation and evaluation. 65 2. Objects 67 Managed objects are accessed via a virtual information store, termed 68 the Management Information Base or MIB. Objects in the MIB are 69 defined using the subset of Abstract Syntax Notation One (ASN.1) 70 defined in the SMI. In particular, each object type is named by an 71 OBJECT IDENTIFIER, an administratively assigned name. The object 72 type together with an object instance serves to uniquely identify a 73 specific instantiation of the object. For human convenience, we 74 often use a textual string, termed the descriptor, to also refer to 75 the object type. 77 3. Overview 79 These objects are used when the particular media being used to 80 realize an interface is a DS0 interface. At present, this applies to 81 these values of the ifType variable in the Internet-standard MIB: 83 ds0 (81) 84 ds0Bundle (82) 86 3.1. BONDing Terminology Please reference The BONDing Spec {9] for 87 definitions of terms used to describe bonding modes. 89 3.2. Use of ifTable for DS0 Layer 91 The following items are defined in rfc1573 [5]. 93 Only the ifGeneralGroup needs to be supported. 95 ifTable Object Use for DS0 Layer 96 ====================================================================== 97 ifIndex Interface index. 99 ifDescr Textual Description of the interface 101 ifType ds0(81) or ds0Bundle (82) 103 ifSpeed 64000 for ds0 104 n * 64000 for ds0Bundle 106 ifPhysAddress The value of the Circuit Identifier. 107 If no Circuit Identifier has been assigned 108 this object should have an octet string with 109 zero length. 111 ifAdminStatus Supports read-only access. 112 The desired administrative status of the 113 interface. 115 ifOperStatus The current operational status of the 116 interface. 118 ifLastChange sysUpTime at the last change in 119 ifOperStatus. 121 ifName Textual name of the interface or an 122 OCTET STRING of zero length. 124 ifLinkUpDownTrapEnable Set to disabled(2). 125 Supports read-only access. 127 ifHighSpeed 0 129 ifConnectorPresent Set to false(2). 131 3.3. Using ifStackTable 133 This section describes by example how to use ifStackTable to 134 represent the relationship of ds0 and ds0Bundles with ds1 interfaces. 135 Implementors of the stack table for ds0 and ds0Bundle interfaces 136 shouls look at the appropriate RFC for the service being stacked on 137 ds0s and ds0Bundles. Examples given below are for illustration 138 purposes only. 140 Example: A Frame Relay Service is being carried on 4 ds0s of a ds1. 142 +---------------------+ 143 | Frame Relay Service | 144 +---------------------+ 145 | 146 +---------------------+ 147 | ds0Bundle | 148 +---------------------+ 149 | | | | 150 +---+ +---+ +---+ +---+ 151 |ds0| |ds0| |ds0| |ds0| 152 +---+ +---+ +---+ +---+ 153 | | | | 154 +---------------------+ 155 | ds1 | 156 +---------------------+ 158 The assignment of the index values could for example be: 160 ifIndex Description 161 1 FrameRelayService (type 44) 162 2 ds0Bundle (type 82) 163 3 ds0 #1 (type 81) 164 4 ds0 #2 (type 81) 165 5 ds0 #3 (type 81) 166 6 ds0 #4 (type 81) 167 7 ds1 (type 18) 169 The ifStackTable is then used to show the relationships between the 170 various interfaces. 172 ifStackTable Entries 174 HigherLayer LowerLayer 175 0 1 176 1 2 177 2 3 178 2 4 179 2 5 180 2 6 181 3 7 182 4 7 183 5 7 184 6 7 185 7 0 187 In the case where the frameRelayService is using a single ds0, then 188 the ds0Bundle is not required. 190 +---------------------+ 191 | Frame Relay Service | 192 +---------------------+ 193 | 194 +---+ 195 |ds0| 196 +---+ 197 | 198 +---------------------+ 199 | ds1 | 200 +---------------------+ 202 The assignment of the index values could for example be: 204 ifIndex Description 205 1 FrameRelayService (type 44) 206 2 ds0 (type 81) 207 3 ds1 (type 18) 209 The ifStackTable is then used to show the relationships between the 210 various interfaces. 212 ifStackTable Entries 214 HigherLayer LowerLayer 215 0 1 216 1 2 217 2 3 218 3 0 220 4. Object Definitions for Ds0 222 DS0-MIB DEFINITIONS ::= BEGIN 224 IMPORTS 225 MODULE-IDENTITY, OBJECT-TYPE 226 FROM SNMPv2-SMI 227 MODULE-COMPLIANCE, OBJECT-GROUP 228 FROM SNMPv2-CONF 229 TruthValue 230 FROM SNMPv2-TC 231 ifIndex 232 FROM IF-MIB 233 transmission 234 FROM RFC1213-MIB; 236 -- This is the MIB module for the DS0 Interface objects. 238 ds0 MODULE-IDENTITY 239 LAST-UPDATED "9602072050Z" 240 ORGANIZATION "IETF Trunk MIB Working Group" 241 CONTACT-INFO 242 " David Fowler 244 Postal: Newbridge Networks Corporation 245 600 March Road 246 Kanata, Ontario, Canada K2K 2E6 248 Tel: +1 613 591 3600 249 Fax: +1 613 591 3680 251 E-mail: davef@newbridge.com" 252 DESCRIPTION 253 "The MIB module to describe 254 DS0 interfaces objects." 256 ::= { transmission 81 } 258 -- The DS0 Config Group 260 -- Implementation of this group is optional for all 261 -- systems that use a DS0 Interface. 263 -- The DS0 Config Group consists of one table: 264 -- DS0 Configuration 266 -- the DS0 Configuration Table 268 dsx0ConfigTable OBJECT-TYPE 269 SYNTAX SEQUENCE OF Dsx0ConfigEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "The DS0 Configuration table." 274 ::= { ds0 1 } 276 dsx0ConfigEntry OBJECT-TYPE 277 SYNTAX Dsx0ConfigEntry 278 MAX-ACCESS not-accessible 279 STATUS current 280 DESCRIPTION 281 "An entry in the DS0 Configuration table." 282 INDEX { ifIndex } 283 ::= { dsx0ConfigTable 1 } 285 Dsx0ConfigEntry ::= 286 SEQUENCE { 287 dsx0Ds0Number 288 INTEGER, 289 dsx0RobbedBitSignalling 290 INTEGER 291 } 293 dsx0Ds0Number OBJECT-TYPE 294 SYNTAX INTEGER(1..31) 295 MAX-ACCESS read-write 296 STATUS current 297 DESCRIPTION 298 "This object indicates the channel number of the 299 ds0 on its ds1/e1." 300 ::= { dsx0ConfigEntry 1 } 302 dsx0RBSEnable OBJECT-TYPE 303 SYNTAX TruthValue 304 MAX-ACCESS read-write 305 STATUS current 306 DESCRIPTION 307 "This object indicates if Robbed Bit Signalling is 308 turned on or off for a given ds0." 309 ::= { dsx0ConfigEntry 2 } 311 -- conformance information 313 ds0Conformance OBJECT IDENTIFIER ::= { ds0 2 } 315 ds0Groups OBJECT IDENTIFIER ::= { ds0Conformance 1 } 316 ds0Compliances OBJECT IDENTIFIER ::= { ds0Conformance 2 } 318 -- compliance statements 320 ds0Compliance MODULE-COMPLIANCE 321 STATUS current 322 DESCRIPTION 323 "The compliance statement for DS0 interfaces." 324 MODULE -- this module 325 GROUP ds0ConfigGroup 326 DESCRIPTION 327 "Implementation of this group is optional for all 328 systems that attach to a DS0 Interface." 329 ::= { ds0Compliances 1 } 331 -- units of conformance 333 ds0ConfigGroup OBJECT-GROUP 334 OBJECTS { dsx0Ds0Number, 335 dsx0RBS } 336 STATUS current 337 DESCRIPTION 338 "A collection of objects providing configuration 339 information applicable to all DS0 interfaces." 340 ::= { ds0Groups 1 } 342 END 344 5. Object Definitions for Ds0 Bundle 346 DS0BUNDLE-MIB DEFINITIONS ::= BEGIN 348 IMPORTS 349 MODULE-IDENTITY, OBJECT-TYPE 350 FROM SNMPv2-SMI 351 MODULE-COMPLIANCE, OBJECT-GROUP 352 FROM SNMPv2-CONF 353 RowStatus 354 FROM SNMPv2-TC 355 ifIndex 356 FROM IF-MIB 357 transmission 358 FROM RFC1213-MIB; 360 -- This is the MIB module for the DS0Bundle Interface objects. 362 ds0Bundle MODULE-IDENTITY 363 LAST-UPDATED "9602072050Z" 364 ORGANIZATION "IETF Trunk MIB Working Group" 365 CONTACT-INFO 366 " David Fowler 368 Postal: Newbridge Networks Corporation 369 600 March Road 370 Kanata, Ontario, Canada K2K 2E6 372 Tel: +1 613 591 3600 373 Fax: +1 613 591 3680 375 E-mail: davef@newbridge.com" 376 DESCRIPTION 377 "The MIB module to describe 378 DS0 Bundle interfaces objects." 380 ::= { transmission 82 } 382 -- The DS0 Bonding Group 384 -- Implementation of this group is optional for all 385 -- systems that use a DS0Bundle Interface. 387 -- The DS0 Bonding Group consists of one table: 388 -- DS0 Bonding 390 -- the DS0 Bonding Table 392 dsx0BondingTable OBJECT-TYPE 393 SYNTAX SEQUENCE OF Dsx0BondingEntry 394 MAX-ACCESS not-accessible 395 STATUS current 396 DESCRIPTION 397 "The DS0 Bonding table." 398 ::= { ds0Bundle 1 } 400 dsx0BondingEntry OBJECT-TYPE 401 SYNTAX Dsx0BondingEntry 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "An entry in the DS0 Bonding table." 406 INDEX { ifIndex } 407 ::= { dsx0BondingTable 1 } 409 Dsx0BondingEntry ::= 410 SEQUENCE { 411 dsx0BondMode 412 INTEGER, 413 dsx0BondStatus 414 INTEGER, 415 dsx0BondRowStatus 416 RowStatus 417 } 419 dsx0BondMode OBJECT-TYPE 420 SYNTAX INTEGER { 421 dsx0BondModeNone(1), 422 dsx0BondModeOther(2), 423 dsx0BondMode0(3), 424 dsx0BondMode1(4), 425 dsx0BondMode2(5), 426 dsx0BondMode3(6) 428 } 429 MAX-ACCESS read-create 430 STATUS current 431 DESCRIPTION 432 "This object indicates which BONDing mode is used, 433 if any, for a ds0Bundle. Mode0 provides paramter 434 and number exchange with no synchronization. Mode1 435 provides parameter but not number exchange with no 436 synchronization. Mode2 does synchronization 437 detection using in-band monitoring. Mode3 does 438 perform synchronization detection using single 439 channel overhead. ModeNone should be used when the 440 interface is not performing bandwidth-on-demand." 441 ::= { dsx0BondingEntry 1 } 443 dsx0BondStatus OBJECT-TYPE 444 SYNTAX INTEGER { 445 dsx0BondIdle(1), 446 dsx0BondCallSetup(2), 447 dsx0BondDataTransfer(3) 448 } 449 MAX-ACCESS read-create 450 STATUS current 451 DESCRIPTION 452 "This object indicates the current status of the 453 bonding call using this ds0Bundle. dsx0BondIdle 454 (1) should be used when the bonding mode is set to 455 dsx0BondModeNone (1)." 456 ::= { dsx0BondingEntry 2 } 458 dsx0BondRowStatus OBJECT-TYPE 459 SYNTAX RowStatus 460 MAX-ACCESS read-create 461 STATUS current 462 DESCRIPTION 463 "This object is used to create new rows in this 464 table, modify existing rows, and to delete 465 existing rows." 466 ::= { dsx0BondingEntry 3 } 468 -- conformance information 469 ds0BundleConformance OBJECT IDENTIFIER ::= { ds0Bundle 2 } 471 ds0BundleGroups OBJECT IDENTIFIER ::= { ds0BundleConformance 1 } 472 ds0BundleCompliances OBJECT IDENTIFIER ::= { ds0BundleConformance 2 } 474 -- compliance statements 476 ds0BundleCompliance MODULE-COMPLIANCE 477 STATUS current 478 DESCRIPTION 479 "The compliance statement for DS0Bundle 480 interfaces." 481 MODULE -- this module 482 GROUP ds0BondingGroup 483 DESCRIPTION 484 "Implementation of this group is optional for all 485 systems that attach to a DS0Bundle Interface." 486 ::= { ds0BundleCompliances 1 } 488 -- units of conformance 490 ds0BondingGroup OBJECT-GROUP 491 OBJECTS { dsx0BondMode, 492 dsx0BondStatus 493 dsx0BondRowStatus } 494 STATUS current 495 DESCRIPTION 496 "A collection of objects providing configuration 497 information applicable to all DS0 interfaces." 498 ::= { ds0BundleGroups 1 } 500 END 502 6. Acknowledgments 504 This document was produced by the Trunk MIB Working Group: 506 7. References 508 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 509 S. Waldbusser, "Structure of Management Information for Version 2 510 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 511 January 1996. 513 [2] McCloghrie, K., and M. Rose, Editors, "Management 514 Information Base for Network Management of TCP/IP-based 515 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 516 Performance Systems International, March 1991. 518 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple 519 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 520 Research, Performance Systems International, MIT Lab for 521 Computer Science, May 1990. 523 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 524 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 525 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 527 [5] McCloghrie, K. and F. Kastenholz, "Evolution of the 528 Interfaces Group of MIB-II", RFC 1573, Hughes LAN 529 Systems, FTP Software, January 1994. 531 [6] Fowler, D., "Definitions of Managed Objects 532 for the DS1/E1/DS2/E2 Interface Types", RFC1406, 533 Newbridge Networks, February 1996. 535 [7] Fowler, D., "Definitions of Managed Objects 536 for the DS3/E3 Interface Types", RFC1407, 537 Newbridge Networks, February 1996. 539 [8] Brown, T., and Tesink, K., "Definitions of Managed Objects 540 for the SONET/SDH Interface Type", RFC1595, Bell Communications 541 Research, March 1994. 543 [9] Sharp, H. (Editor), "Interoperability Requirements for Nx56/64 544 kbit/s Calls", BONDING Spec Version 1.0, BONSING Consortium, 545 Spet 1992. 547 8. Security Considerations 549 Security issues are not discussed in this memo. 551 9. Authors' Addresses 553 David Fowler 554 Newbridge Networks 555 600 March Road 556 Kanata, Ontario, Canada K2K 2E6 558 Phone: (613) 599-3600, ext 3538 560 EMail: davef@newbridge.com 562 Table of Contents 564 1 The SNMPv2 Network Management Framework ...................... 2 565 2 Objects ...................................................... 3 566 3 Overview ..................................................... 4 567 3.1 BONDing Terminology ........................................ 4 568 3.2 Use of ifTable for DS0 Layer ............................... 4 569 3.3 Using ifStackTable ......................................... 5 570 4 Object Definitions for Ds0 ................................... 8 571 4.1 The DS0 Config Group ....................................... 9 572 4.1.1 The DS0 Configuration Table .............................. 9 573 5 Object Definitions for Ds0 Bundle ............................ 11 574 5.1 The DS0 Bonding Group ...................................... 12 575 5.1.1 The DS0 Bonding Table .................................... 12 576 6 Acknowledgments .............................................. 14 577 7 References ................................................... 15 578 8 Security Considerations ...................................... 16 579 9 Authors' Addresses ........................................... 16