-- The IP Multicast Scope Name Table -- ipMcastScopeNameTable OBJECT-TYPE SYNTAX SEQUENCE OF IpMcastScopeNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing multicast scope names." REFERENCE "RFC 4007 Section 4" ::= { ipMcast 8 } ipMcastScopeNameEntry OBJECT-TYPE SYNTAX IpMcastScopeNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) that names a multicast address scope. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit." REFERENCE "RFC 4007 Section 4" INDEX { ipMcastScopeNameAddressType, ipMcastScopeNameAddress, ipMcastScopeNameAddressPrefixLength, ipMcastScopeNameLanguage } ::= { ipMcastScopeNameTable 1 } IpMcastScopeNameEntry ::= SEQUENCE { ipMcastScopeNameAddressType InetAddressType, ipMcastScopeNameAddress InetAddress, ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, ipMcastScopeNameLanguage LangTag, ipMcastScopeNameString SnmpAdminString, ipMcastScopeNameDefault TruthValue, ipMcastScopeNameStatus RowStatus, ipMcastScopeNameStorageType StorageType } ipMcastScopeNameAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "A value indicating the address family of the address
contained in ipMcastScopeNameAddress. Legal values correspond to the subset of address families for which multicast forwarding is supported." ::= { ipMcastScopeNameEntry 1 } ipMcastScopeNameAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The group address which, when combined with the corresponding value of ipMcastScopeNameAddressPrefixLength, identifies the group range associated with the multicast scope. Scoped IPv4 multicast address ranges must be prefixed by 239.0.0.0/8. Scoped IPv6 multicast address ranges are FF0x::/16, where x is a valid RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope name for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table. This address object is only significant up to ipMcastScopeNameAddressPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry." ::= { ipMcastScopeNameEntry 2 } ipMcastScopeNameAddressPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION "The length in bits of the mask which, when combined with the corresponding value of ipMcastScopeNameAddress, identifies the group range associated with the multicast scope. The InetAddressType is given by ipMcastScopeNameAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be set to 16." ::= { ipMcastScopeNameEntry 3 }
ipMcastScopeNameLanguage OBJECT-TYPE SYNTAX LangTag MAX-ACCESS not-accessible STATUS current DESCRIPTION "Language tag associated with the scope name." REFERENCE "RFC 4646" ::= { ipMcastScopeNameEntry 4 } ipMcastScopeNameString OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in this scope. When no name is specified, the default value of this object for IPv4 should be the string 239.x.x.x/y with x and y replaced with decimal values to describe the address and mask length associated with the scope. When no name is specified, the default value of this object for IPv6 should be the string FF0x::/16, with x replaced by the hexadecimal value for the RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope name for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table." REFERENCE "RFC 2365, RFC 3306 Section 4, RFC 4291 Section 2.7" ::= { ipMcastScopeNameEntry 5 } ipMcastScopeNameDefault OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If true, indicates a preference that the name in the following language should be used by applications if no name is available in a desired language." DEFVAL { false } ::= { ipMcastScopeNameEntry 6 }
ipMcastScopeNameStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row, by which rows in this table can be created and destroyed. Before the row can be activated, the object ipMcastScopeNameString must be set to a valid value. All writeable objects in this entry can be modified when the status is active(1)." ::= { ipMcastScopeNameEntry 7 } ipMcastScopeNameStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row." DEFVAL { nonVolatile } ::= { ipMcastScopeNameEntry 8 } -- -- The Multicast Listeners Table -- ipMcastLocalListenerTable OBJECT-TYPE SYNTAX SEQUENCE OF IpMcastLocalListenerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing local applications or services that have joined multicast groups as listeners. Entries exist for all addresses in the multicast range for all applications and services as they are classified on this device." ::= { ipMcast 9 } ipMcastLocalListenerEntry OBJECT-TYPE SYNTAX IpMcastLocalListenerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) identifying a local application or service that has joined a multicast group as a listener.
OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit." INDEX { ipMcastLocalListenerGroupAddressType, ipMcastLocalListenerGroupAddress, ipMcastLocalListenerSourceAddressType, ipMcastLocalListenerSourceAddress, ipMcastLocalListenerSourcePrefixLength, ipMcastLocalListenerIfIndex, ipMcastLocalListenerRunIndex } ::= { ipMcastLocalListenerTable 1 } IpMcastLocalListenerEntry ::= SEQUENCE { ipMcastLocalListenerGroupAddressType InetAddressType, ipMcastLocalListenerGroupAddress InetAddress, ipMcastLocalListenerSourceAddressType InetAddressType, ipMcastLocalListenerSourceAddress InetAddress, ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, ipMcastLocalListenerIfIndex InterfaceIndex, ipMcastLocalListenerRunIndex Unsigned32 } ipMcastLocalListenerGroupAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "A value indicating the address family of the address contained in ipMcastLocalListenerGroupAddress. Legal values correspond to the subset of address families for which multicast is supported." ::= { ipMcastLocalListenerEntry 1 } ipMcastLocalListenerGroupAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP multicast group for which this entry specifies locally joined applications or services." ::= { ipMcastLocalListenerEntry 2 } ipMcastLocalListenerSourceAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION
"A value indicating the address family of the address contained in ipMcastLocalListenerSource. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of ipMcastLocalListenerGroupAddressType." ::= { ipMcastLocalListenerEntry 3 } ipMcastLocalListenerSourceAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network address which, when combined with the corresponding value of the mask specified in ipMcastLocalListenerSourcePrefixLength, identifies the sources for which this entry specifies a local listener. This address object is only significant up to ipMcastLocalListenerSourcePrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this listener address applies only within the given zone. Zone index zero is not valid in this table." ::= { ipMcastLocalListenerEntry 4 } ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION "The length in bits of the mask which, when combined with the corresponding value specified in ipMcastLocalListenerSource, identifies the sources for which this entry specifies a local listener. The InetAddressType is given by ipMcastLocalListenerSourceAddressType. For the value 'unknown', this object must be zero. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range
8..128." ::= { ipMcastLocalListenerEntry 5 } ipMcastLocalListenerIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IfIndex value of the interface for which this entry specifies a local listener." ::= { ipMcastLocalListenerEntry 6 } ipMcastLocalListenerRunIndex OBJECT-TYPE SYNTAX Unsigned32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "A unique value corresponding to a piece of software running on this router or host system. Where possible, this should be the system's native, unique identification number. This identifier is platform-specific. It may correspond to a process ID or application instance number. A value of zero indicates that the application instance(s) cannot be identified. A value of zero indicates that one or more unidentified applications have joined the specified multicast groups (for the specified sources) as listeners." REFERENCE "RFC 2287 sysApplRunIndex" ::= { ipMcastLocalListenerEntry 7 } -- -- The Multicast Zone Table -- ipMcastZoneTable OBJECT-TYPE SYNTAX SEQUENCE OF IpMcastZoneEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing scope zones on this device." REFERENCE "RFC 4007 Section 5" ::= { ipMcast 10 } ipMcastZoneEntry OBJECT-TYPE SYNTAX IpMcastZoneEntry MAX-ACCESS not-accessible STATUS current
DESCRIPTION "An entry (conceptual row) describing a scope zone on this device." REFERENCE "RFC 4007 Section 5" INDEX { ipMcastZoneIndex } ::= { ipMcastZoneTable 1 } IpMcastZoneEntry ::= SEQUENCE { ipMcastZoneIndex InetZoneIndex, ipMcastZoneScopeDefaultZoneIndex InetZoneIndex, ipMcastZoneScopeAddressType InetAddressType, ipMcastZoneScopeAddress InetAddress, ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength } ipMcastZoneIndex OBJECT-TYPE SYNTAX InetZoneIndex (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This zone index uniquely identifies a zone on a device. Each zone is for a given scope. Scope-level information in this table is for the unique scope that corresponds to this zone. Zero is a special value used to request the default zone for a given scope. Zero is not a valid value for this object. To test whether ipMcastZoneIndex is the default zone for this scope, test whether ipMcastZoneIndex is equal to ipMcastZoneScopeDefaultZoneIndex." ::= { ipMcastZoneEntry 1 } ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE SYNTAX InetZoneIndex (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The default zone index for this scope. This is the zone that this device will use if the default (zero) zone is requested for this scope. Zero is not a valid value for this object." ::= { ipMcastZoneEntry 2 } ipMcastZoneScopeAddressType OBJECT-TYPE SYNTAX InetAddressType
MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address type for which this scope zone exists." ::= { ipMcastZoneEntry 3 } ipMcastZoneScopeAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The multicast group address which, when combined with ipMcastZoneScopeAddressPrefixLength, gives the multicast address range for this scope. The InetAddressType is given by ipMcastZoneScopeAddressType. Scoped IPv4 multicast address ranges are prefixed by 239.0.0.0/8. Scoped IPv6 multicast address ranges are FF0x::/16, where x is a valid RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table. This address object is only significant up to ipMcastZoneScopeAddressPrefixLength bits. The remaining address bits are set to zero." REFERENCE "RFC 2365, RFC 3306 Section 4, RFC 4291 Section 2.7" ::= { ipMcastZoneEntry 4 } ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION "The length in bits of the mask which, when combined with ipMcastZoneScopeAddress, gives the multicast address prefix for this scope. The InetAddressType is given by ipMcastZoneScopeAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be set to 16." ::= { ipMcastZoneEntry 5 }
-- -- Conformance information -- ipMcastMIBConformance OBJECT IDENTIFIER ::= { ipMcastMIB 2 } ipMcastMIBCompliances OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } -- -- Compliance statements -- ipMcastMIBComplianceHost MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for hosts supporting IPMCAST-MIB. Support for either InetAddressType ipv4 or ipv6 is mandatory; support for both InetAddressTypes ipv4 and ipv6 is optional. Support for types ipv4z and ipv6z is optional. -- OBJECT ipMcastLocalListenerGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerGroupAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerSourceAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6." MODULE -- this module MANDATORY-GROUPS { ipMcastMIBLocalListenerGroup,
ipMcastMIBBasicGroup } OBJECT ipMcastEnabled MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastDeviceConfigStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." GROUP ipMcastMIBSsmGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteDiagnosticsGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBBoundaryIfGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBScopeNameGroup DESCRIPTION "This group is optional." ::= { ipMcastMIBCompliances 1 } ipMcastMIBComplianceRouter MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for routers supporting IPMCAST-MIB. Support for either InetAddressType ipv4 or ipv6 is mandatory; support for both InetAddressTypes ipv4 and ipv6 is optional. Support for types ipv4z and ipv6z is optional. -- OBJECT ipMcastSsmRangeAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), -- ipv6z(4)}
-- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastSsmRangeAddress -- SYNTAX InetAddress (SIZE (4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopSourceAddressType
-- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6." MODULE -- this module MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, ipMcastMIBBasicGroup, ipMcastMIBSsmGroup, ipMcastMIBRouteGroup } OBJECT ipMcastEnabled MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastDeviceConfigStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceTtl MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceRateLimit MIN-ACCESS read-only
DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastRouteUpstreamNeighborType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) } DESCRIPTION "This compliance requires support for unknown and either ipv4 or ipv6." OBJECT ipMcastRouteUpstreamNeighbor SYNTAX InetAddress (SIZE (0|4|8|16|20)) DESCRIPTION "This compliance requires support for unknown and either ipv4 or ipv6." OBJECT ipMcastRouteRtAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) } DESCRIPTION "This compliance requires support for unknown and either ipv4 or ipv6." OBJECT ipMcastRouteRtAddress SYNTAX InetAddress (SIZE (0|4|8|16|20)) DESCRIPTION "This compliance requires support for unknown and either ipv4 or ipv6." OBJECT ipMcastSsmRangeRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastSsmRangeStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." GROUP ipMcastMIBRouteDiagnosticsGroup DESCRIPTION "This group is not mandatory, but SHOULD be supported where hardware permits."
GROUP ipMcastMIBPktsOutGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBHopCountGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteOctetsGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteBpsGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBLocalListenerGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBBoundaryIfGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBScopeNameGroup DESCRIPTION "This group is optional." ::= { ipMcastMIBCompliances 2 } ipMcastMIBComplianceBorderRouter MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for routers on scope boundaries supporting IPMCAST-MIB. Support for either InetAddressType ipv4z or ipv6z is mandatory; support for both InetAddressTypes ipv4z and ipv6z is optional. -- OBJECT ipMcastSsmRangeAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), -- ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastSsmRangeAddress -- SYNTAX InetAddress (SIZE (4|8|16|20))
-- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z.
-- -- OBJECT ipMcastRouteNextHopSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastBoundaryAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastBoundaryAddress -- SYNTAX InetAddress (SIZE (4|16) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastScopeNameAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastScopeNameAddress -- SYNTAX InetAddress (SIZE (4|16) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6." MODULE -- this module MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, ipMcastMIBBasicGroup, ipMcastMIBSsmGroup, ipMcastMIBRouteGroup, ipMcastMIBBoundaryIfGroup, ipMcastMIBScopeNameGroup }
OBJECT ipMcastEnabled MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastDeviceConfigStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceTtl MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceRateLimit MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastInterfaceStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastRouteUpstreamNeighborType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) } DESCRIPTION "This compliance requires support for unknown and either ipv4 and ipv4z, or ipv6 and ipv6z." OBJECT ipMcastRouteUpstreamNeighbor SYNTAX InetAddress (SIZE (0|4|8|16|20)) DESCRIPTION "This compliance requires support for unknown and either ipv4 and ipv4z, or ipv6 and ipv6z." OBJECT ipMcastRouteRtAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) } DESCRIPTION "This compliance requires support for unknown and either ipv4 and ipv4z, or ipv6 and ipv6z." OBJECT ipMcastRouteRtAddress SYNTAX InetAddress (SIZE (0|4|8|16|20)) DESCRIPTION
"This compliance requires support for unknown and either ipv4 and ipv4z, or ipv6 and ipv6z." OBJECT ipMcastSsmRangeRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT ipMcastSsmRangeStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." GROUP ipMcastMIBRouteDiagnosticsGroup DESCRIPTION "This group is not mandatory, but SHOULD be supported where hardware permits." GROUP ipMcastMIBPktsOutGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBHopCountGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteOctetsGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBRouteBpsGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBLocalListenerGroup DESCRIPTION "This group is optional." OBJECT ipMcastZoneScopeAddressType SYNTAX InetAddressType { ipv4(1), ipv6(2) } DESCRIPTION "This compliance requires support for ipv4 or ipv6." OBJECT ipMcastZoneScopeAddress SYNTAX InetAddress (SIZE (4|16)) DESCRIPTION "This compliance requires support for ipv4 or ipv6."
::= { ipMcastMIBCompliances 3 } -- -- Units of conformance -- ipMcastMIBBasicGroup OBJECT-GROUP OBJECTS { ipMcastEnabled, ipMcastRouteEntryCount, ipMcastDeviceConfigStorageType } STATUS current DESCRIPTION "A collection of objects to support basic management of IP Multicast protocols." ::= { ipMcastMIBGroups 1 } ipMcastMIBSsmGroup OBJECT-GROUP OBJECTS { ipMcastSsmRangeRowStatus, ipMcastSsmRangeStorageType } STATUS current DESCRIPTION "A collection of objects to support management of Source- Specific Multicast routing." ::= { ipMcastMIBGroups 2 } ipMcastMIBRouteGroup OBJECT-GROUP OBJECTS { ipMcastInterfaceTtl, ipMcastInterfaceRateLimit, ipMcastInterfaceStorageType, ipMcastRouteUpstreamNeighborType, ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, ipMcastRouteNextHopState, ipMcastRouteNextHopTimeStamp, ipMcastRouteNextHopExpiryTime } STATUS current DESCRIPTION "A collection of objects to support basic management of IP Multicast routing." ::= { ipMcastMIBGroups 3 } ipMcastMIBRouteDiagnosticsGroup OBJECT-GROUP OBJECTS { ipMcastRoutePkts, ipMcastRouteTtlDropPackets, ipMcastRouteDifferentInIfPackets
} STATUS current DESCRIPTION "A collection of routing diagnostic packet counters." ::= { ipMcastMIBGroups 4 } ipMcastMIBPktsOutGroup OBJECT-GROUP OBJECTS { ipMcastRouteNextHopTimeStamp, ipMcastRouteNextHopPkts } STATUS current DESCRIPTION "A collection of objects to support management of packet counters for each outgoing interface entry of a route." ::= { ipMcastMIBGroups 5 } ipMcastMIBHopCountGroup OBJECT-GROUP OBJECTS { ipMcastRouteNextHopClosestMemberHops } STATUS current DESCRIPTION "A collection of objects to support management of the use of hop counts in IP Multicast routing." ::= { ipMcastMIBGroups 6 } ipMcastMIBRouteOctetsGroup OBJECT-GROUP OBJECTS { ipMcastRouteTimeStamp, ipMcastRouteOctets, ipMcastRouteTtlDropOctets, ipMcastRouteDifferentInIfOctets, ipMcastRouteNextHopTimeStamp, ipMcastRouteNextHopOctets } STATUS current DESCRIPTION "A collection of objects to support management of octet counters for each forwarding entry." ::= { ipMcastMIBGroups 7 } ipMcastMIBRouteBpsGroup OBJECT-GROUP OBJECTS { ipMcastRouteBps } STATUS current DESCRIPTION "A collection of objects to support sampling of data rate in bits per second for each forwarding entry." ::= { ipMcastMIBGroups 8 } ipMcastMIBRouteProtoGroup OBJECT-GROUP OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, ipMcastRouteRtAddressType, ipMcastRouteRtAddress, ipMcastRouteRtPrefixLength, ipMcastRouteRtType,
ipMcastRouteNextHopProtocol } STATUS current DESCRIPTION "A collection of objects providing information on the relationship between multicast routing information and the IP Forwarding Table." ::= { ipMcastMIBGroups 9 } ipMcastMIBLocalListenerGroup OBJECT-GROUP OBJECTS { ipMcastLocalListenerRunIndex } STATUS current DESCRIPTION "A collection of objects to support management of local listeners on hosts or routers." ::= { ipMcastMIBGroups 10 } ipMcastMIBBoundaryIfGroup OBJECT-GROUP OBJECTS { ipMcastBoundaryTimeStamp, ipMcastBoundaryDroppedMcastOctets, ipMcastBoundaryDroppedMcastPkts, ipMcastBoundaryStatus, ipMcastBoundaryStorageType, ipMcastZoneScopeDefaultZoneIndex, ipMcastZoneScopeAddressType, ipMcastZoneScopeAddress, ipMcastZoneScopeAddressPrefixLength } STATUS current DESCRIPTION "A collection of objects to support management of multicast scope zone boundaries." ::= { ipMcastMIBGroups 11 } ipMcastMIBScopeNameGroup OBJECT-GROUP OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, ipMcastScopeNameStatus, ipMcastScopeNameStorageType } STATUS current DESCRIPTION "A collection of objects to support management of multicast address scope names." ::= { ipMcastMIBGroups 12 } END
7. Security Considerations
7.1. SNMPv3
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is 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 provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to access (read/change/create/delete) them.7.2. Writeable Objects
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 section discusses and lists these elements. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. In this MIB module, possible effects that can be induced by SET operations on writeable objects include: o Modifications to multicast routing behavior that prevent or disrupt services provided by the network, including (but not limited to) multicast data traffic delivery. o Modifications to multicast routing behavior that allow interception or subversion of information that is carried by the network. For example, attacks can be envisaged that would pass nominated multicast data streams through a nominated location, without the sources or listeners becoming aware of this subversion.
The following are the read-write and read-create objects defined in this MIB module. ipMcastEnabled ipMcastDeviceConfigStorageType ipMcastInterfaceTtl ipMcastInterfaceRateLimit ipMcastInterfaceStorageType ipMcastSsmRangeRowStatus ipMcastSsmRangeStorageType ipMcastBoundaryStatus ipMcastBoundaryStorageType ipMcastScopeNameString ipMcastScopeNameDefault ipMcastScopeNameStatus ipMcastScopeNameStorageType7.3. Readable Objects
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- accessible) that may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. In this MIB module, possible effects that can be induced by GET and/or NOTIFY operations include: o Determination of the topology, disposition, and composition of the network. This information may be commercially sensitive, and may also be used in preparation for attacks, including any of the attacks described above. o Determinion of whether multicast data is flowing in the network, or has flowed recently, as well as the locations of senders and recipients. An attacker can apply 'traffic analysis' to this data. In some cases, the information revealed by traffic analyses can be as damaging as full knowledge of the data being transported.8. IANA Considerations
IPMCAST-MIB is rooted under the mib-2 subtree. IANA has assigned { mib-2 168 } to the IPMCAST-MIB module specified in this document.9. Acknowledgements
This MIB module is based on the original work in [RFC2932] by K. McCloghrie, D. Farinacci, and D. Thaler. Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have been used for comparison while editing this MIB module.
The authors are grateful to Bill Fenner for fine ideas, and to Bharat Joshi for input and several corrections. The authors also wish to thank John Flick, Bert Wijnen, and Stig Venaas for their reviewing and comments.10. References
10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, RFC 2365, July 1998. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual Conventions for Additional High Capacity Data Types", RFC 2856, June 2000. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast Addresses", RFC 3306, August 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, March 2005. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC5131] McWalter, D., "A MIB Textual Convention for Language Tags", RFC 5131, December 2007.10.2. Informative References
[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level Managed Objects for Applications", RFC 2287, February 1998. [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 Multicast Routing MIB", RFC 2932, October 2000. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific Multicast (SSM)", RFC 3569, July 2003. [RFC4293] Routhier, S., "Management Information Base for the Internet Protocol (IP)", RFC 4293, April 2006. [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006. [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 4646, September 2006. [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, "Bidirectional Protocol Independent Multicast (BIDIR- PIM)", RFC 5015, October 2007.
Authors' Addresses
David McWalter Data Connection Ltd 100 Church Street Enfield EN2 6BQ UK EMail: dmcw@dataconnection.com Dave Thaler Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 USA EMail: dthaler@windows.microsoft.com Andrew Kessler Cisco Systems 425 E. Tasman Drive San Jose, CA 95134 USA EMail: kessler@cisco.com
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 Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.