draft-ietf-idmr-multicast-routmib-14.txt   rfc2932.txt 
IDMR Working Group Keith McCloghrie
INTERNET-DRAFT Dino Farinacci Network Working Group K. McCloghrie
Expires January 2000 cisco Systems Request for Comments: 2932 cisco Systems
Dave Thaler Category: Standards Track D. Farinacci
Microsoft Procket Networks
7 July 2000 D. Thaler
Microsoft
October 2000
IPv4 Multicast Routing MIB IPv4 Multicast Routing MIB
<draft-ietf-idmr-multicast-routmib-14.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document specifies an Internet standards track protocol for the
provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Task Official Protocol Standards" (STD 1) for the standardization state
Force (IETF), its areas, and its working groups. Note that other groups and status of this protocol. Distribution of this memo is unlimited.
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Draft IPv4 Multicast Routing MIB July 2000
1. Abstract Abstract
This memo defines an experimental portion of the Management Information This memo defines a portion of the Management Information Base (MIB)
Base (MIB) for use with network management protocols in the Internet for use with network management protocols in the Internet community.
community. In particular, it describes managed objects used for In particular, it describes managed objects used for managing IP
managing IP Multicast Routing for IPv4, independent of the specific Multicast Routing for IPv4, independent of the specific multicast
multicast routing protocol in use. routing protocol in use.
2. Introduction Table of Contents
This MIB describes objects used for managing IP Multicast Routing [16], 1 Introduction ................................................. 2
independent of the specific multicast routing protocol [17-21] in use. 2 The SNMP Management Framework ................................ 2
Managed objects specific to particular multicast routing protocols are 3 Overview ..................................................... 3
specified elsewhere. Similarly, this MIB does not support management of 4 Definitions .................................................. 4
multicast routing for other address families, including IPv6. Such 5 IANA Considerations .......................................... 22
management may be supported by other MIBs. 6 Security Considerations ...................................... 22
7 Intellectual Property Notice ................................. 23
8 Acknowledgements ............................................. 23
9 Authors' Addresses ........................................... 24
10 References ................................................... 25
11 Full Copyright Statement ..................................... 27
3. The SNMP Management Framework 1. Introduction
The SNMP Management Framework presently consists of five major This MIB describes objects used for managing IP Multicast Routing
components: [16], independent of the specific multicast routing protocol [17-21]
in use. Managed objects specific to particular multicast routing
protocols are specified elsewhere. Similarly, this MIB does not
support management of multicast routing for other address families,
including IPv6. Such management may be supported by other MIBs.
o An overall architecture, described in RFC 2571 [1]. 2. The SNMP Management Framework
o Mechanisms for describing and naming objects and events for the The SNMP Management Framework presently consists of five major
purpose of management. The first version of this Structure of components:
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called
SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. The o An overall architecture, described in RFC 2571 [1].
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o Protocol operations for accessing management information. The first o Mechanisms for describing and naming objects and events for the
set of protocol operations and associated PDU formats is described purpose of management. The first version of this Structure of
in RFC 1157 [8]. A second set of protocol operations and associated Management Information (SMI) is called SMIv1 and described in
PDU formats is described in RFC 1905 [13]. STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
The second version, called SMIv2, is described in STD 58, RFC
2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
Draft IPv4 Multicast Routing MIB July 2000 o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [8]. A second version of the SNMP
message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [9] and
RFC 1906 [10]. The third version of the message protocol is
called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and
RFC 2574 [12].
o A set of fundamental applications described in RFC 2573 [14] and o Protocol operations for accessing management information. The
the view-based access control mechanism described in RFC 2575 [15]. first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[13].
Managed objects are accessed via a virtual information store, termed the o A set of fundamental applications described in RFC 2573 [14] and
Management Information Base or MIB. Objects in the MIB are defined the view-based access control mechanism described in RFC 2575
using the mechanisms defined in the SMI. [15].
This memo specifies a MIB module that is compliant to the SMIv2. A MIB Managed objects are accessed via a virtual information store, termed
conforming to the SMIv1 can be produced through the appropriate the Management Information Base or MIB. Objects in the MIB are
translations. The resulting translated MIB must be semantically defined using the mechanisms defined in the SMI.
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
4. Overview This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
This MIB module contains one scalar and five tables. The tables are: 3. Overview
(1) the IP Multicast Route Table containing multicast routing This MIB module contains one scalar and five tables. The tables are:
information for IP datagrams sent by particular sources to the IP
multicast groups known to a router.
(2) the IP Multicast Routing Next Hop Table containing information on (1) the IP Multicast Route Table containing multicast routing
the next-hops for the routing IP multicast datagrams. Each entry information for IP datagrams sent by particular sources to the
is one of a list of next-hops on outgoing interfaces for IP multicast groups known to a router.
particular sources sending to a particular multicast group
address.
(3) the IP Multicast Routing Interface Table containing multicast (2) the IP Multicast Routing Next Hop Table containing information
routing information specific to interfaces. on the next-hops for the routing IP multicast datagrams. Each
entry is one of a list of next-hops on outgoing interfaces for
particular sources sending to a particular multicast group
address.
(4) the IP Multicast Scope Boundary Table containing the boundaries (3) the IP Multicast Routing Interface Table containing multicast
configured for multicast scopes [22]. routing information specific to interfaces.
(5) the IP Multicast Scope Name Table containing human-readable names (4) the IP Multicast Scope Boundary Table containing the boundaries
of multicast scope. configured for multicast scopes [22].
Draft IPv4 Multicast Routing MIB July 2000 (5) the IP Multicast Scope Name Table containing human-readable
names of multicast scope.
5. Definitions 4. Definitions
IPMROUTE-STD-MIB DEFINITIONS ::= BEGIN IPMROUTE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Integer32, Counter32, Counter64, Gauge32, Integer32, Counter32, Counter64, Gauge32,
IpAddress, TimeTicks FROM SNMPv2-SMI IpAddress, TimeTicks FROM SNMPv2-SMI
RowStatus, TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION,
TruthValue FROM SNMPv2-TC TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InterfaceIndexOrZero, InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB
IANAipRouteProtocol, IANAipRouteProtocol,
IANAipMRouteProtocol FROM IANA-RTPROTO-MIB; IANAipMRouteProtocol FROM IANA-RTPROTO-MIB;
ipMRouteStdMIB MODULE-IDENTITY ipMRouteStdMIB MODULE-IDENTITY
LAST-UPDATED "200001311200Z" -- January 31, 2000 LAST-UPDATED "200009220000Z" -- September 22, 2000
ORGANIZATION "IETF IDMR Working Group" ORGANIZATION "IETF IDMR Working Group"
CONTACT-INFO CONTACT-INFO
" 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
EMail: dthaler@dthaler.microsoft.com" EMail: dthaler@microsoft.com"
DESCRIPTION DESCRIPTION
"The MIB module for management of IP Multicast routing, but "The MIB module for management of IP Multicast routing, but
independent of the specific multicast routing protocol in independent of the specific multicast routing protocol in
use." use."
REVISION "200001311200Z" -- January 31, 2000 REVISION "200009220000Z" -- September 22, 2000
DESCRIPTION DESCRIPTION
"Initial version, published as RFC xxxx (to be filled in by "Initial version, published as RFC 2932."
RFC-Editor)." ::= { mib-2 83 }
::= { mib-2 XX }
-- NOTE TO RFC EDITOR: When this document is published as
-- an RFC, replace XX with IANA-assigned number,
-- and delete this comment.
-- Textual Conventions -- Textual Conventions
LanguageTag ::= TEXTUAL-CONVENTION LanguageTag ::= TEXTUAL-CONVENTION
Draft IPv4 Multicast Routing MIB July 2000
DISPLAY-HINT "100a" DISPLAY-HINT "100a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An RFC 1766-style language tag, with all alphabetic "An RFC 1766-style language tag, with all alphabetic
characters converted to lowercase. This restriction is characters converted to lowercase. This restriction is
intended to make the lexical ordering imposed by SNMP useful intended to make the lexical ordering imposed by SNMP useful
when applied to language tags. Note that it is when applied to language tags. Note that it is
theoretically possible for a valid language tag to exceed theoretically possible for a valid language tag to exceed
the allowed length of this syntax, and thus be impossible to the allowed length of this syntax, and thus be impossible to
represent with this syntax. Sampling of language tags in represent with this syntax. Sampling of language tags in
current use on the Internet suggests that this limit does current use on the Internet suggests that this limit does
not pose a serious problem in practice." not pose a serious problem in practice."
SYNTAX OCTET STRING (SIZE (1..100)) SYNTAX OCTET STRING (SIZE (1..100))
-- Top-level structure of the MIB -- Top-level structure of the MIB
ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 } ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteStdMIB 1 }
ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 }
Draft IPv4 Multicast Routing MIB July 2000
-- the IP Multicast Routing MIB-Group -- the IP Multicast Routing MIB-Group
-- --
-- a collection of objects providing information about -- a collection of objects providing information about
-- IP Multicast Groups -- IP Multicast Groups
ipMRouteEnable OBJECT-TYPE ipMRouteEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 7, line 5 skipping to change at page 6, line 5
ipMRouteTable OBJECT-TYPE ipMRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteEntry SYNTAX SEQUENCE OF IpMRouteEntry
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." the IP multicast groups known to this router."
::= { ipMRoute 2 } ::= { ipMRoute 2 }
Draft IPv4 Multicast Routing MIB July 2000
ipMRouteEntry OBJECT-TYPE ipMRouteEntry OBJECT-TYPE
SYNTAX IpMRouteEntry SYNTAX IpMRouteEntry
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.
Discontinuities in counters in this entry can be detected by Discontinuities in counters in this entry can be detected by
observing the value of ipMRouteUpTime." observing the value of ipMRouteUpTime."
skipping to change at page 8, line 4 skipping to change at page 6, line 50
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address for which this entry "The IP multicast group address for which this entry
contains multicast routing information." contains multicast routing information."
::= { ipMRouteEntry 1 } ::= { ipMRouteEntry 1 }
ipMRouteSource OBJECT-TYPE ipMRouteSource OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
Draft IPv4 Multicast Routing MIB July 2000
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 ipMRouteSourceMask identifies the corresponding value of ipMRouteSourceMask identifies the
sources for which this entry contains multicast routing sources for which this entry contains multicast routing
information." information."
::= { ipMRouteEntry 2 } ::= { ipMRouteEntry 2 }
ipMRouteSourceMask OBJECT-TYPE ipMRouteSourceMask OBJECT-TYPE
skipping to change at page 9, line 4 skipping to change at page 7, line 46
"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 (e.g., in CBT)." on multiple interfaces (e.g., in CBT)."
::= { ipMRouteEntry 5 } ::= { ipMRouteEntry 5 }
ipMRouteUpTime OBJECT-TYPE ipMRouteUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
Draft IPv4 Multicast Routing MIB July 2000
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time since the multicast routing information "The time since the multicast routing information
represented by this entry was learned by the router." represented by this entry was learned by the router."
::= { ipMRouteEntry 6 } ::= { ipMRouteEntry 6 }
ipMRouteExpiryTime OBJECT-TYPE ipMRouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 10, line 4 skipping to change at page 8, line 44
not subject to an incoming interface check (e.g., using CBT) not subject to an incoming interface check (e.g., using CBT)
are not counted." are not counted."
::= { ipMRouteEntry 9 } ::= { ipMRouteEntry 9 }
ipMRouteOctets OBJECT-TYPE ipMRouteOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 which were
Draft IPv4 Multicast Routing MIB July 2000
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."
::= { ipMRouteEntry 10 } ::= { ipMRouteEntry 10 }
ipMRouteProtocol OBJECT-TYPE ipMRouteProtocol OBJECT-TYPE
SYNTAX IANAipMRouteProtocol SYNTAX IANAipMRouteProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast routing protocol via which this multicast "The multicast routing protocol via which this multicast
skipping to change at page 11, line 4 skipping to change at page 9, line 40
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mask associated with the route used to find the upstream "The mask associated with the route used to find the upstream
or parent interface for this multicast forwarding entry." or parent interface for this multicast forwarding entry."
::= { ipMRouteEntry 14 } ::= { ipMRouteEntry 14 }
ipMRouteRtType OBJECT-TYPE ipMRouteRtType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
Draft IPv4 Multicast Routing MIB July 2000
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
skipping to change at page 12, line 5 skipping to change at page 10, line 19
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 which 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.
This object is a 64-bit version of ipMRouteOctets." This object is a 64-bit version of ipMRouteOctets."
::= { ipMRouteEntry 16 } ::= { ipMRouteEntry 16 }
Draft IPv4 Multicast Routing MIB July 2000
-- --
-- The IP Multicast Routing Next Hop Table -- The IP Multicast Routing Next Hop Table
-- --
ipMRouteNextHopTable OBJECT-TYPE ipMRouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteNextHopEntry SYNTAX SEQUENCE OF IpMRouteNextHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing information on the next- "The (conceptual) table containing information on the next-
skipping to change at page 13, line 5 skipping to change at page 10, line 50
"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 a IP multicast group address are particular sources to a IP multicast group address are
routed. Discontinuities in counters in this entry can be routed. Discontinuities in counters in this entry can be
detected by observing the value of ipMRouteUpTime." detected by observing the value of ipMRouteUpTime."
INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource,
ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex,
ipMRouteNextHopAddress } ipMRouteNextHopAddress }
::= { ipMRouteNextHopTable 1 } ::= { ipMRouteNextHopTable 1 }
Draft IPv4 Multicast Routing MIB July 2000
IpMRouteNextHopEntry ::= SEQUENCE { IpMRouteNextHopEntry ::= SEQUENCE {
ipMRouteNextHopGroup IpAddress, ipMRouteNextHopGroup IpAddress,
ipMRouteNextHopSource IpAddress, ipMRouteNextHopSource IpAddress,
ipMRouteNextHopSourceMask IpAddress, ipMRouteNextHopSourceMask IpAddress,
ipMRouteNextHopIfIndex InterfaceIndex, ipMRouteNextHopIfIndex InterfaceIndex,
ipMRouteNextHopAddress IpAddress, ipMRouteNextHopAddress IpAddress,
ipMRouteNextHopState INTEGER, ipMRouteNextHopState INTEGER,
ipMRouteNextHopUpTime TimeTicks, ipMRouteNextHopUpTime TimeTicks,
ipMRouteNextHopExpiryTime TimeTicks, ipMRouteNextHopExpiryTime TimeTicks,
ipMRouteNextHopClosestMemberHops Integer32, ipMRouteNextHopClosestMemberHops Integer32,
skipping to change at page 14, line 5 skipping to change at page 11, line 47
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network mask which when combined with the corresponding "The network mask which when combined with the corresponding
value of ipMRouteNextHopSource identifies the sources for value of ipMRouteNextHopSource identifies the sources for
which this entry specifies a next-hop on an outgoing which this entry specifies a next-hop on an outgoing
interface." interface."
::= { ipMRouteNextHopEntry 3 } ::= { ipMRouteNextHopEntry 3 }
Draft IPv4 Multicast Routing MIB July 2000
ipMRouteNextHopIfIndex OBJECT-TYPE ipMRouteNextHopIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the interface for the outgoing "The ifIndex value of the interface for the outgoing
interface for this next-hop." interface for this next-hop."
::= { ipMRouteNextHopEntry 4 } ::= { ipMRouteNextHopEntry 4 }
ipMRouteNextHopAddress OBJECT-TYPE ipMRouteNextHopAddress OBJECT-TYPE
skipping to change at page 15, line 4 skipping to change at page 12, line 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time since the multicast routing information "The time since the multicast routing information
represented by this entry was learned by the router." represented by this entry was learned by the router."
::= { ipMRouteNextHopEntry 7 } ::= { ipMRouteNextHopEntry 7 }
ipMRouteNextHopExpiryTime OBJECT-TYPE ipMRouteNextHopExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Draft IPv4 Multicast Routing MIB July 2000
DESCRIPTION DESCRIPTION
"The minimum amount of time remaining before this entry will "The minimum amount of time remaining before this entry will
be aged out. If ipMRouteNextHopState is pruned(1), the be aged out. If ipMRouteNextHopState is pruned(1), the
remaining time until the prune expires and the state reverts remaining time until the prune expires and the state reverts
to forwarding(2). Otherwise, the remaining time until this to forwarding(2). Otherwise, the remaining time until this
entry is removed from the table. The time remaining may be entry is removed from the table. The time remaining may be
copied from ipMRouteExpiryTime if the protocol in use for copied from ipMRouteExpiryTime if the protocol in use for
this entry dos not specify next-hop timers. The value 0 this entry does not specify next-hop timers. The value 0
indicates that the entry is not subject to aging." indicates that the entry is not subject to aging."
::= { ipMRouteNextHopEntry 8 } ::= { ipMRouteNextHopEntry 8 }
ipMRouteNextHopClosestMemberHops OBJECT-TYPE ipMRouteNextHopClosestMemberHops OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
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
skipping to change at page 16, line 5 skipping to change at page 13, line 36
ipMRouteNextHopPkts OBJECT-TYPE ipMRouteNextHopPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which have been forwarded using this "The number of packets which have been forwarded using this
route." route."
::= { ipMRouteNextHopEntry 11 } ::= { ipMRouteNextHopEntry 11 }
Draft IPv4 Multicast Routing MIB July 2000
-- --
-- The Multicast Routing Interface Table -- The Multicast Routing Interface Table
-- --
ipMRouteInterfaceTable OBJECT-TYPE ipMRouteInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteInterfaceEntry SYNTAX SEQUENCE OF IpMRouteInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containg multicast routing "The (conceptual) table containing multicast routing
information specific to interfaces." information specific to interfaces."
::= { ipMRoute 4 } ::= { ipMRoute 4 }
ipMRouteInterfaceEntry OBJECT-TYPE ipMRouteInterfaceEntry OBJECT-TYPE
SYNTAX IpMRouteInterfaceEntry SYNTAX IpMRouteInterfaceEntry
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 a particular interface." information for a particular interface."
skipping to change at page 17, line 4 skipping to change at page 14, line 33
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the interface for which this entry "The ifIndex value of the interface for which this entry
contains information." contains information."
::= { ipMRouteInterfaceEntry 1 } ::= { ipMRouteInterfaceEntry 1 }
ipMRouteInterfaceTtl OBJECT-TYPE ipMRouteInterfaceTtl OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
Draft IPv4 Multicast Routing MIB July 2000
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 TTL threshold for the interface. Any IP
multicast datagrams with a TTL less than this threshold will multicast datagrams with a TTL less than this threshold will
not be forwarded out the interface. The default value of 0 not be forwarded out the interface. The default value of 0
means all multicast packets are forwarded out the means all multicast packets are forwarded out the
interface." interface."
::= { ipMRouteInterfaceEntry 2 } ::= { ipMRouteInterfaceEntry 2 }
skipping to change at page 18, line 4 skipping to change at page 15, line 30
on the interface, including framing characters. This object on the interface, including framing characters. This object
is similar to ifInOctets in the Interfaces MIB, except that is similar to ifInOctets in the Interfaces MIB, except that
only multicast packets are counted." only multicast packets are counted."
::= { ipMRouteInterfaceEntry 5 } ::= { ipMRouteInterfaceEntry 5 }
ipMRouteInterfaceOutMcastOctets OBJECT-TYPE ipMRouteInterfaceOutMcastOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft IPv4 Multicast Routing MIB July 2000
"The number of octets of multicast packets that have been "The number of octets of multicast packets that have been
sent on the interface." sent on the interface."
::= { ipMRouteInterfaceEntry 6 } ::= { ipMRouteInterfaceEntry 6 }
ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE ipMRouteInterfaceHCInMcastOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of multicast packets that have arrived "The number of octets of multicast packets that have arrived
skipping to change at page 19, line 5 skipping to change at page 16, line 8
ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of multicast packets that have been "The number of octets of multicast packets that have been
sent on the interface. This object is a 64-bit version of sent on the interface. This object is a 64-bit version of
ipMRouteInterfaceOutMcastOctets." ipMRouteInterfaceOutMcastOctets."
::= { ipMRouteInterfaceEntry 8 } ::= { ipMRouteInterfaceEntry 8 }
Draft IPv4 Multicast Routing MIB July 2000
-- --
-- The IP Multicast Scope Boundary Table -- The IP Multicast Scope Boundary Table
-- --
ipMRouteBoundaryTable OBJECT-TYPE ipMRouteBoundaryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteBoundaryEntry SYNTAX SEQUENCE OF IpMRouteBoundaryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the router's scoped "The (conceptual) table listing the router's scoped
skipping to change at page 20, line 4 skipping to change at page 17, line 5
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 out this associated address/mask range will not be forwarded out this
interface." interface."
::= { ipMRouteBoundaryEntry 1 } ::= { ipMRouteBoundaryEntry 1 }
ipMRouteBoundaryAddress OBJECT-TYPE ipMRouteBoundaryAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
Draft IPv4 Multicast Routing MIB July 2000
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group address which when combined with the "The group address which when combined with the
corresponding value of ipMRouteBoundaryAddressMask corresponding value of ipMRouteBoundaryAddressMask
identifies the group range for which the scoped boundary identifies the group range for which the scoped boundary
exists. Scoped addresses must come from the range 239.x.x.x exists. Scoped addresses must come from the range 239.x.x.x
as specified in RFC 2365." as specified in RFC 2365."
::= { ipMRouteBoundaryEntry 2 } ::= { ipMRouteBoundaryEntry 2 }
ipMRouteBoundaryAddressMask OBJECT-TYPE ipMRouteBoundaryAddressMask OBJECT-TYPE
skipping to change at page 21, line 4 skipping to change at page 17, line 49
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the multicast scope names." "The (conceptual) table listing the multicast scope names."
::= { ipMRoute 6 } ::= { ipMRoute 6 }
ipMRouteScopeNameEntry OBJECT-TYPE ipMRouteScopeNameEntry OBJECT-TYPE
SYNTAX IpMRouteScopeNameEntry SYNTAX IpMRouteScopeNameEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
Draft IPv4 Multicast Routing MIB July 2000
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the ipMRouteScopeNameTable "An entry (conceptual row) in the ipMRouteScopeNameTable
representing a multicast scope name." representing a multicast scope name."
INDEX { ipMRouteScopeNameAddress, INDEX { ipMRouteScopeNameAddress,
ipMRouteScopeNameAddressMask, ipMRouteScopeNameAddressMask,
IMPLIED ipMRouteScopeNameLanguage } IMPLIED ipMRouteScopeNameLanguage }
::= { ipMRouteScopeNameTable 1 } ::= { ipMRouteScopeNameTable 1 }
IpMRouteScopeNameEntry ::= SEQUENCE { IpMRouteScopeNameEntry ::= SEQUENCE {
ipMRouteScopeNameAddress IpAddress, ipMRouteScopeNameAddress IpAddress,
ipMRouteScopeNameAddressMask IpAddress, ipMRouteScopeNameAddressMask IpAddress,
ipMRouteScopeNameLanguage LanguageTag, ipMRouteScopeNameLanguage LanguageTag,
ipMRouteScopeNameString SnmpAdminString, ipMRouteScopeNameString SnmpAdminString,
skipping to change at page 22, line 4 skipping to change at page 18, line 47
corresponding value of ipMRouteScopeNameAddress identifies corresponding value of ipMRouteScopeNameAddress identifies
the group range associated with the multicast scope." the group range associated with the multicast scope."
::= { ipMRouteScopeNameEntry 2 } ::= { ipMRouteScopeNameEntry 2 }
ipMRouteScopeNameLanguage OBJECT-TYPE ipMRouteScopeNameLanguage OBJECT-TYPE
SYNTAX LanguageTag SYNTAX LanguageTag
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RFC 1766-style language tag associated with the scope "The RFC 1766-style language tag associated with the scope
Draft IPv4 Multicast Routing MIB July 2000
name." name."
::= { ipMRouteScopeNameEntry 3 } ::= { ipMRouteScopeNameEntry 3 }
ipMRouteScopeNameString OBJECT-TYPE ipMRouteScopeNameString OBJECT-TYPE
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
skipping to change at page 23, line 5 skipping to change at page 19, line 35
ipMRouteScopeNameStatus OBJECT-TYPE ipMRouteScopeNameStatus 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 new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table." created, or old entries deleted from this table."
::= { ipMRouteScopeNameEntry 6 } ::= { ipMRouteScopeNameEntry 6 }
Draft IPv4 Multicast Routing MIB July 2000
-- conformance information -- conformance information
ipMRouteMIBConformance ipMRouteMIBConformance
OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 } OBJECT IDENTIFIER ::= { ipMRouteStdMIB 2 }
ipMRouteMIBCompliances ipMRouteMIBCompliances
OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 }
ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 }
-- compliance statements -- compliance statements
skipping to change at page 24, line 4 skipping to change at page 20, line 30
GROUP ipMRouteMIBHCInterfaceGroup GROUP ipMRouteMIBHCInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network interfaces "This group is mandatory only for those network interfaces
for which the value of the corresponding instance of ifSpeed for which the value of the corresponding instance of ifSpeed
is greater than 20,000,000 bits/second." is greater than 20,000,000 bits/second."
::= { ipMRouteMIBCompliances 1 } ::= { ipMRouteMIBCompliances 1 }
-- units of conformance -- units of conformance
Draft IPv4 Multicast Routing MIB July 2000
ipMRouteMIBBasicGroup OBJECT-GROUP ipMRouteMIBBasicGroup OBJECT-GROUP
OBJECTS { ipMRouteEnable, ipMRouteEntryCount, OBJECTS { ipMRouteEnable, ipMRouteEntryCount,
ipMRouteUpstreamNeighbor, ipMRouteInIfIndex, ipMRouteUpstreamNeighbor, ipMRouteInIfIndex,
ipMRouteUpTime, ipMRouteExpiryTime, ipMRouteUpTime, ipMRouteExpiryTime,
ipMRouteNextHopState, ipMRouteNextHopState,
ipMRouteNextHopUpTime, ipMRouteNextHopUpTime,
ipMRouteNextHopExpiryTime, ipMRouteNextHopExpiryTime,
ipMRouteNextHopProtocol, ipMRouteNextHopProtocol,
ipMRouteNextHopPkts, ipMRouteNextHopPkts,
skipping to change at page 25, line 5 skipping to change at page 21, line 30
::= { ipMRouteMIBGroups 3 } ::= { ipMRouteMIBGroups 3 }
ipMRouteMIBPktsOutGroup OBJECT-GROUP ipMRouteMIBPktsOutGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopPkts } OBJECTS { ipMRouteNextHopPkts }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of packet "A collection of objects to support management of packet
counters for each outgoing interface entry of a route." counters for each outgoing interface entry of a route."
::= { ipMRouteMIBGroups 4 } ::= { ipMRouteMIBGroups 4 }
Draft IPv4 Multicast Routing MIB July 2000
ipMRouteMIBHCInterfaceGroup OBJECT-GROUP ipMRouteMIBHCInterfaceGroup OBJECT-GROUP
OBJECTS { ipMRouteInterfaceHCInMcastOctets, OBJECTS { ipMRouteInterfaceHCInMcastOctets,
ipMRouteInterfaceHCOutMcastOctets, ipMRouteInterfaceHCOutMcastOctets,
ipMRouteHCOctets } ipMRouteHCOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information specific to "A collection of objects providing information specific to
high speed (greater than 20,000,000 bits/second) network high speed (greater than 20,000,000 bits/second) network
interfaces." interfaces."
::= { ipMRouteMIBGroups 5 } ::= { ipMRouteMIBGroups 5 }
skipping to change at page 26, line 4 skipping to change at page 22, line 12
ipMRouteMIBPktsGroup OBJECT-GROUP ipMRouteMIBPktsGroup OBJECT-GROUP
OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets, OBJECTS { ipMRoutePkts, ipMRouteDifferentInIfPackets,
ipMRouteOctets } ipMRouteOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of packet "A collection of objects to support management of packet
counters for each forwarding entry." counters for each forwarding entry."
::= { ipMRouteMIBGroups 7 } ::= { ipMRouteMIBGroups 7 }
END END
Draft IPv4 Multicast Routing MIB July 2000
6. IANA Considerations
The ipMRouteRtProto, ipMRouteNextHopProtocol, ipMRouteInterfaceProtocol,
and ipMRouteProtocol use textual conventions imported from the IANA-
RTPROTO-MIB. The purpose of defining these textual conventions in a
separate MIB module is to allow additional values to be defined without
having to issue a new version of this document. The Internet Assigned
Numbers Authority (IANA) is responsible for the assignment of all
Internet numbers, including various SNMP-related numbers; it will
administer the values associated with these textual conventions.
The rules for additions or changes to the IANA-RTPROTO-MIB are outlined
in the DESCRIPTION clause associated with its MODULE-IDENTITY statement.
The current versions of the IANA-RTPROTO-MIB can be accessed from the
IANA home page at: "http://www.iana.org/".
7. Security Considerations
This MIB contains readable objects whose values provide information
related to multicast routing, including information on what machines are
sending to which groups. There are also a number of objects that have a
MAX-ACCESS clause of read-write and/or read-create, such as those which
allow an administrator to configure multicast boundaries.
While unauthorized access to the readable objects is relatively
innocuous, unauthorized access to the write-able objects could cause a
denial of service, or could cause wider distribution of packets intended
only for local distribution. Hence, the support for SET operations in a
non-secure environment without proper protection can have a negative
effect on network operations.
SNMPv1 by itself is such an insecure environment. 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 SET
(change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2574 [12] and the View-based Access Control
Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to this MIB, is properly configured to give access to
Draft IPv4 Multicast Routing MIB July 2000
those objects only to those principals (users) that have legitimate
rights to access them.
8. IANA Routing Protocol Registration MIB
This appendix defines the initial content of the IANA-RTPROTO-MIB.
NOTE TO RFC-EDITOR: This section should be removed from this document
prior to its publication, at which time this MIB will be administered by
IANA.
IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaipRouteProtocol MODULE-IDENTITY
LAST-UPDATED "200001311200Z" -- January 31, 2000
ORGANIZATION "IANA"
CONTACT-INFO
" Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
Phone: +1 310 823 9358
EMail: iana@iana.org"
DESCRIPTION
"This MIB module defines the IANAipRouteProtocol and
IANAipMRouteProtocol textual conventions for use in MIBs
which need to identify unicast or multicast routing
mechanisms.
Any additions or changes to the contents of this MIB module
require either publication of an RFC, or Designated Expert
Review as defined in the Guidelines for Writing IANA
Considerations Section document. The Designated Expert will
be selected by the IESG Area Director(s) of the Routing
Area."
::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA
IANAipRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current
Draft IPv4 Multicast Routing MIB July 2000
DESCRIPTION
"A mechanism for learning routes. Inclusion of values for
routing protocols is not intended to imply that those
protocols need be supported."
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
-- the following are all dynamic 5. IANA Considerations
-- routing protocols
egp (5), -- Exterior Gateway Protocol The ipMRouteRtProto, ipMRouteNextHopProtocol,
ggp (6), -- Gateway-Gateway Protocol ipMRouteInterfaceProtocol, and ipMRouteProtocol use textual
hello (7), -- FuzzBall HelloSpeak conventions imported from the IANA-RTPROTO-MIB. The purpose of
rip (8), -- Berkeley RIP or RIP-II defining these textual conventions in a separate MIB module is to
isIs (9), -- Dual IS-IS allow additional values to be defined without having to issue a new
esIs (10), -- ISO 9542 version of this document. The Internet Assigned Numbers Authority
ciscoIgrp (11), -- Cisco IGRP (IANA) is responsible for the assignment of all Internet numbers,
bbnSpfIgp (12), -- BBN SPF IGP including various SNMP-related numbers; it will administer the values
ospf (13), -- Open Shortest Path First associated with these textual conventions.
bgp (14), -- Border Gateway Protocol
idpr (15), -- InterDomain Policy Routing
ciscoEigrp (16), -- Cisco EIGRP
dvmrp (17) -- DVMRP
}
IANAipMRouteProtocol ::= TEXTUAL-CONVENTION The rules for additions or changes to the IANA-RTPROTO-MIB are
STATUS current outlined in the DESCRIPTION clause associated with its MODULE-
DESCRIPTION IDENTITY statement.
"The multicast routing protocol. Inclusion of values for
multicast routing protocols is not intended to imply that
those protocols need be supported."
SYNTAX INTEGER {
other(1), -- none of the following
local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol
dvmrp(4),
mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7),
pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DM
igmpOnly(10),
Draft IPv4 Multicast Routing MIB July 2000 The current versions of the IANA-RTPROTO-MIB can be accessed from the
IANA home page at: "http://www.iana.org/".
bgmp(11), 6. Security Considerations
msdp(12)
}
END This MIB contains readable objects whose values provide information
related to multicast routing, including information on what machines
are sending to which groups. There are also a number of objects that
have a MAX-ACCESS clause of read-write and/or read-create, such as
those which allow an administrator to configure multicast boundaries.
9. Intellectual Property Notice While unauthorized access to the readable objects is relatively
innocuous, unauthorized access to the write-able objects could cause
a denial of service, or could cause wider distribution of packets
intended only for local distribution. Hence, the support for SET
operations in a non-secure environment without proper protection can
have a negative effect on network operations.
The IETF takes no position regarding the validity or scope of any SNMPv1 by itself is such an insecure environment. Even if the
intellectual property or other rights that might be claimed to pertain network itself is secure (for example by using IPSec), even then,
to the implementation or use of the technology described in this there is no control as to who on the secure network is allowed to
document or the extent to which any license under such rights might or access and SET (change/create/delete) the objects in this MIB.
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication 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 Secretariat.
The IETF invites any interested party to bring to its attention any It is recommended that the implementers consider the security
copyrights, patents or patent applications, or other proprietary rights features as provided by the SNMPv3 framework. Specifically, the use
which may cover technology that may be required to practice this of the User-based Security Model RFC 2574 [12] and the View-based
standard. Please address the information to the IETF Executive Access Control Model RFC 2575 [15] is recommended.
Director.
10. Acknowledgements It is then a customer/user responsibility to ensure that the SNMP
entity giving access to this MIB, is properly configured to give
access to those objects only to those principals (users) that have
legitimate rights to access them.
This MIB module was updated based on feedback from the IETF's Inter- 7. Intellectual Property Notice
Domain Multicast Routing (IDMR) Working Group.
11. Authors' Addresses The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 Secretariat.
Keith McCloghrie The IETF invites any interested party to bring to its attention any
cisco Systems, Inc. copyrights, patents or patent applications, or other proprietary
170 West Tasman Drive rights which may cover technology that may be required to practice
San Jose, CA 95134-1706 this standard. Please address the information to the IETF Executive
Phone: +1 408 526 5260 Director.
Draft IPv4 Multicast Routing MIB July 2000 8. Acknowledgements
EMail: kzm@cisco.com This MIB module was updated based on feedback from the IETF's Inter-
Domain Multicast Routing (IDMR) Working Group.
Dino Farinacci 9. Authors' Addresses
cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
Phone: +1 408 526 4696
EMail: dino@cisco.com
Dave Thaler Keith McCloghrie
Microsoft Corporation cisco Systems, Inc.
One Microsoft Way 170 West Tasman Drive
Redmond, WA 98052-6399 San Jose, CA 95134-1706
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com
12. References Phone: +1 408 526 5260
EMail: kzm@cisco.com
[1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for Dino Farinacci
Describing SNMP Management Frameworks", RFC 2571, Cabletron Procket Networks
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 3850 North First Street
1999. San Jose, CA 95134
[2] Rose, M., and K. McCloghrie, "Structure and Identification of Phone: +1 408-954-7909
Management Information for TCP/IP-based Internets", RFC 1155, STD Email: dino@procket.com
16, Performance Systems International, Hughes LAN Systems, May
1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, Dave Thaler
STD 16, Performance Systems International, Hughes LAN Systems, Microsoft Corporation
March 1991. One Microsoft Way
Redmond, WA 98052-6399
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", Phone: +1 425 703 8835
RFC 1215, Performance Systems International, March 1991. EMail: dthaler@microsoft.com
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 10. References
and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU
Braunschweig, SNMP Research, First Virtual Holdings, International
Network Services, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [1] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for
and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD Describing SNMP Management Frameworks", RFC 2571, April 1999.
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First
Draft IPv4 Multicast Routing MIB July 2000 [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
Virtual Holdings, International Network Services, April 1999. [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [4] Rose, M., "A Convention for Defining Traps for use with the
and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, SNMP", RFC 1215, March 1991.
STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research,
First Virtual Holdings, International Network Services, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Management Protocol", RFC 1157, STD 15, SNMP Research, Performance M. and S. Waldbusser, "Structure of Management Information
Systems International, Performance Systems International, MIT Version 2 (SMIv2)", STD 58, RFC 2578, STD 58, April 1999.
Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., RFC 2579, April 1999.
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Mappings for Version 2 of the Simple Network Management Protocol M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 58, RFC 2580, April 1999.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Processing and Dispatching for the Simple Network Management Network Management Protocol", STD 15, RFC 1157, May 1990.
Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC "Introduction to Community-based SNMPv2", RFC 1901, January
2574, IBM T. J. Watson Research, April 1999. 1996.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Operations for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1906, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
2573, SNMP Research, Inc., Secure Computing Corporation, Cisco Processing and Dispatching for the Simple Network Management
Systems, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
Control Model (VACM) for the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., (SNMPv3)", RFC 2574, April 1999.
Draft IPv4 Multicast Routing MIB July 2000 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, January 1996.
Cisco Systems, Inc., April 1999. [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999.
[16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
thesis, Electrical Engineering Dept., Stanford University, December Control Model (VACM) for the Simple Network Management Protocol
1991. (SNMP)", RFC 2575, April 1999.
[17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD
Multicast Routing Protocol", RFC 1075, November 1988. thesis, Electrical Engineering Dept., Stanford University,
December 1991.
[18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., [17] Waitzman, D., Partridge, C. and S. Deering, "Distance Vector
Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, Multicast Routing Protocol", RFC 1075, November 1988.
"Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol
Specification", RFC 2362, June 1998.
[19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode Handley, M., Jacobson, V., Liu, C., Sharma, P. and L. Wei,
Specification". Work in progress, May 1997. "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol
Specification", RFC 2362, June 1998.
[20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A.
and L. Wei, "Protocol Independent Multicast Version 2, Dense
Mode Specification", Work in Progress.
[21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994.
Routing", RFC 2189, September 1997.
[22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, BCP [21] Ballardie, A., "Core Based Trees (CBT version 2) Multicast
23, July 1998. Routing", RFC 2189, September 1997.
13. Full Copyright Statement [22] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, RFC
2365, July 1998.
Copyright (C) The Internet Society (1999). All Rights Reserved. 11. Full Copyright Statement
This document and translations of it may be copied and furnished to Copyright (C) The Internet Society (2000). All Rights Reserved.
others, and derivative works that comment on or otherwise explain it or
assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
Draft IPv4 Multicast Routing MIB July 2000 This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents Acknowledgement
1 Abstract ........................................................ 2 Funding for the RFC Editor function is currently provided by the
2 Introduction .................................................... 2 Internet Society.
3 The SNMP Management Framework ................................... 2
4 Overview ........................................................ 3
5 Definitions ..................................................... 4
6 IANA Considerations ............................................. 26
7 Security Considerations ......................................... 26
8 IANA Routing Protocol Registration MIB .......................... 27
9 Intellectual Property Notice .................................... 29
10 Acknowledgements ............................................... 29
11 Authors' Addresses ............................................. 29
12 References ..................................................... 30
13 Full Copyright Statement ....................................... 32
 End of changes. 108 change blocks. 
439 lines changed or deleted 264 lines changed or added

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