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