draft-ietf-mboned-msdp-mib-01.txt   rfc4624.txt 
MBONED Working Group Bill Fenner
INTERNET-DRAFT AT&T Research
Expires: April 2006 Dave Thaler
Microsoft
October 2005
Multicast Source Discovery protocol MIB
<draft-ietf-mboned-msdp-mib-01.txt>
Status of this Document
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware have
been or will be disclosed, and any of which he or she becomes aware will
be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Network Working Group B. Fenner
Force (IETF), its areas, and its working groups. Note that other groups Request for Comments: 4624 AT&T Research
may also distribute working documents as Internet-Drafts. Category: Experimental D. Thaler
Microsoft
Internet-Drafts are draft documents valid for a maximum of six months October 2006
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 Multicast Source Discovery Protocol (MSDP) MIB
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This document is a product of the MBONED Working Group. Comments should This memo defines an Experimental Protocol for the Internet
be addressed to the authors, or the mailing list at community. It does not specify an Internet standard of any kind.
mboned@lists.uoregon.edu. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management
Base (MIB) for use with network management protocols in the Internet Information Base (MIB) for use with network management protocols in
community. In particular, it describes managed objects used for the Internet community. In particular, it describes managed objects
managing Multicast Source Discovery Protocol (MSDP) (RFC 3618) speakers. used for managing Multicast Source Discovery Protocol (MSDP) (RFC
3618) speakers.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework. . . . . . . . . . . . 2 1. Introduction ....................................................2
2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 2. The Internet-Standard Management Framework ......................2
3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Overview ........................................................2
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Definitions .....................................................3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . . 31 5. Security Considerations ........................................28
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . . 32 6. IANA Considerations ............................................29
7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 32 7. Acknowledgements ...............................................30
8. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 32 8. References .....................................................30
9. Normative References. . . . . . . . . . . . . . . . . . . . . . . 33 8.1. Normative References ......................................30
9.1. Informative References . . . . . . . . . . . . . . . . . . . . 33 8.2. Informative References ....................................30
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 34
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of RFC
3410 [7].
Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. MIB objects are generally accessed
through the Simple Network Management Protocol (SNMP). Objects in the
MIB are defined using the mechanisms defined in the Structure of
Management Information (SMI). This memo specifies a MIB module that is
compliant to the SMIv2, which is described in STD 58, RFC 2578 [4], STD
58, RFC 2579 [5] and STD 58, RFC 2580 [6].
2. Revision History
A record of changes which will be removed before publication.
20 October 2005
Added explicit reasoning for IPv4-only-osity and for the
unorganized organization.
Updated Copyright and IPR statements.
Updated Security Considerations, per RFC4181.
Added IANA Considerations, per RFC4181.
Added REVISION and WG mailing list to MODULE-IDENTITY, per RFC4181.
Changed some TimeTicks to TimeStamp, on RFC4181's advice.
Added advice on non-volatile storage, row creation and column
modification to tables with RowStatus columns, per RFC4181.
Added msdpReadOnlyCompliance to permit implementations that don't
implement writing.
Clarified that msdpSAStatePeriod was an accidental duplication of
msdpCacheLifetime.
Described the epochs for TimeTicks objects, per RFC4181. Add a
note that msdpCacheLifetime would really be better as a
TimeInterval, but is TimeTicks for hysterical raisins.
Renamed to draft-ietf-mboned-msdp-mib-00.
Fixed spec references and defaults for msdpPeerHoldTimeConfigured,
msdpPeerKeepAliveConfigured and msdpPeerConnectRetryInterval, as
pointed out by Ketan Talaulikar.
Deprecated all objects related to SA-Requests and notifications,
since RFC 3618 doesn't have either one. As pointed out by Ketan
Talaulikar.
Clarified that msdpSACachePeerLearnedFrom should be 0.0.0.0 on the
originator. From Mike Davison.
Removed msdpSAStatePeriod. I couldn't figure out what it's for; at
best it should be SG State Period, but that's already
msdpCacheLifetime. From Mike Davison.
17 October 2003
Undid most of the hard work since draft -03, which is the only
implementation I was able to find by querying the MSDP mailing
list.
Republished with no changes. How did it get to be almost 2 years?
Since the INET-ADDRESS-MIB relaxed restrictions on InetAddressType,
remove msdpPeerLocalAddressType, rename msdpSACacheGroupAddrType to
msdpCacheAddrType, remove msdpCacheSourceAddrType,
msdpSACacheOriginRPType, msdpSACachePeerLearnedFromType,
msdpSACacheRPFPeerType.
Updated the DESCRIPTION of msdpRequestsTable to describe exactly
how it is used.
Added msdpPeerDiscontinuityTime.
Changed msdpPeerFsmEstablishedTime to a TimeStamp instead of a
counting number of seconds.
Changed msdpPeerInMessageElapsedTime to msdpPeerInMessageTime and
changed it to a TimeStamp.
Added msdpMeshGroupTable.
Updated conformance information.
Added msdpPeerIfIndex.
Converted all IpAddress items to InetAddressType/InetAddress pairs.
This bigtime violates RFC2578's rules about MIB evolution, so take
extra care when implementing this change.
Added msdpRequestsPriority, in order to allow configuration of
multiple peers to whom Requests will be sent. Note that this
violates RFC2578's rules about MIB evolution, so take extra care
when implementing this change.
Removed DEFVAL on scalars, since it should only be needed for table
row creation.
Removed msdpPeerSAAdvPeriod, since the spec changed to say its
value MUST be 60.
Added none(0) to msdpPeerEncapsulationType enumeration (is this OK?
should it be 4?)
Removed msdpPeerEncapsulationState since the encapsulation
"negotiation" was removed from the spec.
Added msdpRPAddress to specify the RP address to use when sourcing
SA messages.
Added msdpSACacheSourcePrefix to msdpSACacheTable, and added it to
the INDEX. Note that this violates RFC2578's rules about MIB
evolution, so take extra care when implementing this change.
Completely renumbered the MIB, removing the extra level of
msdpMIBobjects and creating an msdpScalars group to contain all
scalars. Note that this violates RFC2578's rules about MIB
evolution, so take extra care when implementing this change.
16 December 1999
Added msdpSAHoldDownPeriod, msdpPeerEncapsulationState,
msdpPeerEncapsulationType, msdpPeerConnectionAttempts,
msdpPeerInNotifications, msdpPeerOutNotifications, and
msdpLastError
Removed msdpPeerConfigMethod, since this has disappeared from the
spec.
Renamed the states in msdpPeerState to go with the state machine in
the spec.
Added msdpPeerLocalPort and msdpPeerRemotePort in order to provide
full information about the TCP connection in use. I'd like to
reorder the Peer Table but that can wait until the MIB gets
published as an RFC in order to only change things like that once.
Added msdpSACacheOriginRP as an INDEX to the msdpSACacheTable.
Note that this violates RFC2578's rules about MIB evolution, so
take extra care when implementing this change.
Renamed to DRAFT-MSDP-MIB. It will be renamed back to MSDP-MIB
when it gets renumbered under mib-2, in order to avoid module
naming problems.
Turned msdpSendRequestsTo into a table in order to handle 1. Introduction
administratively scoped groups with different RP's.
Added IANA-assigned experimental OID This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community. In particular, it describes managed objects
used for managing Multicast Source Discovery Protocol (MSDP) [1]
speakers.
Added msdpSendRequestsTo and msdpPeerProcessRequestsFrom to 2. The Internet-Standard Management Framework
configure MSDP SA-Request/Response processing.
Added msdpPeerDataTtl to allow TTL scoping of data packets For a detailed overview of the documents that describe the current
forwarded across MSDP peerings. Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [7].
Renumbered msdpSACacheInDataPackets and further items in Managed objects are accessed via a virtual information store, termed
msdpSACacheTable, to eliminate duplicate OIDs the Management Information Base or MIB. MIB objects are generally
initial version. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [4], STD 58, RFC 2579 [5] and STD 58, RFC 2580 [6].
3. Overview 3. Overview
This MIB module contains four scalars and four tables, one deprecated. This MIB module contains four scalars and four tables, one
The tables are: deprecated. The tables are:
o the deprecated Requests Table, containing the longest-match table o The deprecated Requests Table, containing the longest-match table
used to determine the peer to send SA-Requests to for a given used to determine the peer to send SA-Requests to for a given
group. This table is deprecated because Requests were removed from group. This table is deprecated because Requests were removed
MSDP before it became an RFC; from MSDP before it became an RFC.
o the Peer Table, containing information on the system's peers; o The Peer Table, containing information on the system's peers.
o the Source-Active Cache Table, containing the SA cache entries; and o The Source-Active (SA) Cache Table, containing the SA cache
entries.
o the Mesh Group Table, containing the list of MSDP mesh groups to o The Mesh Group Table, containing the list of MSDP mesh groups to
which this system belongs. which this system belongs.
This MIB module uses the IpAddress SYNTAX, making it only suitable for This MIB module uses the IpAddress SYNTAX, making it only suitable
IPv4 systems. Although the desired direction for MIBs is to use for IPv4 systems. Although the desired direction for MIBs is to use
InetAddressType/InetAddress pairs to allow both IPv4 and IPv6 (and InetAddressType/InetAddress pairs to allow both IPv4 and IPv6 (and
future formats as well), the MSDP protocol itself is IPv4-only, and the future formats as well), the MSDP protocol itself is IPv4-only, and
MSDP working group made an explicit decision to not create an IPv6 the MSDP working group made an explicit decision not to create an
version of the protocol. IPv6 version of the protocol.
This MIB module is somewhat disorganized, with scalars before and after This MIB module is somewhat disorganized, with scalars before and
tables, holes in the OID space, tables with the RowStatus in the middle, after tables, holes in the OID space, tables with the RowStatus in
and so on. This is because objects were added and removed as necessary the middle, and so on. This is because objects were added and
as the MSDP protocol evolved, and the plan was to renumber the whole MIB removed as necessary as the MSDP protocol evolved, and the plan was
when moving to the standard mib-2 tree. The MSDP Working Group then to renumber the whole MIB when moving to the standard mib-2 tree.
changed direction, publishing the MSDP protcol as Experimental. Since The MSDP Working Group then changed direction, publishing the MSDP
there were existing implementations using the strange object order under protocol as Experimental. Since there were existing implementations
the experimental OID, the WG decided not to renumber the MIB and to using the strange object order under the experimental OID, the WG
publish it as experimental, keeping the experimental OID. decided not to renumber the MIB and to publish it as experimental,
keeping the experimental OID.
4. Definitions 4. Definitions
-- --
-- --
DRAFT-MSDP-MIB DEFINITIONS ::= BEGIN MSDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Counter32, Gauge32, TimeTicks, Integer32, experimental, Counter32, Gauge32, TimeTicks, Integer32,
IpAddress IpAddress
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, TruthValue, TimeStamp, DisplayString RowStatus, TruthValue, TimeStamp, DisplayString
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
msdpMIB MODULE-IDENTITY msdpMIB MODULE-IDENTITY
LAST-UPDATED "200510210000Z" LAST-UPDATED "200608010000Z"
ORGANIZATION "IETF MBONED Working Group" ORGANIZATION "IETF MBONED Working Group"
CONTACT-INFO CONTACT-INFO
"Bill Fenner "Bill Fenner
75 Willow Road 75 Willow Road
Menlo Park, CA 94025 Menlo Park, CA 94025
Phone: +1 650 867 6073 Phone: +1 650 867 6073
E-mail: fenner@research.att.com E-mail: fenner@research.att.com
Dave Thaler Dave Thaler
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone: +1 425 703 8835 Phone: +1 425 703 8835
Email: dthaler@microsoft.com Email: dthaler@microsoft.com
MBONED Working Group: mboned@lists.uoregon.edu" MBONED Working Group: mboned@lists.uoregon.edu"
DESCRIPTION DESCRIPTION
"An experimental MIB module for MSDP Management and "An experimental MIB module for MSDP Management and
Monitoring. Monitoring.
Copyright (C) The Internet Society 2005. This version of Copyright (C) The Internet Society 2006. This version of
this MIB module is part of RFC XXXX; see the RFC itself for this MIB module is part of RFC 4624; see the RFC itself
full legal notices." for full legal notices."
REVISION "200510210000Z" REVISION "200608010000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC 4624."
::= { experimental 92 } ::= { experimental 92 }
msdpMIBobjects OBJECT IDENTIFIER ::= { msdpMIB 1 } msdpMIBobjects OBJECT IDENTIFIER ::= { msdpMIB 1 }
msdp OBJECT IDENTIFIER ::= { msdpMIBobjects 1 } msdp OBJECT IDENTIFIER ::= { msdpMIBobjects 1 }
msdpEnabled OBJECT-TYPE msdpEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of MSDP on this MSDP speaker - globally enabled or "The state of MSDP on this MSDP speaker - globally enabled
disabled. or disabled.
Changes to this object should be stored to non-volatile Changes to this object should be stored to non-volatile
memory." memory."
::= { msdp 1 } ::= { msdp 1 }
msdpCacheLifetime OBJECT-TYPE msdpCacheLifetime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime given to SA cache entries when created or "The lifetime given to SA cache entries when created or
refreshed. This is the [SG-State-Period] in the MSDP spec. refreshed. This is the [SG-State-Period] in the MSDP
A value of 0 means no SA caching is done by this MSDP spec. A value of 0 means no SA caching is done by this
speaker. MSDP speaker.
Changes to this object should be stored to non-volatile Changes to this object should be stored to non-volatile
memory. memory.
This object does not measure time per se; instead, it is the This object does not measure time per se; instead, it
delta from the time at which an SA message is received at is the delta from the time at which an SA message is
which it should be expired if not refreshed. (i.e., it is received at which it should be expired if not refreshed.
the value of msdpSACacheExpiryTime immediately after (i.e., it is the value of msdpSACacheExpiryTime
receiving an SA message applying to that row.) As such, immediately after receiving an SA message applying to
TimeInterval would be a more appropriate SYNTAX; it remains that row.) As such, TimeInterval would be a more
TimeTicks for backwards compatability." appropriate SYNTAX; it remains TimeTicks for backwards
compatibility."
REFERENCE "RFC 3618 section 5.3" REFERENCE "RFC 3618 section 5.3"
::= { msdp 2 } ::= { msdp 2 }
msdpNumSACacheEntries OBJECT-TYPE msdpNumSACacheEntries OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of entries in the SA Cache table." "The total number of entries in the SA Cache table."
::= { msdp 3 } ::= { msdp 3 }
skipping to change at page 9, line 10 skipping to change at page 5, line 28
-- This object was introduced in error, with a similar definition -- This object was introduced in error, with a similar definition
-- to msdpCacheLifetime. -- to msdpCacheLifetime.
-- msdpSAStatePeriod OBJECT-TYPE -- msdpSAStatePeriod OBJECT-TYPE
-- ::= { msdp 10 } -- ::= { msdp 10 }
msdpRPAddress OBJECT-TYPE msdpRPAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RP address used when sourcing MSDP SA messages. May be "The Rendezvous Point (RP) address used when sourcing
0.0.0.0 on non-RP's. MSDP SA messages. May be 0.0.0.0 on non-RPs.
Changes to this object should be stored to non-volatile Changes to this object should be stored to non-volatile
memory." memory."
::= { msdp 11 } ::= { msdp 11 }
-- --
-- The MSDP Requests table -- The MSDP Requests table
-- SA Requests were removed from the MSDP spec, so this entire table -- SA Requests were removed from the MSDP spec, so this entire table
-- is deprecated. -- is deprecated.
msdpRequestsTable OBJECT-TYPE msdpRequestsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MsdpRequestsEntry SYNTAX SEQUENCE OF MsdpRequestsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The (conceptual) table listing group ranges and MSDP peers "The (conceptual) table listing group ranges and MSDP peers
used when deciding where to send an SA Request message when used when deciding where to send an SA Request message, when
required. If SA Requests are not enabled, this table may be required. If SA Requests are not enabled, this table may be
empty. empty.
In order to choose a peer to whom to send an SA Request for In order to choose a peer to whom to send an SA Request for
a given group G, the subset of entries in this table whose a given group, G, the subset of entries in this table whose
(msdpRequestsPeerType, msdpRequestsPeer) tuple represents a (msdpRequestsPeerType, msdpRequestsPeer) tuple represents a
peer whose msdpPeerState is established are examined. The peer whose msdpPeerState is established are examined. The
set is further reduced by examining only those entries for set is further reduced by examining only those entries for
which msdpPeerRequestsGroupAddressType equals the address which msdpPeerRequestsGroupAddressType equals the address
type of G, and the entries with the highest value of type of G. The entries with the highest value of
msdpRequestsGroupPrefix are considered, where the group G msdpRequestsGroupPrefix are considered, where the group G
falls within the range described by the combination of falls within the range described by the combination of
msdpRequestsGroup and msdpRequestsGroupPrefix. (This msdpRequestsGroup and msdpRequestsGroupPrefix. (This
sequence is commonly known as a 'longest-match' lookup.) sequence is commonly known as a 'longest-match' lookup.)
Finally, if multiple entries remain, the entry with the Finally, if multiple entries remain, the entry with the
lowest value of msdpRequestsPriority is chosen. The SA lowest value of msdpRequestsPriority is chosen. The SA
Request message is sent to the peer described by this row." Request message is sent to the peer described by this row."
::= { msdp 4 } ::= { msdp 4 }
msdpRequestsEntry OBJECT-TYPE msdpRequestsEntry OBJECT-TYPE
SYNTAX MsdpRequestsEntry SYNTAX MsdpRequestsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing a group range used "An entry (conceptual row) representing a group range
when deciding where to send an SA Request message." used when deciding where to send an SA Request
message."
INDEX { msdpRequestsGroupAddress, msdpRequestsGroupMask } INDEX { msdpRequestsGroupAddress, msdpRequestsGroupMask }
::= { msdpRequestsTable 1 } ::= { msdpRequestsTable 1 }
MsdpRequestsEntry ::= SEQUENCE { MsdpRequestsEntry ::= SEQUENCE {
msdpRequestsGroupAddress IpAddress, msdpRequestsGroupAddress IpAddress,
msdpRequestsGroupMask IpAddress, msdpRequestsGroupMask IpAddress,
msdpRequestsPeer IpAddress, msdpRequestsPeer IpAddress,
msdpRequestsStatus RowStatus msdpRequestsStatus RowStatus
} }
msdpRequestsGroupAddress OBJECT-TYPE msdpRequestsGroupAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The group address that, when combined with the mask in this "The group address that, when combined with the mask
entry, represents the group range to which this row in this entry, represents the group range to which
applies." this row applies."
::= { msdpRequestsEntry 1 } ::= { msdpRequestsEntry 1 }
msdpRequestsGroupMask OBJECT-TYPE msdpRequestsGroupMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The mask that, when combined with the group address in this "The mask that, when combined with the group address
entry, represents the group range to which this row in this entry, represents the group range to which
applies." this row applies."
::= { msdpRequestsEntry 2 } ::= { msdpRequestsEntry 2 }
msdpRequestsPeer OBJECT-TYPE msdpRequestsPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The peer to which MSDP SA Requests for groups matching this "The peer to which MSDP SA Requests for groups matching
entry's group range will be sent. This object combined with this entry's group range will be sent. This object,
msdpRequestsPeerType must match the INDEX of a row in the combined with msdpRequestsPeerType, must match the INDEX
msdpPeerTable, and to be considered, this peer's of a row in the msdpPeerTable, and to be considered,
msdpPeerState must be established." this peer's msdpPeerState must be established."
::= { msdpRequestsEntry 3 } ::= { msdpRequestsEntry 3 }
msdpRequestsStatus OBJECT-TYPE msdpRequestsStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The status of this row, by which new rows may be added to "The status of this row, by which new rows may be added
the table or old rows may be deleted." to the table or old rows may be deleted."
::= { msdpRequestsEntry 4 } ::= { msdpRequestsEntry 4 }
-- --
-- The MSDP Peer table -- The MSDP Peer table
-- --
msdpPeerTable OBJECT-TYPE msdpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MsdpPeerEntry SYNTAX SEQUENCE OF MsdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 11, line 30 skipping to change at page 7, line 49
::= { msdp 5 } ::= { msdp 5 }
msdpPeerEntry OBJECT-TYPE msdpPeerEntry OBJECT-TYPE
SYNTAX MsdpPeerEntry SYNTAX MsdpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing an MSDP peer. "An entry (conceptual row) representing an MSDP peer.
If row creation is supported, dynamically added rows are If row creation is supported, dynamically added rows are
added to the system's stable configuration (corresponding to added to the system's stable configuration (corresponding
a StorageType value of nonVolatile). " to a StorageType value of nonVolatile). "
INDEX { msdpPeerRemoteAddress } INDEX { msdpPeerRemoteAddress }
::= { msdpPeerTable 1 } ::= { msdpPeerTable 1 }
MsdpPeerEntry ::= SEQUENCE { MsdpPeerEntry ::= SEQUENCE {
msdpPeerRemoteAddress IpAddress, msdpPeerRemoteAddress IpAddress,
msdpPeerState INTEGER, msdpPeerState INTEGER,
msdpPeerRPFFailures Counter32, msdpPeerRPFFailures Counter32,
msdpPeerInSAs Counter32, msdpPeerInSAs Counter32,
msdpPeerOutSAs Counter32, msdpPeerOutSAs Counter32,
msdpPeerInSARequests Counter32, msdpPeerInSARequests Counter32,
skipping to change at page 12, line 51 skipping to change at page 9, line 22
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of the MSDP TCP connection with this peer." "The state of the MSDP TCP connection with this peer."
::= { msdpPeerEntry 3 } ::= { msdpPeerEntry 3 }
msdpPeerRPFFailures OBJECT-TYPE msdpPeerRPFFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of SA messages received from this peer which "The number of SA messages received from this peer that
failed the Peer-RPF check. failed the Peer-RPF check.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 4 } ::= { msdpPeerEntry 4 }
msdpPeerInSAs OBJECT-TYPE msdpPeerInSAs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MSDP SA messages received on this connection. "The number of MSDP SA messages received on this
connection.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 5 } ::= { msdpPeerEntry 5 }
msdpPeerOutSAs OBJECT-TYPE msdpPeerOutSAs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 14, line 10 skipping to change at page 10, line 30
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 7 } ::= { msdpPeerEntry 7 }
msdpPeerOutSARequests OBJECT-TYPE msdpPeerOutSARequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MSDP SA-Request messages transmitted on this "The number of MSDP SA-Request messages transmitted on
connection. this connection.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 8 } ::= { msdpPeerEntry 8 }
msdpPeerInSAResponses OBJECT-TYPE msdpPeerInSAResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 14, line 38 skipping to change at page 11, line 10
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 9 } ::= { msdpPeerEntry 9 }
msdpPeerOutSAResponses OBJECT-TYPE msdpPeerOutSAResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of MSDP SA Response messages transmitted on this "The number of MSDP SA Response messages transmitted on
TCP connection. this TCP connection.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 10 } ::= { msdpPeerEntry 10 }
msdpPeerInControlMessages OBJECT-TYPE msdpPeerInControlMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 15, line 31 skipping to change at page 11, line 52
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 12 } ::= { msdpPeerEntry 12 }
msdpPeerInDataPackets OBJECT-TYPE msdpPeerInDataPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of encapsulated data packets received from "The total number of encapsulated data packets received
this peer. from this peer.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 13 } ::= { msdpPeerEntry 13 }
msdpPeerOutDataPackets OBJECT-TYPE msdpPeerOutDataPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of encapsulated data packets sent to this "The total number of encapsulated data packets sent to
peer. this peer.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other re-initialization of the management system, and at other
times as indicated by the value of times as indicated by the value of
msdpPeerDiscontinuityTime." msdpPeerDiscontinuityTime."
::= { msdpPeerEntry 14 } ::= { msdpPeerEntry 14 }
msdpPeerFsmEstablishedTransitions OBJECT-TYPE msdpPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of times the MSDP FSM transitioned into the "The total number of times the MSDP FSM transitioned into
ESTABLISHED state." the ESTABLISHED state."
REFERENCE "RFC 3618 section 11" REFERENCE "RFC 3618 section 11"
::= { msdpPeerEntry 15 } ::= { msdpPeerEntry 15 }
msdpPeerFsmEstablishedTime OBJECT-TYPE msdpPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This timestamp is set to the value of sysUpTime when a peer "This timestamp is set to the value of sysUpTime when a
transitions into or out of the ESTABLISHED state. It is set peer transitions into or out of the ESTABLISHED state.
to zero when the MSDP speaker is booted." It is set to zero when the MSDP speaker is booted."
REFERENCE "RFC 3618 section 11" REFERENCE "RFC 3618 section 11"
::= { msdpPeerEntry 16 } ::= { msdpPeerEntry 16 }
msdpPeerInMessageTime OBJECT-TYPE msdpPeerInMessageTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sysUpTime value when the last MSDP message was received "The sysUpTime value when the last MSDP message was
from the peer. It is set to zero when the MSDP speaker is received from the peer. It is set to zero when the MSDP
booted." speaker is booted."
::= { msdpPeerEntry 17 } ::= { msdpPeerEntry 17 }
msdpPeerLocalAddress OBJECT-TYPE msdpPeerLocalAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address used for this entry's MSDP TCP "The local IP address used for this entry's MSDP TCP
connection." connection."
::= { msdpPeerEntry 18 } ::= { msdpPeerEntry 18 }
-- msdpPeerSAAdvPeriod ([SA-Advertisement-Timer]) has been removed. -- msdpPeerSAAdvPeriod ([SA-Advertisement-Timer]) has been removed.
-- ::= { msdpPeerEntry 19 } -- ::= { msdpPeerEntry 19 }
-- RFC 3618, Section 5.1, says it MUST be 60 seconds.
msdpPeerConnectRetryInterval OBJECT-TYPE msdpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the [ConnectRetry-period] for "Time interval, in seconds, for the [ConnectRetry-period]
this peer." for this peer."
REFERENCE "RFC 3618 section 5.6" REFERENCE "RFC 3618 section 5.6"
DEFVAL { 30 } DEFVAL { 30 }
::= { msdpPeerEntry 20 } ::= { msdpPeerEntry 20 }
msdpPeerHoldTimeConfigured OBJECT-TYPE msdpPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Integer32 (0|3..65535) SYNTAX Integer32 (0|3..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the [HoldTime-Period] "Time interval, in seconds, for the [HoldTime-Period]
configured for this MSDP speaker with this peer. If the configured for this MSDP speaker with this peer. If the
value of this object is zero (0), the MSDP connection is value of this object is zero (0), the MSDP connection is
never torn down due to the absence of messages from the never torn down due to the absence of messages from the
peer." peer."
REFERENCE "RFC 3618 section 5.4" REFERENCE "RFC 3618 section 5.4"
DEFVAL { 75 } DEFVAL { 75 }
::= { msdpPeerEntry 21 } ::= { msdpPeerEntry 21 }
msdpPeerKeepAliveConfigured OBJECT-TYPE msdpPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Integer32 (0|1..21845) SYNTAX Integer32 (0|1..21845)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the [KeepAlive-Period] "Time interval, in seconds, for the [KeepAlive-Period]
configured for this MSDP speaker with this peer. If the configured for this MSDP speaker with this peer. If the
value of this object is zero (0), no periodic KEEPALIVE value of this object is zero (0), no periodic KEEPALIVE
messages are sent to the peer after the MSDP connection has messages are sent to the peer after the MSDP connection
been established." has been established."
REFERENCE "RFC 3618 section 5.5" REFERENCE "RFC 3618 section 5.5"
DEFVAL { 60 } DEFVAL { 60 }
::= { msdpPeerEntry 22 } ::= { msdpPeerEntry 22 }
msdpPeerDataTtl OBJECT-TYPE msdpPeerDataTtl OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum TTL a packet is required to have before it may "The minimum TTL a packet is required to have before it
be forwarded using SA encapsulation to this peer." may be forwarded using SA encapsulation to this peer."
DEFVAL { 1 } DEFVAL { 1 }
::= { msdpPeerEntry 23 } ::= { msdpPeerEntry 23 }
msdpPeerProcessRequestsFrom OBJECT-TYPE msdpPeerProcessRequestsFrom OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This object indicates whether or not to process MSDP SA "This object indicates whether to process MSDP SA
Request messages from this peer. If True(1), MSDP SA Request messages from this peer. If True(1), MSDP SA
Request messages from this peer are processed and replied to Request messages from this peer are processed and replied
(if appropriate) with SA Response messages. If False(2), to (if appropriate) with SA Response messages. If
MSDP SA Request messages from this peer are silently False(2), MSDP SA Request messages from this peer are
ignored. It defaults to False when msdpCacheLifetime is 0 silently ignored. It defaults to False when
and True when msdpCacheLifetime is non-0. msdpCacheLifetime is 0 and to True when msdpCacheLifetime
is non-0.
This object is deprecated because MSDP SA Requests were This object is deprecated because MSDP SA Requests were
removed from the MSDP specification." removed from the MSDP specification."
::= { msdpPeerEntry 24 } ::= { msdpPeerEntry 24 }
msdpPeerStatus OBJECT-TYPE msdpPeerStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus object by which peers can be added and "The RowStatus object by which peers can be added and
deleted. A transition to 'active' will cause the MSDP deleted. A transition to 'active' will cause the MSDP
'Enable MSDP peering with P' Event to be generated. A 'Enable MSDP peering with P' Event to be generated. A
transition out of the 'active' state will cause the MSDP transition out of the 'active' state will cause the MSDP
'Disable MSDP peering with P' Event to be generated. Care 'Disable MSDP peering with P' Event to be generated.
should be used in providing write access to this object Care should be used in providing write access to this
without adequate authentication. object without adequate authentication.
msdpPeerRemoteAddress is the only variable that must be set msdpPeerRemoteAddress is the only variable that must be
to a valid value before the row can be activated. Since set to a valid value before the row can be activated.
this is the table's INDEX, a row can be activated by simply Since this is the table's INDEX, a row can be activated
setting the msdpPeerStatus variable. by simply setting the msdpPeerStatus variable.
It is possible to modify other columns in the same It is possible to modify other columns in the same
conceptual row when the status value is active(1)." conceptual row when the status value is active(1)."
REFERENCE "RFC 3618 section 11.1" REFERENCE "RFC 3618 section 11.1"
::= { msdpPeerEntry 25 } ::= { msdpPeerEntry 25 }
msdpPeerRemotePort OBJECT-TYPE msdpPeerRemotePort OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 19, line 41 skipping to change at page 16, line 14
DESCRIPTION DESCRIPTION
"The encapsulation in use when encapsulating data in SA "The encapsulation in use when encapsulating data in SA
messages to this peer." messages to this peer."
::= { msdpPeerEntry 29 } ::= { msdpPeerEntry 29 }
msdpPeerConnectionAttempts OBJECT-TYPE msdpPeerConnectionAttempts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times the state machine has transitioned from "The number of times the state machine has transitioned
INACTIVE to CONNECTING." from INACTIVE to CONNECTING."
::= { msdpPeerEntry 30 } ::= { msdpPeerEntry 30 }
msdpPeerInNotifications OBJECT-TYPE msdpPeerInNotifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of MSDP Notification messages received from this "The number of MSDP Notification messages received from
peer. this peer.
This object is deprecated because MSDP Notifications have This object is deprecated because MSDP Notifications have
been removed from the spec." been removed from the spec."
::= { msdpPeerEntry 31 } ::= { msdpPeerEntry 31 }
msdpPeerOutNotifications OBJECT-TYPE msdpPeerOutNotifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of MSDP Notification messages transmitted to this "The number of MSDP Notification messages transmitted to
peer. this peer.
This object is deprecated because MSDP Notifications have This object is deprecated because MSDP Notifications have
been removed from the spec." been removed from the spec."
::= { msdpPeerEntry 32 } ::= { msdpPeerEntry 32 }
msdpPeerLastError OBJECT-TYPE msdpPeerLastError OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The last error code and subcode received via Notification "The last error code and subcode received via Notification
from this peer. If no error has occurred, this field is from this peer. If no error has occurred, this field is
zero. Otherwise, the first byte of this two byte OCTET zero. Otherwise, the first byte of this two-byte OCTET
STRING contains the O-bit and error code, and the second STRING contains the O-bit and error code, and the second
byte contains the subcode. byte contains the subcode.
This object is deprecated because MSDP Notifications have This object is deprecated because MSDP Notifications have
been removed from the spec." been removed from the spec."
DEFVAL { '0000'h } DEFVAL { '0000'h }
::= { msdpPeerEntry 33 } ::= { msdpPeerEntry 33 }
msdpPeerDiscontinuityTime OBJECT-TYPE msdpPeerDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at
one or more of this entry's counters suffered a which one or more of this entry's counters suffered a
discontinuity. See the DESCRIPTION of each object to see if discontinuity. See the DESCRIPTION of each object to see
it is expected to have discontinuities. These if it is expected to have discontinuities. These
discontinuities may occur at peer connection establishment. discontinuities may occur at peer connection
establishment.
If no such discontinuities have occurred since the last If no such discontinuities have occurred since the last
reinitialization of the local management subsystem, then reinitialization of the local management subsystem, then
this object contains a zero value." this object contains a zero value."
::= { msdpPeerEntry 34 } ::= { msdpPeerEntry 34 }
-- --
-- The MSDP Source-Active Cache table -- The MSDP Source-Active Cache table
-- --
skipping to change at page 21, line 26 skipping to change at page 17, line 48
::= { msdp 6 } ::= { msdp 6 }
msdpSACacheEntry OBJECT-TYPE msdpSACacheEntry OBJECT-TYPE
SYNTAX MsdpSACacheEntry SYNTAX MsdpSACacheEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing an MSDP SA "An entry (conceptual row) representing an MSDP SA
advertisement. The INDEX to this table includes advertisement. The INDEX to this table includes
msdpSACacheOriginRP for diagnosing incorrect MSDP msdpSACacheOriginRP for diagnosing incorrect MSDP
advertisements; normally a Group and Source pair would be advertisements; normally, a Group and Source pair would
unique. be unique.
Row creation is not permitted; msdpSACacheStatus may only be Row creation is not permitted; msdpSACacheStatus may only
used to delete rows from this table." be used to delete rows from this table."
INDEX { msdpSACacheGroupAddr, msdpSACacheSourceAddr, INDEX { msdpSACacheGroupAddr, msdpSACacheSourceAddr,
msdpSACacheOriginRP } msdpSACacheOriginRP }
::= { msdpSACacheTable 1 } ::= { msdpSACacheTable 1 }
MsdpSACacheEntry ::= SEQUENCE { MsdpSACacheEntry ::= SEQUENCE {
msdpSACacheGroupAddr IpAddress, msdpSACacheGroupAddr IpAddress,
msdpSACacheSourceAddr IpAddress, msdpSACacheSourceAddr IpAddress,
msdpSACacheOriginRP IpAddress, msdpSACacheOriginRP IpAddress,
msdpSACachePeerLearnedFrom IpAddress, msdpSACachePeerLearnedFrom IpAddress,
msdpSACacheRPFPeer IpAddress, msdpSACacheRPFPeer IpAddress,
skipping to change at page 22, line 20 skipping to change at page 18, line 42
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source address of the SA Cache entry." "The source address of the SA Cache entry."
::= { msdpSACacheEntry 2 } ::= { msdpSACacheEntry 2 }
msdpSACacheOriginRP OBJECT-TYPE msdpSACacheOriginRP OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RP of the SA Cache entry. This field is in the INDEX in "The RP of the SA Cache entry. This field is in the INDEX
order to catch multiple RP's advertising the same source and in order to catch multiple RP's advertising the same
group." source and group."
::= { msdpSACacheEntry 3 } ::= { msdpSACacheEntry 3 }
msdpSACachePeerLearnedFrom OBJECT-TYPE msdpSACachePeerLearnedFrom OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The peer from which this SA Cache entry was last accepted. "The peer from which this SA Cache entry was last
This address must correspond to the msdpPeerRemoteAddress accepted. This address must correspond to the
value for a row in the MSDP Peer Table. This should be msdpPeerRemoteAddress value for a row in the MSDP Peer
0.0.0.0 on the router that originated the entry." Table. This should be 0.0.0.0 on the router that
originated the entry."
::= { msdpSACacheEntry 4 } ::= { msdpSACacheEntry 4 }
msdpSACacheRPFPeer OBJECT-TYPE msdpSACacheRPFPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The peer from which an SA message corresponding to this "The peer from which an SA message corresponding to this
cache entry would be accepted (i.e. the RPF peer for cache entry would be accepted (i.e., the RPF peer for
msdpSACacheOriginRP). This may be different than msdpSACacheOriginRP). This may be different than
msdpSACachePeerLearnedFrom if this entry was created by an msdpSACachePeerLearnedFrom if this entry was created by
MSDP SA-Response. This address must correspond to the an MSDP SA-Response. This address must correspond to
msdpPeerRemoteAddress value for a row in the MSDP Peer the msdpPeerRemoteAddress value for a row in the MSDP
Table, or may be 0.0.0.0 if no RPF peer exists." Peer Table, or it may be 0.0.0.0 if no RPF peer exists."
::= { msdpSACacheEntry 5 } ::= { msdpSACacheEntry 5 }
msdpSACacheInSAs OBJECT-TYPE msdpSACacheInSAs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MSDP SA messages received relevant to this "The number of MSDP SA messages received relevant to this
cache entry. This object must be initialized to zero when cache entry. This object must be initialized to zero
creating a cache entry." when creating a cache entry."
::= { msdpSACacheEntry 6 } ::= { msdpSACacheEntry 6 }
msdpSACacheInDataPackets OBJECT-TYPE msdpSACacheInDataPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of MSDP encapsulated data packets received "The number of MSDP-encapsulated data packets received
relevant to this cache entry. This object must be relevant to this cache entry. This object must be
initialized to zero when creating a cache entry." initialized to zero when creating a cache entry."
::= { msdpSACacheEntry 7 } ::= { msdpSACacheEntry 7 }
msdpSACacheUpTime OBJECT-TYPE msdpSACacheUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time since this entry was first placed in the SA cache. "The time since this entry was first placed in the SA
cache.
The first epoch is the time that the entry was first placed The first epoch is the time that the entry was first
in the SA cache, and the second epoch is the current time." placed in the SA cache, and the second epoch is the
current time."
::= { msdpSACacheEntry 8 } ::= { msdpSACacheEntry 8 }
msdpSACacheExpiryTime OBJECT-TYPE msdpSACacheExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time remaining before this entry will expire from the SA "The time remaining before this entry will expire from
cache. the SA cache.
The first epoch is now, and the second epoch is the time The first epoch is now, and the second epoch is the time
that the entry will expire." that the entry will expire."
::= { msdpSACacheEntry 9 } ::= { msdpSACacheEntry 9 }
msdpSACacheStatus OBJECT-TYPE msdpSACacheStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus { active(1), destroy(6) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row in the table. The only allowable "The status of this row in the table. The only allowable
actions are to retrieve the status, which will be `active', actions are to retrieve the status, which will be
or to set the status to `destroy' in order to remove this 'active', or to set the status to 'destroy' in order to
entry from the cache. remove this entry from the cache.
Row creation is not permitted. Row creation is not permitted.
No columnar objects are writable, so there are none that may No columnar objects are writable, so there are none that
be changed while the status value is active(1). " may be changed while the status value is active(1)."
::= { msdpSACacheEntry 10 } ::= { msdpSACacheEntry 10 }
-- --
-- MSDP Mesh Group Membership table -- MSDP Mesh Group Membership table
-- --
msdpMeshGroupTable OBJECT-TYPE msdpMeshGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF MsdpMeshGroupEntry SYNTAX SEQUENCE OF MsdpMeshGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing MSDP Mesh Group "The (conceptual) table listing MSDP Mesh Group
configuration." configuration."
::= { msdp 12 } ::= { msdp 12 }
msdpMeshGroupEntry OBJECT-TYPE msdpMeshGroupEntry OBJECT-TYPE
SYNTAX MsdpMeshGroupEntry SYNTAX MsdpMeshGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) repesenting a peer in an MSDP Mesh "An entry (conceptual row) representing a peer in an MSDP
Group. Mesh Group.
If row creation is supported, dynamically added rows are If row creation is supported, dynamically added rows are
added to the system's stable configuration (corresponding to added to the system's stable configuration
a StorageType value of nonVolatile). " (corresponding to a StorageType value of nonVolatile)."
INDEX { msdpMeshGroupName, msdpMeshGroupPeerAddress } INDEX { msdpMeshGroupName, msdpMeshGroupPeerAddress }
::= { msdpMeshGroupTable 1 } ::= { msdpMeshGroupTable 1 }
MsdpMeshGroupEntry ::= SEQUENCE { MsdpMeshGroupEntry ::= SEQUENCE {
msdpMeshGroupName DisplayString, msdpMeshGroupName DisplayString,
msdpMeshGroupPeerAddress IpAddress, msdpMeshGroupPeerAddress IpAddress,
msdpMeshGroupStatus RowStatus msdpMeshGroupStatus RowStatus
} }
msdpMeshGroupName OBJECT-TYPE msdpMeshGroupName OBJECT-TYPE
skipping to change at page 25, line 12 skipping to change at page 21, line 36
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the mesh group." "The name of the mesh group."
::= { msdpMeshGroupEntry 1 } ::= { msdpMeshGroupEntry 1 }
msdpMeshGroupPeerAddress OBJECT-TYPE msdpMeshGroupPeerAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A peer address that is a member of the mesh group with name "A peer address that is a member of the mesh group with
msdpMeshGroupName. The msdpMeshGroupPeerAddress must match name msdpMeshGroupName. The msdpMeshGroupPeerAddress
a row in the msdpPeerTable." must match a row in the msdpPeerTable."
::= { msdpMeshGroupEntry 2 } ::= { msdpMeshGroupEntry 2 }
msdpMeshGroupStatus OBJECT-TYPE msdpMeshGroupStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry's status, by which new entries may be added to "This entry's status, by which new entries may be added
the table and old entries deleted. to the table and old entries deleted.
msdpMeshGroupName and msdpMeshGroupPeerAddress must be set msdpMeshGroupName and msdpMeshGroupPeerAddress must be
to valid values before the row can be activated. Since set to valid values before the row can be activated.
these are the table's INDEX, a row can be activated by Since these are the table's INDEX, a row can be activated
simply setting the msdpMeshGroupStatus variable. by simply setting the msdpMeshGroupStatus variable.
It is not possible to modify other columns in the same It is not possible to modify other columns in the same
conceptual row when the status value is active(1), because conceptual row when the status value is active(1),
there only other objects in the row are part of the INDEX. because the only other objects in the row are part of the
Changing one of these changes the row, so an old row must be INDEX. Changing one of these changes the row, so an old
deleted and a new one created. " row must be deleted and a new one created."
::= { msdpMeshGroupEntry 3 } ::= { msdpMeshGroupEntry 3 }
-- Traps -- Traps
msdpTraps OBJECT IDENTIFIER ::= { msdp 0 } msdpTraps OBJECT IDENTIFIER ::= { msdp 0 }
msdpEstablished NOTIFICATION-TYPE msdpEstablished NOTIFICATION-TYPE
OBJECTS { msdpPeerFsmEstablishedTransitions } OBJECTS { msdpPeerFsmEstablishedTransitions }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MSDP Established event is generated when the MSDP FSM "The MSDP Established event is generated when the MSDP FSM
enters the ESTABLISHED state." enters the ESTABLISHED state."
::= { msdpTraps 1 } ::= { msdpTraps 1 }
msdpBackwardTransition NOTIFICATION-TYPE msdpBackwardTransition NOTIFICATION-TYPE
OBJECTS { msdpPeerState } OBJECTS { msdpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MSDPBackwardTransition Event is generated when the MSDP "The MSDPBackwardTransition Event is generated when the
FSM moves from a higher numbered state to a lower numbered MSDP FSM moves from a higher-numbered state to a
state." lower-numbered state."
::= { msdpTraps 2 } ::= { msdpTraps 2 }
-- conformance information -- conformance information
msdpMIBConformance OBJECT IDENTIFIER ::= { msdp 8 } msdpMIBConformance OBJECT IDENTIFIER ::= { msdp 8 }
msdpMIBCompliances OBJECT IDENTIFIER ::= { msdpMIBConformance 1 } msdpMIBCompliances OBJECT IDENTIFIER ::= { msdpMIBConformance 1 }
msdpMIBGroups OBJECT IDENTIFIER ::= { msdpMIBConformance 2 } msdpMIBGroups OBJECT IDENTIFIER ::= { msdpMIBConformance 2 }
-- compliance statements -- compliance statements
msdpMIBCompliance MODULE-COMPLIANCE msdpMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for entities which implement a pre- "The compliance statement for entities that implement a pre-
RFC version of MSDP. This statement is deprecated because RFC version of MSDP. This statement is deprecated because
it includes objects used for managing/monitoring aspects of it includes objects used for managing/monitoring aspects of
MSDP that were removed before it was published as an RFC." MSDP that were removed before it was published as an RFC."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup, MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup,
msdpMIBNotificationGroup } msdpMIBNotificationGroup }
GROUP msdpMIBEncapsulationGroup GROUP msdpMIBEncapsulationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if MSDP encapsulation interfaces are "This group is mandatory if MSDP encapsulation interfaces are
not given their own interface index numbers." not given their own interface index numbers."
GROUP msdpMIBSACacheGroup GROUP msdpMIBSACacheGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker has the ability "This group is mandatory if the MSDP speaker has the ability
to cache SA messages." to cache SA messages."
GROUP msdpMIBRequestsGroup GROUP msdpMIBRequestsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker has the ability "This group is mandatory if the MSDP speaker has the ability
to send SA-Request messages and parse SA-Response to send SA-Request messages and to parse SA-Response
messages." messages."
GROUP msdpMIBRPGroup GROUP msdpMIBRPGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker sources (as "This group is mandatory if the MSDP speaker sources (as
opposed to forwards) MSDP messages." opposed to forwards) MSDP messages."
GROUP msdpMIBMeshGroupGroup GROUP msdpMIBMeshGroupGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker can participate "This group is mandatory if the MSDP speaker can participate
in MSDP Mesh Groups." in MSDP Mesh Groups."
::= { msdpMIBCompliances 1 } ::= { msdpMIBCompliances 1 }
msdpMIBFullCompliance MODULE-COMPLIANCE msdpMIBFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities which implement MSDP "The compliance statement for entities that implement MSDP
(RFC3618)." (RFC3618)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2, MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2,
msdpMIBSACacheGroup, msdpMIBEncapsulationGroup } msdpMIBSACacheGroup, msdpMIBEncapsulationGroup }
GROUP msdpMIBRPGroup GROUP msdpMIBRPGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker sources (as "This group is mandatory if the MSDP speaker sources (as
opposed to forwards) MSDP messages." opposed to forwards) MSDP messages."
GROUP msdpMIBMeshGroupGroup GROUP msdpMIBMeshGroupGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker can participate "This group is mandatory if the MSDP speaker can participate
in MSDP Mesh Groups." in MSDP Mesh Groups."
::= { msdpMIBCompliances 2 } ::= { msdpMIBCompliances 2 }
msdpMIBReadOnlyCompliance MODULE-COMPLIANCE msdpMIBReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities which implement MSDP "The compliance statement for entities that implement MSDP
(RFC3618), but do not permit configuration (or only permit (RFC3618), but do not permit configuration (or only permit
partial configuration) via SNMP." partial configuration) via SNMP."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2, MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2,
msdpMIBSACacheGroup, msdpMIBEncapsulationGroup } msdpMIBSACacheGroup, msdpMIBEncapsulationGroup }
GROUP msdpMIBRPGroup GROUP msdpMIBRPGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the MSDP speaker sources (as "This group is mandatory if the MSDP speaker sources (as
opposed to forwards) MSDP messages." opposed to forwards) MSDP messages."
GROUP msdpMIBMeshGroupGroup GROUP msdpMIBMeshGroupGroup
skipping to change at page 30, line 24 skipping to change at page 26, line 48
"A collection of notifications for signaling changes in MSDP "A collection of notifications for signaling changes in MSDP
peer relationships." peer relationships."
::= { msdpMIBGroups 5 } ::= { msdpMIBGroups 5 }
msdpMIBRequestsGroup OBJECT-GROUP msdpMIBRequestsGroup OBJECT-GROUP
OBJECTS { msdpRequestsPeer, msdpRequestsStatus } OBJECTS { msdpRequestsPeer, msdpRequestsStatus }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects for managing MSDP Request "A collection of objects for managing MSDP Request
transmission. This group is deprecated because Requests transmission. This group is deprecated because Requests
were removed from MSDP before its publication as RFC." were removed from MSDP before its publication as an RFC."
::= { msdpMIBGroups 6 } ::= { msdpMIBGroups 6 }
msdpMIBRPGroup OBJECT-GROUP msdpMIBRPGroup OBJECT-GROUP
OBJECTS { msdpRPAddress } OBJECTS { msdpRPAddress }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for MSDP speakers that source MSDP "A collection of objects for MSDP speakers that source MSDP
messages." messages."
::= { msdpMIBGroups 7 } ::= { msdpMIBGroups 7 }
skipping to change at page 31, line 21 skipping to change at page 28, line 7
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for managing MSDP peers." "A collection of objects for managing MSDP peers."
::= { msdpMIBGroups 9 } ::= { msdpMIBGroups 9 }
END END
5. Security Considerations 5. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB module
MAX-ACCESS clause of read-write and/or read-create. Such objects may be with a MAX-ACCESS clause of read-write and/or read-create. Such
considered sensitive or vulnerable in some network environments. The objects may be considered sensitive or vulnerable in some network
support for SET operations in a non-secure environment without proper environments. The support for SET operations in a non-secure
protection can have a negative effect on network operations. environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
There are a number of managed objects in this MIB that may contain msdpEnabled
sensitive information. These are: Obviously, by modifying msdpEnabled, an attacker could simply
disable MSDP processing on the router.
msdpCacheLifetime
If allowed to modify msdpCacheLifetime, an attacker could set the
value to a value lower than a peer's refresh interval, causing all
state to time out and be refreshed.
msdpRequestsPeer, msdpRequestsStatus
If allowed to modify entries in the msdpRequestsTable, an attacker
could cause this system to send MSDP Requests to an unknown
system, or could simply remove the proper configuration. Note
that the msdpRequestsTable is deprecated, and the MSDP Request
functionality is not in the published MSDP spec.
msdpPeerTable objects
The writable objects in the msdpPeerTable are:
msdpPeerLocalAddress, msdpPeerConnectRetryInterval,
msdpPeerHoldTimeConfigured, msdpPeerKeepAliveConfigured,
msdpPeerDataTtl, msdpPeerProcessRequestsFrom, msdpPeerStatus, and
msdpPeerEncapsulationType. Of these, modifying msdpPeerIpAddress
and msdpPeerStatus could cause a changed or deleted peer
configuration. Modifying any of the other values could cause
subtle protocol misbehavior.
msdpSACacheStatus
This writable object can be used to remove valid values from the
router's SA cache.
msdpRPAddress
Changing this object can cause a failure of the Peer-RPF rules for
SA messages sourced by this router.
msdpMeshGroupStatus
This object can be used to change this router's idea of its mesh
group membership and those of its peers. Misconfiguration of mesh
groups can cause subtle protocol misbehavior.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o The entire msdpPeerTable. Peer information can result in o The entire msdpPeerTable. Peer information can result in
discovering internal topology, which many want to keep secret. discovering internal topology, which many want to keep secret.
o msdpNumSACacheEntries. The size of the SA Cache could reveal o msdpNumSACacheEntries. The size of the SA Cache could reveal
whether this system has MSDP entries for public and/or private whether this system has MSDP entries for public and/or private
groups. groups.
o The entire msdpSACacheTable. The active sources and groups in a o The entire msdpSACacheTable. The active sources and groups in a
network could be private. network could be private.
o The entire msdpMeshGroupTable. This information can also lead to o The entire msdpMeshGroupTable. This information can also lead to
internal topology information. internal topology information.
It is thus important to control even GET access to these objects and SNMP versions prior to SNMPv3 did not include adequate security.
possibly to even encrypt the values of these object when sending them Even if the network itself is secure (for example by using IPsec),
over the network via SNMP. Not all versions of SNMP provide features even then, there is no control as to who on the secure network is
for such a secure environment. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
SNMPv1 by itself is not a secure 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 GET/SET
(read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is RECOMMENDED that implementers consider the security features as
as provided by the SNMPv3 framework. Specifically, the use of the User- provided by the SNMPv3 framework (see [6], Section 8), including full
based Security Model RFC 3414 [2] and the View-based Access Control support for the SNMPv3 cryptographic mechanisms (for authentication
Model RFC 3415 [3] is recommended. and privacy).
It is then a customer/user responsibility to ensure that the SNMP entity Further, deployment of SNMP versions prior to SNMPv3 is NOT
giving access to an instance of this MIB, is properly configured to give RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
access to the objects only to those principals (users) that have enable cryptographic security. It is then a customer/operator
legitimate rights to indeed GET or SET (change/create/delete) them. responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
Since this MIB is for an experimental protocol, it uses an experimental Since this MIB is for an experimental protocol, it uses an
OID. experimental OID.
Decimal Name Description References Decimal Name Description References
------- ---- ----------- ---------- ------- ---- ----------- ----------
92 MSDP-MIB Multicast Source Discovery MIB [Fenner] 92 MSDP-MIB Multicast Source Discovery MIB RFC 4624
The IANA is requested to change the Reference for this entry to point to
this document.
7. Acknowledgements 7. Acknowledgements
Tom Pusateri and Billy Ng both provided valuable input on early versions Tom Pusateri and Billy Ng both provided valuable input on early
of this draft. It was completed based upon feedback from Mike Davison versions of this document. It was completed with feedback from Mike
and Ketan Talaulikar. Lucy Lynch provided a desperately-needed reminder Davison and Ketan Talaulikar. Lucy Lynch provided a desperately
to finish this document. needed reminder to finish this document.
8. Authors' Addresses
Bill Fenner
75 Willow Road
Menlo Park, CA 94025
Phone: +1 650 867 6073
EMail: fenner@research.att.com
Dave Thaler 8. References
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com
9. Normative References 8.1 Normative References
[1] Fenner, B. and D. Meyer, editors, "Multicast Source Discovery [1] Fenner, B., Ed., and D. Meyer, Ed., "Multicast Source Discovery
Protocol (MSDP)", RFC 3618, October 2003. Protocol (MSDP)", RFC 3618, October 2003.
[2] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for [2] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
version 3 of the Simple Network Management Protocol (SNMPv3)", STD for version 3 of the Simple Network Management Protocol
62, RFC 3414, December 2002. (SNMPv3)", STD 62, RFC 3414, December 2002.
[3] Wijnen, B., Preshun, R. and K. McCloghrie, "View-based Access [3] 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)", STD 62, RFC 3415, December 2002. (SNMP)", STD 62, RFC 3415, December 2002.
[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [4] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of
and S. Waldbusser, "Structure of Management Information Version 2 Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
(SMIv2)", STD 58, RFC 2578, April 1999. April 1999.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [5] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC Conventions for SMIv2", STD 58, RFC 2579, April 1999.
2579, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [6] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC Statements for SMIv2", STD 58, RFC 2580, April 1999.
2580, April 1999.
9.1. Informative References 8.2. Informative References
[7] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and [7] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
Applicability Statements for Internet-Standard Management and Applicability Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
10. Full Copyright Statement Authors' Addresses
Copyright (C) The Internet Society (2005). This document is subject to Bill Fenner
the rights, licenses and restrictions contained in BCP 78, and except as 1 River Oaks Place
set forth therein, the authors retain all their rights. San Jose, CA 95134-1918
Phone: +1 (408 493-8505
EMail: fenner@research.att.com
Dave Thaler
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; nor does it represent that it has made any might or might not be available; nor does it represent that it has
independent effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
procedures with respect to rights in RFC documents can be found in BCP on the procedures with respect to rights in RFC documents can be
78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an attempt assurances of licenses to be made available, or the result of an
made to obtain a general license or permission for the use of such attempt made to obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification can be such proprietary rights by implementers or users of this
obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
that may cover technology that may be required to implement this rights that may cover technology that may be required to implement
standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 114 change blocks. 
460 lines changed or deleted 354 lines changed or added

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