< draft-ietf-idmr-multicast-routmib-13.txt   draft-ietf-idmr-multicast-routmib-14.txt >
IDMR Working Group Keith McCloghrie IDMR Working Group Keith McCloghrie
INTERNET-DRAFT Dino Farinacci INTERNET-DRAFT Dino Farinacci
Expires July 2000 cisco Systems Expires January 2000 cisco Systems
Dave Thaler Dave Thaler
Microsoft Microsoft
31 January 2000 7 July 2000
IPv4 Multicast Routing MIB IPv4 Multicast Routing MIB
<draft-ietf-idmr-multicast-routmib-13.txt> <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 is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 5 skipping to change at page 2, line 5
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Draft IPv4 Multicast Routing MIB January 2000 Draft IPv4 Multicast Routing MIB July 2000
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing IP Multicast Routing for IPv4, independent of the specific managing IP Multicast Routing for IPv4, independent of the specific
multicast routing protocol in use. multicast routing protocol in use.
2. Introduction 2. Introduction
skipping to change at page 3, line 5 skipping to change at page 3, line 5
protocol, which is not an Internet standards track protocol, is protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o Protocol operations for accessing management information. The first o Protocol operations for accessing management information. The first
set of protocol operations and associated PDU formats is described set of protocol operations and associated PDU formats is described
in RFC 1157 [8]. A second set of protocol operations and associated in RFC 1157 [8]. A second set of protocol operations and associated
PDU formats is described in RFC 1905 [13]. PDU formats is described in RFC 1905 [13].
Draft IPv4 Multicast Routing MIB January 2000 Draft IPv4 Multicast Routing MIB July 2000
o A set of fundamental applications described in RFC 2573 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2575 [15]. the view-based access control mechanism described in RFC 2575 [15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI. using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
skipping to change at page 4, line 5 skipping to change at page 4, line 5
(3) the IP Multicast Routing Interface Table containing multicast (3) the IP Multicast Routing Interface Table containing multicast
routing information specific to interfaces. routing information specific to interfaces.
(4) the IP Multicast Scope Boundary Table containing the boundaries (4) the IP Multicast Scope Boundary Table containing the boundaries
configured for multicast scopes [22]. configured for multicast scopes [22].
(5) the IP Multicast Scope Name Table containing human-readable names (5) the IP Multicast Scope Name Table containing human-readable names
of multicast scope. of multicast scope.
Draft IPv4 Multicast Routing MIB January 2000 Draft IPv4 Multicast Routing MIB July 2000
5. Definitions 5. 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,
skipping to change at page 5, line 4 skipping to change at page 5, line 4
"Initial version, published as RFC xxxx (to be filled in by "Initial version, published as RFC xxxx (to be filled in by
RFC-Editor)." RFC-Editor)."
::= { mib-2 XX } ::= { mib-2 XX }
-- NOTE TO RFC EDITOR: When this document is published as -- NOTE TO RFC EDITOR: When this document is published as
-- an RFC, replace XX with IANA-assigned number, -- an RFC, replace XX with IANA-assigned number,
-- and delete this comment. -- and delete this comment.
-- Textual Conventions -- Textual Conventions
LanguageTag ::= TEXTUAL-CONVENTION LanguageTag ::= TEXTUAL-CONVENTION
Draft IPv4 Multicast Routing MIB July 2000
Draft IPv4 Multicast Routing MIB January 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
Draft IPv4 Multicast Routing MIB January 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 7, 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 January 2000 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
skipping to change at page 8, line 5 skipping to change at page 8, line 5
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 January 2000 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 }
skipping to change at page 9, line 5 skipping to change at page 9, line 5
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 January 2000 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
skipping to change at page 10, line 5 skipping to change at page 10, line 5
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 January 2000 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
skipping to change at page 11, line 5 skipping to change at page 11, line 5
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 January 2000 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
(instead or in addition) due to local configuration, such as (instead or in addition) due to local configuration, such as
when running PIM over RIP. A value of multicast means that when running PIM over RIP. A value of multicast means that
skipping to change at page 12, line 5 skipping to change at page 12, line 5
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 January 2000 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
skipping to change at page 13, line 5 skipping to change at page 13, line 5
"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 January 2000 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,
skipping to change at page 14, line 5 skipping to change at page 14, line 5
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 January 2000 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 }
skipping to change at page 15, line 5 skipping to change at page 15, line 5
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 January 2000 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 dos 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."
skipping to change at page 16, line 5 skipping to change at page 16, line 5
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 January 2000 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
skipping to change at page 17, line 5 skipping to change at page 17, line 5
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 January 2000 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 5 skipping to change at page 18, line 5
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 January 2000 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
skipping to change at page 19, line 5 skipping to change at page 19, line 5
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 January 2000 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
skipping to change at page 20, line 5 skipping to change at page 20, line 5
"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 January 2000 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 }
skipping to change at page 21, line 5 skipping to change at page 21, line 5
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 January 2000 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 {
skipping to change at page 22, line 5 skipping to change at page 22, line 5
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 January 2000 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
skipping to change at page 23, line 5 skipping to change at page 23, line 5
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 January 2000 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 24, line 4
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
Draft IPv4 Multicast Routing MIB January 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 25, line 5
::= { 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 January 2000 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."
skipping to change at page 26, line 4 skipping to change at page 26, line 4
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
Draft IPv4 Multicast Routing MIB January 2000
6. IANA Considerations 6. IANA Considerations
The The ipMRouteRtProto, ipMRouteNextHopProtocol, The ipMRouteRtProto, ipMRouteNextHopProtocol, ipMRouteInterfaceProtocol,
ipMRouteInterfaceProtocol, and ipMRouteProtocol use textual conventions and ipMRouteProtocol use textual conventions imported from the IANA-
imported from the IANA-RTPROTO-MIB. The purpose of defining these RTPROTO-MIB. The purpose of defining these textual conventions in a
textual conventions in a separate MIB module is to allow additional separate MIB module is to allow additional values to be defined without
values to be defined without having to issue a new version of this having to issue a new version of this document. The Internet Assigned
document. The Internet Assigned Numbers Authority (IANA) is responsible Numbers Authority (IANA) is responsible for the assignment of all
for the assignment of all Internet numbers, including various SNMP- Internet numbers, including various SNMP-related numbers; it will
related numbers; it will administer the values associated with these administer the values associated with these textual conventions.
textual conventions.
The rules for additions or changes to the IANA-RTPROTO-MIB are outlined The rules for additions or changes to the IANA-RTPROTO-MIB are outlined
in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. in the DESCRIPTION clause associated with its MODULE-IDENTITY statement.
The current versions of the IANA-RTPROTO-MIB can be accessed from the The current versions of the IANA-RTPROTO-MIB can be accessed from the
IANA home page at: "http://www.iana.org/". IANA home page at: "http://www.iana.org/".
7. Security Considerations 7. Security Considerations
This MIB contains readable objects whose values provide information This MIB contains readable objects whose values provide information
skipping to change at page 27, line 5 skipping to change at page 26, line 48
SNMPv1 by itself is such an insecure environment. Even if the network 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 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 control as to who on the secure network is allowed to access and SET
(change/create/delete) the objects in this MIB. (change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2574 [12] and the View-based Access Control based Security Model RFC 2574 [12] and the View-based Access Control
Model RFC 2575 [15] is recommended. Model RFC 2575 [15] is recommended.
Draft IPv4 Multicast Routing MIB January 2000
It is then a customer/user responsibility to ensure that the SNMP entity 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 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 those objects only to those principals (users) that have legitimate
rights to access them. rights to access them.
8. IANA Routing Protocol Registration MIB 8. IANA Routing Protocol Registration MIB
This appendix defines the initial content of the IANA-RTPROTO-MIB. This appendix defines the initial content of the IANA-RTPROTO-MIB.
NOTE TO RFC-EDITOR: This section should be removed from this document 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 prior to its publication, at which time this MIB will be administered by
IANA. IANA.
skipping to change at page 27, line 30 skipping to change at page 27, line 27
IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaipRouteProtocol MODULE-IDENTITY ianaipRouteProtocol MODULE-IDENTITY
LAST-UPDATED "200001311200Z" -- January 31, 2000 LAST-UPDATED "200001311200Z" -- January 31, 2000
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
Postal: USC/Information Sciences Institute 4676 Admiralty Way, Suite 330
4676 Admiralty Way, Marina del Rey, CA 90292 Marina del Rey, CA 90292-6601
Tel: +1 310 822 1511 Phone: +1 310 823 9358
E-Mail: iana@isi.edu" EMail: iana@iana.org"
DESCRIPTION DESCRIPTION
"This MIB module defines the IANAipRouteProtocol and "This MIB module defines the IANAipRouteProtocol and
IANAipMRouteProtocol textual conventions for use in IANAipMRouteProtocol textual conventions for use in MIBs
MIBs which need to identify unicast or multicast which need to identify unicast or multicast routing
routing mechanisms. mechanisms.
Any and all requests for additional values require Any additions or changes to the contents of this MIB module
proper documentation. Possible forms of documentation require either publication of an RFC, or Designated Expert
include, but are not limited to, RFCs. Other requests Review as defined in the Guidelines for Writing IANA
may also be accepted under the advice of a 'designated Considerations Section document. The Designated Expert will
expert'. (Contact the IANA for the contact information be selected by the IESG Area Director(s) of the Routing
of the current expert.)" Area."
::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA ::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA
Draft IPv4 Multicast Routing MIB January 2000
IANAipRouteProtocol ::= TEXTUAL-CONVENTION IANAipRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Draft IPv4 Multicast Routing MIB July 2000
DESCRIPTION DESCRIPTION
"A mechanism for learning routes. Inclusion of values for "A mechanism for learning routes. Inclusion of values for
routing protocols is not intended to imply that those routing protocols is not intended to imply that those
protocols need be supported." protocols need be supported."
SYNTAX INTEGER { SYNTAX INTEGER {
other (1), -- not specified other (1), -- not specified
local (2), -- local interface local (2), -- local interface
netmgmt (3), -- static route netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect icmp (4), -- result of ICMP Redirect
skipping to change at page 29, line 4 skipping to change at page 28, line 50
those protocols need be supported." those protocols need be supported."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- none of the following other(1), -- none of the following
local(2), -- e.g., manually configured local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol netmgmt(3), -- set via net.mgmt protocol
dvmrp(4), dvmrp(4),
mospf(5), mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7), cbt(7),
pimSparseMode(8), -- PIM-SM pimSparseMode(8), -- PIM-SM
Draft IPv4 Multicast Routing MIB January 2000
pimDenseMode(9), -- PIM-DM pimDenseMode(9), -- PIM-DM
igmpOnly(10), igmpOnly(10),
Draft IPv4 Multicast Routing MIB July 2000
bgmp(11), bgmp(11),
msdp(12) msdp(12)
} }
END END
9. Intellectual Property Notice 9. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to pertain
skipping to change at page 30, line 4 skipping to change at page 29, line 45
10. Acknowledgements 10. Acknowledgements
This MIB module was updated based on feedback from the IETF's Inter- This MIB module was updated based on feedback from the IETF's Inter-
Domain Multicast Routing (IDMR) Working Group. Domain Multicast Routing (IDMR) Working Group.
11. Authors' Addresses 11. Authors' Addresses
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
Draft IPv4 Multicast Routing MIB January 2000
San Jose, CA 95134-1706 San Jose, CA 95134-1706
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Draft IPv4 Multicast Routing MIB July 2000
EMail: kzm@cisco.com EMail: kzm@cisco.com
Dino Farinacci Dino Farinacci
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
Phone: +1 408 526 4696 Phone: +1 408 526 4696
EMail: dino@cisco.com EMail: dino@cisco.com
Dave Thaler Dave Thaler
skipping to change at page 31, line 5 skipping to change at page 30, line 48
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991. RFC 1215, Performance Systems International, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Structure of Management Information Version 2 and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU
Braunschweig, SNMP Research, First Virtual Holdings, International Braunschweig, SNMP Research, First Virtual Holdings, International
Network Services, April 1999. Network Services, April 1999.
Draft IPv4 Multicast Routing MIB January 2000
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD
58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First
Draft IPv4 Multicast Routing MIB July 2000
Virtual Holdings, International Network Services, April 1999. Virtual Holdings, International Network Services, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580,
STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research,
First Virtual Holdings, International Network Services, April 1999. First Virtual Holdings, International Network Services, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, STD 15, SNMP Research, Performance Management Protocol", RFC 1157, STD 15, SNMP Research, Performance
Systems International, Performance Systems International, MIT Systems International, Performance Systems International, MIT
skipping to change at page 32, line 5 skipping to change at page 31, line 49
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services, Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, April 1999. Systems, April 1999.
Draft IPv4 Multicast Routing MIB January 2000
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc.,
Draft IPv4 Multicast Routing MIB July 2000
Cisco Systems, Inc., April 1999. Cisco Systems, Inc., April 1999.
[16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD [16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD
thesis, Electrical Engineering Dept., Stanford University, December thesis, Electrical Engineering Dept., Stanford University, December
1991. 1991.
[17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector
Multicast Routing Protocol", RFC 1075, November 1988. Multicast Routing Protocol", RFC 1075, November 1988.
[18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
skipping to change at page 33, line 4 skipping to change at page 32, line 47
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implmentation may be prepared, copied, published and assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself 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 may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet which case the procedures for copyrights defined in the Internet
Draft IPv4 Multicast Routing MIB January 2000
Standards process must be followed, or as required to translate it into Standards process must be followed, or as required to translate it into
languages other than English. languages other than English.
Draft IPv4 Multicast Routing MIB July 2000
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 "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 48 change blocks. 
75 lines changed or deleted 72 lines changed or added

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