idnits 2.17.1 draft-ietf-idmr-dvmrp-mib-11.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 26 pages 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. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 354: '...terface key, and MUST be accessible on...' RFC 2119 keyword, line 356: '... agent MAY report an empty s...' RFC 2119 keyword, line 950: '...rpSecurityGroup) MUST NOT be accessibl...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (19 October 1999) is 8949 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 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Downref: Normative reference to an Experimental RFC: RFC 1075 (ref. '16') -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '18' ** Obsolete normative reference: RFC 2667 (ref. '19') (Obsoleted by RFC 4087) Summary: 18 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IDMR Working Group Dave Thaler 2 INTERNET-DRAFT Microsoft 3 Expires April 2000 19 October 1999 5 Distance-Vector Multicast Routing Protocol MIB 6 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with all 11 provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering Task 14 Force (IETF), its areas, and its working groups. Note that other groups 15 may also distribute working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet- Drafts as reference material 20 or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Copyright Notice 30 Copyright (C) The Internet Society (1999). All Rights Reserved. 32 1. Abstract 34 This memo defines a portion of the Management Information Base (MIB) for 35 use with network management protocols in the Internet community. In 36 particular, it describes managed objects used for managing the Distance- 37 Vector Multicast Routing Protocol (DVMRP). 39 Draft DVMRP MIB October 1999 41 2. Introduction 43 This memo defines a portion of the Management Information Base (MIB) for 44 use with network management protocols in the Internet community. In 45 particular, it describes managed objects used for managing the Distance- 46 Vector Multicast Routing Protocol (DVMRP) protocol [16,17]. This MIB 47 module is applicable to IPv4 multicast routers which implement DVMRP. 48 This MIB does not support management of DVMRP for other address 49 families, including IPv6. Such management may be supported by other 50 MIBs. 52 3. The SNMP Network Management Framework 54 The SNMP Management Framework presently consists of five major 55 components: 57 o An overall architecture, described in RFC 2271 [1]. 59 o Mechanisms for describing and naming objects and events for the 60 purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in RFC 62 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 63 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 65 o Message protocols for transferring management information. The 66 first version of the SNMP message protocol is called SNMPv1 and 67 described in RFC 1157 [8]. A second version of the SNMP message 68 protocol, which is not an Internet standards track protocol, is 69 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 70 The third version of the message protocol is called SNMPv3 and 71 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 73 o Protocol operations for accessing management information. The first 74 set of protocol operations and associated PDU formats is described 75 in RFC 1157 [8]. A second set of protocol operations and associated 76 PDU formats is described in RFC 1905 [13]. 78 o A set of fundamental applications described in RFC 2573 [14] and 79 the view-based access control mechanism described in RFC 2575 [15]. 81 Managed objects are accessed via a virtual information store, termed the 82 Management Information Base or MIB. Objects in the MIB are defined 83 using the mechanisms defined in the SMI. 85 Draft DVMRP MIB October 1999 87 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 88 conforming to the SMIv1 can be produced through the appropriate 89 translations. The resulting translated MIB must be semantically 90 equivalent, except where objects or events are omitted because no 91 translation is possible (use of Counter64). Some machine readable 92 information in SMIv2 will be converted into textual descriptions in 93 SMIv1 during the translation process. However, this loss of machine 94 readable information is not considered to change the semantics of the 95 MIB. 97 4. Overview 99 4.1. Structure of MIB 101 Managing DVMRP routers requires the following groups of information: 103 o General statistics. 105 o DVMRP configuration information common to all multicast-capable 106 interfaces. 108 o Information to store DVMRP neighbor information. 110 o Information to store the DVMRP routing table. 112 o Information related to DVMRP tree construction. 114 o Information related to DVMRP security. 116 o Traps used to alert a manager of critical DVMRP events. 118 4.1.1. General Description 120 This MIB controls all aspects of the DVMRP protocol. It consists of six 121 groups of objects, and one group of notifications. The object groups 122 are: 124 o The dvmrpGeneralGroup is used to describe general configuration 125 information. 127 o The dvmrpInterfaceGroup is used to describe interface configuration 128 and statistics, and augments the Multicast Routing Interface Table 129 from the IP Multicast MIB [18]. 131 Draft DVMRP MIB October 1999 133 o The dvmrpNeighborGroup is used to describe peer configuration and 134 statistics. 136 o The dvmrpRoutingGroup is used to describe the DVMRP routing table. 138 o The dvmrpTreeGroup is used to describe DVMRP tree construction 139 state. 141 o The dvmrpSecurityGroup is used to manage keys for securing DVMRP. 143 4.2. Relationship to the IP Tunnel MIB 145 "DVMRP tunnels" (IP-in-IP tunnels which are commonly used with DVMRP) 146 are not managed via this MIB. Instead, the IP Tunnel MIB [19] is used 147 for this purpose. 149 5. Definitions 151 DVMRP-STD-MIB DEFINITIONS ::= BEGIN 153 IMPORTS 154 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 155 Integer32, Counter32, Gauge32, NOTIFICATION-TYPE, 156 IpAddress, TimeTicks FROM SNMPv2-SMI 157 DisplayString, RowStatus FROM SNMPv2-TC 158 MODULE-COMPLIANCE, OBJECT-GROUP, 159 NOTIFICATION-GROUP FROM SNMPv2-CONF 160 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 161 InterfaceIndexOrZero, 162 InterfaceIndex FROM IF-MIB; 164 dvmrpStdMIB MODULE-IDENTITY 165 LAST-UPDATED "9910191200Z" -- October 19, 1999 166 ORGANIZATION "IETF IDMR Working Group." 167 CONTACT-INFO 168 " Dave Thaler 169 Microsoft 170 One Microsoft Way 171 Redmond, WA 98052-6399 172 EMail: dthaler@microsoft.com" 173 DESCRIPTION 174 "The MIB module for management of DVMRP routers." 175 REVISION "9910191200Z" -- October 19, 1999 177 Draft DVMRP MIB October 1999 179 DESCRIPTION 180 "Initial version, published as RFC xxxx (to be filled in by 181 RFC-Editor)." 182 ::= { mib-2 xx } 183 -- NOTE TO RFC EDITOR: When this document is published as an 184 -- RFC, replace xx with IANA assignment, and delete this comment. 186 dvmrpMIBObjects OBJECT IDENTIFIER ::= { dvmrpStdMIB 1 } 188 dvmrp OBJECT IDENTIFIER ::= { dvmrpMIBObjects 1 } 190 dvmrpScalar OBJECT IDENTIFIER ::= { dvmrp 1 } 192 dvmrpVersionString OBJECT-TYPE 193 SYNTAX DisplayString 194 MAX-ACCESS read-only 195 STATUS current 196 DESCRIPTION 197 "The router's DVMRP version information. Similar to 198 sysDescr in MIB-II, this is a free-form field which can be 199 used to display vendor-specific information." 200 ::= { dvmrpScalar 1 } 202 dvmrpGenerationId OBJECT-TYPE 203 SYNTAX Integer32 204 MAX-ACCESS read-only 205 STATUS current 206 DESCRIPTION 207 "The generation identifier for the routing process. This is 208 used by neighboring routers to detect whether the DVMRP 209 routing table should be resent." 210 ::= { dvmrpScalar 2 } 212 dvmrpNumRoutes OBJECT-TYPE 213 SYNTAX Gauge32 214 MAX-ACCESS read-only 215 STATUS current 216 DESCRIPTION 217 "The number of entries in the routing table. This can be 218 used to monitor the routing table size to detect illegal 219 advertisements of unicast routes." 220 ::= { dvmrpScalar 3 } 222 dvmrpReachableRoutes OBJECT-TYPE 223 SYNTAX Gauge32 225 Draft DVMRP MIB October 1999 227 MAX-ACCESS read-only 228 STATUS current 229 DESCRIPTION 230 "The number of entries in the routing table with non 231 infinite metrics. This can be used to detect network 232 partitions by observing the ratio of reachable routes to 233 total routes." 234 ::= { dvmrpScalar 4 } 236 -- The DVMRP Interface Table 238 dvmrpInterfaceTable OBJECT-TYPE 239 SYNTAX SEQUENCE OF DvmrpInterfaceEntry 240 MAX-ACCESS not-accessible 241 STATUS current 242 DESCRIPTION 243 "The (conceptual) table listing the router's multicast- 244 capable interfaces." 245 ::= { dvmrp 2 } 247 dvmrpInterfaceEntry OBJECT-TYPE 248 SYNTAX DvmrpInterfaceEntry 249 MAX-ACCESS not-accessible 250 STATUS current 251 DESCRIPTION 252 "An entry (conceptual row) in the dvmrpInterfaceTable. This 253 row augments ipMRouteInterfaceEntry in the IP Multicast MIB, 254 where the threshold object resides." 255 INDEX { dvmrpInterfaceIfIndex } 256 ::= { dvmrpInterfaceTable 1 } 258 DvmrpInterfaceEntry ::= SEQUENCE { 259 dvmrpInterfaceIfIndex InterfaceIndex, 260 dvmrpInterfaceLocalAddress IpAddress, 261 dvmrpInterfaceMetric Integer32, 262 dvmrpInterfaceStatus RowStatus, 263 dvmrpInterfaceRcvBadPkts Counter32, 264 dvmrpInterfaceRcvBadRoutes Counter32, 265 dvmrpInterfaceSentRoutes Counter32, 266 dvmrpInterfaceInterfaceKey SnmpAdminString, 267 dvmrpInterfaceInterfaceKeyVersion Integer32 268 } 270 dvmrpInterfaceIfIndex OBJECT-TYPE 272 Draft DVMRP MIB October 1999 274 SYNTAX InterfaceIndex 275 MAX-ACCESS not-accessible 276 STATUS current 277 DESCRIPTION 278 "The ifIndex value of the interface for which DVMRP is 279 enabled." 280 ::= { dvmrpInterfaceEntry 1 } 282 dvmrpInterfaceLocalAddress OBJECT-TYPE 283 SYNTAX IpAddress 284 MAX-ACCESS read-create 285 STATUS current 286 DESCRIPTION 287 "The IP address this system will use as a source address on 288 this interface. On unnumbered interfaces, it must be the 289 same value as dvmrpInterfaceLocalAddress for some interface 290 on the system." 291 ::= { dvmrpInterfaceEntry 2 } 293 dvmrpInterfaceMetric OBJECT-TYPE 294 SYNTAX Integer32 (1..31) 295 MAX-ACCESS read-create 296 STATUS current 297 DESCRIPTION 298 "The distance metric for this interface which is used to 299 calculate distance vectors." 300 DEFVAL { 1 } 301 ::= { dvmrpInterfaceEntry 3 } 303 dvmrpInterfaceStatus OBJECT-TYPE 304 SYNTAX RowStatus 305 MAX-ACCESS read-create 306 STATUS current 307 DESCRIPTION 308 "The status of this entry. Creating the entry enables DVMRP 309 on the virtual interface; destroying the entry or setting it 310 to notInService disables DVMRP on the virtual interface." 311 ::= { dvmrpInterfaceEntry 4 } 313 dvmrpInterfaceRcvBadPkts OBJECT-TYPE 314 SYNTAX Counter32 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The number of DVMRP messages received on the interface by 320 Draft DVMRP MIB October 1999 322 the DVMRP process which were subsequently discarded as 323 invalid (e.g. invalid packet format, or a route report from 324 an unknown neighbor)." 325 ::= { dvmrpInterfaceEntry 5 } 327 dvmrpInterfaceRcvBadRoutes OBJECT-TYPE 328 SYNTAX Counter32 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The number of routes, in valid DVMRP packets, which were 333 ignored because the entry was invalid." 334 ::= { dvmrpInterfaceEntry 6 } 336 dvmrpInterfaceSentRoutes OBJECT-TYPE 337 SYNTAX Counter32 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "The number of routes, in DVMRP Report packets, which have 342 been sent on this interface. Together with 343 dvmrpNeighborRcvRoutes at a peer, this object is useful for 344 detecting routes being lost." 345 ::= { dvmrpInterfaceEntry 7 } 347 dvmrpInterfaceInterfaceKey OBJECT-TYPE 348 SYNTAX SnmpAdminString 349 MAX-ACCESS read-create 350 STATUS current 351 DESCRIPTION 352 "The (shared) key for authenticating neighbors on this 353 interface. This object is intended solely for the purpose 354 of setting the interface key, and MUST be accessible only 355 via requests using both authentication and privacy. The 356 agent MAY report an empty string in response to get, get- 357 next, get-bulk requests." 358 ::= { dvmrpInterfaceEntry 8 } 360 dvmrpInterfaceInterfaceKeyVersion OBJECT-TYPE 361 SYNTAX Integer32 362 MAX-ACCESS read-create 363 STATUS current 364 DESCRIPTION 365 "The highest version number of all known interface keys for 366 this interface used for authenticating neighbors." 368 Draft DVMRP MIB October 1999 370 ::= { dvmrpInterfaceEntry 9 } 372 -- The DVMRP Neighbor Table 374 dvmrpNeighborTable OBJECT-TYPE 375 SYNTAX SEQUENCE OF DvmrpNeighborEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "The (conceptual) table listing the router's DVMRP 380 neighbors, as discovered by receiving DVMRP messages." 381 ::= { dvmrp 3 } 383 dvmrpNeighborEntry OBJECT-TYPE 384 SYNTAX DvmrpNeighborEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "An entry (conceptual row) in the dvmrpNeighborTable." 389 INDEX { dvmrpNeighborIfIndex, dvmrpNeighborAddress } 390 ::= { dvmrpNeighborTable 1 } 392 DvmrpNeighborEntry ::= SEQUENCE { 393 dvmrpNeighborIfIndex InterfaceIndex, 394 dvmrpNeighborAddress IpAddress, 395 dvmrpNeighborUpTime TimeTicks, 396 dvmrpNeighborExpiryTime TimeTicks, 397 dvmrpNeighborGenerationId Integer32, 398 dvmrpNeighborMajorVersion Integer32, 399 dvmrpNeighborMinorVersion Integer32, 400 dvmrpNeighborCapabilities BITS, 401 dvmrpNeighborRcvRoutes Counter32, 402 dvmrpNeighborRcvBadPkts Counter32, 403 dvmrpNeighborRcvBadRoutes Counter32, 404 dvmrpNeighborState INTEGER 405 } 407 dvmrpNeighborIfIndex OBJECT-TYPE 408 SYNTAX InterfaceIndex 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "The value of ifIndex for the virtual interface used to 413 reach this DVMRP neighbor." 414 ::= { dvmrpNeighborEntry 1 } 416 Draft DVMRP MIB October 1999 418 dvmrpNeighborAddress OBJECT-TYPE 419 SYNTAX IpAddress 420 MAX-ACCESS not-accessible 421 STATUS current 422 DESCRIPTION 423 "The IP address of the DVMRP neighbor for which this entry 424 contains information." 425 ::= { dvmrpNeighborEntry 2 } 427 dvmrpNeighborUpTime OBJECT-TYPE 428 SYNTAX TimeTicks 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The time since this DVMRP neighbor (last) became a neighbor 433 of the local router." 434 ::= { dvmrpNeighborEntry 3 } 436 dvmrpNeighborExpiryTime OBJECT-TYPE 437 SYNTAX TimeTicks 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The minimum time remaining before this DVMRP neighbor will 442 be aged out." 443 ::= { dvmrpNeighborEntry 4 } 445 dvmrpNeighborGenerationId OBJECT-TYPE 446 SYNTAX Integer32 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The neighboring router's generation identifier." 451 ::= { dvmrpNeighborEntry 5 } 453 dvmrpNeighborMajorVersion OBJECT-TYPE 454 SYNTAX Integer32 (0..255) 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The neighboring router's major DVMRP version number." 459 ::= { dvmrpNeighborEntry 6 } 461 dvmrpNeighborMinorVersion OBJECT-TYPE 462 SYNTAX Integer32 (0..255) 464 Draft DVMRP MIB October 1999 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The neighboring router's minor DVMRP version number." 470 ::= { dvmrpNeighborEntry 7 } 472 dvmrpNeighborCapabilities OBJECT-TYPE 473 SYNTAX BITS { 474 leaf(0), 475 prune(1), 476 generationID(2), 477 mtrace(3) 478 } 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "This object describes the neighboring router's 483 capabilities. The leaf bit indicates that the neighbor has 484 only one interface with neighbors. The prune bit indicates 485 that the neighbor supports pruning. The generationID bit 486 indicates that the neighbor sends its generationID in Probe 487 messages. The mtrace bit indicates that the neighbor can 488 handle mtrace requests." 489 ::= { dvmrpNeighborEntry 8 } 491 dvmrpNeighborRcvRoutes OBJECT-TYPE 492 SYNTAX Counter32 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The total number of routes received in valid DVMRP packets 497 received from this neighbor. This can be used to diagnose 498 problems such as unicast route injection, as well as giving 499 an indication of the level of DVMRP route exchange 500 activity." 501 ::= { dvmrpNeighborEntry 9 } 503 dvmrpNeighborRcvBadPkts OBJECT-TYPE 504 SYNTAX Counter32 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "The number of packet received from this neighbor which were 509 discarded as invalid." 510 ::= { dvmrpNeighborEntry 10 } 512 Draft DVMRP MIB October 1999 514 dvmrpNeighborRcvBadRoutes OBJECT-TYPE 515 SYNTAX Counter32 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "The number of routes, in valid DVMRP packets received from 520 this neighbor, which were ignored because the entry was 521 invalid." 522 ::= { dvmrpNeighborEntry 11 } 524 dvmrpNeighborState OBJECT-TYPE 525 SYNTAX INTEGER { oneway(1), active(2), ignoring(3), down(4) } 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "State of the neighbor adjacency." 530 ::= { dvmrpNeighborEntry 12 } 532 -- The DVMRP Route Table 534 dvmrpRouteTable OBJECT-TYPE 535 SYNTAX SEQUENCE OF DvmrpRouteEntry 536 MAX-ACCESS not-accessible 537 STATUS current 538 DESCRIPTION 539 "The table of routes learned through DVMRP route exchange." 540 ::= { dvmrp 4 } 542 dvmrpRouteEntry OBJECT-TYPE 543 SYNTAX DvmrpRouteEntry 544 MAX-ACCESS not-accessible 545 STATUS current 546 DESCRIPTION 547 "An entry (conceptual row) containing the multicast routing 548 information used by DVMRP in place of the unicast routing 549 information." 550 INDEX { dvmrpRouteSource, dvmrpRouteSourceMask } 551 ::= { dvmrpRouteTable 1 } 553 DvmrpRouteEntry ::= SEQUENCE { 554 dvmrpRouteSource IpAddress, 555 dvmrpRouteSourceMask IpAddress, 556 dvmrpRouteUpstreamNeighbor IpAddress, 557 dvmrpRouteIfIndex InterfaceIndexOrZero, 559 Draft DVMRP MIB October 1999 561 dvmrpRouteMetric Integer32, 562 dvmrpRouteExpiryTime TimeTicks, 563 dvmrpRouteUpTime TimeTicks 564 } 566 dvmrpRouteSource OBJECT-TYPE 567 SYNTAX IpAddress 568 MAX-ACCESS not-accessible 569 STATUS current 570 DESCRIPTION 571 "The network address which when combined with the 572 corresponding value of dvmrpRouteSourceMask identifies the 573 sources for which this entry contains multicast routing 574 information." 575 ::= { dvmrpRouteEntry 1 } 577 dvmrpRouteSourceMask OBJECT-TYPE 578 SYNTAX IpAddress 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "The network mask which when combined with the corresponding 583 value of dvmrpRouteSource identifies the sources for which 584 this entry contains multicast routing information." 585 ::= { dvmrpRouteEntry 2 } 587 dvmrpRouteUpstreamNeighbor OBJECT-TYPE 588 SYNTAX IpAddress 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "The address of the upstream neighbor (e.g., RPF neighbor) 593 from which IP datagrams from these sources are received." 594 ::= { dvmrpRouteEntry 3 } 596 dvmrpRouteIfIndex OBJECT-TYPE 597 SYNTAX InterfaceIndexOrZero 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "The value of ifIndex for the interface on which IP 602 datagrams sent by these sources are received. A value of 0 603 typically means the route is an aggregate for which no next- 604 hop interface exists." 605 ::= { dvmrpRouteEntry 4 } 607 Draft DVMRP MIB October 1999 609 dvmrpRouteMetric OBJECT-TYPE 610 SYNTAX Integer32 (1..32) 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The distance in hops to the source subnet." 615 ::= { dvmrpRouteEntry 5 } 617 dvmrpRouteExpiryTime OBJECT-TYPE 618 SYNTAX TimeTicks 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The minimum amount of time remaining before this entry will 623 be aged out." 624 ::= { dvmrpRouteEntry 6 } 626 dvmrpRouteUpTime OBJECT-TYPE 627 SYNTAX TimeTicks 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The time since the route represented by this entry was 632 learned by the router." 633 ::= { dvmrpRouteEntry 7 } 635 -- The DVMRP Routing Next Hop Table 637 dvmrpRouteNextHopTable OBJECT-TYPE 638 SYNTAX SEQUENCE OF DvmrpRouteNextHopEntry 639 MAX-ACCESS not-accessible 640 STATUS current 641 DESCRIPTION 642 "The (conceptual) table containing information on the next 643 hops on outgoing interfaces for routing IP multicast 644 datagrams." 645 ::= { dvmrp 5 } 647 dvmrpRouteNextHopEntry OBJECT-TYPE 648 SYNTAX DvmrpRouteNextHopEntry 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "An entry (conceptual row) in the list of next hops on 653 outgoing interfaces to which IP multicast datagrams from 655 Draft DVMRP MIB October 1999 657 particular sources are routed." 658 INDEX { dvmrpRouteNextHopSource, dvmrpRouteNextHopSourceMask, 659 dvmrpRouteNextHopIfIndex } 660 ::= { dvmrpRouteNextHopTable 1 } 662 DvmrpRouteNextHopEntry ::= SEQUENCE { 663 dvmrpRouteNextHopSource IpAddress, 664 dvmrpRouteNextHopSourceMask IpAddress, 665 dvmrpRouteNextHopIfIndex InterfaceIndex, 666 dvmrpRouteNextHopType INTEGER 667 } 669 dvmrpRouteNextHopSource OBJECT-TYPE 670 SYNTAX IpAddress 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "The network address which when combined with the 675 corresponding value of dvmrpRouteNextHopSourceMask 676 identifies the sources for which this entry specifies a next 677 hop on an outgoing interface." 678 ::= { dvmrpRouteNextHopEntry 1 } 680 dvmrpRouteNextHopSourceMask OBJECT-TYPE 681 SYNTAX IpAddress 682 MAX-ACCESS not-accessible 683 STATUS current 684 DESCRIPTION 685 "The network mask which when combined with the corresponding 686 value of dvmrpRouteNextHopSource identifies the sources for 687 which this entry specifies a next hop on an outgoing 688 interface." 689 ::= { dvmrpRouteNextHopEntry 2 } 691 dvmrpRouteNextHopIfIndex OBJECT-TYPE 692 SYNTAX InterfaceIndex 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION 696 "The ifIndex value of the interface for the outgoing 697 interface for this next hop." 698 ::= { dvmrpRouteNextHopEntry 3 } 700 dvmrpRouteNextHopType OBJECT-TYPE 701 SYNTAX INTEGER { leaf(1), branch(2) } 703 Draft DVMRP MIB October 1999 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "Type is leaf if no downstream dependent neighbors exist on 709 the outgoing virtual interface. Otherwise, type is branch." 710 ::= { dvmrpRouteNextHopEntry 4 } 712 -- The DVMRP Prune Table 714 dvmrpPruneTable OBJECT-TYPE 715 SYNTAX SEQUENCE OF DvmrpPruneEntry 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "The (conceptual) table listing the router's upstream prune 720 state." 721 ::= { dvmrp 6 } 723 dvmrpPruneEntry OBJECT-TYPE 724 SYNTAX DvmrpPruneEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "An entry (conceptual row) in the dvmrpPruneTable." 729 INDEX { dvmrpPruneGroup, dvmrpPruneSource, 730 dvmrpPruneSourceMask } 731 ::= { dvmrpPruneTable 1 } 733 DvmrpPruneEntry ::= SEQUENCE { 734 dvmrpPruneGroup IpAddress, 735 dvmrpPruneSource IpAddress, 736 dvmrpPruneSourceMask IpAddress, 737 dvmrpPruneExpiryTime TimeTicks 738 } 740 dvmrpPruneGroup OBJECT-TYPE 741 SYNTAX IpAddress 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "The group address which has been pruned." 746 ::= { dvmrpPruneEntry 1 } 748 dvmrpPruneSource OBJECT-TYPE 749 SYNTAX IpAddress 751 Draft DVMRP MIB October 1999 753 MAX-ACCESS not-accessible 754 STATUS current 755 DESCRIPTION 756 "The address of the source or source network which has been 757 pruned." 758 ::= { dvmrpPruneEntry 2 } 760 dvmrpPruneSourceMask OBJECT-TYPE 761 SYNTAX IpAddress 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "The address of the source or source network which has been 766 pruned. The mask must either be all 1's, or else 767 dvmrpPruneSource and dvmrpPruneSourceMask must match 768 dvmrpRouteSource and dvmrpRouteSourceMask for some entry in 769 the dvmrpRouteTable." 770 ::= { dvmrpPruneEntry 3 } 772 dvmrpPruneExpiryTime OBJECT-TYPE 773 SYNTAX TimeTicks 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The amount of time remaining before this prune should 778 expire at the upstream neighbor. This value should be the 779 minimum of the default prune lifetime and the remaining 780 prune lifetimes of the local router's downstream neighbors, 781 if any." 782 ::= { dvmrpPruneEntry 4 } 784 -- DVMRP Traps 786 dvmrpTraps OBJECT IDENTIFIER ::= { dvmrp 7 } 788 dvmrpNeighborLoss NOTIFICATION-TYPE 789 OBJECTS { 790 dvmrpInterfaceLocalAddress, -- The originator of the trap 791 dvmrpNeighborState -- The new state 792 } 793 STATUS current 794 DESCRIPTION 795 "A dvmrpNeighborLoss trap signifies the loss of a 2-way 796 adjacency with a neighbor. This trap should be generated 797 when the neighbor state changes from active to one-way, 799 Draft DVMRP MIB October 1999 801 ignoring, or down. The trap should be generated only if the 802 router has no other neighbors on the same interface with a 803 lower IP address than itself." 804 ::= { dvmrpTraps 1 } 806 dvmrpNeighborNotPruning NOTIFICATION-TYPE 807 OBJECTS { 808 dvmrpInterfaceLocalAddress, -- The originator of the trap 809 dvmrpNeighborCapabilities 810 } 811 STATUS current 812 DESCRIPTION 813 "A dvmrpNeighborNotPruning trap signifies that a non-pruning 814 neighbor has been detected (in an implementation-dependent 815 manner). This trap should be generated at most once per 816 generation ID of the neighbor. For example, it should be 817 generated at the time a neighbor is first heard from if the 818 prune bit is not set in its capabilities. It should also be 819 generated if the local system has the ability to tell that a 820 neighbor which sets the the prune bit in its capabilities is 821 not pruning any branches over an extended period of time. 822 The trap should be generated only if the router has no other 823 neighbors on the same interface with a lower IP address than 824 itself." 825 ::= { dvmrpTraps 2 } 827 -- conformance information 829 dvmrpMIBConformance OBJECT IDENTIFIER ::= { dvmrpStdMIB 2 } 831 dvmrpMIBCompliances OBJECT IDENTIFIER ::= { dvmrpMIBConformance 1 } 833 dvmrpMIBGroups OBJECT IDENTIFIER ::= { dvmrpMIBConformance 2 } 835 -- compliance statements 837 dvmrpMIBCompliance MODULE-COMPLIANCE 838 STATUS current 839 DESCRIPTION 840 "The compliance statement for the DVMRP MIB." 841 MODULE -- this module 842 MANDATORY-GROUPS { dvmrpGeneralGroup, dvmrpInterfaceGroup, 843 dvmrpNeighborGroup, dvmrpRoutingGroup, dvmrpTreeGroup 845 Draft DVMRP MIB October 1999 847 } 849 GROUP dvmrpSecurityGroup 850 DESCRIPTION 851 "This group is mandatory for agents which support both 852 authentication and privacy of SNMP messages, and only for 853 those network interfaces for which DVMRP is authenticating 854 neighbors." 855 ::= { dvmrpMIBCompliances 1 } 857 -- units of conformance 859 dvmrpGeneralGroup OBJECT-GROUP 860 OBJECTS { dvmrpVersionString, dvmrpGenerationId, 861 dvmrpNumRoutes, dvmrpReachableRoutes 862 } 863 STATUS current 864 DESCRIPTION 865 "A collection of objects used to describe general DVMRP 866 configuration information." 867 ::= { dvmrpMIBGroups 2 } 869 dvmrpInterfaceGroup OBJECT-GROUP 870 OBJECTS { dvmrpInterfaceLocalAddress, dvmrpInterfaceMetric, 871 dvmrpInterfaceStatus, 872 dvmrpInterfaceRcvBadPkts, dvmrpInterfaceRcvBadRoutes, 873 dvmrpInterfaceSentRoutes 874 } 875 STATUS current 876 DESCRIPTION 877 "A collection of objects used to describe DVMRP interface 878 configuration and statistics." 879 ::= { dvmrpMIBGroups 3 } 881 dvmrpNeighborGroup OBJECT-GROUP 882 OBJECTS { dvmrpNeighborUpTime, dvmrpNeighborExpiryTime, 883 dvmrpNeighborGenerationId, 884 dvmrpNeighborMajorVersion, dvmrpNeighborMinorVersion, 885 dvmrpNeighborCapabilities, dvmrpNeighborRcvRoutes, 886 dvmrpNeighborRcvBadPkts, dvmrpNeighborRcvBadRoutes, 887 dvmrpNeighborState 888 } 889 STATUS current 890 DESCRIPTION 892 Draft DVMRP MIB October 1999 894 "A collection of objects used to describe DVMRP peer 895 configuration and statistics." 896 ::= { dvmrpMIBGroups 4 } 898 dvmrpRoutingGroup OBJECT-GROUP 899 OBJECTS { dvmrpRouteUpstreamNeighbor, dvmrpRouteIfIndex, 900 dvmrpRouteMetric, dvmrpRouteExpiryTime, 901 dvmrpRouteUpTime, dvmrpRouteNextHopType 902 } 903 STATUS current 904 DESCRIPTION 905 "A collection of objects used to store the DVMRP routing 906 table." 907 ::= { dvmrpMIBGroups 5 } 909 dvmrpSecurityGroup OBJECT-GROUP 910 OBJECTS { dvmrpInterfaceInterfaceKey, 911 dvmrpInterfaceInterfaceKeyVersion } 912 STATUS current 913 DESCRIPTION 914 "A collection of objects used to store information related 915 to DVMRP security." 916 ::= { dvmrpMIBGroups 6 } 918 dvmrpTreeGroup OBJECT-GROUP 919 OBJECTS { dvmrpPruneExpiryTime } 920 STATUS current 921 DESCRIPTION 922 "A collection of objects used to store information related 923 to DVMRP prune state." 924 ::= { dvmrpMIBGroups 7 } 926 dvmrpNotificationGroup NOTIFICATION-GROUP 927 NOTIFICATIONS { dvmrpNeighborLoss, 928 dvmrpNeighborNotPruning } 929 STATUS current 930 DESCRIPTION 931 "A collection of notifications for signaling important DVMRP 932 events." 933 ::= { dvmrpMIBGroups 8 } 935 END 937 Draft DVMRP MIB October 1999 939 6. Security Considerations 941 This MIB contains readable objects whose values provide information 942 related to multicast routing, including information on the network 943 topology. There are also a number of objects that have a MAX-ACCESS 944 clause of read-write and/or read-create, which allow an administrator to 945 configure DVMRP in the router. 947 If the agent allows configuring keys via SNMP, for use by DVMRP, then 948 the security of DVMRP is at best only as secure as SNMP. For this 949 reason, the security-related objects (i.e. those in the 950 dvmrpSecurityGroup) MUST NOT be accessible via unencrypted messages. It 951 is also recommended that keys not be made visible through SNMP GET (or 952 GET-NEXT or GET-BULK) messages, even if encryption is used. 954 While unauthorized access to other readable objects is relatively 955 innocuous, unauthorized access to the write-able objects could cause a 956 denial of service. Hence, the support for SET operations in a non- 957 secure environment without proper protection can have a negative effect 958 on network operations. 960 SNMPv1 by itself is such an insecure environment. Even if the network 961 itself is secure (for example by using IPSec), even then, there is no 962 control as to who on the secure network is allowed to access and SET 963 (change/create/delete) the objects in this MIB. 965 It is recommended that the implementers consider the security features 966 as provided by the SNMPv3 framework. Specifically, the use of the User- 967 based Security Model RFC 2274 [12] and the View-based Access Control 968 Model RFC 2275 [15] is recommended. 970 It is then a customer/user responsibility to ensure that the SNMP entity 971 giving access to this MIB, is properly configured to give access to 972 those objects only to those principals (users) that have legitimate 973 rights to access them. 975 7. Intellectual Property Notice 977 The IETF takes no position regarding the validity or scope of any 978 intellectual property or other rights that might be claimed to pertain 979 to the implementation or use of the technology described in this 980 document or the extent to which any license under such rights might or 981 might not be available; neither does it represent that it has made any 982 effort to identify any such rights. Information on the IETF's 984 Draft DVMRP MIB October 1999 986 procedures with respect to rights in standards-track and standards- 987 related documentation can be found in BCP-11. Copies of claims of 988 rights made available for publication and any assurances of licenses to 989 be made available, or the result of an attempt made to obtain a general 990 license or permission for the use of such proprietary rights by 991 implementers or users of this specification can be obtained from the 992 IETF Secretariat. 994 The IETF invites any interested party to bring to its attention any 995 copyrights, patents or patent applications, or other proprietary rights 996 which may cover technology that may be required to practice this 997 standard. Please address the information to the IETF Executive 998 Director. 1000 8. Acknowledgements 1002 David LeRoy, Tom Pusateri, and Bill Fenner provided valuable feedback on 1003 this document. Jeff Schiller also provided valuable feedback on the 1004 security-related objects in this document. The members of the IDMR WG 1005 and the MBone community provided the motivation for this work. 1007 9. Author's Address 1009 Dave Thaler 1010 Microsoft 1011 One Microsoft Way 1012 Redmond, WA 98052-6399 1013 Phone: (425) 703-8835 1014 EMail: dthaler@microsoft.com 1016 10. References 1018 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1019 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1020 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1021 1999. 1023 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1024 Management Information for TCP/IP-based Internets", RFC 1155, STD 1025 16, Performance Systems International, Hughes LAN Systems, May 1027 Draft DVMRP MIB October 1999 1029 1990. 1031 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1032 STD 16, Performance Systems International, Hughes LAN Systems, 1033 March 1991. 1035 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1036 RFC 1215, Performance Systems International, March 1991. 1038 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1039 and S. Waldbusser, "Structure of Management Information Version 2 1040 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1041 Braunschweig, SNMP Research, First Virtual Holdings, International 1042 Network Services, April 1999. 1044 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1045 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1046 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1047 Virtual Holdings, International Network Services, April 1999. 1049 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1050 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1051 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1052 First Virtual Holdings, International Network Services, April 1999. 1054 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1055 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1056 Systems International, Performance Systems International, MIT 1057 Laboratory for Computer Science, May 1990. 1059 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1060 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1061 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1062 International Network Services, January 1996. 1064 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1065 Mappings for Version 2 of the Simple Network Management Protocol 1066 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1067 Dover Beach Consulting, Inc., International Network Services, 1068 January 1996. 1070 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1071 Processing and Dispatching for the Simple Network Management 1072 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1073 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1075 Draft DVMRP MIB October 1999 1077 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1078 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1079 2574, IBM T. J. Watson Research, April 1999. 1081 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1082 Operations for Version 2 of the Simple Network Management Protocol 1083 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1084 Dover Beach Consulting, Inc., International Network Services, 1085 January 1996. 1087 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1088 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1089 Systems, April 1999. 1091 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1092 Control Model (VACM) for the Simple Network Management Protocol 1093 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1094 Cisco Systems, Inc., April 1999. 1096 [16] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector 1097 Multicast Routing Protocol", RFC 1075, November 1988. 1099 [17] Pusateri, T., "Distance Vector Multicast Routing Protocol", Work in 1100 progress, February 1999. 1102 [18] McCloghrie, K., Farinacci, D., and D. Thaler, "IP Multicast Routing 1103 MIB", Work in progress, May 1999. 1105 [19] Thaler, D., "IP Tunnel MIB", RFC 2667, August 1999. 1107 11. Full Copyright Statement 1109 Copyright (C) The Internet Society (1999). All Rights Reserved. 1111 This document and translations of it may be copied and furnished to 1112 others, and derivative works that comment on or otherwise explain it or 1113 assist in its implmentation may be prepared, copied, published and 1114 distributed, in whole or in part, without restriction of any kind, 1115 provided that the above copyright notice and this paragraph are included 1116 on all such copies and derivative works. However, this document itself 1117 may not be modified in any way, such as by removing the copyright notice 1118 or references to the Internet Society or other Internet organizations, 1119 except as needed for the purpose of developing Internet standards in 1120 which case the procedures for copyrights defined in the Internet 1122 Draft DVMRP MIB October 1999 1124 Standards process must be followed, or as required to translate it into 1125 languages other than English. 1127 The limited permissions granted above are perpetual and will not be 1128 revoked by the Internet Society or its successors or assigns. 1130 This document and the information contained herein is provided on an "AS 1131 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1132 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1133 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1134 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1135 FITNESS FOR A PARTICULAR PURPOSE. 1137 Draft DVMRP MIB October 1999 1139 Table of Contents 1141 1 Abstract ........................................................ 1 1142 2 Introduction .................................................... 2 1143 3 The SNMP Network Management Framework ........................... 2 1144 4 Overview ........................................................ 3 1145 4.1 Structure of MIB .............................................. 3 1146 4.1.1 General Description ......................................... 3 1147 4.2 Relationship to the IP Tunnel MIB ............................. 4 1148 5 Definitions ..................................................... 4 1149 6 Security Considerations ......................................... 21 1150 7 Intellectual Property Notice .................................... 21 1151 8 Acknowledgements ................................................ 22 1152 9 Author's Address ................................................ 22 1153 10 References ..................................................... 22 1154 11 Full Copyright Statement ....................................... 24