idnits 2.17.1 draft-ietf-mboned-ip-mcast-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 2456. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2433. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2440. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2446. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 -- The abstract seems to indicate that this document obsoletes RFC2932, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (March 1, 2007) is 6264 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) == Missing Reference: 'RFCyyyy' is mentioned on line 180, but not defined == Unused Reference: 'RFC2434' is defined on line 2308, but no explicit reference was found in the text == Unused Reference: 'RFC3306' is defined on line 2331, but no explicit reference was found in the text == Unused Reference: 'RFC4007' is defined on line 2343, but no explicit reference was found in the text == Unused Reference: 'RFC4291' is defined on line 2347, but no explicit reference was found in the text == Unused Reference: 'I-D.mcwalter-langtag-mib' is defined on line 2353, but no explicit reference was found in the text == Unused Reference: 'RFC1075' is defined on line 2360, but no explicit reference was found in the text == Unused Reference: 'RFC1584' is defined on line 2364, but no explicit reference was found in the text == Unused Reference: 'RFC2189' is defined on line 2367, but no explicit reference was found in the text == Unused Reference: 'RFC2287' is defined on line 2371, but no explicit reference was found in the text == Unused Reference: 'RFC2934' is defined on line 2378, but no explicit reference was found in the text == Unused Reference: 'RFC4601' is defined on line 2389, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-bidir' is defined on line 2393, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) == Outdated reference: A later version (-03) exists of draft-mcwalter-langtag-mib-02 -- Obsolete informational reference (is this intentional?): RFC 2932 (Obsoleted by RFC 5132) -- Obsolete informational reference (is this intentional?): RFC 4601 (Obsoleted by RFC 7761) Summary: 3 errors (**), 0 flaws (~~), 18 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MBONED WG D. McWalter 3 Internet-Draft Data Connection Ltd 4 Proposed Status: Standards Track D. Thaler 5 Expires: September 2, 2007 Microsoft Corporation 6 A. Kessler 7 Cisco Systems 8 March 1, 2007 10 IP Multicast MIB 11 draft-ietf-mboned-ip-mcast-mib-05.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on September 2, 2007. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2007). 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in the Internet community. 46 In particular, it describes objects used for managing multicast 47 function, independent of the specific multicast protocol(s) in use. 48 This document obsoletes RFC 2932. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. The Internet-Standard Management Framework . . . . . . . . . . 3 55 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6. Security Considerations . . . . . . . . . . . . . . . . . . . 47 58 6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 47 59 6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 47 60 6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 48 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 64 9.1 Normative References . . . . . . . . . . . . . . . . . . . 49 65 9.2 Informative References . . . . . . . . . . . . . . . . . . 50 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 51 67 Intellectual Property and Copyright Statements . . . . . . . . 53 69 1. Introduction 71 This MIB describes objects used for managing IP multicast function, 72 including IP multicast routing. These objects are independent of the 73 specific multicast routing protocol in use. Managed objects specific 74 to particular multicast protocols are defined elsewhere. 76 2. History 78 This document obsoletes [RFC2932]. The MIB module defined by this 79 document is a re-working of the MIB module from [RFC2932], with 80 changes that include the following. 82 o This MIB module includes support for IPv6 addressing and the IPv6 83 scoped address architecture. [RFC2932] supported only IPv4. 85 o This MIB module allows several multicast protocols to perform 86 routing on a single interface, where [RFC2932] assumed each 87 interface supported at most one multicast routing protocol. 88 Multicast routing protocols are now per-route, see 89 ipMcastRouteProtocol. 91 o This MIB module includes objects that are not specific to 92 multicast routing. It allows management of multicast function on 93 systems that do not perform routing, whereas [RFC2932] was 94 restricted to multicast routing. 96 o This MIB module includes a table of Source-Specific Multicast 97 (SSM) address ranges to which SSM semantics [RFC3569] should be 98 applied. 100 o This MIB module includes a table of local applications that are 101 receiving multicast data. 103 o This MIB module includes a table of multicast scope zones. 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in [RFC2119]. 109 3. The Internet-Standard Management Framework 111 For a detailed overview of the documents that describe the current 112 Internet-Standard Management Framework, please refer to section 7 of 113 [RFC3410]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. MIB objects are generally 117 accessed through the Simple Network Management Protocol (SNMP). 118 Objects in the MIB are defined using the mechanisms defined in the 119 Structure of Management Information (SMI). This memo specifies a MIB 120 module that is compliant to the SMIv2, which is described in STD 58, 121 ([RFC2578], [RFC2579] and [RFC2580]). 123 4. Overview 125 This MIB module contains two scalars and eight tables. The tables 126 are: 128 1. The IP Multicast Interface Table, which contains multicast 129 information specific to interfaces. 131 2. The IP Multicast SSM Range Table, which contains one row per 132 range of multicast group addresses to which Source-Specific 133 Multicast semantics [RFC3569] should be applied. 135 3. The IP Multicast Route Table, which contains multicast routing 136 information for IP datagrams sent by particular sources to the IP 137 multicast groups known to a system. 139 4. The IP Multicast Routing Next Hop Table, which contains 140 information about next-hops for the routing of IP multicast 141 datagrams. Each entry is one of a list of next-hops on outgoing 142 interfaces for particular sources sending to a particular 143 multicast group address. 145 5. The IP Multicast Scope Boundary Table, which contains the 146 boundaries configured for multicast scopes [RFC2365]. 148 6. The IP Multicast Scope Name Table, which contains human-readable 149 names for multicast scopes. 151 7. The IP Multicast Local Listener Table, which contains identifiers 152 for local applications that are receiving multicast data. 154 8. The IP Multicast Zone Table, which contains an entry for each 155 scope zone known to a system, and maps each zone to the multicast 156 address range that is the corresponding scope. 158 This MIB module uses textual conventions defined in the IF-MIB 159 [RFC4293], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 161 5. Definitions 163 IPMCAST-MIB DEFINITIONS ::= BEGIN 164 IMPORTS 165 MODULE-IDENTITY, OBJECT-TYPE, 166 mib-2, Unsigned32, Counter64, 167 Gauge32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] 168 RowStatus, TruthValue, 169 StorageType, TimeStamp FROM SNMPv2-TC -- [RFC2579] 170 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 171 CounterBasedGauge64 FROM HCNUM-TC -- [RFC2856] 172 InterfaceIndexOrZero, 173 InterfaceIndex FROM IF-MIB -- [RFC2863] 174 IANAipRouteProtocol, 175 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 176 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 177 InetAddress, InetAddressType, 178 InetAddressPrefixLength, 179 InetZoneIndex, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001] 180 LangTag FROM LANGTAG-TC-MIB; -- [RFCyyyy] 181 -- RFC Ed.: replace yyyy with LangTag RFC number & remove this note 183 ipMcastMIB MODULE-IDENTITY 184 LAST-UPDATED "200703010000Z" -- 1 March 2007 185 ORGANIZATION "IETF MBONE Deployment (MBONED) Working Group" 186 CONTACT-INFO "David McWalter 187 Data Connection Limited 188 100 Church Street 189 Enfield, EN2 6BQ 190 UK 192 Phone: +44 208 366 1177 193 EMail: dmcw@dataconnection.com 195 Dave Thaler 196 Microsoft Corporation 197 One Microsoft Way 198 Redmond, WA 98052-6399 199 US 201 Phone: +1 425 703 8835 202 EMail: dthaler@dthaler.microsoft.com 204 Andrew Kessler 205 Cisco Systems 206 425 E. Tasman Drive 207 San Jose, CA 95134 208 US 210 Phone: +1 408 526 5139 211 EMail: kessler@cisco.com" 213 DESCRIPTION 214 "The MIB module for management of IP Multicast, including 215 multicast routing, data forwarding, and data reception. 217 Copyright (C) The IETF Trust (2007). This version of this 218 MIB module is part of RFC yyyy; see the RFC itself for full 219 legal notices." 220 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 221 REVISION "200703010000Z" -- 1 March 2007 222 DESCRIPTION "Initial version, published as RFC yyyy." 223 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 224 ::= { mib-2 XXX } 225 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 227 -- 228 -- Top-level structure of the MIB 229 -- 231 ipMcastMIBObjects OBJECT IDENTIFIER ::= { ipMcastMIB 1 } 233 ipMcast OBJECT IDENTIFIER ::= { ipMcastMIBObjects 1 } 235 ipMcastEnable OBJECT-TYPE 236 SYNTAX INTEGER { enabled(1), disabled(2) } 237 MAX-ACCESS read-write 238 STATUS current 239 DESCRIPTION 240 "The enabled status of IP Multicast function on this 241 system." 242 ::= { ipMcast 1 } 244 ipMcastRouteEntryCount OBJECT-TYPE 245 SYNTAX Gauge32 246 MAX-ACCESS read-only 247 STATUS current 248 DESCRIPTION 249 "The number of rows in the ipMcastRouteTable. This can be 250 used to check for multicast routing activity, and to monitor 251 the multicast routing table size." 252 ::= { ipMcast 2 } 254 -- 255 -- The Multicast Interface Table 256 -- 258 ipMcastInterfaceTable OBJECT-TYPE 259 SYNTAX SEQUENCE OF IpMcastInterfaceEntry 260 MAX-ACCESS not-accessible 261 STATUS current 262 DESCRIPTION 263 "The (conceptual) table used to manage the multicast 264 protocol active on an interface." 265 ::= { ipMcast 3 } 267 ipMcastInterfaceEntry OBJECT-TYPE 268 SYNTAX IpMcastInterfaceEntry 269 MAX-ACCESS not-accessible 270 STATUS current 271 DESCRIPTION 272 "An entry (conceptual row) containing the multicast protocol 273 information for a particular interface." 274 INDEX { ipMcastInterfaceIPVersion, 275 ipMcastInterfaceIfIndex } 276 ::= { ipMcastInterfaceTable 1 } 278 IpMcastInterfaceEntry ::= SEQUENCE { 279 ipMcastInterfaceIPVersion InetVersion, 280 ipMcastInterfaceIfIndex InterfaceIndex, 281 ipMcastInterfaceTtl Unsigned32, 282 ipMcastInterfaceRateLimit Unsigned32, 283 ipMcastInterfaceInMcastOctets Counter64, 284 ipMcastInterfaceOutMcastOctets Counter64, 285 ipMcastInterfaceInMcastPkts Counter64, 286 ipMcastInterfaceOutMcastPkts Counter64, 287 ipMcastInterfaceDiscontinuityTime TimeStamp 288 } 290 ipMcastInterfaceIPVersion OBJECT-TYPE 291 SYNTAX InetVersion 292 MAX-ACCESS not-accessible 293 STATUS current 294 DESCRIPTION 295 "The IP version of this row." 296 ::= { ipMcastInterfaceEntry 1 } 298 ipMcastInterfaceIfIndex OBJECT-TYPE 299 SYNTAX InterfaceIndex 300 MAX-ACCESS not-accessible 301 STATUS current 302 DESCRIPTION 303 "The index value that uniquely identifies the interface to 304 which this entry is applicable. The interface identified by 305 a particular value of this index is the same interface as 306 identified by the same value of the IF-MIB's ifIndex." 307 ::= { ipMcastInterfaceEntry 2 } 309 ipMcastInterfaceTtl OBJECT-TYPE 310 SYNTAX Unsigned32 (0..255) 311 MAX-ACCESS read-write 312 STATUS current 313 DESCRIPTION 314 "The datagram TTL threshold for the interface. Any IP 315 multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) 316 less than this threshold will not be forwarded out the 317 interface. The default value of 0 means all multicast 318 packets are forwarded out the interface." 319 DEFVAL { 0 } 320 ::= { ipMcastInterfaceEntry 3 } 322 ipMcastInterfaceRateLimit OBJECT-TYPE 323 SYNTAX Unsigned32 324 MAX-ACCESS read-write 325 STATUS current 326 DESCRIPTION 327 "The rate-limit, in kilobits per second, of forwarded 328 multicast traffic on the interface. A rate-limit of 0 329 indicates that no rate limiting is done." 330 DEFVAL { 0 } 331 ::= { ipMcastInterfaceEntry 4 } 333 ipMcastInterfaceInMcastOctets OBJECT-TYPE 334 SYNTAX Counter64 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The number of octets of multicast packets that have arrived 339 on the interface, including framing characters. This object 340 is similar to ifInOctets in the Interfaces MIB, except that 341 only multicast packets are counted. 343 Discontinuities in the value of this counter can occur at 344 re-initialization of the management system, and at other 345 times as indicated by the value of 346 ipMcastInterfaceDiscontinuityTime." 347 REFERENCE "RFC 4293 ifInOctets" 348 ::= { ipMcastInterfaceEntry 5 } 350 ipMcastInterfaceOutMcastOctets OBJECT-TYPE 351 SYNTAX Counter64 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of octets of multicast packets that have been 356 sent on the interface, including framing characters. This 357 object is similar to ifOutOctets in the Interfaces MIB, 358 except that only multicast packets are counted. 360 Discontinuities in the value of this counter can occur at 361 re-initialization of the management system, and at other 362 times as indicated by the value of 363 ipMcastInterfaceDiscontinuityTime." 364 REFERENCE "RFC 4293 ifOutOctets" 365 ::= { ipMcastInterfaceEntry 6 } 367 ipMcastInterfaceInMcastPkts OBJECT-TYPE 368 SYNTAX Counter64 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The number of multicast packets that have arrived on the 373 interface. In many cases, this object is identical to 374 ifInMulticastPkts in the Interfaces MIB. 376 However, some implementations use ifXTable for Layer 2 377 traffic statistics and ipMcastInterfaceTable at Layer 3. In 378 this case a difference between these objects probably 379 indicates that some Layer 3 multicast packets are being 380 transmitted as unicast at Layer 2. 382 Discontinuities in the value of this counter can occur at 383 re-initialization of the management system, and at other 384 times as indicated by the value of 385 ipMcastInterfaceDiscontinuityTime." 386 REFERENCE "RFC 4293 ifInMulticastPkts" 387 ::= { ipMcastInterfaceEntry 7 } 389 ipMcastInterfaceOutMcastPkts OBJECT-TYPE 390 SYNTAX Counter64 391 MAX-ACCESS read-only 392 STATUS current 393 DESCRIPTION 394 "The number of multicast packets that have been sent on the 395 interface. In many cases, this object is identical to 396 ifOutMulticastPkts in the Interfaces MIB. 398 However, some implementations use ifXTable for Layer 2 399 traffic statistics and ipMcastInterfaceTable at Layer 3. In 400 this case a difference between these objects probably 401 indicates that some Layer 3 multicast packets are being 402 transmitted as unicast at Layer 2. 404 Discontinuities in the value of this counter can occur at 405 re-initialization of the management system, and at other 406 times as indicated by the value of 407 ipMcastInterfaceDiscontinuityTime." 408 REFERENCE "RFC 4293 ifOutMulticastPkts" 409 ::= { ipMcastInterfaceEntry 8 } 411 ipMcastInterfaceDiscontinuityTime OBJECT-TYPE 412 SYNTAX TimeStamp 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The value of sysUpTime on the most recent occasion at which 417 any one or more of this entry's counters suffered a 418 discontinuity. 420 If no such discontinuities have occurred since the last re- 421 initialization of the local management subsystem, then this 422 object contains a zero value." 423 ::= { ipMcastInterfaceEntry 9 } 425 -- 426 -- The SSM Range Table 427 -- 429 ipMcastSsmRangeTable OBJECT-TYPE 430 SYNTAX SEQUENCE OF IpMcastSsmRangeEntry 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "This table is used to create and manage the range(s) of 435 group addresses to which SSM semantics should be applied." 436 REFERENCE "RFC 3569" 437 ::= { ipMcast 4 } 439 ipMcastSsmRangeEntry OBJECT-TYPE 440 SYNTAX IpMcastSsmRangeEntry 441 MAX-ACCESS not-accessible 442 STATUS current 443 DESCRIPTION 444 "An entry (conceptual row) containing a range of group 445 addresses to which SSM semantics should be applied." 446 REFERENCE "RFC 3569" 447 INDEX { ipMcastSsmRangeAddressType, 448 ipMcastSsmRangeAddress, 449 ipMcastSsmRangePrefixLength } 450 ::= { ipMcastSsmRangeTable 1 } 452 IpMcastSsmRangeEntry ::= SEQUENCE { 453 ipMcastSsmRangeAddressType InetAddressType, 454 ipMcastSsmRangeAddress InetAddress, 455 ipMcastSsmRangePrefixLength InetAddressPrefixLength, 456 ipMcastSsmRangeRowStatus RowStatus, 457 ipMcastSsmRangeStorageType StorageType 458 } 460 ipMcastSsmRangeAddressType OBJECT-TYPE 461 SYNTAX InetAddressType 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "The address type of the multicast group prefix." 466 ::= { ipMcastSsmRangeEntry 1 } 468 ipMcastSsmRangeAddress OBJECT-TYPE 469 SYNTAX InetAddress (SIZE (4|8|16|20)) 470 MAX-ACCESS not-accessible 471 STATUS current 472 DESCRIPTION 473 "The multicast group address which, when combined with 474 ipMcastSsmRangePrefixLength, gives the group prefix for this 475 SSM range. The InetAddressType is given by 476 ipMcastSsmRangeAddressType. 478 This address object is only significant up to 479 ipMcastSsmRangePrefixLength bits. The remainder of the 480 address bits are zero. This is especially important for 481 this index field, which is part of the index of this entry. 482 Any non-zero bits would signify an entirely different 483 entry. 485 For IPv6 SSM address ranges, only ranges prefixed by 486 FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291 487 multicast address scope. The syntax of the address range is 488 given by RFC 3306 sections 4 and 7. 490 For addresses of type ipv4z or ipv6z, the appended zone 491 index is significant even though it lies beyond the prefix 492 length. The use of these address types indicate that this 493 SSM range entry applies only within the given zone. Zone 494 index zero is not valid in this table. 496 If non-global scope SSM range entries are present, then 497 consistent ipMcastBoundaryTable entries are required on 498 routers at the zone boundary." 499 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 500 and 7" 502 ::= { ipMcastSsmRangeEntry 2 } 504 ipMcastSsmRangePrefixLength OBJECT-TYPE 505 SYNTAX InetAddressPrefixLength (4..128) 506 MAX-ACCESS not-accessible 507 STATUS current 508 DESCRIPTION 509 "The length in bits of the mask which, when combined with 510 ipMcastSsmRangeAddress, gives the group prefix for this SSM 511 range. The InetAddressType is given by 512 ipMcastSsmRangeAddressType. For values 'ipv4' and 'ipv4z', 513 this object must be in the range 4..32. For values 'ipv6' 514 and 'ipv6z', this object must be in the range 8..128." 515 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 516 and 7" 517 ::= { ipMcastSsmRangeEntry 3 } 519 ipMcastSsmRangeRowStatus OBJECT-TYPE 520 SYNTAX RowStatus 521 MAX-ACCESS read-create 522 STATUS current 523 DESCRIPTION 524 "The status of this row, by which rows in this table can 525 be created and destroyed. 527 This status object can be set to active(1) without setting 528 any other columnar objects in this entry. 530 All writeable objects in this entry can be modified when the 531 status of this entry is active(1)." 532 ::= { ipMcastSsmRangeEntry 4 } 534 ipMcastSsmRangeStorageType OBJECT-TYPE 535 SYNTAX StorageType 536 MAX-ACCESS read-create 537 STATUS current 538 DESCRIPTION 539 "The storage type for this row. Rows having the value 540 'permanent' need not allow write-access to any columnar 541 objects in the row." 542 DEFVAL { nonVolatile } 543 ::= { ipMcastSsmRangeEntry 5 } 545 -- 546 -- The IP Multicast Routing Table 547 -- 549 ipMcastRouteTable OBJECT-TYPE 550 SYNTAX SEQUENCE OF IpMcastRouteEntry 551 MAX-ACCESS not-accessible 552 STATUS current 553 DESCRIPTION 554 "The (conceptual) table containing multicast routing 555 information for IP datagrams sent by particular sources to 556 to the IP multicast groups known to this router." 557 ::= { ipMcast 5 } 559 ipMcastRouteEntry OBJECT-TYPE 560 SYNTAX IpMcastRouteEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "An entry (conceptual row) containing the multicast routing 565 information for IP datagrams from a particular source and 566 addressed to a particular IP multicast group address." 567 INDEX { ipMcastRouteGroupAddressType, 568 ipMcastRouteGroup, 569 ipMcastRouteGroupPrefixLength, 570 ipMcastRouteSourceAddressType, 571 ipMcastRouteSource, 572 ipMcastRouteSourcePrefixLength } 573 ::= { ipMcastRouteTable 1 } 575 IpMcastRouteEntry ::= SEQUENCE { 576 ipMcastRouteGroupAddressType InetAddressType, 577 ipMcastRouteGroup InetAddress, 578 ipMcastRouteGroupPrefixLength InetAddressPrefixLength, 579 ipMcastRouteSourceAddressType InetAddressType, 580 ipMcastRouteSource InetAddress, 581 ipMcastRouteSourcePrefixLength InetAddressPrefixLength, 582 ipMcastRouteUpstreamNeighborType InetAddressType, 583 ipMcastRouteUpstreamNeighbor InetAddress, 584 ipMcastRouteInIfIndex InterfaceIndexOrZero, 585 ipMcastRouteTimeStamp TimeStamp, 586 ipMcastRouteExpiryTime TimeTicks, 587 ipMcastRouteProtocol IANAipMRouteProtocol, 588 ipMcastRouteRtProtocol IANAipRouteProtocol, 589 ipMcastRouteRtAddressType InetAddressType, 590 ipMcastRouteRtAddress InetAddress, 591 ipMcastRouteRtPrefixLength InetAddressPrefixLength, 592 ipMcastRouteRtType INTEGER, 593 ipMcastRouteOctets Counter64, 594 ipMcastRoutePkts Counter64, 595 ipMcastRouteTtlDropOctets Counter64, 596 ipMcastRouteTtlDropPackets Counter64, 597 ipMcastRouteDifferentInIfOctets Counter64, 598 ipMcastRouteDifferentInIfPackets Counter64, 599 ipMcastRouteBps CounterBasedGauge64 600 } 602 ipMcastRouteGroupAddressType OBJECT-TYPE 603 SYNTAX InetAddressType 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "A value indicating the address family of the address 608 contained in ipMcastRouteGroup. Legal values correspond to 609 the subset of address families for which multicast 610 forwarding is supported." 611 ::= { ipMcastRouteEntry 1 } 613 ipMcastRouteGroup OBJECT-TYPE 614 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "The IP multicast group address which, when combined with 619 the corresponding value specified in 620 ipMcastRouteGroupPrefixLength, identifies the groups for 621 which this entry contains multicast routing information. 623 This address object is only significant up to 624 ipMcastRouteGroupPrefixLength bits. The remainder of the 625 address bits are zero. This is especially important for 626 this index field, which is part of the index of this entry. 627 Any non-zero bits would signify an entirely different 628 entry. 630 For addresses of type ipv4z or ipv6z, the appended zone 631 index is significant even though it lies beyond the prefix 632 length. The use of these address types indicate that this 633 forwarding state applies only within the given zone. Zone 634 index zero is not valid in this table." 635 ::= { ipMcastRouteEntry 2 } 637 ipMcastRouteGroupPrefixLength OBJECT-TYPE 638 SYNTAX InetAddressPrefixLength (4..128) 639 MAX-ACCESS not-accessible 640 STATUS current 641 DESCRIPTION 642 "The length in bits of the mask which, when combined with 643 the corresponding value of ipMcastRouteGroup, identifies the 644 groups for which this entry contains multicast routing 645 information." 647 ::= { ipMcastRouteEntry 3 } 649 ipMcastRouteSourceAddressType OBJECT-TYPE 650 SYNTAX InetAddressType 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "A value indicating the address family of the address 655 contained in ipMcastRouteSource. The value MUST be the same 656 as the value of ipMcastRouteGroupType." 657 ::= { ipMcastRouteEntry 4 } 659 ipMcastRouteSource OBJECT-TYPE 660 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "The network address which, when combined with the 665 corresponding value of ipMcastRouteSourcePrefixLength, 666 identifies the sources for which this entry contains 667 multicast routing information. 669 This address object is only significant up to 670 ipMcastRouteGroupPrefixLength bits. The remainder of the 671 address bits are zero. This is especially important for 672 this index field, which is part of the index of this entry. 673 Any non-zero bits would signify an entirely different 674 entry. 676 For addresses of type ipv4z or ipv6z, the appended zone 677 index is significant even though it lies beyond the prefix 678 length. The use of these address types indicate that this 679 source address applies only within the given zone. Zone 680 index zero is not valid in this table." 681 ::= { ipMcastRouteEntry 5 } 683 ipMcastRouteSourcePrefixLength OBJECT-TYPE 684 SYNTAX InetAddressPrefixLength (4..128) 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "The length in bits of the mask which, when combined with 689 the corresponding value of ipMcastRouteSource, identifies 690 the sources for which this entry contains multicast routing 691 information." 692 ::= { ipMcastRouteEntry 6 } 694 ipMcastRouteUpstreamNeighborType OBJECT-TYPE 695 SYNTAX InetAddressType 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "A value indicating the address family of the address 700 contained in ipMcastRouteUpstreamNeighbor. 702 An address type of unknown(0) indicates that the upstream 703 neighbor is unknown, for example in BIDIR-PIM." 704 REFERENCE "I-D.ietf-pim-bidir" 705 ::= { ipMcastRouteEntry 7 } 707 ipMcastRouteUpstreamNeighbor OBJECT-TYPE 708 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "The address of the upstream neighbor (for example, RPF 713 neighbor) from which IP datagrams from these sources to 714 this multicast address are received." 715 ::= { ipMcastRouteEntry 8 } 717 ipMcastRouteInIfIndex OBJECT-TYPE 718 SYNTAX InterfaceIndexOrZero 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The value of ifIndex for the interface on which IP 723 datagrams sent by these sources to this multicast address 724 are received. A value of 0 indicates that datagrams are not 725 subject to an incoming interface check, but may be accepted 726 on multiple interfaces (for example, in BIDIR-PIM)." 727 REFERENCE "I-D.ietf-pim-bidir" 728 ::= { ipMcastRouteEntry 9 } 730 ipMcastRouteTimeStamp OBJECT-TYPE 731 SYNTAX TimeStamp 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The value of sysUpTime at which the multicast routing 736 information represented by this entry was learned by the 737 router. 739 If this infomration was present at the most recent re- 740 initialization of the local management subsystem, then this 741 object contains a zero value." 742 ::= { ipMcastRouteEntry 10 } 744 ipMcastRouteExpiryTime OBJECT-TYPE 745 SYNTAX TimeTicks 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The minimum amount of time remaining before this entry will 750 be aged out. The value 0 indicates that the entry is not 751 subject to aging. If ipMcastRouteNextHopState is pruned(1), 752 this object represents the remaining time until the prune 753 expires. If this timer expires, state reverts to 754 forwarding(2). Otherwise, this object represents the time 755 until this entry is removed from the table." 756 ::= { ipMcastRouteEntry 11 } 758 ipMcastRouteProtocol OBJECT-TYPE 759 SYNTAX IANAipMRouteProtocol 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The multicast routing protocol via which this multicast 764 forwarding entry was learned." 765 ::= { ipMcastRouteEntry 12 } 767 ipMcastRouteRtProtocol OBJECT-TYPE 768 SYNTAX IANAipRouteProtocol 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The routing mechanism via which the route used to find the 773 upstream or parent interface for this multicast forwarding 774 entry was learned." 775 ::= { ipMcastRouteEntry 13 } 777 ipMcastRouteRtAddressType OBJECT-TYPE 778 SYNTAX InetAddressType 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "A value indicating the address family of the address 783 contained in ipMcastRouteRtAddress." 784 ::= { ipMcastRouteEntry 14 } 786 ipMcastRouteRtAddress OBJECT-TYPE 787 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The address portion of the route used to find the upstream 792 or parent interface for this multicast forwarding entry. 794 This address object is only significant up to 795 ipMcastRouteGroupPrefixLength bits. The remainder of the 796 address bits are zero. 798 For addresses of type ipv4z or ipv6z, the appended zone 799 index is significant even though it lies beyond the prefix 800 length. The use of these address types indicate that this 801 forwarding state applies only within the given zone. Zone 802 index zero is not valid in this table." 803 ::= { ipMcastRouteEntry 15 } 805 ipMcastRouteRtPrefixLength OBJECT-TYPE 806 SYNTAX InetAddressPrefixLength (4..128) 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The length in bits of the mask associated with the route 811 used to find the upstream or parent interface for this 812 multicast forwarding entry." 813 ::= { ipMcastRouteEntry 16 } 815 ipMcastRouteRtType OBJECT-TYPE 816 SYNTAX INTEGER { 817 unicast (1), -- Unicast route used in multicast RIB 818 multicast (2) -- Multicast route 819 } 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The reason the given route was placed in the (logical) 824 multicast Routing Information Base (RIB). A value of 825 unicast means that the route would normally be placed only 826 in the unicast RIB, but was placed in the multicast RIB 827 (instead or in addition) due to local configuration, such as 828 when running PIM over RIP. A value of multicast means that 829 the route was explicitly added to the multicast RIB by the 830 routing protocol, such as DVMRP or Multiprotocol BGP." 831 ::= { ipMcastRouteEntry 17 } 833 ipMcastRouteOctets OBJECT-TYPE 834 SYNTAX Counter64 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "The number of octets contained in IP datagrams which were 839 received from these sources and addressed to this multicast 840 group address, and which were forwarded by this router. 842 Discontinuities in this monotonically increasing value 843 occur at re-initialization of the management system. 844 Discontinuities can also occur as a result of routes being 845 removed and replaced, which can be detected by observing 846 the value of ipMcastRouteTimeStamp." 847 ::= { ipMcastRouteEntry 18 } 849 ipMcastRoutePkts OBJECT-TYPE 850 SYNTAX Counter64 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The number of packets routed using this multicast route 855 entry. 857 Discontinuities in this monotonically increasing value 858 occur at re-initialization of the management system. 859 Discontinuities can also occur as a result of routes being 860 removed and replaced, which can be detected by observing 861 the value of ipMcastRouteTimeStamp." 862 ::= { ipMcastRouteEntry 19 } 864 ipMcastRouteTtlDropOctets OBJECT-TYPE 865 SYNTAX Counter64 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The number of octets contained in IP datagrams which this 870 router has received from these sources and addressed to this 871 multicast group address, which were dropped because the TTL 872 (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a 873 value less than ipMcastInterfaceTtl for all next hops. 875 Discontinuities in this monotonically increasing value 876 occur at re-initialization of the management system. 877 Discontinuities can also occur as a result of routes being 878 removed and replaced, which can be detected by observing 879 the value of ipMcastRouteTimeStamp." 880 ::= { ipMcastRouteEntry 20 } 882 ipMcastRouteTtlDropPackets OBJECT-TYPE 883 SYNTAX Counter64 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The number of packets which this router has received from 888 these sources and addressed to this multicast group address, 889 which were dropped because the TTL (IPv4) or Hop Limit 890 (IPv6) was decremented to zero, or to a value less than 891 ipMcastInterfaceTtl for all next hops. 893 Discontinuities in this monotonically increasing value 894 occur at re-initialization of the management system. 895 Discontinuities can also occur as a result of routes being 896 removed and replaced, which can be detected by observing 897 the value of ipMcastRouteTimeStamp." 898 ::= { ipMcastRouteEntry 21 } 900 ipMcastRouteDifferentInIfOctets OBJECT-TYPE 901 SYNTAX Counter64 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The number of octets contained in IP datagrams which this 906 router has received from these sources and addressed to this 907 multicast group address, which were dropped because they 908 were received on an unexpected interface. 910 For RPF checking protocols (such as PIM-SM), these packets 911 arrived on interfaces other than ipMcastRouteInIfIndex, and 912 were dropped because of this failed RPF check. (RPF paths 913 are 'Reverse Path Forwarding' path; the unicast routes to 914 the expected origin of multicast data flows). 916 Other protocols may drop packets on an incoming interface 917 check for different reasons (for example, BIDIR-PIM performs 918 a DF check on receipt of packets). All packets dropped as a 919 result of an incoming interface check are counted here. 921 If this counter increases rapidly, this indicates a problem. 922 A significant quantity of multicast data is arriving at this 923 router on unexpected interfaces, and is not being forwarded. 925 For guidance, if the rate of increase of this counter 926 exceeds 1% of the rate of increase of ipMcastRouteOctets, 927 then there are multicast routing problems that require 928 investigation. 930 Discontinuities in this monotonically increasing value 931 occur at re-initialization of the management system. 932 Discontinuities can also occur as a result of routes being 933 removed and replaced, which can be detected by observing 934 the value of ipMcastRouteTimeStamp." 935 REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" 936 ::= { ipMcastRouteEntry 22 } 938 ipMcastRouteDifferentInIfPackets OBJECT-TYPE 939 SYNTAX Counter64 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The number of packets which this router has received from 944 these sources and addressed to this multicast group address, 945 which were dropped because they were received on an 946 unexpected interface. 948 For RPF checking protocols (such as PIM-SM), these packets 949 arrived on interfaces other than ipMcastRouteInIfIndex, and 950 were dropped because of this failed RPF check. (RPF paths 951 are 'Reverse Path Forwarding' path; the unicast routes to 952 the expected origin of multicast data flows). 954 Other protocols may drop packets on an incoming interface 955 check for different reasons (for example, BIDIR-PIM performs 956 a DF check on receipt of packets). All packets dropped as a 957 result of an incoming interface check are counted here. 959 If this counter increases rapidly, this indicates a problem. 960 A significant quantity of multicast data is arriving at this 961 router on unexpected interfaces, and is not being forwarded. 963 For guidance, if the rate of increase of this counter 964 exceeds 1% of the rate of increase of ipMcastRoutePkts, then 965 there are multicast routing problems that require 966 investigation. 968 Discontinuities in this monotonically increasing value 969 occur at re-initialization of the management system. 970 Discontinuities can also occur as a result of routes being 971 removed and replaced, which can be detected by observing 972 the value of ipMcastRouteTimeStamp." 973 REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" 974 ::= { ipMcastRouteEntry 23 } 976 ipMcastRouteBps OBJECT-TYPE 977 SYNTAX CounterBasedGauge64 978 UNITS "bits per second" 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "Bits per second forwarded by this router using this 983 multicast routing entry. 985 This value is a sample; it is the number of bits forwarded 986 during the last whole 1 second sampling period. The value 987 during the current 1 second sampling period is not made 988 available until the period is completed. 990 The quantity being sampled is the same as that measured by 991 ipMcastRouteOctets. The units and the sampling method are 992 different." 993 ::= { ipMcastRouteEntry 24 } 994 -- 995 -- The IP Multicast Routing Next Hop Table 996 -- 998 ipMcastRouteNextHopTable OBJECT-TYPE 999 SYNTAX SEQUENCE OF IpMcastRouteNextHopEntry 1000 MAX-ACCESS not-accessible 1001 STATUS current 1002 DESCRIPTION 1003 "The (conceptual) table containing information on the 1004 next-hops on outgoing interfaces for routing IP multicast 1005 datagrams. Each entry is one of a list of next-hops on 1006 outgoing interfaces for particular sources sending to a 1007 particular multicast group address." 1008 ::= { ipMcast 6 } 1010 ipMcastRouteNextHopEntry OBJECT-TYPE 1011 SYNTAX IpMcastRouteNextHopEntry 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "An entry (conceptual row) in the list of next-hops on 1016 outgoing interfaces to which IP multicast datagrams from 1017 particular sources to an IP multicast group address are 1018 routed." 1019 INDEX { ipMcastRouteNextHopGroupAddressType, 1020 ipMcastRouteNextHopGroup, 1021 ipMcastRouteNextHopGroupPrefixLength, 1022 ipMcastRouteNextHopSourceAddressType, 1023 ipMcastRouteNextHopSource, 1024 ipMcastRouteNextHopSourcePrefixLength, 1025 ipMcastRouteNextHopIfIndex, 1026 ipMcastRouteNextHopAddressType, 1027 ipMcastRouteNextHopAddress } 1028 ::= { ipMcastRouteNextHopTable 1 } 1030 IpMcastRouteNextHopEntry ::= SEQUENCE { 1031 ipMcastRouteNextHopGroupAddressType InetAddressType, 1032 ipMcastRouteNextHopGroup InetAddress, 1033 ipMcastRouteNextHopGroupPrefixLength InetAddressPrefixLength, 1034 ipMcastRouteNextHopSourceAddressType InetAddressType, 1035 ipMcastRouteNextHopSource InetAddress, 1036 ipMcastRouteNextHopSourcePrefixLength InetAddressPrefixLength, 1037 ipMcastRouteNextHopIfIndex InterfaceIndex, 1038 ipMcastRouteNextHopAddressType InetAddressType, 1039 ipMcastRouteNextHopAddress InetAddress, 1040 ipMcastRouteNextHopState INTEGER, 1041 ipMcastRouteNextHopTimeStamp TimeStamp, 1042 ipMcastRouteNextHopExpiryTime TimeTicks, 1043 ipMcastRouteNextHopClosestMemberHops Unsigned32, 1044 ipMcastRouteNextHopProtocol IANAipMRouteProtocol, 1045 ipMcastRouteNextHopOctets Counter64, 1046 ipMcastRouteNextHopPkts Counter64 1047 } 1049 ipMcastRouteNextHopGroupAddressType OBJECT-TYPE 1050 SYNTAX InetAddressType 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "A value indicating the address family of the address 1055 contained in ipMcastRouteNextHopGroup. Legal values 1056 correspond to the subset of address families for which 1057 multicast forwarding is supported." 1058 ::= { ipMcastRouteNextHopEntry 1 } 1060 ipMcastRouteNextHopGroup OBJECT-TYPE 1061 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "The IP multicast group address which, when combined with 1066 the corresponding value specified in 1067 ipMcastRouteNextHopGroupPrefixLength, identifies the groups 1068 for which this entry contains multicast forwarding 1069 information. 1071 This address object is only significant up to 1072 ipMcastRouteNextHopGroupPrefixLength bits. The remainder of 1073 the address bits are zero. This is especially important for 1074 this index field, which is part of the index of this entry. 1075 Any non-zero bits would signify an entirely different 1076 entry. 1078 For addresses of type ipv4z or ipv6z, the appended zone 1079 index is significant even though it lies beyond the prefix 1080 length. The use of these address types indicate that this 1081 forwarding state applies only within the given zone. Zone 1082 index zero is not valid in this table." 1083 ::= { ipMcastRouteNextHopEntry 2 } 1085 ipMcastRouteNextHopGroupPrefixLength OBJECT-TYPE 1086 SYNTAX InetAddressPrefixLength (4..128) 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "The length in bits of the mask which, when combined with 1091 the corresponding value of ipMcastRouteGroup, identifies the 1092 groups for which this entry contains multicast routing 1093 information." 1094 ::= { ipMcastRouteNextHopEntry 3 } 1096 ipMcastRouteNextHopSourceAddressType OBJECT-TYPE 1097 SYNTAX InetAddressType 1098 MAX-ACCESS not-accessible 1099 STATUS current 1100 DESCRIPTION 1101 "A value indicating the address family of the address 1102 contained in ipMcastRouteNextHopSource. The value MUST be 1103 the same as the value of ipMcastRouteNextHopGroupType." 1104 ::= { ipMcastRouteNextHopEntry 4 } 1106 ipMcastRouteNextHopSource OBJECT-TYPE 1107 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1108 MAX-ACCESS not-accessible 1109 STATUS current 1110 DESCRIPTION 1111 "The network address which, when combined with the 1112 corresponding value of the mask specified in 1113 ipMcastRouteNextHopSourcePrefixLength, identifies the 1114 sources for which this entry specifies a next-hop on an 1115 outgoing interface. 1117 This address object is only significant up to 1118 ipMcastRouteNextHopSourcePrefixLength bits. The remainder 1119 of the address bits are zero. This is especially important 1120 for this index field, which is part of the index of this 1121 entry. Any non-zero bits would signify an entirely 1122 different entry. 1124 For addresses of type ipv4z or ipv6z, the appended zone 1125 index is significant even though it lies beyond the prefix 1126 length. The use of these address types indicate that this 1127 source address applies only within the given zone. Zone 1128 index zero is not valid in this table." 1130 ::= { ipMcastRouteNextHopEntry 5 } 1132 ipMcastRouteNextHopSourcePrefixLength OBJECT-TYPE 1133 SYNTAX InetAddressPrefixLength (4..128) 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "The length in bits of the mask which, when combined with 1138 the corresponding value specified in 1139 ipMcastRouteNextHopSource, identifies the sources for which 1140 this entry specifies a next-hop on an outgoing interface." 1141 ::= { ipMcastRouteNextHopEntry 6 } 1143 ipMcastRouteNextHopIfIndex OBJECT-TYPE 1144 SYNTAX InterfaceIndex 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "The ifIndex value of the interface for the outgoing 1149 interface for this next-hop." 1150 ::= { ipMcastRouteNextHopEntry 7 } 1152 ipMcastRouteNextHopAddressType OBJECT-TYPE 1153 SYNTAX InetAddressType 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "A value indicating the address family of the address 1158 contained in ipMcastRouteNextHopAddress." 1159 ::= { ipMcastRouteNextHopEntry 8 } 1161 ipMcastRouteNextHopAddress OBJECT-TYPE 1162 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "The address of the next-hop specific to this entry. For 1167 most interfaces, this is identical to 1168 ipMcastRouteNextHopGroup. NBMA interfaces, however, may 1169 have multiple next-hop addresses out a single outgoing 1170 interface." 1171 ::= { ipMcastRouteNextHopEntry 9 } 1173 ipMcastRouteNextHopState OBJECT-TYPE 1174 SYNTAX INTEGER { pruned(1), forwarding(2) } 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "An indication of whether the outgoing interface and next- 1179 hop represented by this entry is currently being used to 1180 forward IP datagrams. The value 'forwarding' indicates it 1181 is currently being used; the value 'pruned' indicates it is 1182 not." 1183 ::= { ipMcastRouteNextHopEntry 10 } 1185 ipMcastRouteNextHopTimeStamp OBJECT-TYPE 1186 SYNTAX TimeStamp 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "The value of sysUpTime at which the multicast routing 1191 information represented by this entry was learned by the 1192 router. 1194 If this infomration was present at the most recent re- 1195 initialization of the local management subsystem, then this 1196 object contains a zero value." 1197 ::= { ipMcastRouteNextHopEntry 11 } 1199 ipMcastRouteNextHopExpiryTime OBJECT-TYPE 1200 SYNTAX TimeTicks 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "The minimum amount of time remaining before this entry will 1205 be aged out. If ipMcastRouteNextHopState is pruned(1), the 1206 remaining time until the prune expires and the state reverts 1207 to forwarding(2). Otherwise, the remaining time until this 1208 entry is removed from the table. The time remaining may be 1209 copied from ipMcastRouteExpiryTime if the protocol in use 1210 for this entry does not specify next-hop timers. The value 1211 0 indicates that the entry is not subject to aging." 1212 ::= { ipMcastRouteNextHopEntry 12 } 1214 ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE 1215 SYNTAX Unsigned32 (0..255) 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "The minimum number of hops between this router and any 1220 member of this IP multicast group reached via this next-hop 1221 on this outgoing interface. Any IP multicast datagrams for 1222 the group which have a TTL (IPv4) or Hop Count (IPv6) less 1223 than this number of hops will not be forwarded to this 1224 next-hop. 1226 This is an optimization applied by multicast routing 1227 protocols that explicitly track hop counts to downstream 1228 listeners. Multicast protocols that are not aware of hop 1229 counts to downstream listeners set this object to zero." 1230 ::= { ipMcastRouteNextHopEntry 13 } 1232 ipMcastRouteNextHopProtocol OBJECT-TYPE 1233 SYNTAX IANAipMRouteProtocol 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The routing mechanism via which this next-hop was learned." 1238 ::= { ipMcastRouteNextHopEntry 14 } 1240 ipMcastRouteNextHopOctets OBJECT-TYPE 1241 SYNTAX Counter64 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "The number of octets of multicast packets that have been 1246 forwarded using this route. 1248 Discontinuities in this monotonically increasing value 1249 occur at re-initialization of the management system. 1250 Discontinuities can also occur as a result of routes being 1251 removed and replaced, which can be detected by observing 1252 the value of ipMcastRouteNextHopTimeStamp." 1253 ::= { ipMcastRouteNextHopEntry 15 } 1255 ipMcastRouteNextHopPkts OBJECT-TYPE 1256 SYNTAX Counter64 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "The number of packets which have been forwarded using this 1261 route. 1263 Discontinuities in this monotonically increasing value 1264 occur at re-initialization of the management system. 1265 Discontinuities can also occur as a result of routes being 1266 removed and replaced, which can be detected by observing 1267 the value of ipMcastRouteNextHopTimeStamp." 1268 ::= { ipMcastRouteNextHopEntry 16 } 1270 -- 1271 -- The IP Multicast Scope Boundary Table 1272 -- 1273 ipMcastBoundaryTable OBJECT-TYPE 1274 SYNTAX SEQUENCE OF IpMcastBoundaryEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "The (conceptual) table listing the system's multicast scope 1279 zone boundaries." 1280 REFERENCE "RFC 4007 section 5" 1281 ::= { ipMcast 7 } 1283 ipMcastBoundaryEntry OBJECT-TYPE 1284 SYNTAX IpMcastBoundaryEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "An entry (conceptual row) describing one of this device's 1289 multicast scope zone boundaries." 1290 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1291 INDEX { ipMcastBoundaryIfIndex, 1292 ipMcastBoundaryAddressType, 1293 ipMcastBoundaryAddress, 1294 ipMcastBoundaryAddressPrefixLength } 1295 ::= { ipMcastBoundaryTable 1 } 1297 IpMcastBoundaryEntry ::= SEQUENCE { 1298 ipMcastBoundaryIfIndex InterfaceIndex, 1299 ipMcastBoundaryAddressType InetAddressType, 1300 ipMcastBoundaryAddress InetAddress, 1301 ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, 1302 ipMcastBoundaryTimeStamp TimeStamp, 1303 ipMcastBoundaryDroppedMcastOctets Counter64, 1304 ipMcastBoundaryDroppedMcastPkts Counter64, 1305 ipMcastBoundaryStatus RowStatus, 1306 ipMcastBoundaryStorageType StorageType 1307 } 1309 ipMcastBoundaryIfIndex OBJECT-TYPE 1310 SYNTAX InterfaceIndex 1311 MAX-ACCESS not-accessible 1312 STATUS current 1313 DESCRIPTION 1314 "The IfIndex value for the interface to which this boundary 1315 applies. Packets with a destination address in the 1316 associated address/mask range will not be forwarded over 1317 this interface. 1319 For IPv4, zone boundaries cut through links. Therefore this 1320 is an external interface. This may be either a physical or 1321 virtual interface (tunnel, encapsulation, and so forth.) 1323 For IPv6, zone boundaries cut through nodes. Therefore this 1324 is a virtual interface within the node. This is not an 1325 external interface, either real or virtual. Packets 1326 crossing this interface neither arrive at nor leave the 1327 node, but only move between zones within the node." 1328 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1329 ::= { ipMcastBoundaryEntry 1 } 1331 ipMcastBoundaryAddressType OBJECT-TYPE 1332 SYNTAX InetAddressType 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "A value indicating the address family of the address 1337 contained in ipMcastBoundaryAddress. Legal values 1338 correspond to the subset of address families for which 1339 multicast forwarding is supported." 1340 ::= { ipMcastBoundaryEntry 2 } 1342 ipMcastBoundaryAddress OBJECT-TYPE 1343 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "The group address which, when combined with the 1348 corresponding value of ipMcastBoundaryAddressPrefixLength, 1349 identifies the group range for which the scoped boundary 1350 exists. Scoped IPv4 multicast address ranges must be 1351 prefixed by 239.0.0.0/8. Scoped IPv6 multicast address 1352 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1353 scope. 1355 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1356 assigned address. An IPv6 address prefixed by FF3x::/16 is 1357 a unicast-prefix-based multicast addresses. A zone boundary 1358 for FF0x::/16 implies an identical boundary for these other 1359 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1360 in this table. 1362 This address object is only significant up to 1363 ipMcastBoundaryAddressPrefixLength bits. The remainder of 1364 the address bits are zero. This is especially important for 1365 this index field, which is part of the index of this entry. 1366 Any non-zero bits would signify an entirely different 1367 entry. 1369 For addresses of type ipv4z or ipv6z, the appended zone 1370 index is significant even though it lies beyond the prefix 1371 length. Zone index zero is not valid in this table." 1372 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1373 ::= { ipMcastBoundaryEntry 3 } 1375 ipMcastBoundaryAddressPrefixLength OBJECT-TYPE 1376 SYNTAX InetAddressPrefixLength (4..32) 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "The length in bits of the mask which when, combined with 1381 the corresponding value of ipMcastBoundaryAddress, 1382 identifies the group range for which the scoped boundary 1383 exists. 1385 The InetAddressType is given by ipMcastBoundaryAddressType. 1386 For 'ipv4' this object must be in the range 4..32. For 1387 'ipv6', this object must be 16." 1388 ::= { ipMcastBoundaryEntry 4 } 1390 ipMcastBoundaryTimeStamp OBJECT-TYPE 1391 SYNTAX TimeStamp 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The value of sysUpTime at which the multicast boundary 1396 information represented by this entry was learned by the 1397 router. 1399 If this infomration was present at the most recent re- 1400 initialization of the local management subsystem, then this 1401 object contains a zero value." 1402 ::= { ipMcastBoundaryEntry 5 } 1404 ipMcastBoundaryDroppedMcastOctets OBJECT-TYPE 1405 SYNTAX Counter64 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "The number of octets of multicast packets that have been 1410 dropped as a result of this zone boundary configuration. 1412 Discontinuities in this monotonically increasing value 1413 occur at re-initialization of the management system. 1414 Discontinuities can also occur as a result of boundary 1415 configuration being removed and replaced, which can be 1416 detected by observing the value of 1417 ipMcastBoundaryTimeStamp." 1418 ::= { ipMcastBoundaryEntry 6 } 1420 ipMcastBoundaryDroppedMcastPkts OBJECT-TYPE 1421 SYNTAX Counter64 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "The number of multicast packets that have been dropped as a 1426 result of this zone boundary configuration. 1428 Discontinuities in this monotonically increasing value 1429 occur at re-initialization of the management system. 1430 Discontinuities can also occur as a result of boundary 1431 configuration being removed and replaced, which can be 1432 detected by observing the value of 1433 ipMcastBoundaryTimeStamp." 1434 ::= { ipMcastBoundaryEntry 7 } 1436 ipMcastBoundaryStatus OBJECT-TYPE 1437 SYNTAX RowStatus 1438 MAX-ACCESS read-create 1439 STATUS current 1440 DESCRIPTION 1441 "The status of this row, by which rows in this table can 1442 be created and destroyed. 1444 This status object can be set to active(1) without setting 1445 any other columnar objects in this entry. 1447 All writeable objects in this entry can be modified when the 1448 status of this entry is active(1)." 1449 ::= { ipMcastBoundaryEntry 8 } 1451 ipMcastBoundaryStorageType OBJECT-TYPE 1452 SYNTAX StorageType 1453 MAX-ACCESS read-create 1454 STATUS current 1455 DESCRIPTION 1456 "The storage type for this row. Rows having the value 1457 'permanent' need not allow write-access to any columnar 1458 objects in the row." 1459 DEFVAL { nonVolatile } 1460 ::= { ipMcastBoundaryEntry 9 } 1462 -- 1463 -- The IP Multicast Scope Name Table 1464 -- 1465 ipMcastScopeNameTable OBJECT-TYPE 1466 SYNTAX SEQUENCE OF IpMcastScopeNameEntry 1467 MAX-ACCESS not-accessible 1468 STATUS current 1469 DESCRIPTION 1470 "The (conceptual) table listing multicast scope names." 1471 REFERENCE "RFC 4007 section 4" 1472 ::= { ipMcast 8 } 1474 ipMcastScopeNameEntry OBJECT-TYPE 1475 SYNTAX IpMcastScopeNameEntry 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "An entry (conceptual row) that names a multicast address 1480 scope." 1481 REFERENCE "RFC 4007 section 4" 1482 INDEX { ipMcastScopeNameAddressType, 1483 ipMcastScopeNameAddress, 1484 ipMcastScopeNameAddressPrefixLength, 1485 IMPLIED ipMcastScopeNameLanguage } 1486 ::= { ipMcastScopeNameTable 1 } 1488 IpMcastScopeNameEntry ::= SEQUENCE { 1489 ipMcastScopeNameAddressType InetAddressType, 1490 ipMcastScopeNameAddress InetAddress, 1491 ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, 1492 ipMcastScopeNameLanguage LangTag, 1493 ipMcastScopeNameString SnmpAdminString, 1494 ipMcastScopeNameDefault TruthValue, 1495 ipMcastScopeNameStatus RowStatus, 1496 ipMcastScopeNameStorageType StorageType 1497 } 1499 ipMcastScopeNameAddressType OBJECT-TYPE 1500 SYNTAX InetAddressType 1501 MAX-ACCESS not-accessible 1502 STATUS current 1503 DESCRIPTION 1504 "A value indicating the address family of the address 1505 contained in ipMcastScopeNameAddress. Legal values 1506 correspond to the subset of address families for which 1507 multicast forwarding is supported." 1508 ::= { ipMcastScopeNameEntry 1 } 1510 ipMcastScopeNameAddress OBJECT-TYPE 1511 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "The group address which, when combined with the 1516 corresponding value of ipMcastScopeNameAddressPrefixLength, 1517 identifies the group range associated with the multicast 1518 scope. Scoped IPv4 multicast address ranges must be 1519 prefixed by 239.0.0.0/8. Scoped IPv6 multicast address 1520 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1521 scope. 1523 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1524 assigned address. An IPv6 address prefixed by FF3x::/16 is 1525 a unicast-prefix-based multicast addresses. A scope 1526 FF0x::/16 implies an identical scope name for these other 1527 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1528 in this table. 1530 This address object is only significant up to 1531 ipMcastScopeNameAddressPrefixLength bits. The remainder of 1532 the address bits are zero. This is especially important for 1533 this index field, which is part of the index of this entry. 1534 Any non-zero bits would signify an entirely different 1535 entry. 1537 For addresses of type ipv4z or ipv6z, the appended zone 1538 index is significant even though it lies beyond the prefix 1539 length. Zone index zero is not valid in this table." 1540 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1541 ::= { ipMcastScopeNameEntry 2 } 1543 ipMcastScopeNameAddressPrefixLength OBJECT-TYPE 1544 SYNTAX InetAddressPrefixLength (4..32) 1545 MAX-ACCESS not-accessible 1546 STATUS current 1547 DESCRIPTION 1548 "The length in bits of the mask which, when combined with 1549 the corresponding value of ipMcastScopeNameAddress, 1550 identifies the group range associated with the multicast 1551 scope. 1553 The InetAddressType is given by ipMcastScopeNameAddressType. 1554 For 'ipv4' this object must be in the range 4..32. For 1555 'ipv6', this object must be 16." 1556 ::= { ipMcastScopeNameEntry 3 } 1558 ipMcastScopeNameLanguage OBJECT-TYPE 1559 SYNTAX LangTag 1560 MAX-ACCESS not-accessible 1561 STATUS current 1562 DESCRIPTION 1563 "Language tag associated with the scope name." 1564 REFERENCE "RFC 3283" 1565 ::= { ipMcastScopeNameEntry 4 } 1567 ipMcastScopeNameString OBJECT-TYPE 1568 SYNTAX SnmpAdminString 1569 MAX-ACCESS read-create 1570 STATUS current 1571 DESCRIPTION 1572 "The textual name associated with the multicast scope. The 1573 value of this object should be suitable for displaying to 1574 end-users, such as when allocating a multicast address in 1575 this scope. 1577 When no name is specified, the default value of this object 1578 for IPv4 should is the string 239.x.x.x/y with x and y 1579 replaced with decimal values to describe the address and 1580 mask length associated with the scope. 1582 When no name is specified, the default value of this object 1583 for IPv6 should is the string FF0x::/16, with x replaced by 1584 the hexadecimal value for the RFC 4291 multicast scope. 1586 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1587 assigned address. An IPv6 address prefixed by FF3x::/16 is 1588 a unicast-prefix-based multicast addresses. A scope 1589 FF0x::/16 implies an identical scope name for these other 1590 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1591 in this table." 1592 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1593 ::= { ipMcastScopeNameEntry 5 } 1595 ipMcastScopeNameDefault OBJECT-TYPE 1596 SYNTAX TruthValue 1597 MAX-ACCESS read-create 1598 STATUS current 1599 DESCRIPTION 1600 "If true, indicates a preference that the name in the 1601 following language should be used by applications if no name 1602 is available in a desired language." 1603 DEFVAL { false } 1604 ::= { ipMcastScopeNameEntry 6 } 1606 ipMcastScopeNameStatus OBJECT-TYPE 1607 SYNTAX RowStatus 1608 MAX-ACCESS read-create 1609 STATUS current 1610 DESCRIPTION 1611 "The status of this row, by which rows in this table can 1612 be created and destroyed. Before the row can be activated, 1613 the object ipMcastScopeNameString must be set to a valid 1614 value. All writeable objects in this entry can be modified 1615 when the status is active(1)." 1616 ::= { ipMcastScopeNameEntry 7 } 1618 ipMcastScopeNameStorageType OBJECT-TYPE 1619 SYNTAX StorageType 1620 MAX-ACCESS read-create 1621 STATUS current 1622 DESCRIPTION 1623 "The storage type for this row. Rows having the value 1624 'permanent' need not allow write-access to any columnar 1625 objects in the row." 1626 DEFVAL { nonVolatile } 1627 ::= { ipMcastScopeNameEntry 8 } 1629 -- 1630 -- The Multicast Listeners Table 1631 -- 1633 ipMcastLocalListenerTable OBJECT-TYPE 1634 SYNTAX SEQUENCE OF IpMcastLocalListenerEntry 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "The (conceptual) table listing local applications or 1639 services that have joined multicast groups as listeners. 1641 Entries exist for all addresses in the multicast range for 1642 all applications and services as they are classified on this 1643 device." 1644 ::= { ipMcast 9 } 1646 ipMcastLocalListenerEntry OBJECT-TYPE 1647 SYNTAX IpMcastLocalListenerEntry 1648 MAX-ACCESS not-accessible 1649 STATUS current 1650 DESCRIPTION 1651 "An entry (conceptual row) identifying a local application 1652 or service that has joined a multicast group as a listener." 1653 INDEX { ipMcastLocalListenerGroupAddressType, 1654 ipMcastLocalListenerGroupAddress, 1655 ipMcastLocalListenerSourceAddressType, 1656 ipMcastLocalListenerSourceAddress, 1657 ipMcastLocalListenerSourcePrefixLength, 1658 ipMcastLocalListenerRunIndex } 1659 ::= { ipMcastLocalListenerTable 1 } 1661 IpMcastLocalListenerEntry ::= SEQUENCE { 1662 ipMcastLocalListenerGroupAddressType InetAddressType, 1663 ipMcastLocalListenerGroupAddress InetAddress, 1664 ipMcastLocalListenerSourceAddressType InetAddressType, 1665 ipMcastLocalListenerSourceAddress InetAddress, 1666 ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, 1667 ipMcastLocalListenerRunIndex Unsigned32 1668 } 1670 ipMcastLocalListenerGroupAddressType OBJECT-TYPE 1671 SYNTAX InetAddressType 1672 MAX-ACCESS not-accessible 1673 STATUS current 1674 DESCRIPTION 1675 "A value indicating the address family of the address 1676 contained in ipMcastLocalListenerGroupAddress. Legal values 1677 correspond to the subset of address families for which 1678 multicast is supported." 1679 ::= { ipMcastLocalListenerEntry 1 } 1681 ipMcastLocalListenerGroupAddress OBJECT-TYPE 1682 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1683 MAX-ACCESS not-accessible 1684 STATUS current 1685 DESCRIPTION 1686 "The IP multicast group for which this entry specifies 1687 locally joined applications or services." 1688 ::= { ipMcastLocalListenerEntry 2 } 1690 ipMcastLocalListenerSourceAddressType OBJECT-TYPE 1691 SYNTAX InetAddressType 1692 MAX-ACCESS not-accessible 1693 STATUS current 1694 DESCRIPTION 1695 "A value indicating the address family of the address 1696 contained in ipMcastLocalListenerSource. The value MUST be 1697 the same as the value of ipMcastLocalListenerAddressType." 1698 ::= { ipMcastLocalListenerEntry 3 } 1700 ipMcastLocalListenerSourceAddress OBJECT-TYPE 1701 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 "The network address which, when combined with the 1706 corresponding value of the mask specified in 1707 ipMcastLocalListenerSourcePrefixLength, identifies the 1708 sources for which this entry specifies a local listener. 1710 This address object is only significant up to 1711 ipMcastLocalListenerSourcePrefixLength bits. The remainder 1712 of the address bits are zero. This is especially important 1713 for this index field, which is part of the index of this 1714 entry. Any non-zero bits would signify an entirely 1715 different entry. 1717 For addresses of type ipv4z or ipv6z, the appended zone 1718 index is significant even though it lies beyond the prefix 1719 length. The use of these address types indicate that this 1720 listener address applies only within the given zone. Zone 1721 index zero is not valid in this table." 1722 ::= { ipMcastLocalListenerEntry 4 } 1724 ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE 1725 SYNTAX InetAddressPrefixLength (4..128) 1726 MAX-ACCESS not-accessible 1727 STATUS current 1728 DESCRIPTION 1729 "The length in bits of the mask which, when combined with 1730 the corresponding value specified in 1731 ipMcastLocalListenerSource, identifies the sources for which 1732 this entry specifies a local listener. A mask length of 1733 zero corresponds to all sources within the group." 1734 ::= { ipMcastLocalListenerEntry 5 } 1736 ipMcastLocalListenerRunIndex OBJECT-TYPE 1737 SYNTAX Unsigned32 (0..2147483647) 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "A unique value corresponding to a piece of software running 1742 on this router or host system. Where possible, this should 1743 be the system's native, unique identification number. 1745 This identifier is platform-specific. It may correspond to 1746 a process ID or application instance number. 1748 A value of zero indicates that the application instance(s) 1749 cannot be identified. A value of zero indicates that one or 1750 more unidentified applications have joined the specified 1751 multicast groups (for the specified sources) as listeners." 1752 REFERENCE "RFC 2287 sysApplRunIndex" 1753 ::= { ipMcastLocalListenerEntry 6 } 1755 -- 1756 -- The Multicast Zone Table 1757 -- 1759 ipMcastZoneTable OBJECT-TYPE 1760 SYNTAX SEQUENCE OF IpMcastZoneEntry 1761 MAX-ACCESS not-accessible 1762 STATUS current 1763 DESCRIPTION 1764 "The (conceptual) table listing scope zones on this device." 1765 REFERENCE "RFC 4007 section 5" 1766 ::= { ipMcast 10 } 1768 ipMcastZoneEntry OBJECT-TYPE 1769 SYNTAX IpMcastZoneEntry 1770 MAX-ACCESS not-accessible 1771 STATUS current 1772 DESCRIPTION 1773 "An entry (conceptual row) describing a scope zone on this 1774 device." 1775 REFERENCE "RFC 4007 section 5" 1776 INDEX { ipMcastZoneIndex } 1777 ::= { ipMcastZoneTable 1 } 1779 IpMcastZoneEntry ::= SEQUENCE { 1780 ipMcastZoneIndex InetZoneIndex, 1781 ipMcastZoneScopeDefaultZoneIndex InetZoneIndex, 1782 ipMcastZoneScopeAddressType InetAddressType, 1783 ipMcastZoneScopeAddress InetAddress, 1784 ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength 1785 } 1787 ipMcastZoneIndex OBJECT-TYPE 1788 SYNTAX InetZoneIndex (1..4294967295) 1789 MAX-ACCESS not-accessible 1790 STATUS current 1791 DESCRIPTION 1792 "This zone index uniquely identifies a zone on a device. 1794 Each zone is for a given scope. Scope-level information in 1795 this table is for the unique scope that corresponds to this 1796 zone. 1798 Zero is a special value used to request the default zone for 1799 a given scope. Zero is not a valid value for this object. 1801 To test whether ipMcastZoneIndex is the default zone for 1802 this scope, test whether ipMcastZoneIndex is equal to 1803 ipMcastZoneScopeDefaultZoneIndex." 1804 ::= { ipMcastZoneEntry 1 } 1806 ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE 1807 SYNTAX InetZoneIndex (1..4294967295) 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "The default zone index for this scope. This is the zone 1812 that this device will use if the default (zero) zone is 1813 requested for this scope. 1815 Zero is not a valid value for this object." 1816 ::= { ipMcastZoneEntry 2 } 1818 ipMcastZoneScopeAddressType OBJECT-TYPE 1819 SYNTAX InetAddressType 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "The IP address type for which this scope zone exists." 1824 ::= { ipMcastZoneEntry 3 } 1826 ipMcastZoneScopeAddress OBJECT-TYPE 1827 SYNTAX InetAddress (SIZE (4|16)) 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "The multicast group address which, when combined with 1832 ipMcastZoneScopeAddressPrefixLength, gives the multicast 1833 address range for this scope. The InetAddressType is given 1834 by ipMcastZoneScopeAddressType. 1836 Scoped IPv4 multicast address ranges are prefixed by 1837 239.0.0.0/8. Scoped IPv6 multicast address ranges are 1838 FF0x::/16, where x is a valid RFC 4291 multicast scope. 1840 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1841 assigned address. An IPv6 address prefixed by FF3x::/16 is 1842 a unicast-prefix-based multicast addresses. A scope 1843 FF0x::/16 implies an identical scope for these other 1844 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1845 in this table. 1847 This address object is only significant up to 1848 ipMcastZoneScopeAddressPrefixLength bits. The remainder of 1849 the address bits are zero." 1850 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1851 ::= { ipMcastZoneEntry 4 } 1853 ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE 1854 SYNTAX InetAddressPrefixLength (4..32) 1855 MAX-ACCESS read-only 1856 STATUS current 1857 DESCRIPTION 1858 "The length in bits of the mask which, when combined 1859 with ipMcastZoneScopeAddress, gives the multicast address 1860 prefix for this scope. 1862 The InetAddressType is given by ipMcastZoneAddressType. 1863 For 'ipv4' this object must be in the range 4..32. For 1864 'ipv6', this object must be 16." 1865 ::= { ipMcastZoneEntry 5 } 1867 -- 1868 -- Conformance information 1869 -- 1871 ipMcastMIBConformance 1872 OBJECT IDENTIFIER ::= { ipMcastMIB 2 } 1873 ipMcastMIBCompliances 1874 OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } 1875 ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } 1877 -- 1878 -- Compliance statements 1879 -- 1881 ipMcastMIBComplianceHost MODULE-COMPLIANCE 1882 STATUS current 1883 DESCRIPTION 1884 "The compliance statement for hosts supporting IPMCAST-MIB." 1885 MODULE -- this module 1886 MANDATORY-GROUPS { ipMcastMIBLocalListenerGroup, 1887 ipMcastMIBBasicGroup } 1889 OBJECT ipMcastEnable 1890 MIN-ACCESS read-only 1891 DESCRIPTION 1892 "Write access is not required." 1894 GROUP ipMcastMIBSsmGroup 1895 DESCRIPTION 1896 "This group is optional." 1898 GROUP ipMcastMIBRouteGroup 1899 DESCRIPTION 1900 "This group is optional." 1902 GROUP ipMcastMIBIfPktsGroup 1903 DESCRIPTION 1904 "This group is optional." 1906 GROUP ipMcastMIBBoundaryIfGroup 1907 DESCRIPTION 1908 "This group is optional." 1910 GROUP ipMcastMIBScopeNameGroup 1911 DESCRIPTION 1912 "This group is optional." 1914 ::= { ipMcastMIBCompliances 1 } 1916 ipMcastMIBComplianceRouter MODULE-COMPLIANCE 1917 STATUS current 1918 DESCRIPTION 1919 "The compliance statement for routers supporting 1920 IPMCAST-MIB." 1922 MODULE -- this module 1923 MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, 1924 ipMcastMIBBasicGroup, 1925 ipMcastMIBSsmGroup, 1926 ipMcastMIBRouteGroup } 1928 OBJECT ipMcastEnable 1929 MIN-ACCESS read-only 1930 DESCRIPTION 1931 "Write access is not required." 1933 OBJECT ipMcastInterfaceTtl 1934 MIN-ACCESS read-only 1935 DESCRIPTION 1936 "Write access is not required." 1938 OBJECT ipMcastInterfaceRateLimit 1939 MIN-ACCESS read-only 1940 DESCRIPTION 1941 "Write access is not required." 1943 OBJECT ipMcastSsmRangeRowStatus 1944 MIN-ACCESS read-only 1945 DESCRIPTION 1946 "Write access is not required." 1948 OBJECT ipMcastSsmRangeStorageType 1949 MIN-ACCESS read-only 1950 DESCRIPTION 1951 "Write access is not required." 1953 GROUP ipMcastMIBIfPktsGroup 1954 DESCRIPTION 1955 "This group is optional." 1957 GROUP ipMcastMIBPktsOutGroup 1958 DESCRIPTION 1959 "This group is optional." 1961 GROUP ipMcastMIBHopCountGroup 1962 DESCRIPTION 1963 "This group is optional." 1965 GROUP ipMcastMIBRouteOctetsGroup 1966 DESCRIPTION 1967 "This group is optional." 1969 GROUP ipMcastMIBRouteBpsGroup 1970 DESCRIPTION 1971 "This group is optional." 1973 GROUP ipMcastMIBLocalListenerGroup 1974 DESCRIPTION 1975 "This group is optional." 1977 GROUP ipMcastMIBBoundaryIfGroup 1978 DESCRIPTION 1979 "This group is optional." 1981 GROUP ipMcastMIBScopeNameGroup 1982 DESCRIPTION 1983 "This group is optional." 1985 ::= { ipMcastMIBCompliances 2 } 1987 ipMcastMIBComplianceBorderRouter MODULE-COMPLIANCE 1988 STATUS current 1989 DESCRIPTION 1990 "The compliance statement for routers on scope 1991 boundaries supporting IPMCAST-MIB." 1992 MODULE -- this module 1993 MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, 1994 ipMcastMIBBasicGroup, 1995 ipMcastMIBSsmGroup, 1996 ipMcastMIBRouteGroup, 1997 ipMcastMIBBoundaryIfGroup, 1998 ipMcastMIBScopeNameGroup } 2000 OBJECT ipMcastEnable 2001 MIN-ACCESS read-only 2002 DESCRIPTION 2003 "Write access is not required." 2005 OBJECT ipMcastInterfaceTtl 2006 MIN-ACCESS read-only 2007 DESCRIPTION 2008 "Write access is not required." 2010 OBJECT ipMcastInterfaceRateLimit 2011 MIN-ACCESS read-only 2012 DESCRIPTION 2013 "Write access is not required." 2015 OBJECT ipMcastSsmRangeRowStatus 2016 MIN-ACCESS read-only 2017 DESCRIPTION 2018 "Write access is not required." 2020 OBJECT ipMcastSsmRangeStorageType 2021 MIN-ACCESS read-only 2022 DESCRIPTION 2023 "Write access is not required." 2025 GROUP ipMcastMIBIfPktsGroup 2026 DESCRIPTION 2027 "This group is optional." 2029 GROUP ipMcastMIBPktsOutGroup 2030 DESCRIPTION 2031 "This group is optional." 2033 GROUP ipMcastMIBHopCountGroup 2034 DESCRIPTION 2035 "This group is optional." 2037 GROUP ipMcastMIBRouteOctetsGroup 2038 DESCRIPTION 2039 "This group is optional." 2041 GROUP ipMcastMIBRouteBpsGroup 2042 DESCRIPTION 2043 "This group is optional." 2045 GROUP ipMcastMIBLocalListenerGroup 2046 DESCRIPTION 2047 "This group is optional." 2049 ::= { ipMcastMIBCompliances 3 } 2051 -- 2052 -- Units of conformance 2053 -- 2054 ipMcastMIBBasicGroup OBJECT-GROUP 2055 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount 2056 } 2057 STATUS current 2058 DESCRIPTION 2059 "A collection of objects to support basic management of IP 2060 Multicast protocols." 2061 ::= { ipMcastMIBGroups 1 } 2063 ipMcastMIBSsmGroup OBJECT-GROUP 2064 OBJECTS { ipMcastSsmRangeRowStatus, 2065 ipMcastSsmRangeStorageType } 2066 STATUS current 2067 DESCRIPTION 2068 "A collection of objects to support management of Source- 2069 Specific Multicast routing." 2070 ::= { ipMcastMIBGroups 2 } 2072 ipMcastMIBRouteGroup OBJECT-GROUP 2073 OBJECTS { ipMcastInterfaceTtl, 2074 ipMcastInterfaceRateLimit, 2075 ipMcastInterfaceInMcastOctets, 2076 ipMcastInterfaceOutMcastOctets, 2077 ipMcastInterfaceDiscontinuityTime, 2078 ipMcastRouteUpstreamNeighborType, 2079 ipMcastRouteUpstreamNeighbor, 2080 ipMcastRouteInIfIndex, 2081 ipMcastRouteTimeStamp, 2082 ipMcastRouteExpiryTime, 2083 ipMcastRoutePkts, 2084 ipMcastRouteTtlDropPackets, 2085 ipMcastRouteDifferentInIfPackets, 2086 ipMcastRouteNextHopState, 2087 ipMcastRouteNextHopTimeStamp, 2088 ipMcastRouteNextHopExpiryTime 2089 } 2091 STATUS current 2092 DESCRIPTION 2093 "A collection of objects to support basic management of IP 2094 Multicast routing." 2095 ::= { ipMcastMIBGroups 3 } 2097 ipMcastMIBIfPktsGroup OBJECT-GROUP 2098 OBJECTS { ipMcastInterfaceInMcastPkts, 2099 ipMcastInterfaceOutMcastPkts, 2100 ipMcastInterfaceDiscontinuityTime } 2101 STATUS current 2102 DESCRIPTION 2103 "A collection of objects to support management of packet 2104 counters for each interface entry." 2105 ::= { ipMcastMIBGroups 4 } 2107 ipMcastMIBPktsOutGroup OBJECT-GROUP 2108 OBJECTS { ipMcastRouteNextHopTimeStamp, 2109 ipMcastRouteNextHopPkts } 2110 STATUS current 2111 DESCRIPTION 2112 "A collection of objects to support management of packet 2113 counters for each outgoing interface entry of a route." 2114 ::= { ipMcastMIBGroups 5 } 2116 ipMcastMIBHopCountGroup OBJECT-GROUP 2117 OBJECTS { ipMcastRouteNextHopClosestMemberHops } 2118 STATUS current 2119 DESCRIPTION 2120 "A collection of objects to support management of the use of 2121 hop counts in IP Multicast routing." 2122 ::= { ipMcastMIBGroups 6 } 2124 ipMcastMIBRouteOctetsGroup OBJECT-GROUP 2125 OBJECTS { ipMcastRouteTimeStamp, 2126 ipMcastRouteOctets, 2127 ipMcastRouteTtlDropOctets, 2128 ipMcastRouteDifferentInIfOctets, 2129 ipMcastRouteNextHopTimeStamp, 2130 ipMcastRouteNextHopOctets } 2131 STATUS current 2132 DESCRIPTION 2133 "A collection of objects to support management of octet 2134 counters for each forwarding entry." 2135 ::= { ipMcastMIBGroups 7 } 2137 ipMcastMIBRouteBpsGroup OBJECT-GROUP 2138 OBJECTS { ipMcastRouteBps } 2139 STATUS current 2140 DESCRIPTION 2141 "A collection of objects to support sampling of data rate 2142 in bits per second for each forwarding entry." 2143 ::= { ipMcastMIBGroups 8 } 2145 ipMcastMIBRouteProtoGroup OBJECT-GROUP 2146 OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, 2147 ipMcastRouteRtAddressType, ipMcastRouteRtAddress, 2148 ipMcastRouteRtPrefixLength, ipMcastRouteRtType, 2149 ipMcastRouteNextHopProtocol } 2150 STATUS current 2151 DESCRIPTION 2152 "A collection of objects providing information on the 2153 relationship between multicast routing information and the 2154 IP Forwarding Table." 2155 ::= { ipMcastMIBGroups 9 } 2157 ipMcastMIBLocalListenerGroup OBJECT-GROUP 2158 OBJECTS { ipMcastLocalListenerRunIndex } 2159 STATUS current 2160 DESCRIPTION 2161 "A collection of objects to support management of local 2162 listeners on hosts or routers." 2163 ::= { ipMcastMIBGroups 10 } 2165 ipMcastMIBBoundaryIfGroup OBJECT-GROUP 2166 OBJECTS { ipMcastBoundaryTimeStamp, 2167 ipMcastBoundaryDroppedMcastOctets, 2168 ipMcastBoundaryDroppedMcastPkts, 2169 ipMcastBoundaryStatus, 2170 ipMcastBoundaryStorageType, 2171 ipMcastZoneScopeDefaultZoneIndex, 2172 ipMcastZoneScopeAddressType, 2173 ipMcastZoneScopeAddress, 2174 ipMcastZoneScopeAddressPrefixLength 2175 } 2176 STATUS current 2177 DESCRIPTION 2178 "A collection of objects to support management of multicast 2179 scope zone boundaries." 2180 ::= { ipMcastMIBGroups 11 } 2182 ipMcastMIBScopeNameGroup OBJECT-GROUP 2183 OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, 2184 ipMcastScopeNameStatus, ipMcastScopeNameStorageType } 2185 STATUS current 2186 DESCRIPTION 2187 "A collection of objects to support management of multicast 2188 address scope names." 2189 ::= { ipMcastMIBGroups 12 } 2191 END 2193 6. Security Considerations 2195 6.1 SNMPv2 2197 SNMP versions prior to SNMPv3 did not include adequate security. 2198 Even if the network itself is secured (for example by using IPSec), 2199 there is still no control over whom on the secure network is allowed 2200 to access (read/change/create/delete) the objects in this MIB module. 2202 It is RECOMMENDED that implementers consider the security features as 2203 provided by the SNMPv3 framework (see [RFC3410], section 8), 2204 including full support for the SNMPv3 cryptographic mechanisms (for 2205 authentication and privacy). 2207 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2208 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2209 enable cryptographic security. It is then a customer/operator 2210 responsibility to ensure that the SNMP entity giving access to an 2211 instance of this MIB module is properly configured to give access to 2212 the objects only to those principals (users) that have legitimate 2213 rights to access (read/change/create/delete) them. 2215 6.2 Writeable objects 2217 There are a number of management objects defined in this MIB module 2218 with a MAX-ACCESS clause of read-write and/or read-create. This 2219 section discusses and lists these elements. 2221 Such objects may be considered sensitive or vulnerable in some 2222 network environments. The support for SET operations in a non-secure 2223 environment without proper protection can have a negative effect on 2224 network operations. 2226 In this MIB module, possible effects that can be induced by SET 2227 operations on writeable objects include: 2229 o Modifications to multicast routing behavior that prevent or 2230 disrupt services provided by the network, including (but not 2231 limited to) multicast data traffic delivery. 2233 o Modifications to multicast routing behavior that allow 2234 interception or subversion of information that is carried by the 2235 network. For example, attacks can be envisaged that would pass 2236 nominated multicast data streams through a nominated location, 2237 without the sources or listeners becoming aware of this 2238 subversion. 2240 The following are the read-write and read-create objects defined in 2241 this MIB module. 2243 ipMcastEnable 2244 ipMcastInterfaceTtl 2245 ipMcastInterfaceRateLimit 2246 ipMcastSsmRangeRowStatus 2247 ipMcastSsmRangeStorageType 2248 ipMcastBoundaryStatus 2249 ipMcastBoundaryStorageType 2250 ipMcastScopeNameTable 2251 ipMcastScopeNameString 2252 ipMcastScopeNameDefault 2253 ipMcastScopeNameStatus 2254 ipMcastScopeNameStorageType 2256 6.3 Readable objects 2258 As well as the writeable objects discussed above, there are a number 2259 of readable objects (i.e., objects with a MAX-ACCESS other than not- 2260 accessible) that may be considered sensitive or vulnerable in some 2261 network environments. It is thus important to control even GET 2262 and/or NOTIFY access to these objects and possibly to even encrypt 2263 the values of these objects when sending them over the network via 2264 SNMP. 2266 In this MIB module, possible effects that can be induced by GET 2267 and/or NOTIFY operations include: 2269 o Determination of the topology, disposition, and composition of the 2270 network. This information may be commercially sensitive, and may 2271 also be used in preparation for attacks, including any of the 2272 attacks described above. 2274 o Determinion of whether multicast data is flowing in the network, 2275 or has flowed recently, as well as the locations of senders and 2276 recipients. An attacker can apply 'traffic analysis' to this 2277 data. In some cases, the information revealed by traffic analyses 2278 can be as damaging as full knowledge of the data being 2279 transported. 2281 7. IANA Considerations 2283 IP-MCAST-MIB should be rooted under the mib-2 subtree. IANA is 2284 requested to assign { mib-2 XXX } to the IP-MCAST-MIB module 2285 specified in this document. 2287 8. Acknowledgements 2289 This MIB module is based on the original work in [RFC2932] by K. 2290 McCloghrie, D. Farinacci and D. Thaler. 2292 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 2293 been used for comparison while editing this MIB module. 2295 The authors are also grateful to Bill Fenner for fine ideas, and to 2296 Bharat Joshi for input and several corrections. 2298 9. References 2300 9.1 Normative References 2302 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2303 Requirement Levels", BCP 14, RFC 2119, March 1997. 2305 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 2306 RFC 2365, July 1998. 2308 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2309 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 2310 October 1998. 2312 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2313 Schoenwaelder, Ed., "Structure of Management Information 2314 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2316 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2317 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2318 STD 58, RFC 2579, April 1999. 2320 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2321 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2322 April 1999. 2324 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 2325 Conventions for Additional High Capacity Data Types", 2326 RFC 2856, June 2000. 2328 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2329 MIB", RFC 2863, June 2000. 2331 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 2332 Multicast Addresses", RFC 3306, August 2002. 2334 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2335 Architecture for Describing Simple Network Management 2336 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2337 December 2002. 2339 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2340 Schoenwaelder, "Textual Conventions for Internet Network 2341 Addresses", RFC 4001, February 2005. 2343 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 2344 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 2345 March 2005. 2347 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2348 Architecture", RFC 4291, February 2006. 2350 [RFC4293] Routhier, S., "Management Information Base for the 2351 Internet Protocol (IP)", RFC 4293, April 2006. 2353 [I-D.mcwalter-langtag-mib] 2354 McWalter, D., "Language Tag MIB", 2355 draft-mcwalter-langtag-mib-02 (work in progress), I-D 2356 Status active, March 2007. 2358 9.2 Informative References 2360 [RFC1075] Waitzman, D., Partridge, C., and S. Deering, "Distance 2361 Vector Multicast Routing Protocol", RFC 1075, 2362 November 1988. 2364 [RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, 2365 March 1994. 2367 [RFC2189] Ballardie, T., "Core Based Trees (CBT version 2) Multicast 2368 Routing -- Protocol Specification --", RFC 2189, 2369 September 1997. 2371 [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level 2372 Managed Objects for Applications", RFC 2287, 2373 February 1998. 2375 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 2376 Multicast Routing MIB", RFC 2932, October 2000. 2378 [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, 2379 "Protocol Independent Multicast MIB for IPv4", RFC 2934, 2380 October 2000. 2382 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2383 "Introduction and Applicability Statements for Internet- 2384 Standard Management Framework", RFC 3410, December 2002. 2386 [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific 2387 Multicast (SSM)", RFC 3569, July 2003. 2389 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2390 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 2391 Protocol Specification (Revised)", RFC 4601, August 2006. 2393 [I-D.ietf-pim-bidir] 2394 Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 2395 "Bi-directional Protocol Independent Multicast (BIDIR- 2396 PIM)", draft-ietf-pim-bidir-09 (work in progress), 2397 February 2007. 2399 Authors' Addresses 2401 David McWalter 2402 Data Connection Ltd 2403 100 Church Street 2404 Enfield EN2 6BQ 2405 UK 2407 Email: dmcw@dataconnection.com 2409 Dave Thaler 2410 Microsoft Corporation 2411 One Microsoft Way 2412 Redmond WA 98052-6399 2413 USA 2415 Email: dthaler@windows.microsoft.com 2416 Andrew Kessler 2417 Cisco Systems 2418 425 E. Tasman Drive 2419 San Jose CA 95134 2420 USA 2422 Email: kessler@cisco.com 2424 Intellectual Property Statement 2426 The IETF takes no position regarding the validity or scope of any 2427 Intellectual Property Rights or other rights that might be claimed to 2428 pertain to the implementation or use of the technology described in 2429 this document or the extent to which any license under such rights 2430 might or might not be available; nor does it represent that it has 2431 made any independent effort to identify any such rights. Information 2432 on the procedures with respect to rights in RFC documents can be 2433 found in BCP 78 and BCP 79. 2435 Copies of IPR disclosures made to the IETF Secretariat and any 2436 assurances of licenses to be made available, or the result of an 2437 attempt made to obtain a general license or permission for the use of 2438 such proprietary rights by implementers or users of this 2439 specification can be obtained from the IETF on-line IPR repository at 2440 http://www.ietf.org/ipr. 2442 The IETF invites any interested party to bring to its attention any 2443 copyrights, patents or patent applications, or other proprietary 2444 rights that may cover technology that may be required to implement 2445 this standard. Please address the information to the IETF at 2446 ietf-ipr@ietf.org. 2448 Disclaimer of Validity 2450 This document and the information contained herein are provided on an 2451 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2452 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2453 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2454 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2455 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2456 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2458 Copyright Statement 2460 Copyright (C) The IETF Trust (2007). This document is subject to the 2461 rights, licenses and restrictions contained in BCP 78, and except as 2462 set forth therein, the authors retain all their rights. 2464 Acknowledgment 2466 Funding for the RFC Editor function is currently provided by the 2467 Internet Society.