idnits 2.17.1 draft-ietf-mboned-ip-mcast-mib-02.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 on line 2406. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2383. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2390. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2396. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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 is 1 instance of lines with control characters in the document. == There is 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 == There is 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- 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 RFC 3978 Section 5.4 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 (July 17, 2006) is 6493 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2434' is defined on line 2269, but no explicit reference was found in the text == Unused Reference: 'RFC3283' is defined on line 2288, but no explicit reference was found in the text == Unused Reference: 'RFC3306' is defined on line 2291, but no explicit reference was found in the text == Unused Reference: 'RFC4007' is defined on line 2298, but no explicit reference was found in the text == Unused Reference: 'RFC4291' is defined on line 2302, but no explicit reference was found in the text == Unused Reference: 'RFC1075' is defined on line 2307, but no explicit reference was found in the text == Unused Reference: 'RFC1584' is defined on line 2311, but no explicit reference was found in the text == Unused Reference: 'RFC2189' is defined on line 2314, but no explicit reference was found in the text == Unused Reference: 'RFC2287' is defined on line 2318, but no explicit reference was found in the text == Unused Reference: 'RFC2934' is defined on line 2325, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-sm-v2-new' is defined on line 2336, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-bidir' is defined on line 2343, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Downref: Normative reference to an Informational RFC: RFC 3283 -- Obsolete informational reference (is this intentional?): RFC 2932 (Obsoleted by RFC 5132) == Outdated reference: A later version (-09) exists of draft-ietf-pim-bidir-08 Summary: 7 errors (**), 0 flaws (~~), 18 warnings (==), 9 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 Expires: January 18, 2007 D. Thaler 5 Microsoft Corporation 6 Obsoletes (if approved): RFC2932 A. Kessler 7 Cisco Systems 8 July 17, 2006 10 IP Multicast MIB 11 draft-ietf-mboned-ip-mcast-mib-02.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 January 18, 2007. 38 Copyright Notice 40 Copyright (C) The Internet Society (2006). 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 . . . . . . . . . . . . . . . . . . . 45 58 6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 46 59 6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 46 60 6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 47 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 64 9.1 Normative References . . . . . . . . . . . . . . . . . . . 48 65 9.2 Informative References . . . . . . . . . . . . . . . . . . 49 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 50 67 Intellectual Property and Copyright Statements . . . . . . . . 52 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 is includes support for IPv6 addressing and the 83 IPv6 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. 89 o This MIB module includes objects that are not specific to 90 multicast routing. It allows management of multicast function on 91 systems that do not perform routing, whereas RFC 2932 was 92 restricted to multicast routing. 94 o This MIB module includes a table of Source-Specific Multicast 95 (SSM) address ranges to which SSM semantics [RFC3569] should be 96 applied. 98 o This MIB module includes a table of local applications that are 99 receiving multicast data. 101 o This MIB module includes a table of multicast scope zones. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 3. The Internet-Standard Management Framework 109 For a detailed overview of the documents that describe the current 110 Internet-Standard Management Framework, please refer to section 7 of 111 [RFC3410]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. MIB objects are generally 115 accessed through the Simple Network Management Protocol (SNMP). 116 Objects in the MIB are defined using the mechanisms defined in the 117 Structure of Management Information (SMI). This memo specifies a MIB 118 module that is compliant to the SMIv2, which is described in STD 58, 119 ([RFC2578], [RFC2579] and [RFC2580]). 121 4. Overview 123 This MIB module contains two scalars and seven tables. The tables 124 are: 126 1. The IP Multicast Interface Table containing multicast information 127 specific to interfaces. 129 2. The IP Multicast SSM Range Table, which contains one row per 130 range of multicast group addresses to which Source-Specific 131 Multicast semantics [RFC3569] should be applied. 133 3. The IP Multicast Route Table containing multicast routing 134 information for IP datagrams sent by particular sources to the IP 135 multicast groups known to a system. 137 4. The IP Multicast Routing Next Hop Table containing information on 138 next-hops for the routing of IP multicast datagrams. Each entry 139 is one of a list of next-hops on outgoing interfaces for 140 particular sources sending to a particular multicast group 141 address. 143 5. The IP Multicast Scope Boundary Table containing the boundaries 144 configured for multicast scopes [RFC2365]. 146 6. The IP Multicast Scope Name Table containing human-readable names 147 of multicast scope. 149 7. The IP Multicast Local Listener Table containing identifiers for 150 local applications that are receiving multicast data. 152 This MIB module uses textual conventions defined in the IF-MIB 153 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 155 5. Definitions 157 IPMCAST-MIB DEFINITIONS ::= BEGIN 159 IMPORTS 160 MODULE-IDENTITY, OBJECT-TYPE, 161 mib-2, Unsigned32, Counter32, 162 Counter64, Gauge32, TimeTicks FROM SNMPv2-SMI 163 RowStatus, TEXTUAL-CONVENTION, 164 TruthValue, StorageType, 165 TimeStamp FROM SNMPv2-TC 166 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 167 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 168 InterfaceIndexOrZero, 169 InterfaceIndex FROM IF-MIB 170 IANAipRouteProtocol, 171 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 172 InetAddress, InetAddressType, 173 InetAddressPrefixLength, 174 InetZoneIndex FROM INET-ADDRESS-MIB; 176 ipMcastMIB MODULE-IDENTITY 177 LAST-UPDATED "200607170000Z" -- 17 July 2006 178 ORGANIZATION "IETF MBONED Working Group" 179 CONTACT-INFO "David McWalter 180 Data Connection Limited 181 100 Church Street 182 Enfield, EN2 6BQ 183 UK 185 Phone: +44 208 366 1177 186 EMail: dmcw@dataconnection.com 188 Dave Thaler 189 Microsoft Corporation 190 One Microsoft Way 191 Redmond, WA 98052-6399 192 US 194 Phone: +1 425 703 8835 195 EMail: dthaler@dthaler.microsoft.com 197 Andrew Kessler 198 Cisco Systems 199 425 E. Tasman Drive 200 San Jose, CA 95134 201 US 203 Phone: +1 408 526 5139 204 EMail: kessler@cisco.com" 205 DESCRIPTION 206 "The MIB module for management of IP Multicast function. 208 This MIB module contains information about IP Multicast 209 routing, data forwarding, and data reception. This MIB 210 module is independent of the multicast protocol(s) and 211 address type(s) that are in use. 213 Copyright (C) The Internet Society (2006). This version of 214 this MIB module is part of RFC yyyy; see the RFC itself for 215 full legal notices." 216 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 217 REVISION "200607170000Z" -- 17 July 2006 218 DESCRIPTION 219 "Changes from RFC 2932: 221 1) This MIB module is independent of address type, whereas 222 RFC 2932 only supported IPv4. 223 2) This MIB module allows several multicast protocols to 224 perform routing on a single interface, whereas RFC 2932 225 assumed each interface supported at most one multicast 226 routing protocol. This MIB module retains but deprecates 227 the object ipMcastInterfaceProtocol. 228 3) This MIB module includes objects that are not specific to 229 multicast routing. It allows management of multicast 230 function on systems that do not perform routing, whereas 231 RFC 2932 was restricted to multicast routing. 232 4) This MIB module includes a table of Source-Specific 233 Multicast (SSM) address ranges to which RFC 3569 SSM 234 semantics should be applied. 235 5) This MIB module includes a table of local applications 236 that are receiving multicast data. 238 Published as RFC yyyy." 239 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 240 ::= { mib-2 XXX } 241 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 243 -- 244 -- Textual conventions 245 -- 247 LanguageTag ::= TEXTUAL-CONVENTION 249 DISPLAY-HINT "99a" 250 STATUS current 251 DESCRIPTION 252 "A language tag with all alphabetic characters converted to 253 lowercase. This restriction is intended to make the lexical 254 ordering imposed by SNMP useful when applied to language 255 tags. Note that it is theoretically possible for a valid 256 language tag to exceed the allowed length of this syntax, 257 and thus be impossible to represent with this syntax. 258 Sampling of language tags in current use on the Internet 259 suggests that this limit does not pose a serious problem in 260 practice." 262 REFERENCE "RFC 3283" 263 SYNTAX OCTET STRING (SIZE (1..99)) 265 -- 266 -- Top-level structure of the MIB 267 -- 269 ipMcastMIBObjects OBJECT IDENTIFIER ::= { ipMcastMIB 1 } 271 ipMcast OBJECT IDENTIFIER ::= { ipMcastMIBObjects 1 } 273 ipMcastEnable OBJECT-TYPE 274 SYNTAX INTEGER { enabled(1), disabled(2) } 275 MAX-ACCESS read-write 276 STATUS current 277 DESCRIPTION 278 "The enabled status of IP Multicast function on this 279 system." 280 ::= { ipMcast 1 } 282 ipMcastRouteEntryCount OBJECT-TYPE 283 SYNTAX Gauge32 284 MAX-ACCESS read-only 285 STATUS current 286 DESCRIPTION 287 "The number of rows in the ipMcastRouteTable. This can be 288 used to check for multicast routing activity, and to monitor 289 the multicast routing table size." 290 ::= { ipMcast 7 } 292 -- 293 -- The Multicast Interface Table 294 -- 296 ipMcastInterfaceTable OBJECT-TYPE 297 SYNTAX SEQUENCE OF IpMcastInterfaceEntry 298 MAX-ACCESS not-accessible 299 STATUS current 300 DESCRIPTION 301 "The (conceptual) table used to manage the multicast 302 protocol active on an interface." 303 ::= { ipMcast 4 } 305 ipMcastInterfaceEntry OBJECT-TYPE 306 SYNTAX IpMcastInterfaceEntry 307 MAX-ACCESS not-accessible 308 STATUS current 309 DESCRIPTION 310 "An entry (conceptual row) containing the multicast protocol 311 information for a particular interface." 312 INDEX { ipMcastInterfaceIfIndex } 313 ::= { ipMcastInterfaceTable 1 } 315 IpMcastInterfaceEntry ::= SEQUENCE { 316 ipMcastInterfaceIfIndex InterfaceIndex, 317 ipMcastInterfaceTtl Unsigned32, 318 ipMcastInterfaceProtocol IANAipMRouteProtocol, 319 ipMcastInterfaceRateLimit Unsigned32, 320 ipMcastInterfaceInMcastOctets Counter32, 321 ipMcastInterfaceOutMcastOctets Counter32, 322 ipMcastInterfaceInMcastPkts Counter32, 323 ipMcastInterfaceOutMcastPkts Counter32, 324 ipMcastInterfaceHCInMcastOctets Counter64, 325 ipMcastInterfaceHCOutMcastOctets Counter64, 326 ipMcastInterfaceHCInMcastPkts Counter64, 327 ipMcastInterfaceHCOutMcastPkts Counter64 328 } 330 ipMcastInterfaceIfIndex OBJECT-TYPE 331 SYNTAX InterfaceIndex 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "The ifIndex value of the interface for which this entry 336 contains information." 337 ::= { ipMcastInterfaceEntry 1 } 339 ipMcastInterfaceTtl OBJECT-TYPE 340 SYNTAX Unsigned32 (0..255) 341 MAX-ACCESS read-write 342 STATUS current 343 DESCRIPTION 344 "The datagram TTL threshold for the interface. Any IP 345 multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) 346 less than this threshold will not be forwarded out the 347 interface. The default value of 0 means all multicast 348 packets are forwarded out the interface." 349 DEFVAL { 0 } 350 ::= { ipMcastInterfaceEntry 2 } 352 ipMcastInterfaceProtocol OBJECT-TYPE 353 SYNTAX IANAipMRouteProtocol 354 MAX-ACCESS read-write 355 STATUS deprecated 356 DESCRIPTION 357 "The multicast protocol running on this interface. 359 More than one multicast protocol can be used on an 360 interface, so this object is ambiguous. Use of this 361 object is deprecated." 362 ::= { ipMcastInterfaceEntry 3 } 364 ipMcastInterfaceRateLimit OBJECT-TYPE 365 SYNTAX Unsigned32 (0..2147483647) 366 MAX-ACCESS read-write 367 STATUS current 368 DESCRIPTION 369 "The rate-limit, in kilobits per second, of forwarded 370 multicast traffic on the interface. A rate-limit of 0 371 indicates that no rate limiting is done." 372 DEFVAL { 0 } 373 ::= { ipMcastInterfaceEntry 4 } 375 ipMcastInterfaceInMcastOctets OBJECT-TYPE 376 SYNTAX Counter32 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "The number of octets of multicast packets that have arrived 381 on the interface, including framing characters. This object 382 is similar to ifInOctets in the Interfaces MIB, except that 383 only multicast packets are counted." 384 ::= { ipMcastInterfaceEntry 5 } 386 ipMcastInterfaceOutMcastOctets OBJECT-TYPE 387 SYNTAX Counter32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The number of octets of multicast packets that have been 392 sent on the interface." 393 ::= { ipMcastInterfaceEntry 6 } 395 ipMcastInterfaceInMcastPkts OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of multicast packets that have arrived on the 401 interface. In many cases, this object is identical to 402 ifInMulticastPkts in the Interfaces MIB. 404 However, some implementations use ifXTable for Layer 2 405 traffic statistics and ipMcastInterfaceTable at Layer 3. In 406 this case a difference between these objects probably 407 indicates that some Layer 3 multicast packets are being 408 transmitted as unicast at Layer 2." 409 REFERENCE "RFC 2863 ifInMulticastPkts" 410 ::= { ipMcastInterfaceEntry 7 } 412 ipMcastInterfaceOutMcastPkts OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The number of multicast packets that have been sent on the 418 interface. In many cases, this object is identical to 419 ifOutMulticastPkts in the Interfaces MIB. 421 However, some implementations use ifXTable for Layer 2 422 traffic statistics and ipMcastInterfaceTable at Layer 3. In 423 this case a difference between these objects probably 424 indicates that some Layer 3 multicast packets are being 425 transmitted as unicast at Layer 2." 426 REFERENCE "RFC 2863 ifOutMulticastPkts" 427 ::= { ipMcastInterfaceEntry 8 } 429 ipMcastInterfaceHCInMcastOctets OBJECT-TYPE 430 SYNTAX Counter64 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The number of octets of multicast packets that have arrived 435 on the interface, including framing characters. This object 436 is a 64-bit version of ipMcastRouteInterfaceInMcastOctets. 437 It is similar to ifHCInOctets in the Interfaces MIB, except 438 that only multicast packets are counted." 439 ::= { ipMcastInterfaceEntry 9 } 441 ipMcastInterfaceHCOutMcastOctets OBJECT-TYPE 442 SYNTAX Counter64 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The number of octets of multicast packets that have been 447 sent on the interface. This object is a 64-bit version of 448 ipMcastRouteInterfaceOutMcastOctets." 449 ::= { ipMcastInterfaceEntry 10 } 451 ipMcastInterfaceHCInMcastPkts OBJECT-TYPE 452 SYNTAX Counter64 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "The number of multicast packets that have arrived on the 457 interface. In many cases, this object is identical to 458 ifHCInMulticastPkts in the Interfaces MIB. 460 However, some implementations use ifXTable for Layer 2 461 traffic statistics and ipMcastInterfaceTable at Layer 3. In 462 this case a difference between these objects probably 463 indicates that some Layer 3 multicast packets are being 464 transmitted as unicast at Layer 2." 465 REFERENCE "RFC 2863 ifHCInMulticastPkts" 466 ::= { ipMcastInterfaceEntry 11 } 468 ipMcastInterfaceHCOutMcastPkts OBJECT-TYPE 469 SYNTAX Counter64 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "The number of multicast packets that have been sent on the 474 interface. In many cases, this object is identical to 475 ifHCOutMulticastPkts in the Interfaces MIB. 477 However, some implementations use ifXTable for Layer 2 478 traffic statistics and ipMcastInterfaceTable at Layer 3. In 479 this case a difference between these objects probably 480 indicates that some Layer 3 multicast packets are being 481 transmitted as unicast at Layer 2." 482 REFERENCE "RFC 2863 ifHCOutMulticastPkts" 483 ::= { ipMcastInterfaceEntry 12 } 485 -- 486 -- The SSM Range Table 487 -- 489 ipMcastSsmRangeTable OBJECT-TYPE 490 SYNTAX SEQUENCE OF IpMcastSsmRangeEntry 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "This table is used to create and manage the range(s) of 495 group addresses to which SSM semantics should be applied." 496 REFERENCE "RFC 3569" 497 ::= { ipMcast 8 } 499 ipMcastSsmRangeEntry OBJECT-TYPE 500 SYNTAX IpMcastSsmRangeEntry 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 "An entry (conceptual row) containing a range of group 505 addresses to which SSM semantics should be applied." 506 REFERENCE "RFC 3569" 507 INDEX { ipMcastSsmRangeAddressType, 508 ipMcastSsmRangeAddress, 509 ipMcastSsmRangePrefixLength } 510 ::= { ipMcastSsmRangeTable 1 } 512 IpMcastSsmRangeEntry ::= SEQUENCE { 513 ipMcastSsmRangeAddressType InetAddressType, 514 ipMcastSsmRangeAddress InetAddress, 515 ipMcastSsmRangePrefixLength InetAddressPrefixLength, 516 ipMcastSsmRangeRowStatus RowStatus, 517 ipMcastSsmRangeStorageType StorageType 518 } 520 ipMcastSsmRangeAddressType OBJECT-TYPE 521 SYNTAX InetAddressType 522 MAX-ACCESS not-accessible 523 STATUS current 524 DESCRIPTION 525 "The address type of the multicast group prefix." 526 ::= { ipMcastSsmRangeEntry 1 } 528 ipMcastSsmRangeAddress OBJECT-TYPE 529 SYNTAX InetAddress (SIZE (4|8|16|20)) 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "The multicast group address which, when combined with 534 ipMcastSsmRangePrefixLength, gives the group prefix for this 535 SSM range. The InetAddressType is given by 536 ipMcastSsmRangeAddressType. 538 This address object is only significant up to 539 ipMcastSsmRangePrefixLength bits. The remainder of the 540 address bits are zero. This is especially important for 541 this index field, which is part of the index of this entry. 542 Any non-zero bits would signify an entirely different 543 entry. 545 For IPv6 SSM address ranges, only ranges prefixed by 546 FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291 547 multicast address scope. The syntax of the address range is 548 given by RFC 3306 sections 4 and 7. 550 For addresses of type ipv4z or ipv6z, the appended zone 551 index is significant even though it lies beyond the prefix 552 length. The use of these address types indicate that this 553 SSM range entry applies only within the given zone. Zone 554 index zero is not valid in this table. 556 If non-global scope SSM range entries are present, then 557 consistent ipMcastBoundaryTable entries are required on 558 routers at the zone boundary." 559 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 560 and 7" 561 ::= { ipMcastSsmRangeEntry 2 } 563 ipMcastSsmRangePrefixLength OBJECT-TYPE 564 SYNTAX InetAddressPrefixLength (4..128) 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "The length in bits of the mask which, when combined with 569 ipMcastSsmRangeAddress, gives the group prefix for this SSM 570 range. The InetAddressType is given by 571 ipMcastSsmRangeAddressType. For values 'ipv4' and 'ipv4z', 572 this object must be in the range 4..32. For values 'ipv6' 573 and 'ipv6z', this object must be in the range 8..128." 574 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 575 and 7" 576 ::= { ipMcastSsmRangeEntry 3 } 578 ipMcastSsmRangeRowStatus OBJECT-TYPE 579 SYNTAX RowStatus 580 MAX-ACCESS read-create 581 STATUS current 582 DESCRIPTION 583 "The status of this row, by which rows in this table can 584 be created and destroyed. 586 This status object can be set to active(1) without setting 587 any other columnar objects in this entry. 589 All writeable objects in this entry can be modified when the 590 status of this entry is active(1)." 591 ::= { ipMcastSsmRangeEntry 4 } 593 ipMcastSsmRangeStorageType OBJECT-TYPE 594 SYNTAX StorageType 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "The storage type for this row. Rows having the value 599 'permanent' need not allow write-access to any columnar 600 objects in the row." 601 DEFVAL { nonVolatile } 602 ::= { ipMcastSsmRangeEntry 5 } 604 -- 605 -- The IP Multicast Routing Table 606 -- 608 ipMcastRouteTable OBJECT-TYPE 609 SYNTAX SEQUENCE OF IpMcastRouteEntry 610 MAX-ACCESS not-accessible 611 STATUS current 612 DESCRIPTION 613 "The (conceptual) table containing multicast routing 614 information for IP datagrams sent by particular sources to 615 to the IP multicast groups known to this router." 616 ::= { ipMcast 2 } 618 ipMcastRouteEntry OBJECT-TYPE 619 SYNTAX IpMcastRouteEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "An entry (conceptual row) containing the multicast routing 624 information for IP datagrams from a particular source and 625 addressed to a particular IP multicast group address." 626 INDEX { ipMcastRouteGroupAddressType, 627 ipMcastRouteGroup, 628 ipMcastRouteGroupPrefixLength, 629 ipMcastRouteSourceAddressType, 630 ipMcastRouteSource, 631 ipMcastRouteSourcePrefixLength } 632 ::= { ipMcastRouteTable 1 } 634 IpMcastRouteEntry ::= SEQUENCE { 635 ipMcastRouteGroupAddressType InetAddressType, 636 ipMcastRouteGroup InetAddress, 637 ipMcastRouteGroupPrefixLength InetAddressPrefixLength, 638 ipMcastRouteSourceAddressType InetAddressType, 639 ipMcastRouteSource InetAddress, 640 ipMcastRouteSourcePrefixLength InetAddressPrefixLength, 641 ipMcastRouteUpstreamNeighborType InetAddressType, 642 ipMcastRouteUpstreamNeighbor InetAddress, 643 ipMcastRouteInIfIndex InterfaceIndexOrZero, 644 ipMcastRouteTimeStamp TimeStamp, 645 ipMcastRouteExpiryTime TimeTicks, 646 ipMcastRoutePkts Counter32, 647 ipMcastRouteDifferentInIfPackets Counter32, 648 ipMcastRouteOctets Counter32, 649 ipMcastRouteProtocol IANAipMRouteProtocol, 650 ipMcastRouteRtProtocol IANAipRouteProtocol, 651 ipMcastRouteRtAddressType InetAddressType, 652 ipMcastRouteRtAddress InetAddress, 653 ipMcastRouteRtPrefixLength InetAddressPrefixLength, 654 ipMcastRouteRtType INTEGER, 655 ipMcastRouteHCOctets Counter64, 656 ipMcastRouteDifferentInIfOctets Counter32, 657 ipMcastRouteTtlDropPackets Counter32, 658 ipMcastRouteTtlDropOctets Counter32 659 } 661 ipMcastRouteGroupAddressType OBJECT-TYPE 662 SYNTAX InetAddressType 663 MAX-ACCESS not-accessible 664 STATUS current 665 DESCRIPTION 666 "A value indicating the address family of the address 667 contained in ipMcastRouteGroup. Legal values correspond to 668 the subset of address families for which multicast 669 forwarding is supported." 670 ::= { ipMcastRouteEntry 1 } 672 ipMcastRouteGroup OBJECT-TYPE 673 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "The IP multicast group address which, when combined with 678 the corresponding value specified in 679 ipMcastRouteGroupPrefixLength, identifies the groups for 680 which this entry contains multicast routing information. 682 This address object is only significant up to 683 ipMcastRouteGroupPrefixLength bits. The remainder of the 684 address bits are zero. This is especially important for 685 this index field, which is part of the index of this entry. 686 Any non-zero bits would signify an entirely different 687 entry." 688 ::= { ipMcastRouteEntry 2 } 690 ipMcastRouteGroupPrefixLength OBJECT-TYPE 691 SYNTAX InetAddressPrefixLength (4..128) 692 MAX-ACCESS not-accessible 693 STATUS current 694 DESCRIPTION 695 "The length in bits of the mask which, when combined with 696 the corresponding value of ipMcastRouteGroup, identifies the 697 groups for which this entry contains multicast routing 698 information." 699 ::= { ipMcastRouteEntry 3 } 701 ipMcastRouteSourceAddressType OBJECT-TYPE 702 SYNTAX InetAddressType 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "A value indicating the address family of the address 707 contained in ipMcastRouteSource. The value MUST be the same 708 as the value of ipMcastRouteGroupType." 709 ::= { ipMcastRouteEntry 4 } 711 ipMcastRouteSource OBJECT-TYPE 712 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "The network address which, when combined with the 717 corresponding value of ipMcastRouteSourcePrefixLength, 718 identifies the sources for which this entry contains 719 multicast routing information. 721 This address object is only significant up to 722 ipMcastRouteGroupPrefixLength bits. The remainder of the 723 address bits are zero. This is especially important for 724 this index field, which is part of the index of this entry. 725 Any non-zero bits would signify an entirely different 726 entry." 727 ::= { ipMcastRouteEntry 5 } 729 ipMcastRouteSourcePrefixLength OBJECT-TYPE 730 SYNTAX InetAddressPrefixLength (4..128) 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "The length in bits of the mask which, when combined with 735 the corresponding value of ipMcastRouteSource, identifies 736 the sources for which this entry contains multicast routing 737 information." 738 ::= { ipMcastRouteEntry 6 } 740 ipMcastRouteUpstreamNeighborType OBJECT-TYPE 741 SYNTAX InetAddressType 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "A value indicating the address family of the address 746 contained in ipMcastRouteUpstreamNeighbor. The value MUST 747 be the same as the value of ipMcastRouteGroupType." 748 ::= { ipMcastRouteEntry 7 } 750 ipMcastRouteUpstreamNeighbor OBJECT-TYPE 751 SYNTAX InetAddress 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The address of the upstream neighbor (for example, RPF 756 neighbor) from which IP datagrams from these sources to 757 this multicast address are received. If the upstream 758 neighbor is unknown, then ipMcastRouteUpstreamNeighbor 759 will be 0.0.0.0 in the case of an IPv4 entry, and 760 0:0:0:0:0:0:0:0 in the case of an IPv6 entry (for example, 761 in BIDIR-PIM)." 762 ::= { ipMcastRouteEntry 8 } 764 ipMcastRouteInIfIndex OBJECT-TYPE 765 SYNTAX InterfaceIndexOrZero 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The value of ifIndex for the interface on which IP 770 datagrams sent by these sources to this multicast address 771 are received. A value of 0 indicates that datagrams are not 772 subject to an incoming interface check, but may be accepted 773 on multiple interfaces (for example, in BIDIR-PIM)." 774 ::= { ipMcastRouteEntry 9 } 776 ipMcastRouteTimeStamp OBJECT-TYPE 777 SYNTAX TimeStamp 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The value of sysUpTime at which the multicast routing 782 information represented by this entry was learned by the 783 router." 784 ::= { ipMcastRouteEntry 10 } 786 ipMcastRouteExpiryTime OBJECT-TYPE 787 SYNTAX TimeTicks 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The minimum amount of time remaining before this entry will 792 be aged out. The value 0 indicates that the entry is not 793 subject to aging. If ipMcastRouteNextHopState is pruned(1), 794 this object represents the remaining time until the prune 795 expires. If this timer expires, state reverts to 796 forwarding(2). Otherwise, this object represents the time 797 until this entry is removed from the table." 798 ::= { ipMcastRouteEntry 11 } 800 ipMcastRoutePkts OBJECT-TYPE 801 SYNTAX Counter32 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The number of packets routed using this multicast route 806 entry. 808 Discontinuities in this monotonically increasing value 809 occur at re-initialization of the management system. 810 Discontinuities can also occur as a result of routes being 811 removed and replaced, which can be detected by observing 812 the value of ipMcastRouteTimeStamp." 813 ::= { ipMcastRouteEntry 12 } 815 ipMcastRouteDifferentInIfPackets OBJECT-TYPE 816 SYNTAX Counter32 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The number of packets which this router has received from 821 these sources and addressed to this multicast group address, 822 which were dropped because they were received on an 823 unexpected interface. 825 For RPF checking protocols (such as PIM-SM), these packets 826 arrived on interfaces other than ipMcastRouteInIfIndex, and 827 were dropped because of this failed RPF check. (RPF paths 828 are 'Reverse Path Forwarding' path; the unicast routes to 829 the expected origin of multicast data flows). 831 Other protocols may drop packets on an incoming interface 832 check for different reasons (for example, BIDIR-PIM performs 833 a DF check on receipt of packets). All packets dropped as a 834 result of an incoming interface check are counted here. 836 If this counter increases rapidly, this indicates a problem. 837 A significant quantity of multicast data is arriving at this 838 router on unexpected interfaces, and is not being forwarded. 840 For guidance, if the rate of increase of this counter 841 exceeds 1% of the rate of increase of ipMcastRoutePkts, then 842 there are multicast routing problems that require 843 investigation. 845 Discontinuities in this monotonically increasing value 846 occur at re-initialization of the management system. 847 Discontinuities can also occur as a result of routes being 848 removed and replaced, which can be detected by observing 849 the value of ipMcastRouteTimeStamp." 850 ::= { ipMcastRouteEntry 13 } 852 ipMcastRouteOctets OBJECT-TYPE 853 SYNTAX Counter32 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "The number of octets contained in IP datagrams which were 858 received from these sources and addressed to this multicast 859 group address, and which were forwarded by this router. 861 Discontinuities in this monotonically increasing value 862 occur at re-initialization of the management system. 863 Discontinuities can also occur as a result of routes being 864 removed and replaced, which can be detected by observing 865 the value of ipMcastRouteTimeStamp." 866 ::= { ipMcastRouteEntry 14 } 868 ipMcastRouteProtocol OBJECT-TYPE 869 SYNTAX IANAipMRouteProtocol 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "The multicast routing protocol via which this multicast 874 forwarding entry was learned." 875 ::= { ipMcastRouteEntry 15 } 877 ipMcastRouteRtProtocol OBJECT-TYPE 878 SYNTAX IANAipRouteProtocol 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "The routing mechanism via which the route used to find the 883 upstream or parent interface for this multicast forwarding 884 entry was learned. Inclusion of values for routing 885 protocols is not intended to imply that those protocols need 886 be supported." 887 ::= { ipMcastRouteEntry 16 } 889 ipMcastRouteRtAddressType OBJECT-TYPE 890 SYNTAX InetAddressType 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "A value indicating the address family of the address 895 contained in ipMcastRouteRtAddress. The value MUST be the 896 same as the value of ipMcastRouteGroupType." 897 ::= { ipMcastRouteEntry 17 } 899 ipMcastRouteRtAddress OBJECT-TYPE 900 SYNTAX InetAddress 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "The address portion of the route used to find the upstream 905 or parent interface for this multicast forwarding entry. 907 This address object is only significant up to 908 ipMcastRouteGroupPrefixLength bits. The remainder of the 909 address bits are zero." 910 ::= { ipMcastRouteEntry 18 } 912 ipMcastRouteRtPrefixLength OBJECT-TYPE 913 SYNTAX InetAddressPrefixLength (4..128) 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The length in bits of the mask associated with the route 918 used to find the upstream or parent interface for this 919 multicast forwarding entry." 920 ::= { ipMcastRouteEntry 19 } 922 ipMcastRouteRtType OBJECT-TYPE 923 SYNTAX INTEGER { 924 unicast (1), -- Unicast route used in multicast RIB 925 multicast (2) -- Multicast route 926 } 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "The reason the given route was placed in the (logical) 931 multicast Routing Information Base (RIB). A value of 932 unicast means that the route would normally be placed only 933 in the unicast RIB, but was placed in the multicast RIB 934 (instead or in addition) due to local configuration, such as 935 when running PIM over RIP. A value of multicast means that 936 the route was explicitly added to the multicast RIB by the 937 routing protocol, such as DVMRP or Multiprotocol BGP." 938 ::= { ipMcastRouteEntry 20 } 940 ipMcastRouteHCOctets OBJECT-TYPE 941 SYNTAX Counter64 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "The number of octets contained in IP datagrams which were 946 received from these sources and addressed to this multicast 947 group address, and which were forwarded by this router. 948 This object is a 64-bit version of ipMcastRouteOctets. 950 Discontinuities in this monotonically increasing value 951 occur at re-initialization of the management system. 952 Discontinuities can also occur as a result of routes being 953 removed and replaced, which can be detected by observing 954 the value of ipMcastRouteTimeStamp." 955 ::= { ipMcastRouteEntry 21 } 957 ipMcastRouteDifferentInIfOctets OBJECT-TYPE 958 SYNTAX Counter32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "The number of octets contained in IP datagrams which this 963 router has received from these sources and addressed to this 964 multicast group address, which were dropped because they 965 were received on an unexpected interface. 967 For RPF checking protocols (such as PIM-SM), these packets 968 arrived on interfaces other than ipMcastRouteInIfIndex, and 969 were dropped because of this failed RPF check. (RPF paths 970 are 'Reverse Path Forwarding' path; the unicast routes to 971 the expected origin of multicast data flows). 973 Other protocols may drop packets on an incoming interface 974 check for different reasons (for example, BIDIR-PIM performs 975 a DF check on receipt of packets). All packets dropped as a 976 result of an incoming interface check are counted here. 978 If this counter increases rapidly, this indicates a problem. 979 A significant quantity of multicast data is arriving at this 980 router on unexpected interfaces, and is not being forwarded. 982 For guidance, if the rate of increase of this counter 983 exceeds 1% of the rate of increase of ipMcastRouteOctets, 984 then there are multicast routing problems that require 985 investigation. 987 Discontinuities in this monotonically increasing value 988 occur at re-initialization of the management system. 989 Discontinuities can also occur as a result of routes being 990 removed and replaced, which can be detected by observing 991 the value of ipMcastRouteTimeStamp." 992 ::= { ipMcastRouteEntry 22 } 994 ipMcastRouteTtlDropPackets OBJECT-TYPE 995 SYNTAX Counter32 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "The number of packets which this router has received from 1000 these sources and addressed to this multicast group address, 1001 which were dropped because the TTL (IPv4) or Hop Limit 1002 (IPv6) was decremented to zero, or to a value less than 1003 ipMcastInterfaceTtl for all next hops. 1005 Discontinuities in this monotonically increasing value 1006 occur at re-initialization of the management system. 1007 Discontinuities can also occur as a result of routes being 1008 removed and replaced, which can be detected by observing 1009 the value of ipMcastRouteTimeStamp." 1010 ::= { ipMcastRouteEntry 23 } 1012 ipMcastRouteTtlDropOctets OBJECT-TYPE 1013 SYNTAX Counter32 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "The number of octets contained in IP datagrams which this 1018 router has received from these sources and addressed to this 1019 multicast group address, which were dropped because the TTL 1020 (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a 1021 value less than ipMcastInterfaceTtl for all next hops. 1023 Discontinuities in this monotonically increasing value 1024 occur at re-initialization of the management system. 1025 Discontinuities can also occur as a result of routes being 1026 removed and replaced, which can be detected by observing 1027 the value of ipMcastRouteTimeStamp." 1028 ::= { ipMcastRouteEntry 24 } 1030 -- 1031 -- The IP Multicast Routing Next Hop Table 1032 -- 1033 ipMcastRouteNextHopTable OBJECT-TYPE 1034 SYNTAX SEQUENCE OF IpMcastRouteNextHopEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "The (conceptual) table containing information on the 1039 next-hops on outgoing interfaces for routing IP multicast 1040 datagrams. Each entry is one of a list of next-hops on 1041 outgoing interfaces for particular sources sending to a 1042 particular multicast group address." 1043 ::= { ipMcast 3 } 1045 ipMcastRouteNextHopEntry OBJECT-TYPE 1046 SYNTAX IpMcastRouteNextHopEntry 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "An entry (conceptual row) in the list of next-hops on 1051 outgoing interfaces to which IP multicast datagrams from 1052 particular sources to an IP multicast group address are 1053 routed." 1054 INDEX { ipMcastRouteNextHopGroupAddressType, 1055 ipMcastRouteNextHopGroup, 1056 ipMcastRouteNextHopSourceAddressType, 1057 ipMcastRouteNextHopSource, 1058 ipMcastRouteNextHopSourcePrefixLength, 1059 ipMcastRouteNextHopIfIndex, 1060 ipMcastRouteNextHopAddressType, 1061 ipMcastRouteNextHopAddress } 1062 ::= { ipMcastRouteNextHopTable 1 } 1064 IpMcastRouteNextHopEntry ::= SEQUENCE { 1065 ipMcastRouteNextHopGroupAddressType InetAddressType, 1066 ipMcastRouteNextHopGroup InetAddress, 1067 ipMcastRouteNextHopSourceAddressType InetAddressType, 1068 ipMcastRouteNextHopSource InetAddress, 1069 ipMcastRouteNextHopSourcePrefixLength InetAddressPrefixLength, 1070 ipMcastRouteNextHopIfIndex InterfaceIndex, 1071 ipMcastRouteNextHopAddressType InetAddressType, 1072 ipMcastRouteNextHopAddress InetAddress, 1073 ipMcastRouteNextHopState INTEGER, 1074 ipMcastRouteNextHopTimeStamp TimeStamp, 1075 ipMcastRouteNextHopExpiryTime TimeTicks, 1076 ipMcastRouteNextHopClosestMemberHops Unsigned32, 1077 ipMcastRouteNextHopProtocol IANAipMRouteProtocol, 1078 ipMcastRouteNextHopPkts Counter32, 1079 ipMcastRouteNextHopOctets Counter32 1080 } 1081 ipMcastRouteNextHopGroupAddressType OBJECT-TYPE 1082 SYNTAX InetAddressType 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "A value indicating the address family of the address 1087 contained in ipMcastRouteNextHopGroup. Legal values 1088 correspond to the subset of address families for which 1089 multicast forwarding is supported." 1090 ::= { ipMcastRouteNextHopEntry 1 } 1092 ipMcastRouteNextHopGroup OBJECT-TYPE 1093 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "The IP multicast group for which this entry specifies a 1098 next-hop on an outgoing interface." 1099 ::= { ipMcastRouteNextHopEntry 2 } 1101 ipMcastRouteNextHopSourceAddressType OBJECT-TYPE 1102 SYNTAX InetAddressType 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "A value indicating the address family of the address 1107 contained in ipMcastRouteNextHopSource. The value MUST be 1108 the same as the value of ipMcastRouteNextHopGroupType." 1109 ::= { ipMcastRouteNextHopEntry 3 } 1111 ipMcastRouteNextHopSource OBJECT-TYPE 1112 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1113 MAX-ACCESS not-accessible 1114 STATUS current 1115 DESCRIPTION 1116 "The network address which, when combined with the 1117 corresponding value of the mask specified in 1118 ipMcastRouteNextHopSourcePrefixLength, identifies the 1119 sources for which this entry specifies a next-hop on an 1120 outgoing interface. 1122 This address object is only significant up to 1123 ipMcastRouteNextHopSourcePrefixLength bits. The remainder 1124 of the address bits are zero. This is especially important 1125 for this index field, which is part of the index of this 1126 entry. Any non-zero bits would signify an entirely 1127 different entry." 1128 ::= { ipMcastRouteNextHopEntry 4 } 1130 ipMcastRouteNextHopSourcePrefixLength OBJECT-TYPE 1131 SYNTAX InetAddressPrefixLength (4..128) 1132 MAX-ACCESS not-accessible 1133 STATUS current 1134 DESCRIPTION 1135 "The length in bits of the mask which, when combined with 1136 the corresponding value specified in 1137 ipMcastRouteNextHopSource, identifies the sources for which 1138 this entry specifies a next-hop on an outgoing interface." 1139 ::= { ipMcastRouteNextHopEntry 5 } 1141 ipMcastRouteNextHopIfIndex OBJECT-TYPE 1142 SYNTAX InterfaceIndex 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "The ifIndex value of the interface for the outgoing 1147 interface for this next-hop." 1148 ::= { ipMcastRouteNextHopEntry 6 } 1150 ipMcastRouteNextHopAddressType OBJECT-TYPE 1151 SYNTAX InetAddressType 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "A value indicating the address family of the address 1156 contained in ipMcastRouteNextHopAddress. The value MUST be 1157 the same as the value of ipMcastRouteNextHopGroupType." 1158 ::= { ipMcastRouteNextHopEntry 7 } 1160 ipMcastRouteNextHopAddress OBJECT-TYPE 1161 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1162 MAX-ACCESS not-accessible 1163 STATUS current 1164 DESCRIPTION 1165 "The address of the next-hop specific to this entry. For 1166 most interfaces, this is identical to 1167 ipMcastRouteNextHopGroup. NBMA interfaces, however, may 1168 have multiple next-hop addresses out a single outgoing 1169 interface." 1170 ::= { ipMcastRouteNextHopEntry 8 } 1172 ipMcastRouteNextHopState OBJECT-TYPE 1173 SYNTAX INTEGER { pruned(1), forwarding(2) } 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "An indication of whether the outgoing interface and next- 1178 hop represented by this entry is currently being used to 1179 forward IP datagrams. The value 'forwarding' indicates it 1180 is currently being used; the value 'pruned' indicates it is 1181 not." 1182 ::= { ipMcastRouteNextHopEntry 9 } 1184 ipMcastRouteNextHopTimeStamp OBJECT-TYPE 1185 SYNTAX TimeStamp 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "The value of sysUpTime at which the multicast routing 1190 information represented by this entry was learned by the 1191 router." 1192 ::= { ipMcastRouteNextHopEntry 10 } 1194 ipMcastRouteNextHopExpiryTime OBJECT-TYPE 1195 SYNTAX TimeTicks 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The minimum amount of time remaining before this entry will 1200 be aged out. If ipMcastRouteNextHopState is pruned(1), the 1201 remaining time until the prune expires and the state reverts 1202 to forwarding(2). Otherwise, the remaining time until this 1203 entry is removed from the table. The time remaining may be 1204 copied from ipMcastRouteExpiryTime if the protocol in use 1205 for this entry does not specify next-hop timers. The value 1206 0 indicates that the entry is not subject to aging." 1207 ::= { ipMcastRouteNextHopEntry 11 } 1209 ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE 1210 SYNTAX Unsigned32 (0..255) 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The minimum number of hops between this router and any 1215 member of this IP multicast group reached via this next-hop 1216 on this outgoing interface. Any IP multicast datagrams for 1217 the group which have a TTL (IPv4) or Hop Count (IPv6) less 1218 than this number of hops will not be forwarded to this 1219 next-hop. 1221 This is an optimization applied by multicast routing 1222 protocols that explicitly track hop counts to downstream 1223 listeners. Multicast protocols that are not aware of hop 1224 counts to downstream listeners set this object to zero." 1225 ::= { ipMcastRouteNextHopEntry 12 } 1227 ipMcastRouteNextHopProtocol OBJECT-TYPE 1228 SYNTAX IANAipMRouteProtocol 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 "The routing mechanism via which this next-hop was learned." 1233 ::= { ipMcastRouteNextHopEntry 13 } 1235 ipMcastRouteNextHopPkts OBJECT-TYPE 1236 SYNTAX Counter32 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "The number of packets which have been forwarded using this 1241 route. 1243 Discontinuities in this monotonically increasing value 1244 occur at re-initialization of the management system. 1245 Discontinuities can also occur as a result of routes being 1246 removed and replaced, which can be detected by observing 1247 the value of ipMcastRouteNextHopTimeStamp." 1248 ::= { ipMcastRouteNextHopEntry 14 } 1250 ipMcastRouteNextHopOctets OBJECT-TYPE 1251 SYNTAX Counter32 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "The number of octets of multicast packets that have been 1256 forwarded using this route. 1258 Discontinuities in this monotonically increasing value 1259 occur at re-initialization of the management system. 1260 Discontinuities can also occur as a result of routes being 1261 removed and replaced, which can be detected by observing 1262 the value of ipMcastRouteNextHopTimeStamp." 1263 ::= { ipMcastRouteNextHopEntry 15 } 1265 -- 1266 -- The IP Multicast Scope Boundary Table 1267 -- 1269 ipMcastBoundaryTable OBJECT-TYPE 1270 SYNTAX SEQUENCE OF IpMcastBoundaryEntry 1271 MAX-ACCESS not-accessible 1272 STATUS current 1273 DESCRIPTION 1274 "The (conceptual) table listing the system's multicast scope 1275 zone boundaries." 1276 REFERENCE "RFC 4007 section 5" 1277 ::= { ipMcast 5 } 1279 ipMcastBoundaryEntry OBJECT-TYPE 1280 SYNTAX IpMcastBoundaryEntry 1281 MAX-ACCESS not-accessible 1282 STATUS current 1283 DESCRIPTION 1284 "An entry (conceptual row) describing one of this device's 1285 multicast scope zone boundaries." 1286 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1287 INDEX { ipMcastBoundaryIfIndex, 1288 ipMcastBoundaryAddressType, 1289 ipMcastBoundaryAddress, 1290 ipMcastBoundaryAddressPrefixLength } 1291 ::= { ipMcastBoundaryTable 1 } 1293 IpMcastBoundaryEntry ::= SEQUENCE { 1294 ipMcastBoundaryIfIndex InterfaceIndex, 1295 ipMcastBoundaryAddressType InetAddressType, 1296 ipMcastBoundaryAddress InetAddress, 1297 ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, 1298 ipMcastBoundaryStatus RowStatus, 1299 ipMcastBoundaryStorageType StorageType, 1300 ipMcastBoundaryDroppedMcastOctets Counter32, 1301 ipMcastBoundaryDroppedMcastPkts Counter32, 1302 ipMcastBoundaryHCDroppedMcastOctets Counter64, 1303 ipMcastBoundaryHCDroppedMcastPkts Counter64 1304 } 1306 ipMcastBoundaryIfIndex OBJECT-TYPE 1307 SYNTAX InterfaceIndex 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "The IfIndex value for the interface to which this boundary 1312 applies. Packets with a destination address in the 1313 associated address/mask range will not be forwarded over 1314 this interface. 1316 For IPv4, zone boundaries cut through links. Therefore this 1317 is an external interface. This may be either a physical or 1318 virtual interface (tunnel, encapsulation, and so forth.) 1320 For IPv6, zone boundaries cut through nodes. Therefore this 1321 is a virtual interface within the node. This is not an 1322 external interface, either real or virtual. Packets 1323 crossing this interface neither arrive at nor leave the 1324 node, but only move between zones within the node." 1325 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1326 ::= { ipMcastBoundaryEntry 1 } 1328 ipMcastBoundaryAddressType OBJECT-TYPE 1329 SYNTAX InetAddressType 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "A value indicating the address family of the address 1334 contained in ipMcastBoundaryAddress. Legal values 1335 correspond to the subset of address families for which 1336 multicast forwarding is supported." 1337 ::= { ipMcastBoundaryEntry 2 } 1339 ipMcastBoundaryAddress OBJECT-TYPE 1340 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1341 MAX-ACCESS not-accessible 1342 STATUS current 1343 DESCRIPTION 1344 "The group address which, when combined with the 1345 corresponding value of ipMcastBoundaryAddressPrefixLength, 1346 identifies the group range for which the scoped boundary 1347 exists. Scoped IPv4 multicast address ranges must be 1348 prefixed by 239.0.0.0/4. Scoped IPv6 multicast address 1349 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1350 scope. 1352 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1353 assigned address. An IPv6 address prefixed by FF3x::/16 is 1354 a unicast-prefix based multicast addresses. A zone boundary 1355 for FF0x::/16 implies an identical boundary for these other 1356 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1357 in this table. 1359 This address object is only significant up to 1360 ipMcastBoundaryAddressPrefixLength bits. The remainder of 1361 the address bits are zero. This is especially important for 1362 this index field, which is part of the index of this entry. 1363 Any non-zero bits would signify an entirely different 1364 entry." 1365 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1366 ::= { ipMcastBoundaryEntry 3 } 1368 ipMcastBoundaryAddressPrefixLength OBJECT-TYPE 1369 SYNTAX InetAddressPrefixLength (4..32) 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "The length in bits of the mask which when, combined with 1374 the corresponding value of ipMcastBoundaryAddress, 1375 identifies the group range for which the scoped boundary 1376 exists. 1378 The InetAddressType is given by ipMcastBoundaryAddressType. 1379 For 'ipv4' this object must be in the range 4..32. For 1380 'ipv6', this object must be 32." 1381 ::= { ipMcastBoundaryEntry 4 } 1383 ipMcastBoundaryStatus OBJECT-TYPE 1384 SYNTAX RowStatus 1385 MAX-ACCESS read-create 1386 STATUS current 1387 DESCRIPTION 1388 "The status of this row, by which rows in this table can 1389 be created and destroyed. 1391 This status object can be set to active(1) without setting 1392 any other columnar objects in this entry. 1394 All writeable objects in this entry can be modified when the 1395 status of this entry is active(1)." 1396 ::= { ipMcastBoundaryEntry 5 } 1398 ipMcastBoundaryStorageType OBJECT-TYPE 1399 SYNTAX StorageType 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "The storage type for this row. Rows having the value 1404 'permanent' need not allow write-access to any columnar 1405 objects in the row." 1406 DEFVAL { nonVolatile } 1407 ::= { ipMcastBoundaryEntry 6 } 1409 ipMcastBoundaryDroppedMcastOctets OBJECT-TYPE 1410 SYNTAX Counter32 1411 MAX-ACCESS read-only 1412 STATUS current 1413 DESCRIPTION 1414 "The number of octets of multicast packets that have been 1415 dropped as a result of this zone boundary configuration." 1416 ::= { ipMcastBoundaryEntry 7 } 1418 ipMcastBoundaryDroppedMcastPkts OBJECT-TYPE 1419 SYNTAX Counter32 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "The number of multicast packets that have been dropped as a 1424 result of this zone boundary configuration." 1425 ::= { ipMcastBoundaryEntry 8 } 1427 ipMcastBoundaryHCDroppedMcastOctets OBJECT-TYPE 1428 SYNTAX Counter64 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "The number of octets of multicast packets that have been 1433 dropped as a result of this zone boundary configuration. 1435 This object is a 64-bit version of 1436 ipMcastBoundaryDroppedMcastOctets." 1437 ::= { ipMcastBoundaryEntry 9 } 1439 ipMcastBoundaryHCDroppedMcastPkts OBJECT-TYPE 1440 SYNTAX Counter64 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "The number of multicast packets that have been dropped as a 1445 result of this zone boundary configuration. 1447 This object is a 64-bit version of 1448 ipMcastBoundaryDroppedMcastPkts." 1449 ::= { ipMcastBoundaryEntry 10 } 1451 -- 1452 -- The IP Multicast Scope Name Table 1453 -- 1455 ipMcastScopeNameTable OBJECT-TYPE 1456 SYNTAX SEQUENCE OF IpMcastScopeNameEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "The (conceptual) table listing multicast scope names." 1461 REFERENCE "RFC 4007 section 4" 1462 ::= { ipMcast 6 } 1464 ipMcastScopeNameEntry OBJECT-TYPE 1465 SYNTAX IpMcastScopeNameEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "An entry (conceptual row) that names a multicast address 1470 scope." 1471 REFERENCE "RFC 4007 section 4" 1472 INDEX { ipMcastScopeNameAddressType, 1473 ipMcastScopeNameAddress, 1474 ipMcastScopeNameAddressPrefixLength, 1475 IMPLIED ipMcastScopeNameLanguage } 1476 ::= { ipMcastScopeNameTable 1 } 1478 IpMcastScopeNameEntry ::= SEQUENCE { 1479 ipMcastScopeNameAddressType InetAddressType, 1480 ipMcastScopeNameAddress InetAddress, 1481 ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, 1482 ipMcastScopeNameLanguage LanguageTag, 1483 ipMcastScopeNameString SnmpAdminString, 1484 ipMcastScopeNameDefault TruthValue, 1485 ipMcastScopeNameStatus RowStatus, 1486 ipMcastScopeNameStorageType StorageType 1487 } 1489 ipMcastScopeNameAddressType OBJECT-TYPE 1490 SYNTAX InetAddressType 1491 MAX-ACCESS not-accessible 1492 STATUS current 1493 DESCRIPTION 1494 "A value indicating the address family of the address 1495 contained in ipMcastScopeNameAddress. Legal values 1496 correspond to the subset of address families for which 1497 multicast forwarding is supported." 1498 ::= { ipMcastScopeNameEntry 1 } 1500 ipMcastScopeNameAddress OBJECT-TYPE 1501 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1502 MAX-ACCESS not-accessible 1503 STATUS current 1504 DESCRIPTION 1505 "The group address which, when combined with the 1506 corresponding value of ipMcastScopeNameAddressPrefixLength, 1507 identifies the group range associated with the multicast 1508 scope. Scoped IPv4 multicast address ranges must be 1509 prefixed by 239.0.0.0/4. Scoped IPv6 multicast address 1510 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1511 scope. 1513 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1514 assigned address. An IPv6 address prefixed by FF3x::/16 is 1515 a unicast-prefix based multicast addresses. A scope 1516 FF0x::/16 implies an identical scope name for these other 1517 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1518 in this table. 1520 This address object is only significant up to 1521 ipMcastScopeNameAddressPrefixLength bits. The remainder of 1522 the address bits are zero. This is especially important for 1523 this index field, which is part of the index of this entry. 1524 Any non-zero bits would signify an entirely different 1525 entry." 1526 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1527 ::= { ipMcastScopeNameEntry 2 } 1529 ipMcastScopeNameAddressPrefixLength OBJECT-TYPE 1530 SYNTAX InetAddressPrefixLength (4..32) 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "The length in bits of the mask which, when combined with 1535 the corresponding value of ipMcastScopeNameAddress, 1536 identifies the group range associated with the multicast 1537 scope. 1539 The InetAddressType is given by ipMcastScopeNameAddressType. 1540 For 'ipv4' this object must be in the range 4..32. For 1541 'ipv6', this object must be 32." 1542 ::= { ipMcastScopeNameEntry 3 } 1544 ipMcastScopeNameLanguage OBJECT-TYPE 1545 SYNTAX LanguageTag 1546 MAX-ACCESS not-accessible 1547 STATUS current 1548 DESCRIPTION 1549 "Language tag associated with the scope name." 1550 REFERENCE "RFC 3283" 1551 ::= { ipMcastScopeNameEntry 4 } 1553 ipMcastScopeNameString OBJECT-TYPE 1554 SYNTAX SnmpAdminString 1555 MAX-ACCESS read-create 1556 STATUS current 1557 DESCRIPTION 1558 "The textual name associated with the multicast scope. The 1559 value of this object should be suitable for displaying to 1560 end-users, such as when allocating a multicast address in 1561 this scope. 1563 When no name is specified, the default value of this object 1564 for IPv4 should is the string 239.x.x.x/y with x and y 1565 replaced with decimal values to describe the address and 1566 mask length associated with the scope. 1568 When no name is specified, the default value of this object 1569 for IPv6 should is the string FF0x::/16, with x replaced by 1570 the hexadecimal value for the RFC 4291 multicast scope. 1572 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1573 assigned address. An IPv6 address prefixed by FF3x::/16 is 1574 a unicast-prefix based multicast addresses. A scope 1575 FF0x::/16 implies an identical scope name for these other 1576 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1577 in this table." 1578 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1579 ::= { ipMcastScopeNameEntry 5 } 1581 ipMcastScopeNameDefault OBJECT-TYPE 1582 SYNTAX TruthValue 1583 MAX-ACCESS read-create 1584 STATUS current 1585 DESCRIPTION 1586 "If true, indicates a preference that the name in the 1587 following language should be used by applications if no name 1588 is available in a desired language." 1589 DEFVAL { false } 1590 ::= { ipMcastScopeNameEntry 6 } 1592 ipMcastScopeNameStatus OBJECT-TYPE 1593 SYNTAX RowStatus 1594 MAX-ACCESS read-create 1595 STATUS current 1596 DESCRIPTION 1597 "The status of this row, by which rows in this table can 1598 be created and destroyed. Before the row can be activated, 1599 the object ipMcastScopeNameString must be set to a valid 1600 value. All writeable objects in this entry can be modified 1601 when the status is active(1)." 1602 ::= { ipMcastScopeNameEntry 7 } 1604 ipMcastScopeNameStorageType OBJECT-TYPE 1605 SYNTAX StorageType 1606 MAX-ACCESS read-create 1607 STATUS current 1608 DESCRIPTION 1609 "The storage type for this row. Rows having the value 1610 'permanent' need not allow write-access to any columnar 1611 objects in the row." 1612 DEFVAL { nonVolatile } 1613 ::= { ipMcastScopeNameEntry 8 } 1615 -- 1616 -- The Multicast Listeners Table 1617 -- 1619 ipMcastLocalListenerTable OBJECT-TYPE 1620 SYNTAX SEQUENCE OF IpMcastLocalListenerEntry 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "The (conceptual) table listing local applications or 1625 services that have joined multicast groups as listeners. 1627 Entries exist for all addresses in the multicast range for 1628 all applications and services as they are classified on this 1629 device." 1630 ::= { ipMcast 9 } 1632 ipMcastLocalListenerEntry OBJECT-TYPE 1633 SYNTAX IpMcastLocalListenerEntry 1634 MAX-ACCESS not-accessible 1635 STATUS current 1636 DESCRIPTION 1637 "An entry (conceptual row) identifying a local application 1638 or service that has joined a multicast group as a listener." 1639 INDEX { ipMcastLocalListenerGroupAddressType, 1640 ipMcastLocalListenerGroupAddress, 1641 ipMcastLocalListenerSourceAddressType, 1642 ipMcastLocalListenerSourceAddress, 1643 ipMcastLocalListenerSourcePrefixLength, 1644 ipMcastLocalListenerRunIndex } 1645 ::= { ipMcastLocalListenerTable 1 } 1647 IpMcastLocalListenerEntry ::= SEQUENCE { 1648 ipMcastLocalListenerGroupAddressType InetAddressType, 1649 ipMcastLocalListenerGroupAddress InetAddress, 1650 ipMcastLocalListenerSourceAddressType InetAddressType, 1651 ipMcastLocalListenerSourceAddress InetAddress, 1652 ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, 1653 ipMcastLocalListenerRunIndex Unsigned32 1654 } 1656 ipMcastLocalListenerGroupAddressType OBJECT-TYPE 1657 SYNTAX InetAddressType 1658 MAX-ACCESS not-accessible 1659 STATUS current 1660 DESCRIPTION 1661 "A value indicating the address family of the address 1662 contained in ipMcastLocalListenerGroupAddress. Legal values 1663 correspond to the subset of address families for which 1664 multicast is supported." 1665 ::= { ipMcastLocalListenerEntry 1 } 1667 ipMcastLocalListenerGroupAddress OBJECT-TYPE 1668 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "The IP multicast group for which this entry specifies 1673 locally joined applications or services." 1674 ::= { ipMcastLocalListenerEntry 2 } 1676 ipMcastLocalListenerSourceAddressType OBJECT-TYPE 1677 SYNTAX InetAddressType 1678 MAX-ACCESS not-accessible 1679 STATUS current 1680 DESCRIPTION 1681 "A value indicating the address family of the address 1682 contained in ipMcastLocalListenerSource. The value MUST be 1683 the same as the value of ipMcastLocalListenerAddressType." 1684 ::= { ipMcastLocalListenerEntry 3 } 1686 ipMcastLocalListenerSourceAddress OBJECT-TYPE 1687 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 "The network address which, when combined with the 1692 corresponding value of the mask specified in 1693 ipMcastLocalListenerSourcePrefixLength, identifies the 1694 sources for which this entry specifies a local listener. 1696 This address object is only significant up to 1697 ipMcastLocalListenerSourcePrefixLength bits. The remainder 1698 of the address bits are zero. This is especially important 1699 for this index field, which is part of the index of this 1700 entry. Any non-zero bits would signify an entirely 1701 different entry." 1702 ::= { ipMcastLocalListenerEntry 4 } 1704 ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE 1705 SYNTAX InetAddressPrefixLength (4..128) 1706 MAX-ACCESS not-accessible 1707 STATUS current 1708 DESCRIPTION 1709 "The length in bits of the mask which, when combined with 1710 the corresponding value specified in 1711 ipMcastLocalListenerSource, identifies the sources for which 1712 this entry specifies a local listener. A mask length of 1713 zero corresponds to all sources within the group." 1714 ::= { ipMcastLocalListenerEntry 5 } 1716 ipMcastLocalListenerRunIndex OBJECT-TYPE 1717 SYNTAX Unsigned32 (0..2147483647) 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "A unique value corresponding to a piece of software running 1722 on this router or host system. Where possible, this should 1723 be the system's native, unique identification number. 1725 This identifier is platform-specific. It may correspond to 1726 a process ID or application instance number. 1728 A value of zero indicates that the application instance(s) 1729 cannot be identified. A value of zero indicates that one or 1730 more unidentified applications have joined the specified 1731 multicast groups (for the specified sources) as listeners." 1732 REFERENCE "RFC 2287 sysApplRunIndex" 1733 ::= { ipMcastLocalListenerEntry 6 } 1735 -- 1736 -- The Multicast Zone Table 1737 -- 1739 ipMcastZoneTable OBJECT-TYPE 1740 SYNTAX SEQUENCE OF IpMcastZoneEntry 1741 MAX-ACCESS not-accessible 1742 STATUS current 1743 DESCRIPTION 1744 "The (conceptual) table listing scope zones on this device." 1745 REFERENCE "RFC 4007 section 5" 1746 ::= { ipMcast 10 } 1748 ipMcastZoneEntry OBJECT-TYPE 1749 SYNTAX IpMcastZoneEntry 1750 MAX-ACCESS not-accessible 1751 STATUS current 1752 DESCRIPTION 1753 "An entry (conceptual row) describing a scope zone on this 1754 device." 1756 REFERENCE "RFC 4007 section 5" 1757 INDEX { ipMcastZoneIndex } 1758 ::= { ipMcastZoneTable 1 } 1760 IpMcastZoneEntry ::= SEQUENCE { 1761 ipMcastZoneIndex InetZoneIndex, 1762 ipMcastZoneScopeDefaultZoneIndex InetZoneIndex, 1763 ipMcastZoneScopeAddressType InetAddressType, 1764 ipMcastZoneScopeAddress InetAddress, 1765 ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength 1766 } 1768 ipMcastZoneIndex OBJECT-TYPE 1769 SYNTAX InetZoneIndex (1..4294967295) 1770 MAX-ACCESS not-accessible 1771 STATUS current 1772 DESCRIPTION 1773 "This zone index uniquely identifies a zone on a device. 1775 Each zone is for a given scope. Scope-level information in 1776 this table is for the unique scope that corresponds to this 1777 zone. 1779 Zero is a special value used to request the default zone for 1780 a given scope. Zero is not a valid value for this object." 1781 ::= { ipMcastZoneEntry 1 } 1783 ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE 1784 SYNTAX InetZoneIndex (1..4294967295) 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "The default zone index for this scope. This is the zone 1789 that this device will use if the default (zero) zone is 1790 requested for this scope. 1792 Zero is not a valid value for this object." 1793 ::= { ipMcastZoneEntry 2 } 1795 ipMcastZoneScopeAddressType OBJECT-TYPE 1796 SYNTAX InetAddressType 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The IP address type for which this scope zone exists." 1801 ::= { ipMcastZoneEntry 3 } 1803 ipMcastZoneScopeAddress OBJECT-TYPE 1804 SYNTAX InetAddress (SIZE (4|16)) 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "The multicast group address which, when combined with 1809 ipMcastZoneScopeAddressPrefixLength, gives the multicast 1810 address range for this scope. The InetAddressType is given 1811 given by ipMcastZoneScopeAddressType. 1813 Scoped IPv4 multicast address ranges are prefixed by 1814 prefixed by 239.0.0.0/4. Scoped IPv6 multicast address 1815 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1816 scope. 1818 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1819 assigned address. An IPv6 address prefixed by FF3x::/16 is 1820 a unicast-prefix based multicast addresses. A scope 1821 FF0x::/16 implies an identical scope for these other 1822 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1823 in this table. 1825 This address object is only significant up to 1826 ipMcastSsmRangePrefixLength bits. The remainder of the 1827 address bits are zero." 1828 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1829 ::= { ipMcastZoneEntry 4 } 1831 ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE 1832 SYNTAX InetAddressPrefixLength (4..32) 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "The length in bits of the mask which, when combined 1837 with ipMcastZoneScopeAddress, gives the multicast address 1838 prefix for this scope. 1840 The InetAddressType is given by ipMcastZoneAddressType. 1841 For 'ipv4' this object must be in the range 4..32. For 1842 'ipv6', this object must be 32." 1843 ::= { ipMcastZoneEntry 5 } 1845 -- 1846 -- Conformance information 1847 -- 1849 ipMcastMIBConformance 1850 OBJECT IDENTIFIER ::= { ipMcastMIB 2 } 1851 ipMcastMIBCompliances 1852 OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } 1853 ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } 1855 -- 1856 -- Compliance statements 1857 -- 1859 ipMcastMIBCompliance MODULE-COMPLIANCE 1860 STATUS current 1861 DESCRIPTION 1862 "Implementations of all the mandatory MIB groups listed 1863 below can claim full compliance. 1865 This MIB contains several InetAddressType and InetAddress 1866 objects, but not all IP address types are supported by all 1867 protocol implementations. 1869 A MIB implementation can claim full compliance if all IP 1870 address types supported by the protocol implementation are 1871 supported by the MIB implementation." 1873 MODULE -- this module 1874 MANDATORY-GROUPS { ipMcastMIBBasicGroup } 1876 OBJECT ipMcastEnable 1877 MIN-ACCESS read-only 1878 DESCRIPTION 1879 "Write access is not required." 1881 GROUP ipMcastMIBRouteGroup 1882 DESCRIPTION 1883 "This group is mandatory if the system is a router." 1885 OBJECT ipMcastInterfaceTtl 1886 MIN-ACCESS read-only 1887 DESCRIPTION 1888 "Write access is not required." 1890 OBJECT ipMcastInterfaceRateLimit 1891 MIN-ACCESS read-only 1892 DESCRIPTION 1893 "Write access is not required." 1895 GROUP ipMcastMIBHopCountGroup 1896 DESCRIPTION 1897 "This group is optional." 1899 GROUP ipMcastMIBPktsOutGroup 1900 DESCRIPTION 1901 "This group is optional." 1903 GROUP ipMcastMIBHCInterfaceGroup 1904 DESCRIPTION 1905 "This group is mandatory only for those network interfaces 1906 for which the value of the corresponding instance of ifSpeed 1907 is greater than 20,000,000 bits/second." 1909 GROUP ipMcastMIBRouteProtoGroup 1910 DESCRIPTION 1911 "This group is mandatory if the system is a router." 1913 GROUP ipMcastMIBSsmGroup 1914 DESCRIPTION 1915 "This group is optional." 1917 GROUP ipMcastMIBLocalListenerGroup 1918 DESCRIPTION 1919 "This group is optional." 1921 GROUP ipMcastMIBBoundaryIfGroup 1922 DESCRIPTION 1923 "This group is mandatory if the system is a router that 1924 supports administratively-scoped multicast address 1925 boundaries." 1927 OBJECT ipMcastBoundaryStatus 1928 MIN-ACCESS read-only 1929 DESCRIPTION 1930 "Write access is not required." 1932 GROUP ipMcastMIBScopeNameGroup 1933 DESCRIPTION 1934 "This group is mandatory if the system is a router that 1935 supports multicast scope names." 1937 OBJECT ipMcastScopeNameString 1938 MIN-ACCESS read-only 1939 DESCRIPTION 1940 "Write access is not required." 1942 OBJECT ipMcastScopeNameDefault 1943 MIN-ACCESS read-only 1944 DESCRIPTION 1945 "Write access is not required." 1947 OBJECT ipMcastScopeNameStatus 1948 MIN-ACCESS read-only 1949 DESCRIPTION 1950 "Write access is not required." 1952 GROUP ipMcastMIBIfPktsGroup 1953 DESCRIPTION 1954 "This group is optional." 1956 GROUP ipMcastMIBRouteOctetsGroup 1957 DESCRIPTION 1958 "This group is optional." 1960 ::= { ipMcastMIBCompliances 1 } 1962 ipMcastMIBMRouteCompliance MODULE-COMPLIANCE 1963 STATUS deprecated 1964 DESCRIPTION 1965 "Implementations of this compliance statement are equivalent 1966 to compliance with the deprecated IPMROUTE-MIB module." 1968 MODULE -- this module 1969 MANDATORY-GROUPS { ipMcastMIBMRouteBasicGroup } 1971 ::= { ipMcastMIBCompliances 2 } 1972 -- 1973 -- Units of conformance 1974 -- 1975 ipMcastMIBMRouteBasicGroup OBJECT-GROUP 1976 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount, 1977 ipMcastRouteUpstreamNeighborType, 1978 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 1979 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 1980 ipMcastRouteNextHopState, 1981 ipMcastRouteNextHopTimeStamp, 1982 ipMcastRouteNextHopExpiryTime, 1983 ipMcastRouteNextHopProtocol, 1984 ipMcastRouteNextHopPkts, 1985 ipMcastInterfaceTtl, 1986 ipMcastInterfaceProtocol, 1987 ipMcastInterfaceRateLimit, 1988 ipMcastInterfaceInMcastOctets, 1989 ipMcastInterfaceOutMcastOctets 1990 } 1991 STATUS deprecated 1992 DESCRIPTION 1993 "A collection of objects to support basic management of IP 1994 Multicast routing. 1996 This conformance group is deprecated. It is replaced by 1997 ipMcastMIBBasicGroup and ipMcastMIBRouteGroup" 1998 ::= { ipMcastMIBGroups 1 } 2000 ipMcastMIBHopCountGroup OBJECT-GROUP 2001 OBJECTS { ipMcastRouteNextHopClosestMemberHops } 2002 STATUS current 2003 DESCRIPTION 2004 "A collection of objects to support management of the use of 2005 hop counts in IP Multicast routing." 2006 ::= { ipMcastMIBGroups 2 } 2008 ipMcastMIBPktsOutGroup OBJECT-GROUP 2009 OBJECTS { ipMcastRouteNextHopPkts } 2010 STATUS current 2011 DESCRIPTION 2012 "A collection of objects to support management of packet 2013 counters for each outgoing interface entry of a route." 2014 ::= { ipMcastMIBGroups 3 } 2016 ipMcastMIBHCInterfaceGroup OBJECT-GROUP 2017 OBJECTS { ipMcastInterfaceHCInMcastOctets, 2018 ipMcastInterfaceHCOutMcastOctets, 2019 ipMcastInterfaceHCInMcastPkts, 2020 ipMcastInterfaceHCOutMcastPkts, 2021 ipMcastRouteHCOctets, 2022 ipMcastBoundaryHCDroppedMcastOctets, 2023 ipMcastBoundaryHCDroppedMcastPkts } 2024 STATUS current 2025 DESCRIPTION 2026 "A collection of objects providing information specific to 2027 high speed (greater than 20,000,000 bits/second) network 2028 interfaces." 2029 ::= { ipMcastMIBGroups 4 } 2031 ipMcastMIBRouteProtoGroup OBJECT-GROUP 2032 OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, 2033 ipMcastRouteRtAddressType, ipMcastRouteRtAddress, 2034 ipMcastRouteRtPrefixLength, ipMcastRouteRtType } 2035 STATUS current 2036 DESCRIPTION 2037 "A collection of objects providing information on the 2038 relationship between multicast routing information and the 2039 IP Forwarding Table." 2040 ::= { ipMcastMIBGroups 5 } 2042 ipMcastMIBBasicGroup OBJECT-GROUP 2043 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount 2044 } 2045 STATUS current 2046 DESCRIPTION 2047 "A collection of objects to support basic management of IP 2048 Multicast protocols." 2049 ::= { ipMcastMIBGroups 6 } 2051 ipMcastMIBRouteGroup OBJECT-GROUP 2052 OBJECTS { ipMcastRouteUpstreamNeighborType, 2053 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 2054 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 2055 ipMcastRoutePkts, 2056 ipMcastRouteDifferentInIfPackets, 2057 ipMcastRouteOctets, 2058 ipMcastRouteNextHopState, ipMcastRouteNextHopTimeStamp, 2059 ipMcastRouteNextHopExpiryTime, 2060 ipMcastRouteNextHopProtocol, 2061 ipMcastRouteNextHopPkts, 2062 ipMcastInterfaceTtl, 2063 ipMcastInterfaceRateLimit, 2064 ipMcastInterfaceInMcastOctets, 2065 ipMcastInterfaceOutMcastOctets, 2066 ipMcastRouteTtlDropPackets, 2067 ipMcastRouteTtlDropOctets 2068 } 2069 STATUS current 2070 DESCRIPTION 2071 "A collection of objects to support basic management of IP 2072 Multicast routing." 2073 ::= { ipMcastMIBGroups 7 } 2075 ipMcastMIBSsmGroup OBJECT-GROUP 2076 OBJECTS { ipMcastSsmRangeRowStatus, ipMcastSsmRangeStorageType } 2077 STATUS current 2078 DESCRIPTION 2079 "A collection of objects to support management of the use of 2080 Source-Specific Multicast routing." 2081 ::= { ipMcastMIBGroups 8 } 2083 ipMcastMIBLocalListenerGroup OBJECT-GROUP 2084 OBJECTS { ipMcastLocalListenerRunIndex } 2085 STATUS current 2086 DESCRIPTION 2087 "A collection of objects to support management of local 2088 listeners on hosts or routers." 2089 ::= { ipMcastMIBGroups 9 } 2091 ipMcastMIBBoundaryIfGroup OBJECT-GROUP 2092 OBJECTS { ipMcastBoundaryStatus, 2093 ipMcastBoundaryStorageType, 2094 ipMcastBoundaryDroppedMcastOctets, 2095 ipMcastBoundaryDroppedMcastPkts, 2096 ipMcastZoneScopeDefaultZoneIndex, 2097 ipMcastZoneScopeAddressType, 2098 ipMcastZoneScopeAddress, 2099 ipMcastZoneScopeAddressPrefixLength 2100 } 2101 STATUS current 2102 DESCRIPTION 2103 "A collection of objects to support management of scoped 2104 multicast address boundaries." 2105 ::= { ipMcastMIBGroups 10 } 2107 ipMcastMIBScopeNameGroup OBJECT-GROUP 2108 OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, 2109 ipMcastScopeNameStatus, ipMcastScopeNameStorageType } 2110 STATUS current 2111 DESCRIPTION 2112 "A collection of objects to support management of multicast 2113 address scope names." 2114 ::= { ipMcastMIBGroups 11 } 2116 ipMcastMIBIfPktsGroup OBJECT-GROUP 2117 OBJECTS { ipMcastInterfaceInMcastPkts, 2118 ipMcastInterfaceOutMcastPkts } 2119 STATUS current 2120 DESCRIPTION 2121 "A collection of objects to support management of packet 2122 counters for each interface entry." 2123 ::= { ipMcastMIBGroups 12 } 2125 ipMcastMIBRouteOctetsGroup OBJECT-GROUP 2126 OBJECTS { ipMcastRouteOctets, ipMcastRouteNextHopOctets, 2127 ipMcastRouteDifferentInIfOctets } 2128 STATUS current 2129 DESCRIPTION 2130 "A collection of objects to support management of octet 2131 counters for each forwarding entry." 2132 ::= { ipMcastMIBGroups 13 } 2134 END 2136 6. Security Considerations 2137 6.1 SNMPv2 2139 SNMP versions prior to SNMPv3 did not include adequate security. 2140 Even if the network itself is secured (for example by using IPSec), 2141 there is still no control over whom on the secure network is allowed 2142 to access (read/change/create/delete) the objects in this MIB module. 2144 It is RECOMMENDED that implementers consider the security features as 2145 provided by the SNMPv3 framework (see [RFC3410], section 8), 2146 including full support for the SNMPv3 cryptographic mechanisms (for 2147 authentication and privacy). 2149 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2150 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2151 enable cryptographic security. It is then a customer/operator 2152 responsibility to ensure that the SNMP entity giving access to an 2153 instance of this MIB module is properly configured to give access to 2154 the objects only to those principals (users) that have legitimate 2155 rights to access (read/change/create/delete) them. 2157 6.2 Writeable objects 2159 There are a number of management objects defined in this MIB module 2160 with a MAX-ACCESS clause of read-write and/or read-create. This 2161 section discusses and lists these elements. 2163 Such objects may be considered sensitive or vulnerable in some 2164 network environments. The support for SET operations in a non-secure 2165 environment without proper protection can have a negative effect on 2166 network operations. 2168 In this MIB module, possible effects that can be induced by SET 2169 operations on writeable objects include: 2171 o Modifications multicast routing behavior that prevent or disrupt 2172 services provided by the network, including (but not limited to) 2173 multicast data traffic delivery. 2175 o Modifications multicast routing behavior that allow interception 2176 or subversion of information that is carried by the network. For 2177 example, attacks can be envisaged that would pass nominated 2178 multicast data streams through a nominated location, without the 2179 sources or listeners becoming aware of this subversion. 2181 The following are the read-write and read-create objects defined in 2182 this MIB module. 2184 ipMcastEnable 2185 ipMcastInterfaceTable 2186 ipMcastInterfaceEntry 2187 ipMcastInterfaceIfIndex 2188 ipMcastInterfaceTtl 2189 ipMcastInterfaceProtocol 2190 ipMcastInterfaceRateLimit 2191 ipMcastSsmRangeTable 2192 ipMcastSsmRangeEntry 2193 ipMcastSsmRangeAddressType 2194 ipMcastSsmRangeAddress 2195 ipMcastSsmRangePrefixLength 2196 ipMcastSsmRangeRowStatus 2197 ipMcastSsmRangeStorageType 2198 ipMcastBoundaryTable 2199 ipMcastBoundaryEntry 2200 ipMcastBoundaryIfIndex 2201 ipMcastBoundaryAddressType 2202 ipMcastBoundaryAddress 2203 ipMcastBoundaryAddressPrefixLength 2204 ipMcastBoundaryStatus 2205 ipMcastBoundaryStorageType 2206 ipMcastScopeNameTable 2207 ipMcastScopeNameEntry 2208 ipMcastScopeNameAddressType 2209 ipMcastScopeNameAddress 2210 ipMcastScopeNameAddressPrefixLength 2211 ipMcastScopeNameLanguage 2212 ipMcastScopeNameString 2213 ipMcastScopeNameDefault 2214 ipMcastScopeNameStatus 2215 ipMcastScopeNameStorageType 2217 6.3 Readable objects 2219 As well as the writeable objects discussed above, there are a number 2220 of readable objects (i.e., objects with a MAX-ACCESS other than not- 2221 accessible) that may be considered sensitive or vulnerable in some 2222 network environments. It is thus important to control even GET 2223 and/or NOTIFY access to these objects and possibly to even encrypt 2224 the values of these objects when sending them over the network via 2225 SNMP. 2227 In this MIB module, possible effects that can be induced by GET 2228 and/or NOTIFY operations include: 2230 o Determination of the topology, disposition, and composition of the 2231 network. This information may be commercially sensitive, and may 2232 also be used in preparation for attacks, including any of the 2233 attacks described above. 2235 o Determinion of whether multicast data is flowing in the network, 2236 or has flowed recently, as well as the locations of senders and 2237 recipients. An attacker can apply 'traffic analysis' to this 2238 data. In some cases, the information revealed by traffic analyses 2239 can be as damaging as full knowledge of the data being 2240 transported. 2242 7. IANA Considerations 2244 IP-MCAST-MIB should be rooted under the mib-2 subtree. IANA is 2245 requested to assign { mib-2 XXX } to the IP-MCAST-MIB module 2246 specified in this document. 2248 8. Acknowledgements 2250 This MIB module is based on the original work in [RFC2932] by K. 2251 McCloghrie, D. Farinacci and D. Thaler. 2253 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 2254 been used for comparison while editing this MIB module. 2256 The authors are also grateful to Bill Fenner for fine ideas, and to 2257 Bharat Joshi for input and several corrections. 2259 9. References 2261 9.1 Normative References 2263 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2264 Requirement Levels", BCP 14, RFC 2119, March 1997. 2266 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 2267 RFC 2365, July 1998. 2269 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2270 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 2271 October 1998. 2273 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2274 Schoenwaelder, Ed., "Structure of Management Information 2275 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2277 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2278 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2279 STD 58, RFC 2579, April 1999. 2281 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2282 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2283 April 1999. 2285 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2286 MIB", RFC 2863, June 2000. 2288 [RFC3283] Mahoney, B., Babics, G., and A. Taler, "Guide to Internet 2289 Calendaring", RFC 3283, June 2002. 2291 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 2292 Multicast Addresses", RFC 3306, August 2002. 2294 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2295 Schoenwaelder, "Textual Conventions for Internet Network 2296 Addresses", RFC 4001, February 2005. 2298 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 2299 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 2300 March 2005. 2302 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2303 Architecture", RFC 4291, February 2006. 2305 9.2 Informative References 2307 [RFC1075] Waitzman, D., Partridge, C., and S. Deering, "Distance 2308 Vector Multicast Routing Protocol", RFC 1075, 2309 November 1988. 2311 [RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, 2312 March 1994. 2314 [RFC2189] Ballardie, T., "Core Based Trees (CBT version 2) Multicast 2315 Routing -- Protocol Specification --", RFC 2189, 2316 September 1997. 2318 [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level 2319 Managed Objects for Applications", RFC 2287, 2320 February 1998. 2322 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 2323 Multicast Routing MIB", RFC 2932, October 2000. 2325 [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, 2326 "Protocol Independent Multicast MIB for IPv4", RFC 2934, 2327 October 2000. 2329 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2330 "Introduction and Applicability Statements for Internet- 2331 Standard Management Framework", RFC 3410, December 2002. 2333 [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific 2334 Multicast (SSM)", RFC 3569, July 2003. 2336 [I-D.ietf-pim-sm-v2-new] 2337 Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2338 "Protocol Independent Multicast - Sparse Mode PIM-SM): 2339 Protocol Specification (Revised)", 2340 draft-ietf-pim-sm-v2-new-12 (work in progress), 2341 March 2006. 2343 [I-D.ietf-pim-bidir] 2344 Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 2345 "Bi-directional Protocol Independent Multicast (BIDIR- 2346 PIM)", draft-ietf-pim-bidir-08 (work in progress), 2347 October 2005. 2349 Authors' Addresses 2351 David McWalter 2352 Data Connection Ltd 2353 100 Church Street 2354 Enfield EN2 6BQ 2355 UK 2357 Email: dmcw@dataconnection.com 2359 Dave Thaler 2360 Microsoft Corporation 2361 One Microsoft Way 2362 Redmond WA 98052-6399 2363 USA 2365 Email: dthaler@windows.microsoft.com 2366 Andrew Kessler 2367 Cisco Systems 2368 425 E. Tasman Drive 2369 San Jose CA 95134 2370 USA 2372 Email: kessler@cisco.com 2374 Intellectual Property Statement 2376 The IETF takes no position regarding the validity or scope of any 2377 Intellectual Property Rights or other rights that might be claimed to 2378 pertain to the implementation or use of the technology described in 2379 this document or the extent to which any license under such rights 2380 might or might not be available; nor does it represent that it has 2381 made any independent effort to identify any such rights. Information 2382 on the procedures with respect to rights in RFC documents can be 2383 found in BCP 78 and BCP 79. 2385 Copies of IPR disclosures made to the IETF Secretariat and any 2386 assurances of licenses to be made available, or the result of an 2387 attempt made to obtain a general license or permission for the use of 2388 such proprietary rights by implementers or users of this 2389 specification can be obtained from the IETF on-line IPR repository at 2390 http://www.ietf.org/ipr. 2392 The IETF invites any interested party to bring to its attention any 2393 copyrights, patents or patent applications, or other proprietary 2394 rights that may cover technology that may be required to implement 2395 this standard. Please address the information to the IETF at 2396 ietf-ipr@ietf.org. 2398 Disclaimer of Validity 2400 This document and the information contained herein are provided on an 2401 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2402 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2403 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2404 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2405 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2406 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2408 Copyright Statement 2410 Copyright (C) The Internet Society (2006). This document is subject 2411 to the rights, licenses and restrictions contained in BCP 78, and 2412 except as set forth therein, the authors retain all their rights. 2414 Acknowledgment 2416 Funding for the RFC Editor function is currently provided by the 2417 Internet Society.