idnits 2.17.1 draft-ietf-trunkmib-ds0-mib-00.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-23) 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. == Mismatching filename: the document gives the document name as 'draft-ietf-trunkmib-ds0-00', but the file name used is 'draft-ietf-trunkmib-ds0-mib-00' ** 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: ---------------------------------------------------------------------------- == 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 (February 1996) is 10295 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) ** 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) Summary: 18 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT DS0 MIB February 1996 4 Definitions of Managed Objects 5 for the DS0 and DS0 Bundle Interface Type 7 Fri Feb 9 14:44:57 1996 9 draft-ietf-trunkmib-ds0-00.txt 11 David Fowler (editor) 12 Newbridge Networks 13 davef@newbridge.com 15 Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as ``work in progress.'' 27 To learn the current status of any Internet-Draft, please check the 28 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 29 Directories on ds.internic.net (US East Coast), nic.nordu.net 30 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 31 Rim). 33 Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management protocols in 37 the Internet community. In particular, it describes objects used for 38 managing DS0 and DS0 Bundle interfaces. This document is a companion 39 document with Definitions of Managed Objects for the DS1/E1/DS2/E2, 40 DS3/E3 and SONET/SDH Interface Types, rfc1406 [6], rfc1407 [7] and 41 rfc1595 [8]. 43 This memo specifies a MIB module in a manner that is both compliant 44 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 45 definitions. 47 This memo does not specify a standard for the Internet community. 49 1. The SNMPv2 Network Management Framework 51 The SNMPv2 Network Management Framework consists of four major 52 components. They are: 54 o the SMI, described in RFC 1902 [1] - the mechanisms used for 55 describing and naming objects for the purpose of management. 57 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 58 objects for the Internet suite of protocols. 60 o the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], - the 61 protocol for accessing managed objects. 63 The Framework permits new objects to be defined for the 64 purpose of experimentation and evaluation. 66 2. Objects 68 Managed objects are accessed via a virtual information store, termed 69 the Management Information Base or MIB. Objects in the MIB are 70 defined using the subset of Abstract Syntax Notation One (ASN.1) 71 defined in the SMI. In particular, each object type is named by an 72 OBJECT IDENTIFIER, an administratively assigned name. The object 73 type together with an object instance serves to uniquely identify a 74 specific instantiation of the object. For human convenience, we 75 often use a textual string, termed the descriptor, to also refer to 76 the object type. 78 3. Overview 80 These objects are used when the particular media being used to 81 realize an interface is a DS0 interface. At present, this applies to 82 these values of the ifType variable in the Internet-standard MIB: 84 ds0 (81) 85 ds0Bundle (82) 87 3.1. Use of ifTable for DS0 Layer 89 The following items are defined in rfc1573 [5]. 91 Only the ifGeneralGroup needs to be supported. 93 ifTable Object Use for DS0 Layer 94 ====================================================================== 95 ifIndex Interface index. 97 ifDescr Textual Description of the interface 99 ifType ds0(81) or ds0Bundle (82) 101 ifSpeed 64000 for ds0 102 n * 64000 for ds0Bundle 104 ifPhysAddress The value of the Circuit Identifier. 105 If no Circuit Identifier has been assigned 106 this object should have an octet string with 107 zero length. 109 ifAdminStatus Supports read-only access. 110 The desired administrative status of the 111 interface. 113 ifOperStatus The current operational status of the 114 interface. 116 ifLastChange sysUpTime at the last change in 117 ifOperStatus. 119 ifName Textual name of the interface or an 120 OCTET STRING of zero length. 122 ifLinkUpDownTrapEnable Set to disabled(2). 123 Supports read-only access. 125 ifHighSpeed 0 127 ifConnectorPresent Set to false(2). 129 3.2. Using ifStackTable 131 This section describes by example how to use ifStackTable to 132 represent the relationship of ds0 and ds0Bundles with ds1 interfaces. 134 Example: A Frame Relay Service is being carried on 4 ds0s of a ds1. 136 +---------------------+ 137 | Frame Relay Service | 138 +---------------------+ 139 | 140 +---------------------+ 141 | ds0Bundle | 142 +---------------------+ 143 | | | | 144 +---+ +---+ +---+ +---+ 145 |ds0| |ds0| |ds0| |ds0| 146 +---+ +---+ +---+ +---+ 147 | | | | 148 +---------------------+ 149 | ds1 | 150 +---------------------+ 152 The assignment of the index values could for example be: 154 ifIndex Description 155 1 FrameRelayService (type 44) 156 2 ds0Bundle (type 82) 157 3 ds0 #1 (type 81) 158 4 ds0 #2 (type 81) 159 5 ds0 #3 (type 81) 160 6 ds0 #4 (type 81) 161 7 ds1 (type 18) 163 The ifStackTable is then used to show the relationships between the 164 various interfaces. 166 ifStackTable Entries 168 HigherLayer LowerLayer 169 0 1 170 1 2 171 2 3 172 2 4 173 2 5 174 2 6 175 3 7 176 4 7 177 5 7 178 6 7 179 7 0 181 In the case where the frameRelayService is using a single ds0, then 182 the ds0Bundle is not required. 184 +---------------------+ 185 | Frame Relay Service | 186 +---------------------+ 187 | 188 +---+ 189 |ds0| 190 +---+ 191 | 192 +---------------------+ 193 | ds1 | 194 +---------------------+ 196 The assignment of the index values could for example be: 198 ifIndex Description 199 1 FrameRelayService (type 44) 200 2 ds0 (type 81) 201 3 ds1 (type 18) 203 The ifStackTable is then used to show the relationships between the 204 various interfaces. 206 ifStackTable Entries 208 HigherLayer LowerLayer 209 0 1 210 1 2 211 2 3 212 3 0 214 4. Object Definitions for Ds0 216 DS0-MIB DEFINITIONS ::= BEGIN 218 IMPORTS 219 MODULE-IDENTITY, OBJECT-TYPE 220 FROM SNMPv2-SMI 221 MODULE-COMPLIANCE, OBJECT-GROUP 222 FROM SNMPv2-CONF 223 ifIndex 224 FROM IF-MIB 225 transmission 226 FROM RFC1213-MIB; 228 -- This is the MIB module for the DS0 Interface objects. 230 ds0 MODULE-IDENTITY 231 LAST-UPDATED "9602072050Z" 232 ORGANIZATION "IETF Trunk MIB Working Group" 233 CONTACT-INFO 234 " David Fowler 236 Postal: Newbridge Networks Corporation 237 600 March Road 238 Kanata, Ontario, Canada K2K 2E6 240 Tel: +1 613 591 3600 241 Fax: +1 613 591 3680 243 E-mail: davef@newbridge.com" 244 DESCRIPTION 245 "The MIB module to describe 246 DS0 interfaces objects." 248 ::= { transmission 81 } 250 -- The DS0 Config Group 252 -- Implementation of this group is optional for all 253 -- systems that use a DS0 Interface. 255 -- The DS0 Config Group consists of one table: 256 -- DS0 Configuration 258 -- the DS0 Configuration Table 260 dsx0ConfigTable OBJECT-TYPE 261 SYNTAX SEQUENCE OF Dsx0ConfigEntry 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "The DS0 Configuration table." 266 ::= { ds0 1 } 268 dsx0ConfigEntry OBJECT-TYPE 269 SYNTAX Dsx0ConfigEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "An entry in the DS0 Configuration table." 274 INDEX { ifIndex } 275 ::= { dsx0ConfigTable 1 } 277 Dsx0ConfigEntry ::= 278 SEQUENCE { 279 dsx0Ds0Number 280 INTEGER, 281 dsx0RBS 282 INTEGER 283 } 285 dsx0Ds0Number OBJECT-TYPE 286 SYNTAX INTEGER(1..31) 287 MAX-ACCESS read-write 288 STATUS current 289 DESCRIPTION 290 "This object indicates the channel number of the 291 ds0 on its ds1/e1." 292 ::= { dsx0ConfigEntry 1 } 294 dsx0RBS OBJECT-TYPE 295 SYNTAX INTEGER { 296 dsx0RBSOn(1), 297 dsx0RBSOff(2) 298 } 299 MAX-ACCESS read-write 300 STATUS current 301 DESCRIPTION 302 "This object indicates if Robbed Bit Signalling is 303 turned on or off for a given ds0." 304 ::= { dsx0ConfigEntry 2 } 306 -- conformance information 308 ds0Conformance OBJECT IDENTIFIER ::= { ds0 2 } 310 ds0Groups OBJECT IDENTIFIER ::= { ds0Conformance 1 } 311 ds0Compliances OBJECT IDENTIFIER ::= { ds0Conformance 2 } 313 -- compliance statements 315 ds0Compliance MODULE-COMPLIANCE 316 STATUS current 317 DESCRIPTION 318 "The compliance statement for DS0 interfaces." 319 MODULE -- this module 320 GROUP ds0ConfigGroup 321 DESCRIPTION 322 "Implementation of this group is optional for all 323 systems that attach to a DS0 Interface." 324 ::= { ds0Compliances 1 } 326 -- units of conformance 328 ds0ConfigGroup OBJECT-GROUP 329 OBJECTS { dsx0Ds0Number, 330 dsx0RBS } 331 STATUS current 332 DESCRIPTION 333 "A collection of objects providing configuration 334 information applicable to all DS0 interfaces." 335 ::= { ds0Groups 1 } 337 END 339 5. Object Definitions for Ds0 Bundle 341 DS0BUNDLE-MIB DEFINITIONS ::= BEGIN 343 IMPORTS 344 MODULE-IDENTITY, OBJECT-TYPE 345 FROM SNMPv2-SMI 346 MODULE-COMPLIANCE, OBJECT-GROUP 347 FROM SNMPv2-CONF 348 RowStatus 349 FROM SNMPv2-TC 350 ifIndex 351 FROM IF-MIB 352 transmission 353 FROM RFC1213-MIB; 355 -- This is the MIB module for the DS0Bundle Interface objects. 357 ds0Bundle MODULE-IDENTITY 358 LAST-UPDATED "9602072050Z" 359 ORGANIZATION "IETF Trunk MIB Working Group" 360 CONTACT-INFO 361 " David Fowler 363 Postal: Newbridge Networks Corporation 364 600 March Road 365 Kanata, Ontario, Canada K2K 2E6 367 Tel: +1 613 591 3600 368 Fax: +1 613 591 3680 370 E-mail: davef@newbridge.com" 371 DESCRIPTION 372 "The MIB module to describe 373 DS0 Bundle interfaces objects." 375 ::= { transmission 82 } 377 -- The DS0 Bonding Group 379 -- Implementation of this group is optional for all 380 -- systems that use a DS0Bundle Interface. 382 -- The DS0 Bonding Group consists of one table: 383 -- DS0 Bonding 385 -- the DS0 Bonding Table 387 dsx0BondingTable OBJECT-TYPE 388 SYNTAX SEQUENCE OF Dsx0BondingEntry 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The DS0 Bonding table." 393 ::= { ds0Bundle 1 } 395 dsx0BondingEntry OBJECT-TYPE 396 SYNTAX Dsx0BondingEntry 397 MAX-ACCESS not-accessible 398 STATUS current 399 DESCRIPTION 400 "An entry in the DS0 Bonding table." 401 INDEX { ifIndex } 402 ::= { dsx0BondingTable 1 } 404 Dsx0BondingEntry ::= 405 SEQUENCE { 406 dsx0BondMode 407 INTEGER, 408 dsx0BondStatus 409 INTEGER, 410 dsx0BondRowStatus 411 RowStatus 412 } 414 dsx0BondMode OBJECT-TYPE 415 SYNTAX INTEGER { 416 dsx0BondModeNone(1), 417 dsx0BondModeOther(2), 418 dsx0BondMode0(3), 419 dsx0BondMode1(4), 420 dsx0BondMode2(5), 421 dsx0BondMode3(6) 423 } 424 MAX-ACCESS read-create 425 STATUS current 426 DESCRIPTION 427 "This object indicates which BONDing mode is used, 428 if any, for a ds0Bundle. Mode0 provides paramter 429 and number exchange with no synchronization. Mode1 430 provides parameter but not number exchange with no 431 synchronization. Mode2 does synchronization 432 detection using in-band monitoring. Mode3 does 433 perform synchronization detection using single 434 channel overhead." 435 ::= { dsx0BondingEntry 1 } 437 dsx0BondStatus OBJECT-TYPE 438 SYNTAX INTEGER { 439 dsx0BondIdle(1), 440 dsx0BondCallSetup(2), 441 dsx0BondDataTransfer(3) 442 } 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "This object indicates the current status of the 447 bonding call using this ds0Bundle. dsx0BondIdle 448 (1) should be used when the bonding mode is set to 449 dsx0BondModeNode (1)." 450 ::= { dsx0BondingEntry 2 } 452 dsx0BondRowStatus OBJECT-TYPE 453 SYNTAX RowStatus 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "This object is used to create new rows in this 458 table, modify existing rows, and to delete 459 existing rows." 460 ::= { dsx0BondingEntry 3 } 462 -- conformance information 464 ds0BundleConformance OBJECT IDENTIFIER ::= { ds0Bundle 2 } 465 ds0BundleGroups OBJECT IDENTIFIER ::= { ds0BundleConformance 1 } 466 ds0BundleCompliances OBJECT IDENTIFIER ::= { ds0BundleConformance 2 } 468 -- compliance statements 470 ds0BundleCompliance MODULE-COMPLIANCE 471 STATUS current 472 DESCRIPTION 473 "The compliance statement for DS0Bundle 474 interfaces." 475 MODULE -- this module 476 GROUP ds0BondingGroup 477 DESCRIPTION 478 "Implementation of this group is optional for all 479 systems that attach to a DS0Bundle Interface." 480 ::= { ds0BundleCompliances 1 } 482 -- units of conformance 484 ds0BondingGroup OBJECT-GROUP 485 OBJECTS { dsx0BondMode, 486 dsx0BondStatus 487 dsx0BondRowStatus } 488 STATUS current 489 DESCRIPTION 490 "A collection of objects providing configuration 491 information applicable to all DS0 interfaces." 492 ::= { ds0BundleGroups 1 } 494 END 496 6. Acknowledgments 498 This document was produced by the Trunk MIB Working Group: 500 7. References 502 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 503 S. Waldbusser, "Structure of Management Information for Version 2 504 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 505 January 1996. 507 [2] McCloghrie, K., and M. Rose, Editors, "Management 508 Information Base for Network Management of TCP/IP-based 509 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 510 Performance Systems International, March 1991. 512 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple 513 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 514 Research, Performance Systems International, MIT Lab for 515 Computer Science, May 1990. 517 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 518 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 519 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 521 [5] McCloghrie, K. and F. Kastenholz, "Evolution of the 522 Interfaces Group of MIB-II", RFC 1573, Hughes LAN 523 Systems, FTP Software, January 1994. 525 [6] Fowler, D., "Definitions of Managed Objects 526 for the DS1/E1/DS2/E2 Interface Types", RFC1406, 527 Newbridge Networks, February 1996. 529 [7] Fowler, D., "Definitions of Managed Objects 530 for the DS3/E3 Interface Types", RFC1407, 531 Newbridge Networks, February 1996. 533 [8] Brown, T., and Tesink, K., "Definitions of Managed Objects 534 for the SONET/SDH Interface Type", RFC1595, Bell Communications 535 Research, March 1994. 537 8. Security Considerations 539 Security issues are not discussed in this memo. 541 9. Authors' Addresses 543 David Fowler 544 Newbridge Networks 545 600 March Road 546 Kanata, Ontario, Canada K2K 2E6 548 Phone: (613) 599-3600, ext 3538 550 EMail: davef@newbridge.com 552 Table of Contents 554 1 The SNMPv2 Network Management Framework ...................... 2 555 2 Objects ...................................................... 3 556 3 Overview ..................................................... 4 557 3.1 Use of ifTable for DS0 Layer ............................... 4 558 3.2 Using ifStackTable ......................................... 5 559 4 Object Definitions for Ds0 ................................... 8 560 4.1 The DS0 Config Group ....................................... 9 561 4.1.1 The DS0 Configuration Table .............................. 9 562 5 Object Definitions for Ds0 Bundle ............................ 11 563 5.1 The DS0 Bonding Group ...................................... 12 564 5.1.1 The DS0 Bonding Table .................................... 12 565 6 Acknowledgments .............................................. 14 566 7 References ................................................... 15 567 8 Security Considerations ...................................... 16 568 9 Authors' Addresses ........................................... 16