draft-ietf-mboned-ip-mcast-mib-07.txt   rfc5132.txt 
MBONED WG D. McWalter Network Working Group D. McWalter
Internet-Draft Data Connection Ltd Request for Comments: 5132 Data Connection Ltd
Proposed Status: Standards Track D. Thaler Obsoletes: 2932 D. Thaler
Obsoletes: RFC 2932 (if approved) Microsoft Corporation Category: Standards Track Microsoft Corporation
Expires: March 1, 2008 A. Kessler A. Kessler
Cisco Systems Cisco Systems
August 29, 2007 December 2007
IP Multicast MIB IP Multicast MIB
draft-ietf-mboned-ip-mcast-mib-07.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 1, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007). This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects used for managing multicast In particular, it describes objects used for managing multicast
function, independent of the specific multicast protocol(s) in use. function, independent of the specific multicast protocol(s) in use.
This document obsoletes RFC 2932. This document obsoletes RFC 2932.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. History . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
3. The Internet-Standard Management Framework . . . . . . . . . 3 2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. The Internet-Standard Management Framework . . . . . . . . . . 2
5. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5 5. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . 55 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1 SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54
7.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 55 7.1. SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 56 7.2. Writeable Objects . . . . . . . . . . . . . . . . . . . . 54
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 57 7.3. Readable Objects . . . . . . . . . . . . . . . . . . . . . 55
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 55
10.1 Normative References . . . . . . . . . . . . . . . . . . 57 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.2 Informative References . . . . . . . . . . . . . . . . . 58 10.1. Normative References . . . . . . . . . . . . . . . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 59 10.2. Informative References . . . . . . . . . . . . . . . . . . 57
Intellectual Property and Copyright Statements . . . . . . . 61
1. Introduction 1. Introduction
This MIB describes objects used for managing IP multicast function, This MIB describes objects used for managing IP multicast function,
including IP multicast routing. These objects are independent of the including IP multicast routing. These objects are independent of the
specific multicast routing protocol in use. Managed objects specific specific multicast routing protocol in use. Managed objects specific
to particular multicast protocols are defined elsewhere. to particular multicast protocols are defined elsewhere.
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. History 2. History
This document obsoletes [RFC2932]. The MIB module defined by this This document obsoletes [RFC2932]. The MIB module defined by this
document is a re-working of the MIB module from [RFC2932], with document is a re-working of the MIB module from [RFC2932], with
changes that include the following. changes that include the following:
o This MIB module includes support for IPv6 addressing and the IPv6 o This MIB module includes support for IPv6 addressing and the IPv6
scoped address architecture. [RFC2932] supported only IPv4. scoped address architecture. [RFC2932] supported only IPv4.
o This MIB module allows several multicast protocols to perform o This MIB module allows several multicast protocols to perform
routing on a single interface, where [RFC2932] assumed each routing on a single interface, where [RFC2932] assumed each
interface supported at most one multicast routing protocol. interface supported at most one multicast routing protocol.
Multicast routing protocols are now per-route, see Multicast routing protocols are now per-route, see
ipMcastRouteProtocol. ipMcastRouteProtocol.
skipping to change at page 3, line 41 skipping to change at page 2, line 47
o This MIB module includes a table of Source-Specific Multicast o This MIB module includes a table of Source-Specific Multicast
(SSM) address ranges to which SSM semantics [RFC3569] should be (SSM) address ranges to which SSM semantics [RFC3569] should be
applied. applied.
o This MIB module includes a table of local applications that are o This MIB module includes a table of local applications that are
receiving multicast data. receiving multicast data.
o This MIB module includes a table of multicast scope zones. o This MIB module includes a table of multicast scope zones.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 5, line 5 skipping to change at page 4, line 10
address range that is the corresponding scope. address range that is the corresponding scope.
This MIB module uses textual conventions defined in the IF-MIB This MIB module uses textual conventions defined in the IF-MIB
[RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB.
5. IMPORTed MIB Modules and REFERENCE Clauses 5. IMPORTed MIB Modules and REFERENCE Clauses
The MIB modules defined in this document IMPORTs definitions The MIB modules defined in this document IMPORTs definitions
normatively from the following MIB modules, beyond [RFC2578], normatively from the following MIB modules, beyond [RFC2578],
[RFC2579], and [RFC2580]: HCNUM-TC [RFC2856], IF-MIB [RFC2863], IANA- [RFC2579], and [RFC2580]: HCNUM-TC [RFC2856], IF-MIB [RFC2863], IANA-
RTPROTO-MIB, SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] RTPROTO-MIB, SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB
and LANGTAG-TC-MIB [I-D.mcwalter-langtag-mib]. [RFC4001], and LANGTAG-TC-MIB [RFC5131].
This MIB module also includes REFERENCE clauses that make normative This MIB module also includes REFERENCE clauses that make normative
references to Administratively Scoped IP Multicast [RFC2365], references to Administratively Scoped IP Multicast [RFC2365],
Unicast-Prefix-based IPv6 Multicast Addresses [RFC3306], IPv6 Scoped Unicast-Prefix-based IPv6 Multicast Addresses [RFC3306], IPv6 Scoped
Address Architecture [RFC4007], and IPv6 Addressing Architecture Address Architecture [RFC4007], and IPv6 Addressing Architecture
[RFC4291]. [RFC4291].
Finally, this MIB module makes informative references to several RFCs Finally, this MIB module makes informative references to several RFCs
in text of DESCRIPTION clauses, including sysApplMIB [RFC2287], IP- in the text of DESCRIPTION clauses, including sysApplMIB [RFC2287],
MIB [RFC4293], Source-Specific Multicast [RFC3569], PIM-SMv2 Protocol IP-MIB [RFC4293], Source-Specific Multicast [RFC3569], Protocol
Specification [RFC4601], BIDIR-PIM Protocol Specification [I-D.ietf- Independent Multicast-Sparse Mode version 2 (PIM-SMv2) Protocol
pim-bidir], and Tags for Identifying Languages [RFC4646]. Specification [RFC4601], Bidirectional Protocol Independent Multicast
(BIDIR-PIM) [RFC5015], and Tags for Identifying Languages [RFC4646].
6. Definitions 6. Definitions
IPMCAST-MIB DEFINITIONS ::= BEGIN IPMCAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
mib-2, Unsigned32, Counter64, mib-2, Unsigned32, Counter64,
Gauge32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] Gauge32, TimeTicks FROM SNMPv2-SMI -- [RFC2578]
RowStatus, TruthValue, RowStatus, TruthValue,
skipping to change at page 5, line 40 skipping to change at page 4, line 46
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
CounterBasedGauge64 FROM HCNUM-TC -- [RFC2856] CounterBasedGauge64 FROM HCNUM-TC -- [RFC2856]
InterfaceIndexOrZero, InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB -- [RFC2863] InterfaceIndex FROM IF-MIB -- [RFC2863]
IANAipRouteProtocol, IANAipRouteProtocol,
IANAipMRouteProtocol FROM IANA-RTPROTO-MIB IANAipMRouteProtocol FROM IANA-RTPROTO-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength, InetAddressPrefixLength,
InetZoneIndex, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001] InetZoneIndex, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001]
LangTag FROM LANGTAG-TC-MIB; -- [RFCzzzz] LangTag FROM LANGTAG-TC-MIB; -- [RFC5131]
ipMcastMIB MODULE-IDENTITY ipMcastMIB MODULE-IDENTITY
LAST-UPDATED "200708290000Z" -- 29 August 2007 LAST-UPDATED "200711090000Z" -- 9 November 2007
ORGANIZATION "IETF MBONE Deployment (MBONED) Working Group" ORGANIZATION "IETF MBONE Deployment (MBONED) Working Group"
CONTACT-INFO "David McWalter CONTACT-INFO "David McWalter
Data Connection Limited Data Connection Limited
100 Church Street 100 Church Street
Enfield, EN2 6BQ Enfield, EN2 6BQ
UK UK
Phone: +44 208 366 1177 Phone: +44 208 366 1177
EMail: dmcw@dataconnection.com EMail: dmcw@dataconnection.com
Dave Thaler Dave Thaler
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052-6399 Redmond, WA 98052-6399
US US
Phone: +1 425 703 8835 Phone: +1 425 703 8835
skipping to change at page 6, line 29 skipping to change at page 5, line 33
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408 526 5139 Phone: +1 408 526 5139
EMail: kessler@cisco.com" EMail: kessler@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for management of IP Multicast, including "The MIB module for management of IP Multicast, including
multicast routing, data forwarding, and data reception. multicast routing, data forwarding, and data reception.
Copyright (C) The IETF Trust (2007). This version of this Copyright (C) The IETF Trust (2007). This version of this
MIB module is part of RFC yyyy; see the RFC itself for full MIB module is part of RFC 5132; see the RFC itself for full
legal notices." legal notices."
REVISION "200708290000Z" -- 29 August 2007 REVISION "200711090000Z" -- 9 November 2007
DESCRIPTION "Initial version, published as RFC yyyy. DESCRIPTION "Initial version, published as RFC 5132.
This MIB module obsoletes IPMROUTE-STD-MIB defined by This MIB module obsoletes IPMROUTE-STD-MIB defined by
[RFC2932]. Changes include the following. [RFC2932]. Changes include the following:
o This MIB module includes support for IPv6 addressing o This MIB module includes support for IPv6 addressing
and the IPv6 scoped address architecture. [RFC2932] and the IPv6 scoped address architecture. [RFC2932]
supported only IPv4. supported only IPv4.
o This MIB module allows several multicast protocols o This MIB module allows several multicast protocols
to perform routing on a single interface, where to perform routing on a single interface, where
[RFC2932] assumed each interface supported at most [RFC2932] assumed each interface supported at most
one multicast routing protocol. Multicast routing one multicast routing protocol. Multicast routing
protocols are now per-route, see protocols are now per-route, see
skipping to change at page 7, line 16 skipping to change at page 6, line 20
o This MIB module includes a table of Source-Specific o This MIB module includes a table of Source-Specific
Multicast (SSM) address ranges to which SSM Multicast (SSM) address ranges to which SSM
semantics [RFC3569] should be applied. semantics [RFC3569] should be applied.
o This MIB module includes a table of local o This MIB module includes a table of local
applications that are receiving multicast data. applications that are receiving multicast data.
o This MIB module includes a table of multicast scope o This MIB module includes a table of multicast scope
zones." zones."
::= { mib-2 XXX } ::= { mib-2 168 }
-- --
-- Top-level structure of the MIB -- Top-level structure of the MIB
-- --
ipMcast OBJECT IDENTIFIER ::= { ipMcastMIB 1 } ipMcast OBJECT IDENTIFIER ::= { ipMcastMIB 1 }
ipMcastEnabled OBJECT-TYPE ipMcastEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 9, line 29 skipping to change at page 8, line 29
which this entry is applicable. The interface identified by which this entry is applicable. The interface identified by
a particular value of this index is the same interface as a particular value of this index is the same interface as
identified by the same value of the IF-MIB's ifIndex." identified by the same value of the IF-MIB's ifIndex."
::= { ipMcastInterfaceEntry 2 } ::= { ipMcastInterfaceEntry 2 }
ipMcastInterfaceTtl OBJECT-TYPE ipMcastInterfaceTtl OBJECT-TYPE
SYNTAX Unsigned32 (0..256) SYNTAX Unsigned32 (0..256)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The datagram TTL threshold for the interface. Any IP "The datagram Time to Live (TTL) threshold for the
multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) interface. Any IP multicast datagrams with a TTL (IPv4) or
less than this threshold will not be forwarded out the Hop Limit (IPv6) less than this threshold will not be
interface. The default value of 0 means all multicast forwarded out the interface. The default value of 0 means
packets are forwarded out the interface. A value of 256 all multicast packets are forwarded out the interface. A
means that no multicast packets are forwarded out the value of 256 means that no multicast packets are forwarded
interface." out the interface."
DEFVAL { 0 } DEFVAL { 0 }
::= { ipMcastInterfaceEntry 3 } ::= { ipMcastInterfaceEntry 3 }
ipMcastInterfaceRateLimit OBJECT-TYPE ipMcastInterfaceRateLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The rate-limit, in kilobits per second, of forwarded "The rate-limit, in kilobits per second, of forwarded
multicast traffic on the interface. A rate-limit of 0 multicast traffic on the interface. A rate-limit of 0
skipping to change at page 10, line 34 skipping to change at page 9, line 34
::= { ipMcast 4 } ::= { ipMcast 4 }
ipMcastSsmRangeEntry OBJECT-TYPE ipMcastSsmRangeEntry OBJECT-TYPE
SYNTAX IpMcastSsmRangeEntry SYNTAX IpMcastSsmRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) containing a range of group "An entry (conceptual row) containing a range of group
addresses to which SSM semantics should be applied. addresses to which SSM semantics should be applied.
OIDs are limited to 128 sub-identifiers, but this limit Object Identifiers (OIDs) are limited to 128
is not enforced by the syntax of this entry. In practice sub-identifiers, but this limit is not enforced by the
this does not present a problem, because IP address types syntax of this entry. In practice, this does not present
allowed by conformance statements do not exceed this limit." a problem, because IP address types allowed by conformance
statements do not exceed this limit."
REFERENCE "RFC 3569" REFERENCE "RFC 3569"
INDEX { ipMcastSsmRangeAddressType, INDEX { ipMcastSsmRangeAddressType,
ipMcastSsmRangeAddress, ipMcastSsmRangeAddress,
ipMcastSsmRangePrefixLength } ipMcastSsmRangePrefixLength }
::= { ipMcastSsmRangeTable 1 } ::= { ipMcastSsmRangeTable 1 }
IpMcastSsmRangeEntry ::= SEQUENCE { IpMcastSsmRangeEntry ::= SEQUENCE {
ipMcastSsmRangeAddressType InetAddressType, ipMcastSsmRangeAddressType InetAddressType,
ipMcastSsmRangeAddress InetAddress, ipMcastSsmRangeAddress InetAddress,
ipMcastSsmRangePrefixLength InetAddressPrefixLength, ipMcastSsmRangePrefixLength InetAddressPrefixLength,
skipping to change at page 11, line 24 skipping to change at page 10, line 24
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast group address which, when combined with "The multicast group address which, when combined with
ipMcastSsmRangePrefixLength, gives the group prefix for this ipMcastSsmRangePrefixLength, gives the group prefix for this
SSM range. The InetAddressType is given by SSM range. The InetAddressType is given by
ipMcastSsmRangeAddressType. ipMcastSsmRangeAddressType.
This address object is only significant up to This address object is only significant up to
ipMcastSsmRangePrefixLength bits. The remainder of the ipMcastSsmRangePrefixLength bits. The remaining address
address bits are zero. This is especially important for bits are set to zero. This is especially important for this
this index field, which is part of the index of this entry. index field, which is part of the index of this entry. Any
Any non-zero bits would signify an entirely different non-zero bits would signify an entirely different entry.
entry.
For IPv6 SSM address ranges, only ranges prefixed by For IPv6 SSM address ranges, only ranges prefixed by
FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291 FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291
multicast address scope. The syntax of the address range is multicast address scope. The syntax of the address range is
given by RFC 3306 sections 4 and 7. given by RFC 3306, Sections 4 and 7.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
SSM range entry applies only within the given zone. Zone SSM range entry applies only within the given zone. Zone
index zero is not valid in this table. index zero is not valid in this table.
If non-global scope SSM range entries are present, then If non-global scope SSM range entries are present, then
consistent ipMcastBoundaryTable entries are required on consistent ipMcastBoundaryTable entries are required on
routers at the zone boundary." routers at the zone boundary."
REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 REFERENCE "RFC 2365, RFC 4291 Section 2.7, RFC 3306 Sections 4, 6,
and 7" and 7"
::= { ipMcastSsmRangeEntry 2 } ::= { ipMcastSsmRangeEntry 2 }
ipMcastSsmRangePrefixLength OBJECT-TYPE ipMcastSsmRangePrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when combined with "The length in bits of the mask which, when combined with
ipMcastSsmRangeAddress, gives the group prefix for this SSM ipMcastSsmRangeAddress, gives the group prefix for this SSM
range. range.
The InetAddressType is given by ipMcastSsmRangeAddressType. The InetAddressType is given by ipMcastSsmRangeAddressType.
For values 'ipv4' and 'ipv4z', this object must be in the For values 'ipv4' and 'ipv4z', this object must be in the
range 4..32. For values 'ipv6' and 'ipv6z', this object range 4..32. For values 'ipv6' and 'ipv6z', this object
must be in the range 8..128." must be in the range 8..128."
REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 REFERENCE "RFC 2365, RFC 4291 Section 2.7, RFC 3306 Sections 4, 6,
and 7" and 7"
::= { ipMcastSsmRangeEntry 3 } ::= { ipMcastSsmRangeEntry 3 }
ipMcastSsmRangeRowStatus OBJECT-TYPE ipMcastSsmRangeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which rows in this table can "The status of this row, by which rows in this table can
be created and destroyed. be created and destroyed.
skipping to change at page 13, line 4 skipping to change at page 11, line 51
-- --
-- The IP Multicast Routing Table -- The IP Multicast Routing Table
-- --
ipMcastRouteTable OBJECT-TYPE ipMcastRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMcastRouteEntry SYNTAX SEQUENCE OF IpMcastRouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing multicast routing "The (conceptual) table containing multicast routing
information for IP datagrams sent by particular sources to information for IP datagrams sent by particular sources
to the IP multicast groups known to this router." to the IP multicast groups known to this router."
::= { ipMcast 5 } ::= { ipMcast 5 }
ipMcastRouteEntry OBJECT-TYPE ipMcastRouteEntry OBJECT-TYPE
SYNTAX IpMcastRouteEntry SYNTAX IpMcastRouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) containing the multicast routing "An entry (conceptual row) containing the multicast routing
information for IP datagrams from a particular source and information for IP datagrams from a particular source and
addressed to a particular IP multicast group address. addressed to a particular IP multicast group address.
OIDs are limited to 128 sub-identifiers, but this limit OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit." allowed by conformance statements do not exceed this limit."
INDEX { ipMcastRouteGroupAddressType, INDEX { ipMcastRouteGroupAddressType,
ipMcastRouteGroup, ipMcastRouteGroup,
ipMcastRouteGroupPrefixLength, ipMcastRouteGroupPrefixLength,
ipMcastRouteSourceAddressType, ipMcastRouteSourceAddressType,
ipMcastRouteSource, ipMcastRouteSource,
ipMcastRouteSourcePrefixLength } ipMcastRouteSourcePrefixLength }
::= { ipMcastRouteTable 1 } ::= { ipMcastRouteTable 1 }
skipping to change at page 14, line 30 skipping to change at page 13, line 29
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address which, when combined with "The IP multicast group address which, when combined with
the corresponding value specified in the corresponding value specified in
ipMcastRouteGroupPrefixLength, identifies the groups for ipMcastRouteGroupPrefixLength, identifies the groups for
which this entry contains multicast routing information. which this entry contains multicast routing information.
This address object is only significant up to This address object is only significant up to
ipMcastRouteGroupPrefixLength bits. The remainder of the ipMcastRouteGroupPrefixLength bits. The remaining address
address bits are zero. This is especially important for bits are set to zero. This is especially important for this
this index field, which is part of the index of this entry. index field, which is part of the index of this entry. Any
Any non-zero bits would signify an entirely different non-zero bits would signify an entirely different entry.
entry.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastRouteEntry 2 } ::= { ipMcastRouteEntry 2 }
ipMcastRouteGroupPrefixLength OBJECT-TYPE ipMcastRouteGroupPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
skipping to change at page 15, line 37 skipping to change at page 14, line 35
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address which, when combined with the "The network address which, when combined with the
corresponding value of ipMcastRouteSourcePrefixLength, corresponding value of ipMcastRouteSourcePrefixLength,
identifies the sources for which this entry contains identifies the sources for which this entry contains
multicast routing information. multicast routing information.
This address object is only significant up to This address object is only significant up to
ipMcastRouteSourcePrefixLength bits. The remainder of the ipMcastRouteSourcePrefixLength bits. The remaining address
address bits are zero. This is especially important for bits are set to zero. This is especially important for this
this index field, which is part of the index of this entry. index field, which is part of the index of this entry. Any
Any non-zero bits would signify an entirely different non-zero bits would signify an entirely different entry.
entry.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
source address applies only within the given zone. Zone source address applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastRouteEntry 5 } ::= { ipMcastRouteEntry 5 }
ipMcastRouteSourcePrefixLength OBJECT-TYPE ipMcastRouteSourcePrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
skipping to change at page 16, line 28 skipping to change at page 15, line 26
ipMcastRouteUpstreamNeighborType OBJECT-TYPE ipMcastRouteUpstreamNeighborType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating the address family of the address "A value indicating the address family of the address
contained in ipMcastRouteUpstreamNeighbor. contained in ipMcastRouteUpstreamNeighbor.
An address type of unknown(0) indicates that the upstream An address type of unknown(0) indicates that the upstream
neighbor is unknown, for example in BIDIR-PIM." neighbor is unknown, for example in BIDIR-PIM."
REFERENCE "I-D.ietf-pim-bidir" REFERENCE "RFC 5015"
::= { ipMcastRouteEntry 7 } ::= { ipMcastRouteEntry 7 }
ipMcastRouteUpstreamNeighbor OBJECT-TYPE ipMcastRouteUpstreamNeighbor OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the upstream neighbor (for example, RPF "The address of the upstream neighbor (for example, RPF
neighbor) from which IP datagrams from these sources to neighbor) from which IP datagrams from these sources to
this multicast address are received." this multicast address are received."
skipping to change at page 16, line 51 skipping to change at page 15, line 49
ipMcastRouteInIfIndex OBJECT-TYPE ipMcastRouteInIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex for the interface on which IP "The value of ifIndex for the interface on which IP
datagrams sent by these sources to this multicast address datagrams sent by these sources to this multicast address
are received. A value of 0 indicates that datagrams are not are received. A value of 0 indicates that datagrams are not
subject to an incoming interface check, but may be accepted subject to an incoming interface check, but may be accepted
on multiple interfaces (for example, in BIDIR-PIM)." on multiple interfaces (for example, in BIDIR-PIM)."
REFERENCE "I-D.ietf-pim-bidir" REFERENCE "RFC 5015"
::= { ipMcastRouteEntry 9 } ::= { ipMcastRouteEntry 9 }
ipMcastRouteTimeStamp OBJECT-TYPE ipMcastRouteTimeStamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at which the multicast routing "The value of sysUpTime at which the multicast routing
information represented by this entry was learned by the information represented by this entry was learned by the
router. router.
skipping to change at page 18, line 23 skipping to change at page 17, line 21
ipMcastRouteRtAddress OBJECT-TYPE ipMcastRouteRtAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address portion of the route used to find the upstream "The address portion of the route used to find the upstream
or parent interface for this multicast forwarding entry. or parent interface for this multicast forwarding entry.
This address object is only significant up to This address object is only significant up to
ipMcastRouteRtPrefixLength bits. The remainder of the ipMcastRouteRtPrefixLength bits. The remaining address bits
address bits are zero. are set to zero.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastRouteEntry 15 } ::= { ipMcastRouteEntry 15 }
ipMcastRouteRtPrefixLength OBJECT-TYPE ipMcastRouteRtPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
skipping to change at page 19, line 11 skipping to change at page 18, line 10
unicast (1), -- Unicast route used in multicast RIB unicast (1), -- Unicast route used in multicast RIB
multicast (2) -- Multicast route multicast (2) -- Multicast route
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reason the given route was placed in the (logical) "The reason the given route was placed in the (logical)
multicast Routing Information Base (RIB). A value of multicast Routing Information Base (RIB). A value of
unicast means that the route would normally be placed only unicast means that the route would normally be placed only
in the unicast RIB, but was placed in the multicast RIB in the unicast RIB, but was placed in the multicast RIB
(instead or in addition) due to local configuration, such as due (instead or in addition) to local configuration, such as
when running PIM over RIP. A value of multicast means that when running PIM over RIP. A value of multicast means that
the route was explicitly added to the multicast RIB by the the route was explicitly added to the multicast RIB by the
routing protocol, such as DVMRP or Multiprotocol BGP." routing protocol, such as the Distance Vector Multicast
Routing Protocol (DVMRP) or Multiprotocol BGP."
::= { ipMcastRouteEntry 17 } ::= { ipMcastRouteEntry 17 }
ipMcastRouteOctets OBJECT-TYPE ipMcastRouteOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams which were "The number of octets contained in IP datagrams that were
received from these sources and addressed to this multicast received from these sources and addressed to this multicast
group address, and which were forwarded by this router. group address, and which were forwarded by this router.
Discontinuities in this monotonically increasing value Discontinuities in this monotonically increasing value
occur at re-initialization of the management system. occur at re-initialization of the management system.
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
::= { ipMcastRouteEntry 18 } ::= { ipMcastRouteEntry 18 }
skipping to change at page 20, line 5 skipping to change at page 19, line 5
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
::= { ipMcastRouteEntry 19 } ::= { ipMcastRouteEntry 19 }
ipMcastRouteTtlDropOctets OBJECT-TYPE ipMcastRouteTtlDropOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams which this "The number of octets contained in IP datagrams that this
router has received from these sources and addressed to this router has received from these sources and addressed to this
multicast group address, which were dropped because the TTL multicast group address, which were dropped because the TTL
(IPv4) or Hop Limit (IPv6) was decremented to zero, or to a (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a
value less than ipMcastInterfaceTtl for all next hops. value less than ipMcastInterfaceTtl for all next hops.
Discontinuities in this monotonically increasing value Discontinuities in this monotonically increasing value
occur at re-initialization of the management system. occur at re-initialization of the management system.
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
::= { ipMcastRouteEntry 20 } ::= { ipMcastRouteEntry 20 }
ipMcastRouteTtlDropPackets OBJECT-TYPE ipMcastRouteTtlDropPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which this router has received from "The number of packets that this router has received from
these sources and addressed to this multicast group address, these sources and addressed to this multicast group address,
which were dropped because the TTL (IPv4) or Hop Limit which were dropped because the TTL (IPv4) or Hop Limit
(IPv6) was decremented to zero, or to a value less than (IPv6) was decremented to zero, or to a value less than
ipMcastInterfaceTtl for all next hops. ipMcastInterfaceTtl for all next hops.
Discontinuities in this monotonically increasing value Discontinuities in this monotonically increasing value
occur at re-initialization of the management system. occur at re-initialization of the management system.
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
::= { ipMcastRouteEntry 21 } ::= { ipMcastRouteEntry 21 }
ipMcastRouteDifferentInIfOctets OBJECT-TYPE ipMcastRouteDifferentInIfOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets contained in IP datagrams which this "The number of octets contained in IP datagrams that this
router has received from these sources and addressed to this router has received from these sources and addressed to this
multicast group address, which were dropped because they multicast group address, which were dropped because they
were received on an unexpected interface. were received on an unexpected interface.
For RPF checking protocols (such as PIM-SM), these packets For RPF checking protocols (such as PIM-SM), these packets
arrived on interfaces other than ipMcastRouteInIfIndex, and arrived on interfaces other than ipMcastRouteInIfIndex, and
were dropped because of this failed RPF check. (RPF paths were dropped because of this failed RPF check. (RPF paths
are 'Reverse Path Forwarding' path; the unicast routes to are 'Reverse Path Forwarding' paths; the unicast routes to
the expected origin of multicast data flows). the expected origin of multicast data flows).
Other protocols may drop packets on an incoming interface Other protocols may drop packets on an incoming interface
check for different reasons (for example, BIDIR-PIM performs check for different reasons (for example, BIDIR-PIM performs
a DF check on receipt of packets). All packets dropped as a a DF check on receipt of packets). All packets dropped as a
result of an incoming interface check are counted here. result of an incoming interface check are counted here.
If this counter increases rapidly, this indicates a problem. If this counter increases rapidly, this indicates a problem.
A significant quantity of multicast data is arriving at this A significant quantity of multicast data is arriving at this
router on unexpected interfaces, and is not being forwarded. router on unexpected interfaces, and is not being forwarded.
skipping to change at page 21, line 24 skipping to change at page 20, line 24
For guidance, if the rate of increase of this counter For guidance, if the rate of increase of this counter
exceeds 1% of the rate of increase of ipMcastRouteOctets, exceeds 1% of the rate of increase of ipMcastRouteOctets,
then there are multicast routing problems that require then there are multicast routing problems that require
investigation. investigation.
Discontinuities in this monotonically increasing value Discontinuities in this monotonically increasing value
occur at re-initialization of the management system. occur at re-initialization of the management system.
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" REFERENCE "RFC 4601 and RFC 5015"
::= { ipMcastRouteEntry 22 } ::= { ipMcastRouteEntry 22 }
ipMcastRouteDifferentInIfPackets OBJECT-TYPE ipMcastRouteDifferentInIfPackets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which this router has received from "The number of packets which this router has received from
these sources and addressed to this multicast group address, these sources and addressed to this multicast group address,
which were dropped because they were received on an which were dropped because they were received on an
skipping to change at page 22, line 13 skipping to change at page 21, line 13
For guidance, if the rate of increase of this counter For guidance, if the rate of increase of this counter
exceeds 1% of the rate of increase of ipMcastRoutePkts, then exceeds 1% of the rate of increase of ipMcastRoutePkts, then
there are multicast routing problems that require there are multicast routing problems that require
investigation. investigation.
Discontinuities in this monotonically increasing value Discontinuities in this monotonically increasing value
occur at re-initialization of the management system. occur at re-initialization of the management system.
Discontinuities can also occur as a result of routes being Discontinuities can also occur as a result of routes being
removed and replaced, which can be detected by observing removed and replaced, which can be detected by observing
the value of ipMcastRouteTimeStamp." the value of ipMcastRouteTimeStamp."
REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" REFERENCE "RFC 4601 and RFC 5015"
::= { ipMcastRouteEntry 23 } ::= { ipMcastRouteEntry 23 }
ipMcastRouteBps OBJECT-TYPE ipMcastRouteBps OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
UNITS "bits per second" UNITS "bits per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bits per second forwarded by this router using this "Bits per second forwarded by this router using this
multicast routing entry. multicast routing entry.
skipping to change at page 23, line 13 skipping to change at page 22, line 13
SYNTAX IpMcastRouteNextHopEntry SYNTAX IpMcastRouteNextHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the list of next-hops on "An entry (conceptual row) in the list of next-hops on
outgoing interfaces to which IP multicast datagrams from outgoing interfaces to which IP multicast datagrams from
particular sources to an IP multicast group address are particular sources to an IP multicast group address are
routed. routed.
OIDs are limited to 128 sub-identifiers, but this limit OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit." allowed by conformance statements do not exceed this limit."
INDEX { ipMcastRouteNextHopGroupAddressType, INDEX { ipMcastRouteNextHopGroupAddressType,
ipMcastRouteNextHopGroup, ipMcastRouteNextHopGroup,
ipMcastRouteNextHopGroupPrefixLength, ipMcastRouteNextHopGroupPrefixLength,
ipMcastRouteNextHopSourceAddressType, ipMcastRouteNextHopSourceAddressType,
ipMcastRouteNextHopSource, ipMcastRouteNextHopSource,
ipMcastRouteNextHopSourcePrefixLength, ipMcastRouteNextHopSourcePrefixLength,
ipMcastRouteNextHopIfIndex, ipMcastRouteNextHopIfIndex,
ipMcastRouteNextHopAddressType, ipMcastRouteNextHopAddressType,
skipping to change at page 24, line 21 skipping to change at page 23, line 21
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address which, when combined with "The IP multicast group address which, when combined with
the corresponding value specified in the corresponding value specified in
ipMcastRouteNextHopGroupPrefixLength, identifies the groups ipMcastRouteNextHopGroupPrefixLength, identifies the groups
for which this entry contains multicast forwarding for which this entry contains multicast forwarding
information. information.
This address object is only significant up to This address object is only significant up to
ipMcastRouteNextHopGroupPrefixLength bits. The remainder of ipMcastRouteNextHopGroupPrefixLength bits. The remaining
the address bits are zero. This is especially important for address bits are set to zero. This is especially important
this index field, which is part of the index of this entry. for this index field, which is part of the index of this
Any non-zero bits would signify an entirely different entry. Any non-zero bits would signify an entirely
entry. different entry.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
forwarding state applies only within the given zone. Zone forwarding state applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastRouteNextHopEntry 2 } ::= { ipMcastRouteNextHopEntry 2 }
ipMcastRouteNextHopGroupPrefixLength OBJECT-TYPE ipMcastRouteNextHopGroupPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
skipping to change at page 25, line 29 skipping to change at page 24, line 29
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address which, when combined with the "The network address which, when combined with the
corresponding value of the mask specified in corresponding value of the mask specified in
ipMcastRouteNextHopSourcePrefixLength, identifies the ipMcastRouteNextHopSourcePrefixLength, identifies the
sources for which this entry specifies a next-hop on an sources for which this entry specifies a next-hop on an
outgoing interface. outgoing interface.
This address object is only significant up to This address object is only significant up to
ipMcastRouteNextHopSourcePrefixLength bits. The remainder ipMcastRouteNextHopSourcePrefixLength bits. The remaining
of the address bits are zero. This is especially important address bits are set to zero. This is especially important
for this index field, which is part of the index of this for this index field, which is part of the index of this
entry. Any non-zero bits would signify an entirely entry. Any non-zero bits would signify an entirely
different entry. different entry.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
source address applies only within the given zone. Zone source address applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastRouteNextHopEntry 5 } ::= { ipMcastRouteNextHopEntry 5 }
skipping to change at page 26, line 38 skipping to change at page 25, line 38
contained in ipMcastRouteNextHopAddress." contained in ipMcastRouteNextHopAddress."
::= { ipMcastRouteNextHopEntry 8 } ::= { ipMcastRouteNextHopEntry 8 }
ipMcastRouteNextHopAddress OBJECT-TYPE ipMcastRouteNextHopAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the next-hop specific to this entry. For "The address of the next-hop specific to this entry. For
most interfaces, this is identical to most interfaces, this is identical to
ipMcastRouteNextHopGroup. NBMA interfaces, however, may ipMcastRouteNextHopGroup. Non-Broadcast Multi-Access
(NBMA) interfaces, however, may
have multiple next-hop addresses out a single outgoing have multiple next-hop addresses out a single outgoing
interface." interface."
::= { ipMcastRouteNextHopEntry 9 } ::= { ipMcastRouteNextHopEntry 9 }
ipMcastRouteNextHopState OBJECT-TYPE ipMcastRouteNextHopState OBJECT-TYPE
SYNTAX INTEGER { pruned(1), forwarding(2) } SYNTAX INTEGER { pruned(1), forwarding(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether the outgoing interface and next- "An indication of whether the outgoing interface and next-
skipping to change at page 27, line 43 skipping to change at page 26, line 44
::= { ipMcastRouteNextHopEntry 12 } ::= { ipMcastRouteNextHopEntry 12 }
ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE
SYNTAX Unsigned32 (0..256) SYNTAX Unsigned32 (0..256)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum number of hops between this router and any "The minimum number of hops between this router and any
member of this IP multicast group reached via this next-hop member of this IP multicast group reached via this next-hop
on this outgoing interface. Any IP multicast datagrams for on this outgoing interface. Any IP multicast datagrams for
the group which have a TTL (IPv4) or Hop Count (IPv6) less the group that have a TTL (IPv4) or Hop Count (IPv6) less
than this number of hops will not be forwarded to this than this number of hops will not be forwarded to this
next-hop. next-hop.
A value of 0 means all multicast datagrams are forwarded out A value of 0 means all multicast datagrams are forwarded out
the interface. A value of 256 means that no multicast the interface. A value of 256 means that no multicast
datagrams are forwarded out the interface. datagrams are forwarded out the interface.
This is an optimization applied by multicast routing This is an optimization applied by multicast routing
protocols that explicitly track hop counts to downstream protocols that explicitly track hop counts to downstream
listeners. Multicast protocols that are not aware of hop listeners. Multicast protocols that are not aware of hop
skipping to change at page 29, line 10 skipping to change at page 28, line 12
-- The IP Multicast Scope Boundary Table -- The IP Multicast Scope Boundary Table
-- --
ipMcastBoundaryTable OBJECT-TYPE ipMcastBoundaryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMcastBoundaryEntry SYNTAX SEQUENCE OF IpMcastBoundaryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the system's multicast scope "The (conceptual) table listing the system's multicast scope
zone boundaries." zone boundaries."
REFERENCE "RFC 4007 section 5" REFERENCE "RFC 4007 Section 5"
::= { ipMcast 7 } ::= { ipMcast 7 }
ipMcastBoundaryEntry OBJECT-TYPE ipMcastBoundaryEntry OBJECT-TYPE
SYNTAX IpMcastBoundaryEntry SYNTAX IpMcastBoundaryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) describing one of this device's "An entry (conceptual row) describing one of this device's
multicast scope zone boundaries. multicast scope zone boundaries.
OIDs are limited to 128 sub-identifiers, but this limit OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit." allowed by conformance statements do not exceed this limit."
REFERENCE "RFC 2365 section 5, RFC 4007 section 5" REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5"
INDEX { ipMcastBoundaryIfIndex, INDEX { ipMcastBoundaryIfIndex,
ipMcastBoundaryAddressType, ipMcastBoundaryAddressType,
ipMcastBoundaryAddress, ipMcastBoundaryAddress,
ipMcastBoundaryAddressPrefixLength } ipMcastBoundaryAddressPrefixLength }
::= { ipMcastBoundaryTable 1 } ::= { ipMcastBoundaryTable 1 }
IpMcastBoundaryEntry ::= SEQUENCE { IpMcastBoundaryEntry ::= SEQUENCE {
ipMcastBoundaryIfIndex InterfaceIndex, ipMcastBoundaryIfIndex InterfaceIndex,
ipMcastBoundaryAddressType InetAddressType, ipMcastBoundaryAddressType InetAddressType,
ipMcastBoundaryAddress InetAddress, ipMcastBoundaryAddress InetAddress,
skipping to change at page 30, line 6 skipping to change at page 29, line 7
ipMcastBoundaryIfIndex OBJECT-TYPE ipMcastBoundaryIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IfIndex value for the interface to which this boundary "The IfIndex value for the interface to which this boundary
applies. Packets with a destination address in the applies. Packets with a destination address in the
associated address/mask range will not be forwarded over associated address/mask range will not be forwarded over
this interface. this interface.
For IPv4, zone boundaries cut through links. Therefore this For IPv4, zone boundaries cut through links. Therefore,
is an external interface. This may be either a physical or this is an external interface. This may be either a
virtual interface (tunnel, encapsulation, and so forth.) physical or virtual interface (tunnel, encapsulation, and
so forth.)
For IPv6, zone boundaries cut through nodes. Therefore this For IPv6, zone boundaries cut through nodes. Therefore,
is a virtual interface within the node. This is not an this is a virtual interface within the node. This is not
external interface, either real or virtual. Packets an external interface, either real or virtual. Packets
crossing this interface neither arrive at nor leave the crossing this interface neither arrive at nor leave the
node, but only move between zones within the node." node, but only move between zones within the node."
REFERENCE "RFC 2365 section 5, RFC 4007 section 5" REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5"
::= { ipMcastBoundaryEntry 1 } ::= { ipMcastBoundaryEntry 1 }
ipMcastBoundaryAddressType OBJECT-TYPE ipMcastBoundaryAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating the address family of the address "A value indicating the address family of the address
contained in ipMcastBoundaryAddress. Legal values contained in ipMcastBoundaryAddress. Legal values
correspond to the subset of address families for which correspond to the subset of address families for which
skipping to change at page 30, line 50 skipping to change at page 30, line 4
scope. scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix-based multicast addresses. A zone boundary a unicast-prefix-based multicast addresses. A zone boundary
for FF0x::/16 implies an identical boundary for these other for FF0x::/16 implies an identical boundary for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastBoundaryAddressPrefixLength bits. The remainder of ipMcastBoundaryAddressPrefixLength bits. The remaining
the address bits are zero. This is especially important for address bits are set to zero. This is especially important
this index field, which is part of the index of this entry. for this index field, which is part of the index of this
Any non-zero bits would signify an entirely different entry. Any non-zero bits would signify an entirely
entry." different entry."
::= { ipMcastBoundaryEntry 3 } ::= { ipMcastBoundaryEntry 3 }
ipMcastBoundaryAddressPrefixLength OBJECT-TYPE ipMcastBoundaryAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which when, combined with "The length in bits of the mask which when, combined with
the corresponding value of ipMcastBoundaryAddress, the corresponding value of ipMcastBoundaryAddress,
identifies the group range for which the scoped boundary identifies the group range for which the scoped boundary
skipping to change at page 32, line 50 skipping to change at page 32, line 4
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this row. Rows having the value "The storage type for this row. Rows having the value
'permanent' need not allow write-access to any columnar 'permanent' need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { ipMcastBoundaryEntry 9 } ::= { ipMcastBoundaryEntry 9 }
-- --
-- The IP Multicast Scope Name Table -- The IP Multicast Scope Name Table
-- --
ipMcastScopeNameTable OBJECT-TYPE ipMcastScopeNameTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMcastScopeNameEntry SYNTAX SEQUENCE OF IpMcastScopeNameEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing multicast scope names." "The (conceptual) table listing multicast scope names."
REFERENCE "RFC 4007 section 4" REFERENCE "RFC 4007 Section 4"
::= { ipMcast 8 } ::= { ipMcast 8 }
ipMcastScopeNameEntry OBJECT-TYPE ipMcastScopeNameEntry OBJECT-TYPE
SYNTAX IpMcastScopeNameEntry SYNTAX IpMcastScopeNameEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) that names a multicast address "An entry (conceptual row) that names a multicast address
scope. scope.
OIDs are limited to 128 sub-identifiers, but this limit OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit." allowed by conformance statements do not exceed this limit."
REFERENCE "RFC 4007 section 4" REFERENCE "RFC 4007 Section 4"
INDEX { ipMcastScopeNameAddressType, INDEX { ipMcastScopeNameAddressType,
ipMcastScopeNameAddress, ipMcastScopeNameAddress,
ipMcastScopeNameAddressPrefixLength, ipMcastScopeNameAddressPrefixLength,
ipMcastScopeNameLanguage } ipMcastScopeNameLanguage }
::= { ipMcastScopeNameTable 1 } ::= { ipMcastScopeNameTable 1 }
IpMcastScopeNameEntry ::= SEQUENCE { IpMcastScopeNameEntry ::= SEQUENCE {
ipMcastScopeNameAddressType InetAddressType, ipMcastScopeNameAddressType InetAddressType,
ipMcastScopeNameAddress InetAddress, ipMcastScopeNameAddress InetAddress,
ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength,
skipping to change at page 34, line 27 skipping to change at page 33, line 30
scope. scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix-based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope name for these other FF0x::/16 implies an identical scope name for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastScopeNameAddressPrefixLength bits. The remainder of ipMcastScopeNameAddressPrefixLength bits. The remaining
the address bits are zero. This is especially important for address bits are set to zero. This is especially important
this index field, which is part of the index of this entry. for this index field, which is part of the index of this
Any non-zero bits would signify an entirely different entry. Any non-zero bits would signify an entirely
entry." different entry."
::= { ipMcastScopeNameEntry 2 } ::= { ipMcastScopeNameEntry 2 }
ipMcastScopeNameAddressPrefixLength OBJECT-TYPE ipMcastScopeNameAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when combined with "The length in bits of the mask which, when combined with
the corresponding value of ipMcastScopeNameAddress, the corresponding value of ipMcastScopeNameAddress,
identifies the group range associated with the multicast identifies the group range associated with the multicast
skipping to change at page 35, line 22 skipping to change at page 34, line 25
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name associated with the multicast scope. The "The textual name associated with the multicast scope. The
value of this object should be suitable for displaying to value of this object should be suitable for displaying to
end-users, such as when allocating a multicast address in end-users, such as when allocating a multicast address in
this scope. this scope.
When no name is specified, the default value of this object When no name is specified, the default value of this object
for IPv4 should is the string 239.x.x.x/y with x and y for IPv4 should be the string 239.x.x.x/y with x and y
replaced with decimal values to describe the address and replaced with decimal values to describe the address and
mask length associated with the scope. mask length associated with the scope.
When no name is specified, the default value of this object When no name is specified, the default value of this object
for IPv6 should is the string FF0x::/16, with x replaced by for IPv6 should be the string FF0x::/16, with x replaced by
the hexadecimal value for the RFC 4291 multicast scope. the hexadecimal value for the RFC 4291 multicast scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix-based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope name for these other FF0x::/16 implies an identical scope name for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table." in this table."
REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" REFERENCE "RFC 2365, RFC 3306 Section 4, RFC 4291 Section 2.7"
::= { ipMcastScopeNameEntry 5 } ::= { ipMcastScopeNameEntry 5 }
ipMcastScopeNameDefault OBJECT-TYPE ipMcastScopeNameDefault OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, indicates a preference that the name in the "If true, indicates a preference that the name in the
following language should be used by applications if no name following language should be used by applications if no name
is available in a desired language." is available in a desired language."
skipping to change at page 36, line 51 skipping to change at page 36, line 6
ipMcastLocalListenerEntry OBJECT-TYPE ipMcastLocalListenerEntry OBJECT-TYPE
SYNTAX IpMcastLocalListenerEntry SYNTAX IpMcastLocalListenerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) identifying a local application "An entry (conceptual row) identifying a local application
or service that has joined a multicast group as a listener. or service that has joined a multicast group as a listener.
OIDs are limited to 128 sub-identifiers, but this limit OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit." allowed by conformance statements do not exceed this limit."
INDEX { ipMcastLocalListenerGroupAddressType, INDEX { ipMcastLocalListenerGroupAddressType,
ipMcastLocalListenerGroupAddress, ipMcastLocalListenerGroupAddress,
ipMcastLocalListenerSourceAddressType, ipMcastLocalListenerSourceAddressType,
ipMcastLocalListenerSourceAddress, ipMcastLocalListenerSourceAddress,
ipMcastLocalListenerSourcePrefixLength, ipMcastLocalListenerSourcePrefixLength,
ipMcastLocalListenerIfIndex, ipMcastLocalListenerIfIndex,
ipMcastLocalListenerRunIndex } ipMcastLocalListenerRunIndex }
::= { ipMcastLocalListenerTable 1 } ::= { ipMcastLocalListenerTable 1 }
skipping to change at page 38, line 22 skipping to change at page 37, line 24
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address which, when combined with the "The network address which, when combined with the
corresponding value of the mask specified in corresponding value of the mask specified in
ipMcastLocalListenerSourcePrefixLength, identifies the ipMcastLocalListenerSourcePrefixLength, identifies the
sources for which this entry specifies a local listener. sources for which this entry specifies a local listener.
This address object is only significant up to This address object is only significant up to
ipMcastLocalListenerSourcePrefixLength bits. The remainder ipMcastLocalListenerSourcePrefixLength bits. The remaining
of the address bits are zero. This is especially important address bits are set to zero. This is especially important
for this index field, which is part of the index of this for this index field, which is part of the index of this
entry. Any non-zero bits would signify an entirely entry. Any non-zero bits would signify an entirely
different entry. different entry.
For addresses of type ipv4z or ipv6z, the appended zone For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this length. The use of these address types indicate that this
listener address applies only within the given zone. Zone listener address applies only within the given zone. Zone
index zero is not valid in this table." index zero is not valid in this table."
::= { ipMcastLocalListenerEntry 4 } ::= { ipMcastLocalListenerEntry 4 }
skipping to change at page 39, line 43 skipping to change at page 38, line 45
-- --
-- The Multicast Zone Table -- The Multicast Zone Table
-- --
ipMcastZoneTable OBJECT-TYPE ipMcastZoneTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMcastZoneEntry SYNTAX SEQUENCE OF IpMcastZoneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing scope zones on this device." "The (conceptual) table listing scope zones on this device."
REFERENCE "RFC 4007 section 5" REFERENCE "RFC 4007 Section 5"
::= { ipMcast 10 } ::= { ipMcast 10 }
ipMcastZoneEntry OBJECT-TYPE ipMcastZoneEntry OBJECT-TYPE
SYNTAX IpMcastZoneEntry SYNTAX IpMcastZoneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) describing a scope zone on this "An entry (conceptual row) describing a scope zone on this
device." device."
REFERENCE "RFC 4007 section 5" REFERENCE "RFC 4007 Section 5"
INDEX { ipMcastZoneIndex } INDEX { ipMcastZoneIndex }
::= { ipMcastZoneTable 1 } ::= { ipMcastZoneTable 1 }
IpMcastZoneEntry ::= SEQUENCE { IpMcastZoneEntry ::= SEQUENCE {
ipMcastZoneIndex InetZoneIndex, ipMcastZoneIndex InetZoneIndex,
ipMcastZoneScopeDefaultZoneIndex InetZoneIndex, ipMcastZoneScopeDefaultZoneIndex InetZoneIndex,
ipMcastZoneScopeAddressType InetAddressType, ipMcastZoneScopeAddressType InetAddressType,
ipMcastZoneScopeAddress InetAddress, ipMcastZoneScopeAddress InetAddress,
ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength
} }
skipping to change at page 41, line 29 skipping to change at page 40, line 32
FF0x::/16, where x is a valid RFC 4291 multicast scope. FF0x::/16, where x is a valid RFC 4291 multicast scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix-based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope for these other FF0x::/16 implies an identical scope for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastZoneScopeAddressPrefixLength bits. The remainder of ipMcastZoneScopeAddressPrefixLength bits. The remaining
the address bits are zero." address bits are set to zero."
REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" REFERENCE "RFC 2365, RFC 3306 Section 4, RFC 4291 Section 2.7"
::= { ipMcastZoneEntry 4 } ::= { ipMcastZoneEntry 4 }
ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when combined "The length in bits of the mask which, when combined
with ipMcastZoneScopeAddress, gives the multicast address with ipMcastZoneScopeAddress, gives the multicast address
prefix for this scope. prefix for this scope.
skipping to change at page 46, line 11 skipping to change at page 45, line 15
"Write access is not required." "Write access is not required."
OBJECT ipMcastInterfaceStorageType OBJECT ipMcastInterfaceStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT ipMcastRouteUpstreamNeighborType OBJECT ipMcastRouteUpstreamNeighborType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
ipv4z(3), ipv6z(4) } ipv4z(3), ipv6z(4) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
or ipv6." or ipv6."
OBJECT ipMcastRouteUpstreamNeighbor OBJECT ipMcastRouteUpstreamNeighbor
SYNTAX InetAddress (SIZE (0|4|8|16|20)) SYNTAX InetAddress (SIZE (0|4|8|16|20))
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
or ipv6." or ipv6."
OBJECT ipMcastRouteRtAddressType OBJECT ipMcastRouteRtAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
ipv4z(3), ipv6z(4) } ipv4z(3), ipv6z(4) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
or ipv6." or ipv6."
OBJECT ipMcastRouteRtAddress OBJECT ipMcastRouteRtAddress
SYNTAX InetAddress (SIZE (0|4|8|16|20)) SYNTAX InetAddress (SIZE (0|4|8|16|20))
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
or ipv6." or ipv6."
OBJECT ipMcastSsmRangeRowStatus OBJECT ipMcastSsmRangeRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT ipMcastSsmRangeStorageType OBJECT ipMcastSsmRangeStorageType
skipping to change at page 50, line 32 skipping to change at page 49, line 32
"Write access is not required." "Write access is not required."
OBJECT ipMcastInterfaceStorageType OBJECT ipMcastInterfaceStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT ipMcastRouteUpstreamNeighborType OBJECT ipMcastRouteUpstreamNeighborType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
ipv4z(3), ipv6z(4) } ipv4z(3), ipv6z(4) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
and ipv4z, or ipv6 and ipv6z." and ipv4z, or ipv6 and ipv6z."
OBJECT ipMcastRouteUpstreamNeighbor OBJECT ipMcastRouteUpstreamNeighbor
SYNTAX InetAddress (SIZE (0|4|8|16|20)) SYNTAX InetAddress (SIZE (0|4|8|16|20))
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
and ipv4z, or ipv6 and ipv6z." and ipv4z, or ipv6 and ipv6z."
OBJECT ipMcastRouteRtAddressType OBJECT ipMcastRouteRtAddressType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
ipv4z(3), ipv6z(4) } ipv4z(3), ipv6z(4) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
and ipv4z, or ipv6 and ipv6z." and ipv4z, or ipv6 and ipv6z."
OBJECT ipMcastRouteRtAddress OBJECT ipMcastRouteRtAddress
SYNTAX InetAddress (SIZE (0|4|8|16|20)) SYNTAX InetAddress (SIZE (0|4|8|16|20))
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for unknown and either ipv4 "This compliance requires support for unknown and either ipv4
and ipv4z, or ipv6 and ipv6z." and ipv4z, or ipv6 and ipv6z."
OBJECT ipMcastSsmRangeRowStatus OBJECT ipMcastSsmRangeRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT ipMcastSsmRangeStorageType OBJECT ipMcastSsmRangeStorageType
skipping to change at page 51, line 48 skipping to change at page 50, line 44
GROUP ipMcastMIBRouteBpsGroup GROUP ipMcastMIBRouteBpsGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
GROUP ipMcastMIBLocalListenerGroup GROUP ipMcastMIBLocalListenerGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
OBJECT ipMcastZoneScopeAddressType OBJECT ipMcastZoneScopeAddressType
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for ipv4 or ipv6." "This compliance requires support for ipv4 or ipv6."
OBJECT ipMcastZoneScopeAddress OBJECT ipMcastZoneScopeAddress
SYNTAX InetAddress (SIZE (4|16)) SYNTAX InetAddress (SIZE (4|16))
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"This compliance requires support for ipv4 or ipv6." "This compliance requires support for ipv4 or ipv6."
::= { ipMcastMIBCompliances 3 } ::= { ipMcastMIBCompliances 3 }
-- --
-- Units of conformance -- Units of conformance
-- --
ipMcastMIBBasicGroup OBJECT-GROUP ipMcastMIBBasicGroup OBJECT-GROUP
OBJECTS { ipMcastEnabled, OBJECTS { ipMcastEnabled,
ipMcastRouteEntryCount, ipMcastRouteEntryCount,
ipMcastDeviceConfigStorageType ipMcastDeviceConfigStorageType
} }
skipping to change at page 55, line 9 skipping to change at page 54, line 7
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of multicast "A collection of objects to support management of multicast
address scope names." address scope names."
::= { ipMcastMIBGroups 12 } ::= { ipMcastMIBGroups 12 }
END END
7. Security Considerations 7. Security Considerations
7.1 SNMPv3 7.1. SNMPv3
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secured (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
there is still no control over whom on the secure network is allowed even then, there is no control as to who on the secure network is
to access (read/change/create/delete) the objects in this MIB module. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to access (read/change/create/delete) them. rights to access (read/change/create/delete) them.
7.2 Writeable objects 7.2. Writeable Objects
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. This with a MAX-ACCESS clause of read-write and/or read-create. This
section discusses and lists these elements. section discusses and lists these elements.
Such objects may be considered sensitive or vulnerable in some Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a non-secure network environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
skipping to change at page 56, line 9 skipping to change at page 55, line 8
o Modifications to multicast routing behavior that allow o Modifications to multicast routing behavior that allow
interception or subversion of information that is carried by the interception or subversion of information that is carried by the
network. For example, attacks can be envisaged that would pass network. For example, attacks can be envisaged that would pass
nominated multicast data streams through a nominated location, nominated multicast data streams through a nominated location,
without the sources or listeners becoming aware of this without the sources or listeners becoming aware of this
subversion. subversion.
The following are the read-write and read-create objects defined in The following are the read-write and read-create objects defined in
this MIB module. this MIB module.
ipMcastEnabled ipMcastEnabled ipMcastDeviceConfigStorageType ipMcastInterfaceTtl
ipMcastDeviceConfigStorageType ipMcastInterfaceRateLimit ipMcastInterfaceStorageType
ipMcastInterfaceTtl ipMcastSsmRangeRowStatus ipMcastSsmRangeStorageType
ipMcastInterfaceRateLimit ipMcastBoundaryStatus ipMcastBoundaryStorageType
ipMcastInterfaceStorageType ipMcastScopeNameString ipMcastScopeNameDefault ipMcastScopeNameStatus
ipMcastSsmRangeRowStatus
ipMcastSsmRangeStorageType
ipMcastBoundaryStatus
ipMcastBoundaryStorageType
ipMcastScopeNameTable
ipMcastScopeNameString
ipMcastScopeNameDefault
ipMcastScopeNameStatus
ipMcastScopeNameStorageType ipMcastScopeNameStorageType
7.3 Readable objects 7.3. Readable Objects
As well as the writeable objects discussed above, there are a number As well as the writeable objects discussed above, there are a number
of readable objects (i.e., objects with a MAX-ACCESS other than not- of readable objects (i.e., objects with a MAX-ACCESS other than not-
accessible) that may be considered sensitive or vulnerable in some accessible) that may be considered sensitive or vulnerable in some
network environments. It is thus important to control even GET network environments. It is thus important to control even GET
and/or NOTIFY access to these objects and possibly to even encrypt and/or NOTIFY access to these objects and possibly to even encrypt
the values of these objects when sending them over the network via the values of these objects when sending them over the network via
SNMP. SNMP.
In this MIB module, possible effects that can be induced by GET In this MIB module, possible effects that can be induced by GET
skipping to change at page 57, line 7 skipping to change at page 55, line 42
o Determinion of whether multicast data is flowing in the network, o Determinion of whether multicast data is flowing in the network,
or has flowed recently, as well as the locations of senders and or has flowed recently, as well as the locations of senders and
recipients. An attacker can apply 'traffic analysis' to this recipients. An attacker can apply 'traffic analysis' to this
data. In some cases, the information revealed by traffic analyses data. In some cases, the information revealed by traffic analyses
can be as damaging as full knowledge of the data being can be as damaging as full knowledge of the data being
transported. transported.
8. IANA Considerations 8. IANA Considerations
The MIB module in this document uses the following IANA-assigned IPMCAST-MIB is rooted under the mib-2 subtree. IANA has assigned {
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: mib-2 168 } to the IPMCAST-MIB module specified in this document.
Descriptor OBJECT IDENTIFIER value
-----------------------------------------
ipMcastMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
9. Acknowledgements 9. Acknowledgements
This MIB module is based on the original work in [RFC2932] by K. This MIB module is based on the original work in [RFC2932] by K.
McCloghrie, D. Farinacci and D. Thaler. McCloghrie, D. Farinacci, and D. Thaler.
Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have
been used for comparison while editing this MIB module. been used for comparison while editing this MIB module.
The authors are grateful to Bill Fenner for fine ideas, and to Bharat The authors are grateful to Bill Fenner for fine ideas, and to Bharat
Joshi for input and several corrections. Joshi for input and several corrections.
The authors also wish to thank John Flick, Bert Wijnen and Stig The authors also wish to thank John Flick, Bert Wijnen, and Stig
Venaas for their reviewing and comments. Venaas for their reviewing and comments.
10. References 10. References
10.1 Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23,
RFC 2365, July 1998. RFC 2365, July 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
skipping to change at page 58, line 36 skipping to change at page 57, line 12
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005. March 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[I-D.mcwalter-langtag-mib] [RFC5131] McWalter, D., "A MIB Textual Convention for Language
McWalter, D., "Language Tag MIB", Tags", RFC 5131, December 2007.
draft-mcwalter-langtag-mib-03 (work in progress), I-D
Status active, March 2007.
10.2 Informative References 10.2. Informative References
[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287, Managed Objects for Applications", RFC 2287,
February 1998. February 1998.
[RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4
Multicast Routing MIB", RFC 2932, October 2000. Multicast Routing MIB", RFC 2932, October 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
skipping to change at page 59, line 19 skipping to change at page 57, line 41
[RFC4293] Routhier, S., "Management Information Base for the [RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006. Internet Protocol (IP)", RFC 4293, April 2006.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 4646, September 2006. Languages", BCP 47, RFC 4646, September 2006.
[I-D.ietf-pim-bidir] [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, "Bidirectional Protocol Independent Multicast (BIDIR-
"Bi-directional Protocol Independent Multicast (BIDIR- PIM)", RFC 5015, October 2007.
PIM)", draft-ietf-pim-bidir-09 (work in progress),
March 2007.
Authors' Addresses Authors' Addresses
David McWalter David McWalter
Data Connection Ltd Data Connection Ltd
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
UK UK
Email: dmcw@dataconnection.com EMail: dmcw@dataconnection.com
Dave Thaler Dave Thaler
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond WA 98052-6399 Redmond, WA 98052-6399
USA USA
Email: dthaler@windows.microsoft.com EMail: dthaler@windows.microsoft.com
Andrew Kessler Andrew Kessler
Cisco Systems Cisco Systems
425 E. Tasman Drive 425 E. Tasman Drive
San Jose CA 95134 San Jose, CA 95134
USA USA
Email: kessler@cisco.com EMail: kessler@cisco.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 61, line 28 skipping to change at line 2788
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 97 change blocks. 
221 lines changed or deleted 188 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/