idnits 2.17.1 draft-ietf-idmr-cbt-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. ** 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. == 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 2 characters in excess of 72. ** The abstract seems to contain references ([5], [6]), 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 (July 18, 1997) is 9776 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) -- Possible downref: Non-RFC (?) normative reference: ref. '5' == Outdated reference: A later version (-14) exists of draft-ietf-idmr-multicast-routmib-05 Summary: 13 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Inter-Domain Multicast Routing (IDMR) A. Ballardie 2 INTERNET-DRAFT Consultant 3 Expires January 1998 D. Thaler 4 U. Michigan 5 July 18, 1997 7 Core Based Trees (CBT) Multicast Routing MIB 8 10 Status of this Memo 12 This document is an Internet Draft. Internet Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its Areas, and 14 its Working Groups. Note that other groups may also distribute working 15 documents as Internet Drafts. 17 Internet Drafts are valid for a maximum of six months and may be 18 updated, replaced, or obsoleted by other documents at any time. It is 19 inappropriate to use Internet Drafts as reference material or to cite 20 them other than as a "work in progress". 22 Abstract 24 This memo defines an experimental portion of the Management Information 25 Base (MIB) for use with network management protocols in the Internet 26 community. More precisely, it describes managed objects specific to the 27 Core Based Trees (CBT) multicast routing protocol version 2 [5]. Managed 28 objects which are common to all multicast routing protocols, including 29 CBT, can be found in [6]. 31 This MIB module is applicable to IP multicast routers which implement 32 CBTv2. 34 1. Introduction 36 This memo defines an experimental portion of the Management Information 37 Base (MIB) for use with network management protocols in the Internet 38 community. More precisely, it describes managed objects specific to the 39 Core Based Trees (CBT) multicast routing protocol version 2 [5]. Managed 40 objects which are common to all multicast routing protocols, including 41 CBT, can be found in [6]. 43 This MIB module is applicable to IP multicast routers which implement 44 CBTv2. 46 2. The SNMPv2 Network Management Framework 48 The SNMPv2 Network Management Framework presently consists of three 49 major components. They are: 51 o RFC 1902 [1] defines the structure of management information (SMI) 52 for SNMPv2. This deals with the mechanisms used for describing and 53 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 1157 [3] and RFC 1905 [4] define two versions of the protocol 59 used for network access to managed objects. This protocol is called 60 the "Simple Network Management Protocol". 62 The Framework permits new objects to be defined for the purpose of 63 experimentation and evaluation. 65 2.1. Object Definitions 67 Managed objects are accessed via a virtual information store, known as 68 the Management Information Base or MIB. Objects in the MIB are defined 69 using a subset of the Abstract Syntax Notation One (ASN.1) data 70 definition language; this subset is defined in the SMI [1]. Each object 71 type is named by an Object Identifier - an administratively assigned 72 name. The object type together with an object instance serves to 73 uniquely identify a specific instantiation of the object. 75 3. Overview 77 This MIB controls all aspects of the CBT protocol. It consists of five 78 groups: 80 o The cbtGeneralGroup is used to describe general configuration 81 information for all CBT routers. 83 o The cbtInterfaceGroup is used to describe interface configuration 84 and statistics. 86 o The cbtBootstrapGroup is used to describe information relating to 87 auto-bootstrapping for core discovery. 89 o The cbtStaticMappingGroup is used to describe static 90 mappings when auto-bootstrapping is not in use. 92 o The cbtBorderGroup is used to describe configuration information 93 for CBT border routers. 95 4. Definitions 97 CBT-MIB DEFINITIONS ::= BEGIN 99 IMPORTS 100 MODULE-IDENTITY, OBJECT-TYPE, experimental, 101 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 102 RowStatus, TruthValue FROM SNMPv2-TC 103 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 105 cbtMIB MODULE-IDENTITY 106 LAST-UPDATED "9706041500Z" 107 ORGANIZATION "IETF IDMR Working Group." 108 CONTACT-INFO 109 " Tony Ballardie, 110 Research Consultant, 112 EMail: ABallardie@acm.org" 113 DESCRIPTION 114 "The MIB module for management of CBT routers." 115 ::= { experimental XX } 117 cbtMIBObjects OBJECT IDENTIFIER ::= { cbtMIB 1 } 119 cbt OBJECT IDENTIFIER ::= { cbtMIBObjects 1 } 121 -- 122 -- The CBT General Group 123 -- 125 cbtCoreDiscoveryMethod OBJECT-TYPE 126 SYNTAX INTEGER { 127 static(1), -- using static configuration 128 bootstrap(2) -- using bootstrap for core discovery 129 } 130 MAX-ACCESS read-write 131 STATUS current 132 DESCRIPTION 133 "Indicates which method this CBT router is using for core 134 discovery. Note that all routers in the CBT domain must use 135 the same method." 136 ::= { cbt 3 } 138 -- 139 -- The CBT Interface Group 140 -- 142 cbtInterfaceTable OBJECT-TYPE 143 SYNTAX SEQUENCE OF CbtInterfaceEntry 144 MAX-ACCESS not-accessible 145 STATUS current 146 DESCRIPTION 147 "The (conceptual) table listing the router's CBT interfaces. 148 CBT is enabled on all interfaces listed in this table." 149 ::= { cbt 4 } 151 cbtInterfaceEntry OBJECT-TYPE 152 SYNTAX CbtInterfaceEntry 153 MAX-ACCESS not-accessible 154 STATUS current 155 DESCRIPTION 156 "An entry (conceptual row) in the cbtInterfaceTable." 157 INDEX { cbtInterfaceIfIndex } 158 ::= { cbtInterfaceTable 1 } 160 CbtInterfaceEntry ::= SEQUENCE { 161 cbtInterfaceIfIndex Integer32, 162 cbtInterfaceAddress IpAddress, 163 cbtInterfaceDR IpAddress, 164 cbtInterfaceHelloPreference Integer32, 165 cbtInterfaceHelloInterval Integer32, 166 cbtInterfaceStatus RowStatus 167 } 169 cbtInterfaceIfIndex OBJECT-TYPE 170 SYNTAX Integer32 171 MAX-ACCESS not-accessible 172 STATUS current 173 DESCRIPTION 174 "The ifIndex value of this CBT interface." 175 ::= { cbtInterfaceEntry 1 } 177 cbtInterfaceAddress OBJECT-TYPE 178 SYNTAX IpAddress 179 MAX-ACCESS read-only 180 STATUS current 181 DESCRIPTION 182 "The IP address of the CBT interface." 184 ::= { cbtInterfaceEntry 2 } 186 cbtInterfaceDR OBJECT-TYPE 187 SYNTAX IpAddress 188 MAX-ACCESS read-only 189 STATUS current 190 DESCRIPTION 191 "The Designated Router's address on this CBT interface. For 192 point-to-point interfaces, this object has the value 193 0.0.0.0. If the local router is the DR, then the value will 194 be equal to cbtInterfaceAddress." 195 ::= { cbtInterfaceEntry 5 } 197 cbtInterfaceHelloPreference OBJECT-TYPE 198 SYNTAX Integer32 (1..255) 199 MAX-ACCESS read-create 200 STATUS current 201 DESCRIPTION 202 "This router's configured Hello preference value on this 203 interface. This object does not report the preference value 204 currently in use by the DR, which is always zero." 205 DEFVAL { 255 } 206 ::= { cbtInterfaceEntry 6 } 208 cbtInterfaceHelloInterval OBJECT-TYPE 209 SYNTAX Integer32 210 UNITS "seconds" 211 MAX-ACCESS read-create 212 STATUS current 213 DESCRIPTION 214 "The frequency at which CBT HELLO messages are transmitted 215 on this CBT interface." 216 DEFVAL { 60 } 217 ::= { cbtInterfaceEntry 7 } 219 cbtInterfaceStatus OBJECT-TYPE 220 SYNTAX RowStatus 221 MAX-ACCESS read-create 222 STATUS current 223 DESCRIPTION 224 "The status of this entry. Creating the entry enables CBT 225 on the interface; destroying the entry disables CBT on the 226 interface." 227 ::= { cbtInterfaceEntry 10 } 229 -- 230 -- The CBT Bootstrap Group 231 -- 233 cbtBSRAddress OBJECT-TYPE 234 SYNTAX IpAddress 235 MAX-ACCESS read-only 236 STATUS current 237 DESCRIPTION 238 "The IP address of the bootstrap router (BSR) for the local 239 CBT region." 240 ::= { cbt 8 } 242 cbtBSRExpiryTime OBJECT-TYPE 243 SYNTAX TimeTicks 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 "The minimum time remaining before the bootstrap router will 248 be declared down. For candidate BSRs, this is the time until 249 it sends an Core-Set message. For other routers, this is the 250 time until it may accept an Core-Set message from a lower 251 candidate BSR." 252 ::= { cbt 9 } 254 cbtCandidateBSRPreference OBJECT-TYPE 255 SYNTAX Integer32 (-1..255) 256 MAX-ACCESS read-write 257 STATUS current 258 DESCRIPTION 259 "The preference value for the local system as a candidate 260 bootstrap router. The value of -1 is used to indicate that 261 the local system is not a candidate BSR." 262 ::= { cbt 10 } 264 cbtCandidateCoreHoldTime OBJECT-TYPE 265 SYNTAX Integer32 (0..255) 266 UNITS "seconds" 267 MAX-ACCESS read-write 268 STATUS current 269 DESCRIPTION 270 "The holdtime of the local system when it is a candidate 271 Core. The value of 0 is used to indicate that the local 272 system is not a Candidate-Core." 273 ::= { cbt 11 } 275 -- The CBT Core-Set Table 277 cbtCoreSetTable OBJECT-TYPE 278 SYNTAX SEQUENCE OF CbtCoreSetEntry 279 MAX-ACCESS not-accessible 280 STATUS current 281 DESCRIPTION 282 "The (conceptual) table listing CBT information for 283 candidate Core routers for IP multicast groups. When the 284 local router is the BSR, this information is obtained from 285 received Candidate-Core-Advertisements. When the local 286 router is not the BSR, this information is obtained from 287 received Core-Set messages." 288 ::= { cbt 5 } 290 cbtCoreSetEntry OBJECT-TYPE 291 SYNTAX CbtCoreSetEntry 292 MAX-ACCESS not-accessible 293 STATUS current 294 DESCRIPTION 295 "An entry (conceptual row) in the cbtCoreSetTable." 296 INDEX { cbtCoreSetGroupAddress, cbtCoreSetGroupMask, 297 cbtCoreSetAddress } 298 ::= { cbtCoreSetTable 1 } 300 CbtCoreSetEntry ::= SEQUENCE { 301 cbtCoreSetGroupAddress IpAddress, 302 cbtCoreSetGroupMask IpAddress, 303 cbtCoreSetAddress IpAddress, 304 cbtCoreSetHoldTime Integer32, 305 cbtCoreSetExpiryTime TimeTicks 306 } 308 cbtCoreSetGroupAddress OBJECT-TYPE 309 SYNTAX IpAddress 310 MAX-ACCESS not-accessible 311 STATUS current 312 DESCRIPTION 313 "The IP multicast group address which, when combined with 314 cbtCoreSetGroupMask, gives the group prefix for which this 315 entry contains information about the Candidate-Core." 316 ::= { cbtCoreSetEntry 1 } 318 cbtCoreSetGroupMask OBJECT-TYPE 319 SYNTAX IpAddress 320 MAX-ACCESS not-accessible 321 STATUS current 322 DESCRIPTION 323 "The multicast group address mask which, when combined with 324 cbtCoreSetGroupAddress, gives the group prefix for which 325 this entry contains information about the Candidate-Core." 326 ::= { cbtCoreSetEntry 2 } 328 cbtCoreSetAddress OBJECT-TYPE 329 SYNTAX IpAddress 330 MAX-ACCESS not-accessible 331 STATUS current 332 DESCRIPTION 333 "The IP address of the Candidate-Core." 334 ::= { cbtCoreSetEntry 3 } 336 cbtCoreSetHoldTime OBJECT-TYPE 337 SYNTAX Integer32 (0..255) 338 UNITS "seconds" 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The holdtime of a Candidate-Core. If the local router is 343 not the BSR, this value is 0." 344 ::= { cbtCoreSetEntry 4 } 346 cbtCoreSetExpiryTime OBJECT-TYPE 347 SYNTAX TimeTicks 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The minimum time remaining before the Candidate-Core will 352 be declared down. If the local router is not the BSR, this 353 value is 0." 354 ::= { cbtCoreSetEntry 5 } 356 -- The CBT Candidate-Core Table 358 cbtCandidateCoreTable OBJECT-TYPE 359 SYNTAX SEQUENCE OF CbtCandidateCoreEntry 360 MAX-ACCESS not-accessible 361 STATUS current 362 DESCRIPTION 363 "The (conceptual) table listing the IP multicast groups for 364 which the local router is to advertise itself as a 365 Candidate-Core when the value of cbtCandidateCoreHoldTime is 366 non-zero. If this table is empty, then the local router 367 will advertise itself as a Candidate-Core for all groups 368 (providing the value of cbtCandidateCoreHoldTime is non- 369 zero)." 370 ::= { cbt 6 } 372 cbtCandidateCoreEntry OBJECT-TYPE 373 SYNTAX CbtCandidateCoreEntry 374 MAX-ACCESS not-accessible 375 STATUS current 376 DESCRIPTION 377 "An entry (conceptual row) in the cbtCandidateCoreTable." 378 INDEX { cbtCandidateCoreGroupAddress, 379 cbtCandidateCoreGroupMask } 380 ::= { cbtCandidateCoreTable 1 } 382 CbtCandidateCoreEntry ::= SEQUENCE { 383 cbtCandidateCoreGroupAddress IpAddress, 384 cbtCandidateCoreGroupMask IpAddress, 385 cbtCandidateCoreAddress IpAddress, 386 cbtCandidateCoreRowStatus RowStatus 387 } 389 cbtCandidateCoreGroupAddress OBJECT-TYPE 390 SYNTAX IpAddress 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "The IP multicast group address which, when combined with 395 cbtCandidateCoreGroupMask, identifies a group prefix for 396 which the local router will advertise itself as a 397 Candidate-Core." 398 ::= { cbtCandidateCoreEntry 1 } 400 cbtCandidateCoreGroupMask OBJECT-TYPE 401 SYNTAX IpAddress 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "The multicast group address mask which, when combined with 406 cbtCandidateCoreGroupMask, identifies a group prefix for 407 which the local router will advertise itself as a 408 Candidate-Core." 410 ::= { cbtCandidateCoreEntry 2 } 412 cbtCandidateCoreAddress OBJECT-TYPE 413 SYNTAX IpAddress 414 MAX-ACCESS read-create 415 STATUS current 416 DESCRIPTION 417 "The (unicast) address of the interface which will be 418 advertised as a Candidate-Core." 419 ::= { cbtCandidateCoreEntry 3 } 421 cbtCandidateCoreRowStatus OBJECT-TYPE 422 SYNTAX RowStatus 423 MAX-ACCESS read-create 424 STATUS current 425 DESCRIPTION 426 "The status of this row, by which new entries may be 427 created, or old entries deleted from this table." 428 ::= { cbtCandidateCoreEntry 4 } 430 -- 431 -- The CBT Static Mapping Group 432 -- 434 -- CBT Static Core Mapping Table 436 cbtStaticCoreTable OBJECT-TYPE 437 SYNTAX SEQUENCE OF CbtStaticCoreEntry 438 MAX-ACCESS not-accessible 439 STATUS current 440 DESCRIPTION 441 "The (conceptual) table containing mappings." 442 ::= { cbt 7 } 444 cbtStaticCoreEntry OBJECT-TYPE 445 SYNTAX CbtStaticCoreEntry 446 MAX-ACCESS not-accessible 447 STATUS current 448 DESCRIPTION 449 "An entry (conceptual row) containing mapping 450 information." 451 INDEX { cbtCoreGroupAddress, 452 cbtCoreGroupMask } 453 ::= { cbtStaticCoreTable 1} 455 CbtStaticCoreEntry ::= SEQUENCE { 456 cbtCoreGroupAddress IpAddress, 457 cbtCoreGroupMask IpAddress, 458 cbtCoreAddress IpAddress, 459 cbtCoreRowStatus RowStatus 460 } 462 cbtCoreGroupAddress OBJECT-TYPE 463 SYNTAX IpAddress 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "IP class D (group) address." 468 ::= { cbtStaticCoreEntry 1 } 470 cbtCoreGroupMask OBJECT-TYPE 471 SYNTAX IpAddress 472 MAX-ACCESS not-accessible 473 STATUS current 474 DESCRIPTION 475 "Network mask covering group address to represent a 476 contiguous range of group addresses associated with a 477 particular core router." 478 ::= { cbtStaticCoreEntry 2 } 480 cbtCoreAddress OBJECT-TYPE 481 SYNTAX IpAddress 482 MAX-ACCESS read-create 483 STATUS current 484 DESCRIPTION 485 "IP address of core router for the given group(s)." 486 ::= { cbtStaticCoreEntry 3 } 488 cbtCoreRowStatus OBJECT-TYPE 489 SYNTAX RowStatus 490 MAX-ACCESS read-create 491 STATUS current 492 DESCRIPTION 493 "The status of this row, by which entries may be created or 494 deleted from this table." 495 ::= { cbtStaticCoreEntry 4 } 497 -- 498 -- The CBT Border Group 499 -- 501 cbtBorderRouterAddress OBJECT-TYPE 502 SYNTAX TruthValue 503 MAX-ACCESS read-write 504 STATUS current 505 DESCRIPTION 506 "The IP address which the router is using as the source 507 address in BR_HELLO messages." 508 ::= { cbt 1 } 510 cbtDesignatedBR OBJECT-TYPE 511 SYNTAX IpAddress 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The IP address of the domain's designated border router." 516 ::= { cbt 2 } 518 cbtBRHelloPreference OBJECT-TYPE 519 SYNTAX Integer32 (0..255) 520 MAX-ACCESS read-write 521 STATUS current 522 DESCRIPTION 523 "This router's preference value for BR Hello messages. This 524 object does not report the DBR preference value, which is 525 zero. A value of 0 indicates that the router is not acting 526 as a border router." 527 ::= { cbt 12 } 529 -- conformance information 531 cbtMIBConformance 532 OBJECT IDENTIFIER ::= { cbtMIB 2 } 533 cbtMIBCompliances 534 OBJECT IDENTIFIER ::= { cbtMIBConformance 1 } 535 cbtMIBGroups OBJECT IDENTIFIER ::= { cbtMIBConformance 2 } 537 -- compliance statements 539 cbtRouterMIBCompliance MODULE-COMPLIANCE 540 STATUS current 541 DESCRIPTION 542 "The compliance statement for routers running CBTv2, and 543 implementing the CBT MIB." 544 MODULE -- this module 545 MANDATORY-GROUPS { cbtGeneralGroup, cbtInterfaceGroup } 547 OBJECT cbtInterfaceStatus 548 MIN-ACCESS read-only 549 DESCRIPTION 550 "Write access is not required." 552 GROUP cbtBootstrapGroup 553 DESCRIPTION 554 "The cbtBootstrapGroup is mandatory only for those CBTv2 555 routers which implement auto-bootstrap for Core Discovery." 557 GROUP cbtStaticMappingGroup 558 DESCRIPTION 559 "The cbtBootstrapGroup is mandatory only for those CBTv2 560 routers which implement static mappings." 562 GROUP cbtBorderGroup 563 DESCRIPTION 564 "The cbtBorderGroup is mandatory only for those CBTv2 565 routers which implement multicast border router 566 functionality." 567 ::= { cbtMIBCompliances 1 } 569 -- units of conformance 571 cbtGeneralGroup OBJECT-GROUP 572 OBJECTS { cbtCoreDiscoveryMethod } 573 STATUS current 574 DESCRIPTION 575 "A collection of objects to support management of general 576 CBT configuration information." 577 ::= { cbtMIBGroups 1 } 579 cbtInterfaceGroup OBJECT-GROUP 580 OBJECTS { cbtInterfaceAddress, cbtInterfaceDR, 581 cbtInterfaceHelloPreference, 582 cbtInterfaceHelloInterval, 583 cbtInterfaceStatus } 584 STATUS current 585 DESCRIPTION 586 "A collection of objects to support management of CBT 587 interfaces." 588 ::= { cbtMIBGroups 2 } 590 cbtBorderGroup OBJECT-GROUP 591 OBJECTS { cbtBorderRouterAddress, cbtDesignatedBR, 592 cbtBRHelloPreference } 593 STATUS current 594 DESCRIPTION 595 "A collection of objects to support management of CBT border 596 routers." 597 ::= { cbtMIBGroups 3 } 599 cbtBootstrapGroup OBJECT-GROUP 600 OBJECTS { cbtBSRAddress, cbtBSRExpiryTime, 601 cbtCandidateBSRPreference, cbtCandidateCoreHoldTime, 602 cbtCoreSetHoldTime, cbtCoreSetExpiryTime, 603 cbtCandidateCoreAddress, cbtCandidateCoreRowStatus } 604 STATUS current 605 DESCRIPTION 606 "A collection of objects to support management of 607 information relating to auto-bootstrap as the core discovery 608 mechanism." 609 ::= { cbtMIBGroups 4 } 611 cbtStaticMappingGroup OBJECT-GROUP 612 OBJECTS { cbtCoreAddress, cbtCoreRowStatus } 613 STATUS current 614 DESCRIPTION 615 "A collection of objects to support management of 616 information relating to static configuration as the core 617 discovery mechanism." 619 ::= { cbtMIBGroups 5 } 621 END 622 5. Security Considerations 624 Security issues are not discussed in this memo. 626 6. Acknowledgements 628 Thanks to James Cowan for his review and comments. 630 7. References 632 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 633 S. Waldbusser, "Structure of Management Information for version 2 634 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 635 January 1996. 637 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 638 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 639 RFC 1213, March 1991. 641 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 642 Management Protocol", RFC 1157, May 1990. 644 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 645 S. Waldbusser, "Protocol Operations for version 2 of the Simple 646 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 648 [5] A. Ballardie, "Core Based Trees (CBT version 2) Multicast Routing: 649 Protocol Specification", Working Draft, April 1997. 651 [6] McCloghrie, K., Farinacci, D., and D. Thaler, "IP Multicast Routing 652 MIB", Working draft, draft-ietf-idmr-multicast-routmib-05.txt, 653 March 1997. 655 8. Authors' Addresses 657 Tony Ballardie, 658 Research Consultant. 659 E-mail: ABallardie@acm.org 661 Dave Thaler 662 Department of Electrical Engineering and Computer Science 663 University of Michigan 664 1301 Beal Ave. 665 Ann Arbor, MI 48109-2122 666 Phone: +1 313 763 5243 667 EMail: thalerd@eecs.umich.edu 669 Table of Contents 671 1 Introduction .................................................... 1 672 2 The SNMPv2 Network Management Framework ......................... 2 673 2.1 Object Definitions ............................................ 2 674 3 Overview ........................................................ 2 675 4 Definitions ..................................................... 4 676 5 Security Considerations ......................................... 18 677 6 Acknowledgements ................................................ 18 678 7 References ...................................................... 18 679 8 Authors' Addresses .............................................. 18