idnits 2.17.1 draft-ietf-trunkmib-ds0-mib-03.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 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 is 1 instance of too long lines in the document, the longest one being 1 character 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 (September 1996) is 10078 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 634, 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) == Outdated reference: A later version (-05) exists of draft-ietf-ifmib-mib-03 == Outdated reference: A later version (-09) exists of draft-ietf-trunkmib-ds1-mib-03 ** 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: 16 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT DS0 MIB September 1996 3 Definitions of Managed Objects 4 for the DS0 and DS0 Bundle Interface Type 6 Thu Sep 26 13:55:25 EDT 1996 8 draft-ietf-trunkmib-ds0-mib-03.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, rfcTBD [6], rfcTBD [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 See interfaces MIB [5] 101 ifType ds0(81) or ds0Bundle (82) 103 ifSpeed 64000 for ds0 regardless of the setting 104 of robbed bit signalling 105 n * 64000 for ds0Bundle 107 ifPhysAddress The value of the Circuit Identifier. 108 If no Circuit Identifier has been assigned 109 this object should have an octet string 110 with zero length. 112 ifAdminStatus See interfaces MIB [5] 114 ifOperStatus See interfaces MIB [5] 116 ifLastChange See interfaces MIB [5] 118 ifName See interfaces MIB [5] 119 ifLinkUpDownTrapEnable Set to disabled(2). 120 Supports read-only access. 122 ifHighSpeed 0 124 ifConnectorPresent Set to false(2). 126 3.3. Using ifStackTable 128 This section describes by example how to use ifStackTable to 129 represent the relationship of ds0 and ds0Bundles with ds1 interfaces. 130 Implementors of the stack table for ds0 and ds0Bundle interfaces 131 should look at the appropriate RFC for the service being stacked on 132 ds0s and ds0Bundles. Examples given below are for illustration 133 purposes only. 135 Example: A Frame Relay Service is being carried on 4 ds0s of a ds1. 137 +---------------------+ 138 | Frame Relay Service | 139 +---------------------+ 140 | 141 +---------------------+ 142 | ds0Bundle | 143 +---------------------+ 144 | | | | 145 +---+ +---+ +---+ +---+ 146 |ds0| |ds0| |ds0| |ds0| 147 +---+ +---+ +---+ +---+ 148 | | | | 149 +---------------------+ 150 | ds1 | 151 +---------------------+ 153 The assignment of the index values could for example be: 155 ifIndex Description 156 1 FrameRelayService (type 44) 157 2 ds0Bundle (type 82) 158 3 ds0 #1 (type 81) 159 4 ds0 #2 (type 81) 160 5 ds0 #3 (type 81) 161 6 ds0 #4 (type 81) 162 7 ds1 (type 18) 164 The ifStackTable is then used to show the relationships between the 165 various interfaces. 167 ifStackTable Entries 169 HigherLayer LowerLayer 170 0 1 171 1 2 172 2 3 173 2 4 174 2 5 175 2 6 176 3 7 177 4 7 178 5 7 179 6 7 180 7 0 182 In the case where the frameRelayService is using a single ds0, then 183 the ds0Bundle is not required. 185 +---------------------+ 186 | Frame Relay Service | 187 +---------------------+ 188 | 189 +---+ 190 |ds0| 191 +---+ 192 | 193 +---------------------+ 194 | ds1 | 195 +---------------------+ 197 The assignment of the index values could for example be: 199 ifIndex Description 200 1 FrameRelayService (type 44) 201 2 ds0 (type 81) 202 3 ds1 (type 18) 204 The ifStackTable is then used to show the relationships between the 205 various interfaces. 207 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 transmission FROM SNMPv2-SMI 221 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 222 TruthValue FROM SNMPv2-TC 223 ifIndex FROM IF-MIB; 225 -- This is the MIB module for the DS0 Interface objects. 227 ds0 MODULE-IDENTITY 228 LAST-UPDATED "9609261755Z" 229 ORGANIZATION "IETF Trunk MIB Working Group" 230 CONTACT-INFO 231 " David Fowler 233 Postal: Newbridge Networks Corporation 234 600 March Road 235 Kanata, Ontario, Canada K2K 2E6 237 Tel: +1 613 591 3600 238 Fax: +1 613 599 3669 240 E-mail: davef@newbridge.com" 241 DESCRIPTION 242 "The MIB module to describe 243 DS0 interfaces objects." 245 ::= { transmission 81 } 247 -- The DS0 Config Group 249 -- Implementation of this group is optional for all 250 -- systems that use a DS0 Interface. 252 -- The DS0 Config Group consists of one table: 253 -- DS0 Configuration 255 -- the DS0 Configuration Table 257 dsx0ConfigTable OBJECT-TYPE 258 SYNTAX SEQUENCE OF Dsx0ConfigEntry 259 MAX-ACCESS not-accessible 260 STATUS current 261 DESCRIPTION 262 "The DS0 Configuration table." 263 ::= { ds0 1 } 265 dsx0ConfigEntry OBJECT-TYPE 266 SYNTAX Dsx0ConfigEntry 267 MAX-ACCESS not-accessible 268 STATUS current 269 DESCRIPTION 270 "An entry in the DS0 Configuration table." 271 INDEX { ifIndex } 272 ::= { dsx0ConfigTable 1 } 274 Dsx0ConfigEntry ::= 275 SEQUENCE { 276 dsx0Ds0Number INTEGER, 277 dsx0RobbedBitSignalling TruthValue 278 } 280 dsx0Ds0Number OBJECT-TYPE 281 SYNTAX INTEGER(1..31) 282 MAX-ACCESS read-write 283 STATUS current 284 DESCRIPTION 285 "This object indicates the channel number of the 286 ds0 on its ds1/e1." 287 ::= { dsx0ConfigEntry 1 } 289 dsx0RobbedBitSignalling OBJECT-TYPE 290 SYNTAX TruthValue 291 MAX-ACCESS read-write 292 STATUS current 293 DESCRIPTION 294 "This object indicates if Robbed Bit Signalling is 295 turned on or off for a given ds0. This only 296 applies to DS0s on a T1 link." 297 ::= { dsx0ConfigEntry 2 } 299 -- conformance information 301 ds0Conformance OBJECT IDENTIFIER ::= { ds0 2 } 303 ds0Groups OBJECT IDENTIFIER ::= { ds0Conformance 1 } 304 ds0Compliances OBJECT IDENTIFIER ::= { ds0Conformance 2 } 306 -- compliance statements 308 ds0Compliance MODULE-COMPLIANCE 309 STATUS current 310 DESCRIPTION 311 "The compliance statement for DS0 interfaces." 312 MODULE -- this module 313 GROUP ds0ConfigGroup 314 DESCRIPTION 315 "Implementation of this group is optional for all 316 systems that attach to a DS0 Interface." 317 ::= { ds0Compliances 1 } 319 -- units of conformance 321 ds0ConfigGroup OBJECT-GROUP 322 OBJECTS { dsx0Ds0Number, 323 dsx0RobbedBitSignalling } 324 STATUS current 325 DESCRIPTION 326 "A collection of objects providing configuration 327 information applicable to all DS0 interfaces." 328 ::= { ds0Groups 1 } 330 END 332 5. Object Definitions for Ds0 Bundle 334 DS0BUNDLE-MIB DEFINITIONS ::= BEGIN 336 IMPORTS 337 MODULE-IDENTITY, OBJECT-TYPE, 338 transmission FROM SNMPv2-SMI 339 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 340 RowStatus, TestAndIncr FROM SNMPv2-TC 341 ifIndex, InterfaceIndex FROM IF-MIB; 343 -- This is the MIB module for the DS0Bundle Interface 344 -- objects. 346 ds0Bundle MODULE-IDENTITY 347 LAST-UPDATED "9609261755Z" 348 ORGANIZATION "IETF Trunk MIB Working Group" 349 CONTACT-INFO 350 " David Fowler 352 Postal: Newbridge Networks Corporation 353 600 March Road 354 Kanata, Ontario, Canada K2K 2E6 356 Tel: +1 613 591 3600 357 Fax: +1 613 599 3669 359 E-mail: davef@newbridge.com" 360 DESCRIPTION 361 "The MIB module to describe 362 DS0 Bundle interfaces objects." 364 ::= { transmission 82 } 366 -- The DS0 Bonding Group 368 -- Implementation of this group is optional for all 369 -- systems that use a DS0Bundle Interface. 371 -- The DS0 Bonding Group consists of one table: 372 -- DS0 Bonding 374 -- the DS0 Bonding Table 376 dsx0BondingTable OBJECT-TYPE 377 SYNTAX SEQUENCE OF Dsx0BondingEntry 378 MAX-ACCESS not-accessible 379 STATUS current 380 DESCRIPTION 381 "The DS0 Bonding table." 382 ::= { ds0Bundle 1 } 384 dsx0BondingEntry OBJECT-TYPE 385 SYNTAX Dsx0BondingEntry 386 MAX-ACCESS not-accessible 387 STATUS current 388 DESCRIPTION 389 "An entry in the DS0 Bonding table." 390 INDEX { ifIndex } 391 ::= { dsx0BondingTable 1 } 393 Dsx0BondingEntry ::= 394 SEQUENCE { 395 dsx0BondMode INTEGER, 396 dsx0BondStatus INTEGER, 397 dsx0BondRowStatus RowStatus 398 } 400 dsx0BondMode OBJECT-TYPE 401 SYNTAX INTEGER { 402 dsx0BondModeNone(1), 403 dsx0BondModeOther(2), 404 dsx0BondMode0(3), 405 dsx0BondMode1(4), 406 dsx0BondMode2(5), 407 dsx0BondMode3(6) 408 } 409 MAX-ACCESS read-create 410 STATUS current 411 DESCRIPTION 412 "This object indicates which BONDing mode is used, 413 if any, for a ds0Bundle. Mode0 provides parameter 414 and number exchange with no synchronization. Mode 415 1 provides parameter and number exchange. Mode 1 416 also provides synchronization during 417 initialization but does not include inband 418 monitoring. Mode 2 provides all of the above plus 419 inband monitoring. Mode 2 also steals 1/64th of 420 the bandwidth of each channel (thus not supporting 421 n x 56/64 kbit/s data channels for most values of 422 n). Mode 3 provides all of the above, but also 423 provides n x 56/64 kbit/s data channels. Most 424 common implementations of Mode 3 add an extra 425 channel to support the inband monitoring overhead. 426 ModeNone should be used when the interface is not 427 performing bandwidth-on-demand." 428 ::= { dsx0BondingEntry 1 } 430 dsx0BondStatus OBJECT-TYPE 431 SYNTAX INTEGER { 432 dsx0BondIdle(1), 433 dsx0BondCallSetup(2), 434 dsx0BondDataTransfer(3) 435 } 436 MAX-ACCESS read-create 437 STATUS current 438 DESCRIPTION 439 "This object indicates the current status of the 440 bonding call using this ds0Bundle. dsx0BondIdle 441 (1) should be used when the bonding mode is set to 442 dsx0BondModeNone (1)." 443 ::= { dsx0BondingEntry 2 } 445 dsx0BondRowStatus OBJECT-TYPE 446 SYNTAX RowStatus 447 MAX-ACCESS read-create 448 STATUS current 449 DESCRIPTION 450 "This object is used to create new rows in this 451 table, modify existing rows, and to delete 452 existing rows." 453 ::= { dsx0BondingEntry 3 } 455 -- 456 -- The DS0 Bundle Stub Group 457 -- 459 dsx0BundleStubNextIndex OBJECT-TYPE 460 SYNTAX TestAndIncr 461 MAX-ACCESS read-write 462 STATUS current 463 DESCRIPTION 464 "This object is used to assist the manager in 465 selecting a value for dsx0BundleStubIndex. 466 Because this object is of syntax TestAndIncr (see 467 the SNMPv2-TC document, RFC1903) it can also be 468 used to avoid race conditions with multiple 469 managers trying to create rows in the table. The 470 alorithm is: 471 while done == false 472 index = GET (dsx0BundleStubNextIndex.0) 473 SET (dsx0BundleStubNextIndex.0=index, 474 dsx0BundleStubRowStatus.index=createAndGo) 476 if errorindex == 1 (failure was because of the 477 TestAndIncr object) 478 done = false 479 else 480 done = true 481 other error handling" 482 ::= { ds0Bundle 2 } 484 dsx0BundleStubTable OBJECT-TYPE 485 SYNTAX SEQUENCE OF Dsx0BundleStubEntry 486 MAX-ACCESS not-accessible 487 STATUS current 488 DESCRIPTION 489 "This table is used to (indirectly) create rows in 490 the ifTable with ifType='ds0Bundle(82)'." 491 ::= { ds0Bundle 3 } 493 dsx0BundleStubEntry OBJECT-TYPE 494 SYNTAX Dsx0BundleStubEntry 495 MAX-ACCESS not-accessible 496 STATUS current 497 DESCRIPTION 498 "A 'stub' for a ds0Bundle interface." 499 INDEX { dsx0BundleStubIndex } 500 ::= { dsx0BundleStubTable 1 } 502 Dsx0BundleStubEntry ::= 503 SEQUENCE { 504 dsx0BundleStubIndex INTEGER, 505 dsx0BundleStubIfIndex InterfaceIndex, 506 dsx0BundleStubRowStatus RowStatus 507 } 509 dsx0BundleStubIndex OBJECT-TYPE 510 SYNTAX INTEGER (0..65535) 511 MAX-ACCESS read-create 512 STATUS current 513 DESCRIPTION 514 "A unique identifier for a ds0Bundle stub. This is 515 not the same value as ifIndex. This table is not 516 indexed by ifIndex because the manager has to 517 choose the index in a createable row and the agent 518 must be allowed to select ifIndex values." 519 ::= { dsx0BundleStubEntry 1 } 521 dsx0BundleStubIfIndex OBJECT-TYPE 522 SYNTAX InterfaceIndex 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "The ifIndex value the agent selected for the new 527 ds0Bundle interface." 528 ::= { dsx0BundleStubEntry 2 } 530 dsx0BundleStubRowStatus OBJECT-TYPE 531 SYNTAX RowStatus 532 MAX-ACCESS read-create 533 STATUS current 534 DESCRIPTION 535 "This object is used to create and delete rows in 536 this table." 537 ::= { dsx0BundleStubEntry 3 } 539 -- conformance information 541 ds0BundleConformance OBJECT IDENTIFIER ::= { ds0Bundle 4} 543 ds0BundleGroups OBJECT IDENTIFIER 544 ::= { ds0BundleConformance 1 } 546 ds0BundleCompliances OBJECT IDENTIFIER 547 ::= { ds0BundleConformance 2 } 549 -- compliance statements 551 ds0BundleCompliance MODULE-COMPLIANCE 552 STATUS current 553 DESCRIPTION 554 "The compliance statement for DS0Bundle 555 interfaces." 556 MODULE -- this module 557 GROUP ds0BondingGroup 558 DESCRIPTION 559 "Implementation of this group is optional for all 560 systems that attach to a DS0Bundle Interface." 562 GROUP ds0BundleStubGroup 563 DESCRIPTION 564 "Implementation of this group is optional for all 565 systems that attach to a DS0Bundle Interface." 566 ::= { ds0BundleCompliances 1 } 568 -- units of conformance 570 ds0BondingGroup OBJECT-GROUP 571 OBJECTS { dsx0BondMode, 572 dsx0BondStatus, 573 dsx0BondRowStatus } 574 STATUS current 575 DESCRIPTION 576 "A collection of objects providing configuration 577 information applicable to all DS0 interfaces." 578 ::= { ds0BundleGroups 1 } 580 ds0BundleStubGroup OBJECT-GROUP 581 OBJECTS { dsx0BundleStubNextIndex, 582 dsx0BundleStubIndex, 583 dsx0BundleStubIfIndex, 584 dsx0BundleStubRowStatus } 585 STATUS current 586 DESCRIPTION 587 "A collection of objects providing the ability to 588 create a new ds0Bundle in the ifTable." 589 ::= { ds0BundleGroups 2 } 590 END 592 6. Acknowledgments 594 This document was produced by the Trunk MIB Working Group: 596 7. References 598 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 599 S. Waldbusser, "Structure of Management Information for Version 600 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 601 January 1996. 603 [2] McCloghrie, K., and M. Rose, Editors, "Management 604 Information Base for Network Management of TCP/IP-based 605 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 606 Performance Systems International, March 1991. 608 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple 609 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 610 Research, Performance Systems International, MIT Lab for 611 Computer Science, May 1990. 613 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 614 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 615 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 617 [5] McCloghrie, K. and F. Kastenholz, "Evolution of the 618 Interfaces Group of MIB-II", draft-ietf-ifmib-mib-03.txt, Cisco, 619 FTP Software, March 1996. 621 [6] Fowler, D., "Definitions of Managed Objects for the 622 DS1/E1/DS2/E2 Interface Types", 623 draft-ietf-trunkmib-ds1-mib-03.txt Newbridge Networks, 624 March 1996. 626 [7] Fowler, D., "Definitions of Managed Objects 627 for the DS3/E3 Interface Types", RFC1407, 628 Newbridge Networks, February 1996. 630 [8] Brown, T., and Tesink, K., "Definitions of Managed Objects 631 for the SONET/SDH Interface Type", RFC1595, Bell Communications 632 Research, March 1994. 634 [9] Sharp, H. (Editor), "Interoperability Requirements for Nx56/64 635 kbit/s Calls", BONDING Spec Version 1.0, BONDING Consortium, 636 Sept 1992. 638 8. Security Considerations 640 Security issues are not discussed in this memo. 642 9. Authors' Addresses 644 David Fowler 645 Newbridge Networks 646 600 March Road 647 Kanata, Ontario, Canada K2K 2E6 649 Phone: (613) 599-3600, ext 6559 651 EMail: davef@newbridge.com 653 Table of Contents 655 1 The SNMPv2 Network Management Framework ...................... 2 656 2 Objects ...................................................... 3 657 3 Overview ..................................................... 4 658 3.1 BONDing Terminology ........................................ 4 659 3.2 Use of ifTable for DS0 Layer ............................... 4 660 3.3 Using ifStackTable ......................................... 5 661 4 Object Definitions for Ds0 ................................... 8 662 4.1 The DS0 Config Group ....................................... 9 663 4.1.1 The DS0 Configuration Table .............................. 9 664 5 Object Definitions for Ds0 Bundle ............................ 11 665 5.1 The DS0 Bonding Group ...................................... 12 666 5.1.1 The DS0 Bonding Table .................................... 12 667 6 Acknowledgments .............................................. 17 668 7 References ................................................... 18 669 8 Security Considerations ...................................... 19 670 9 Authors' Addresses ........................................... 19