draft-ietf-idr-bgp4-mib-12.txt   draft-ietf-idr-bgp4-mib-13.txt 
Network Working Group Editors of this version: Network Working Group Editors of this version:
INTERNET DRAFT J. Haas INTERNET DRAFT J. Haas
S. Hares S. Hares
NextHop Technologies NextHop Technologies
September 2003 October 2003
Definitions of Managed Objects Definitions of Managed Objects
for the Fourth Version of Border Gateway Protocol (BGP-4) for the Fourth Version of Border Gateway Protocol (BGP-4)
<draft-ietf-idr-bgp4-mib-12.txt> <draft-ietf-idr-bgp4-mib-13.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This memo is an extension to the SNMP MIB. The origin of this memo This memo is an extension to the SNMP MIB. It obsoletes RFC 1657 and
is from RFC 1269 "Definitions of Managed Objects for the Border RFC 1269.
Gateway Protocol (Version 3)", which was updated to support BGP-4 in
RFC 1657. This memo fixes errors introduced when the MIB was The origin of this memo is from RFC 1269 "Definitions of Managed
converted to use the SNMPv2 SMI, as well as updates references to the Objects for the Border Gateway Protocol (Version 3)", which was
current SNMP framework documents. updated to support BGP-4 in RFC 1657. This memo fixes errors
introduced when the MIB was converted to use the SNMPv2 SMI, as well
as updates references to the current SNMP framework documents.
This memo is intended to document deployed implementations of this This memo is intended to document deployed implementations of this
MIB in a historical context, provide clarifications of some items and MIB in a historical context, provide clarifications of some items and
also note errors where the MIB fails to fully represent the BGP also note errors where the MIB fails to fully represent the BGP
protocol. Work is currently in progress to replace this MIB with a protocol. Work is currently in progress to replace this MIB with a
new one representing the current state of the BGP protocol and its new one representing the current state of the BGP protocol and its
extensions. extensions.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
idr@ietf.org. idr@ietf.org.
skipping to change at page 3, line 12 skipping to change at page 3, line 12
10. Editors' Address ............................................. 35 10. Editors' Address ............................................. 35
11. Full Copyright Statement ..................................... 35 11. Full Copyright Statement ..................................... 35
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Border Gateway Protocol Version 4 or lower [BGP, BGP4APP]. Border Gateway Protocol Version 4 or lower [BGP, BGP4APP].
This memo obsoletes RFC 1657 and RFC 1269.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 4, line 17 skipping to change at page 4, line 17
BGP4-MIB DEFINITIONS ::= BEGIN BGP4-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
IpAddress, Integer32, Counter32, Gauge32, mib-2 IpAddress, Integer32, Counter32, Gauge32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "200309050000Z" LAST-UPDATED "200310090000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@ietf.org CONTACT-INFO "E-mail: idr@ietf.org
Jeffrey Haas, Susan Hares (Editors) Jeffrey Haas, Susan Hares (Editors)
NextHop Technologies NextHop Technologies
825 Victors Way 825 Victors Way
Suite 100 Suite 100
Ann Arbor, MI 48108-2738 Ann Arbor, MI 48108-2738
Tel: +1 734 222-1600 Tel: +1 734 222-1600
Fax: +1 734 222-1602 Fax: +1 734 222-1602
skipping to change at page 4, line 40 skipping to change at page 4, line 40
DESCRIPTION DESCRIPTION
"The MIB module for the BGP-4 protocol. "The MIB module for the BGP-4 protocol.
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200309050000Z" REVISION "200310090000Z"
DESCRIPTION DESCRIPTION
"Changes from RFC 1657: "Changes from RFC 1657:
1) Fixed the definitions of the traps to 1) Fixed the definitions of the traps to
make them equivalent to their initial make them equivalent to their initial
definition in RFC 1269. definition in RFC 1269.
2) Added compliance and conformance info. 2) Added compliance and conformance info.
3) Updated information for the values of 3) Updated information for the values of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,
skipping to change at page 5, line 18 skipping to change at page 5, line 18
needed. needed.
5) Noted where objects do not fully reflect 5) Noted where objects do not fully reflect
the protocol as Known Issues. the protocol as Known Issues.
6) Updated the DESCRIPTION for the 6) Updated the DESCRIPTION for the
bgp4PathAttrAtomicAggregate object. bgp4PathAttrAtomicAggregate object.
7) The following objects have had their DESCRIPTION 7) The following objects have had their DESCRIPTION
clause modified to remove the requirement to clause modified to remove the requirement to
reset the counter to zero on a transition to reset the counter to zero on a transition to
the established state: the established state:
bgpPeerInUpdates, bgpPeerOutUpdates, bgpPeerInUpdates, bgpPeerOutUpdates,
bgpPeerInTotalMessages, bgpPeerOutTotalMessages" bgpPeerInTotalMessages, bgpPeerOutTotalMessages
Published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "199405050000Z"
DESCRIPTION
"Translated to SMIv2 and published as RFC 1657."
REVISION "199110261839Z"
DESCRIPTION
"Initial version, published as RFC 1269."
::= { mib-2 15 } ::= { mib-2 15 }
bgpVersion OBJECT-TYPE bgpVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vector of supported BGP protocol version "Vector of supported BGP protocol version
numbers. Each peer negotiates the version numbers. Each peer negotiates the version
from this vector. Versions are identified from this vector. Versions are identified
skipping to change at page 8, line 21 skipping to change at page 8, line 30
bgpPeerAdminStatus OBJECT-TYPE bgpPeerAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stop(1), stop(1),
start(2) start(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired state of the BGP connection. "The desired state of the BGP connection.
A transition from 'stop' to 'start' will A transition from 'stop' to 'start' will cause
cause the BGP Start Event to be generated. the BGP Manual Start Event to be generated.
A transition from 'start' to 'stop' will A transition from 'start' to 'stop' will cause
cause the BGP Stop Event to be generated. the BGP Manual Stop Event to be generated.
This parameter can be used to restart BGP This parameter can be used to restart BGP peer
peer connections. Care should be used in connections. Care should be used in providing
providing write access to this object write access to this object without adequate
without adequate authentication." authentication."
::= { bgpPeerEntry 3 } ::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated version of BGP running between "The negotiated version of BGP running between
the two peers. the two peers.
skipping to change at page 14, line 37 skipping to change at page 14, line 46
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Identifier of local system." "The BGP Identifier of local system."
::= { bgp 4 } ::= { bgp 4 }
-- BGP Received Path Attribute Table. This table contains, -- BGP Received Path Attribute Table. This table contains,
-- one entry per path to a network, path attributes -- one entry per path to a network, path attributes
-- received from all peers running BGP version 3 or less. -- received from all peers running BGP version 3 or less.
-- This table is deprecated, having been replaced in -- This table is obsolete, having been replaced in
-- functionality with the bgp4PathAttrTable. -- functionality with the bgp4PathAttrTable.
bgpRcvdPathAttrTable OBJECT-TYPE bgpRcvdPathAttrTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpPathAttrEntry SYNTAX SEQUENCE OF BgpPathAttrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The BGP Received Path Attribute Table "The BGP Received Path Attribute Table
contains information about paths to contains information about paths to
destination networks received from all destination networks received from all
peers running BGP version 3 or less." peers running BGP version 3 or less."
::= { bgp 5 } ::= { bgp 5 }
bgpPathAttrEntry OBJECT-TYPE bgpPathAttrEntry OBJECT-TYPE
SYNTAX BgpPathAttrEntry SYNTAX BgpPathAttrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"Information about a path to a network." "Information about a path to a network."
INDEX { bgpPathAttrDestNetwork, INDEX { bgpPathAttrDestNetwork,
bgpPathAttrPeer } bgpPathAttrPeer }
::= { bgpRcvdPathAttrTable 1 } ::= { bgpRcvdPathAttrTable 1 }
BgpPathAttrEntry ::= SEQUENCE { BgpPathAttrEntry ::= SEQUENCE {
bgpPathAttrPeer bgpPathAttrPeer
IpAddress, IpAddress,
bgpPathAttrDestNetwork bgpPathAttrDestNetwork
skipping to change at page 15, line 35 skipping to change at page 15, line 44
OCTET STRING, OCTET STRING,
bgpPathAttrNextHop bgpPathAttrNextHop
IpAddress, IpAddress,
bgpPathAttrInterASMetric bgpPathAttrInterASMetric
Integer32 Integer32
} }
bgpPathAttrPeer OBJECT-TYPE bgpPathAttrPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The IP address of the peer where the path "The IP address of the peer where the path
information was learned." information was learned."
::= { bgpPathAttrEntry 1 } ::= { bgpPathAttrEntry 1 }
bgpPathAttrDestNetwork OBJECT-TYPE bgpPathAttrDestNetwork OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the destination network." "The address of the destination network."
::= { bgpPathAttrEntry 2 } ::= { bgpPathAttrEntry 2 }
bgpPathAttrOrigin OBJECT-TYPE bgpPathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via the egp(2),-- networks learned via the
-- EGP protocol -- EGP protocol
incomplete(3) -- networks that incomplete(3) -- networks that
-- are learned by some other -- are learned by some other
-- means -- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 16, line 14 skipping to change at page 16, line 22
bgpPathAttrOrigin OBJECT-TYPE bgpPathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via the egp(2),-- networks learned via the
-- EGP protocol -- EGP protocol
incomplete(3) -- networks that incomplete(3) -- networks that
-- are learned by some other -- are learned by some other
-- means -- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The ultimate origin of the path information." "The ultimate origin of the path information."
::= { bgpPathAttrEntry 3 } ::= { bgpPathAttrEntry 3 }
bgpPathAttrASPath OBJECT-TYPE bgpPathAttrASPath OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..255)) SYNTAX OCTET STRING (SIZE (2..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The set of ASs that must be traversed to reach "The set of ASs that must be traversed to reach
the network. This object is probably best the network. This object is probably best
represented as SEQUENCE OF INTEGER. For SMI represented as SEQUENCE OF INTEGER. For SMI
compatibility, though, it is represented as compatibility, though, it is represented as
OCTET STRING. Each AS is represented as a pair OCTET STRING. Each AS is represented as a pair
of octets according to the following algorithm: of octets according to the following algorithm:
first-byte-of-pair = ASNumber / 256; first-byte-of-pair = ASNumber / 256;
second-byte-of-pair = ASNumber & 255;" second-byte-of-pair = ASNumber & 255;"
::= { bgpPathAttrEntry 4 } ::= { bgpPathAttrEntry 4 }
bgpPathAttrNextHop OBJECT-TYPE bgpPathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the border router that should "The address of the border router that should
be used for the destination network." be used for the destination network."
::= { bgpPathAttrEntry 5 } ::= { bgpPathAttrEntry 5 }
bgpPathAttrInterASMetric OBJECT-TYPE bgpPathAttrInterASMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"The optional inter-AS metric. If this "The optional inter-AS metric. If this
attribute has not been provided for this route, attribute has not been provided for this route,
the value for this object is 0." the value for this object is 0."
::= { bgpPathAttrEntry 6 } ::= { bgpPathAttrEntry 6 }
-- BGP-4 Received Path Attribute Table. This table -- BGP-4 Received Path Attribute Table. This table
-- contains, one entry per path to a network, path -- contains, one entry per path to a network, path
-- attributes received from all peers running BGP-4. -- attributes received from all peers running BGP-4.
skipping to change at page 25, line 46 skipping to change at page 26, line 6
"Implementation of BGP Notifications are "Implementation of BGP Notifications are
completely optional in this MIB." completely optional in this MIB."
::= { bgp4MIBCompliances 1 } ::= { bgp4MIBCompliances 1 }
bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement documenting deprecated "The compliance statement documenting deprecated
objects in the BGP4 mib." objects in the BGP4 mib."
MODULE -- this module MODULE -- this module
GROUP bgp4MIBRcvdPathAttrGroup
DESCRIPTION
"Group containing objects relevant to BGP-3
and earlier objects."
GROUP bgp4MIBTrapGroup GROUP bgp4MIBTrapGroup
DESCRIPTION DESCRIPTION
"Group containing TRAP objects that were "Group containing TRAP objects that were
improperly converted from SMIv1 in RFC 1657. improperly converted from SMIv1 in RFC 1657.
The proper semantics have been restored The proper semantics have been restored
with the objects in bgp4MIBNotificationGroup." with the objects in bgp4MIBNotificationGroup."
::= { bgp4MIBCompliances 2 } ::= { bgp4MIBCompliances 2 }
bgp4MIBObsoleteCompliances MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement documenting obsolete
objects in the BGP4 mib."
MODULE -- this module
GROUP bgpRcvdPathAttrGroup
DESCRIPTION
"Group containing objects relevant to BGP-3
and earlier objects."
::= { bgp4MIBCompliances 3 }
-- Units of conformance -- Units of conformance
bgp4MIBGlobalsGroup OBJECT-GROUP bgp4MIBGlobalsGroup OBJECT-GROUP
OBJECTS { bgpVersion, OBJECTS { bgpVersion,
bgpLocalAs, bgpLocalAs,
bgpIdentifier } bgpIdentifier }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing "A collection of objects providing
information on global BGP state." information on global BGP state."
skipping to change at page 27, line 13 skipping to change at page 27, line 24
bgpPeerKeepAliveConfigured, bgpPeerKeepAliveConfigured,
bgpPeerMinASOriginationInterval, bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval, bgpPeerMinRouteAdvertisementInterval,
bgpPeerInUpdateElapsedTime } bgpPeerInUpdateElapsedTime }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for managing "A collection of objects for managing
BGP peers." BGP peers."
::= { bgp4MIBGroups 2 } ::= { bgp4MIBGroups 2 }
bgp4MIBRcvdPathAttrGroup OBJECT-GROUP bgpRcvdPathAttrGroup OBJECT-GROUP
OBJECTS { bgpPathAttrPeer, OBJECTS { bgpPathAttrPeer,
bgpPathAttrDestNetwork, bgpPathAttrDestNetwork,
bgpPathAttrOrigin, bgpPathAttrOrigin,
bgpPathAttrASPath, bgpPathAttrASPath,
bgpPathAttrNextHop, bgpPathAttrNextHop,
bgpPathAttrInterASMetric } bgpPathAttrInterASMetric }
STATUS deprecated STATUS obsolete
DESCRIPTION DESCRIPTION
"A collection of objects for managing BGP-3 and "A collection of objects for managing BGP-3 and
earlier path entries. earlier path entries.
This conformance group is deprecated." This conformance group, like BGP-3, is obsolete."
::= { bgp4MIBGroups 3 } ::= { bgp4MIBGroups 3 }
bgp4MIBPathAttrGroup OBJECT-GROUP bgp4MIBPathAttrGroup OBJECT-GROUP
OBJECTS { bgp4PathAttrPeer, OBJECTS { bgp4PathAttrPeer,
bgp4PathAttrIpAddrPrefixLen, bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrIpAddrPrefix, bgp4PathAttrIpAddrPrefix,
bgp4PathAttrOrigin, bgp4PathAttrOrigin,
bgp4PathAttrASPathSegment, bgp4PathAttrASPathSegment,
bgp4PathAttrNextHop, bgp4PathAttrNextHop,
bgp4PathAttrMultiExitDisc, bgp4PathAttrMultiExitDisc,
skipping to change at page 28, line 23 skipping to change at page 28, line 33
::= { bgp4MIBGroups 5 } ::= { bgp4MIBGroups 5 }
bgp4MIBNotificationGroup NOTIFICATION-GROUP bgp4MIBNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablishedNotification, NOTIFICATIONS { bgpEstablishedNotification,
bgpBackwardTransNotification } bgpBackwardTransNotification }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling "A collection of notifications for signaling
changes in BGP peer relationships. changes in BGP peer relationships.
Obsoletes bgp4MIBNotificationGroup." Obsoletes bgp4MIBTrapGroup."
::= { bgp4MIBGroups 6 } ::= { bgp4MIBGroups 6 }
END END
5. Intellectual Property 5. 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 or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
skipping to change at page 30, line 18 skipping to change at page 30, line 18
such, improper manipulation of the objects represented by this MIB such, improper manipulation of the objects represented by this MIB
may result in denial of service to a large number of end-users. may result in denial of service to a large number of end-users.
There are several management objects defined in this MIB that have a There are several management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects MAX-ACCESS clause of read-write and/or read-create. Such objects
should be considered sensitive or vulnerable in most network should be considered sensitive or vulnerable in most network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These objects include: network operations. These objects include:
o bgpPeerAdminStatus +o bgpPeerAdminStatus
Improper change of bgpPeerAdminStatus from start to stop can Improper change of bgpPeerAdminStatus from start to stop can
cause significant disruption of the connectivity to those cause significant disruption of the connectivity to those
portions of the Internet reached via the applicable remote BGP portions of the Internet reached via the applicable remote BGP
peer. peer.
o bgpPeerConnectRetryInterval +o bgpPeerConnectRetryInterval
Improper change of this object can cause connections to be Improper change of this object can cause connections to be
disrupted for extremely long time periods when otherwise they disrupted for extremely long time periods when otherwise they
would be restored in a relatively short period of time. would be restored in a relatively short period of time.
o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured +o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured
Misconfiguration of these objects can make BGP sessions more Misconfiguration of these objects can make BGP sessions more
fragile and less resilient to denial of service attacks on the fragile and less resilient to denial of service attacks on the
inter-domain routing system. inter-domain routing system.
o bgpPeerMinASOriginationInterval, +o bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval bgpPeerMinRouteAdvertisementInterval
Misconfiguration of these objects may adversely affect global Misconfiguration of these objects may adversely affect global
Internet convergence of the routes advertised by this BGP Internet convergence of the routes advertised by this BGP
speaker. This may result in long-lived routing loops and speaker. This may result in long-lived routing loops and
blackholes for the portions of the Internet that utilize these blackholes for the portions of the Internet that utilize these
routes." routes."
There are a number of managed objects in this MIB that There are a number of managed objects in this MIB that
contain sensitive information regarding the operation of a network. contain sensitive information regarding the operation of a network.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/