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