draft-ietf-idr-bgp4-mib-10.txt   draft-ietf-idr-bgp4-mib-11.txt 
Network Working Group Editors of this version: Network Working Group Editors of this version:
INTERNET DRAFT J. Haas INTERNET DRAFT J. Haas
NextHop
S. Hares S. Hares
NextHop NextHop Technologies
Authors of previous version: August 2003
S. Willis
Argon Networks
J. Burruss
WinData
Editor of previous version:
J. Chu
Cosine
March 2002
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-10.txt> <draft-ietf-idr-bgp4-mib-11.txt>
1. 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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts. http://www.ietf.org/ietf/1id-abstracts.
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.
2. Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
3. 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. The origin of this memo
is from RFC 1269 "Definitions of Managed Objects for the Border is from RFC 1269 "Definitions of Managed Objects for the Border
Gateway Protocol (Version 3)", which was updated to support BGP-4 in Gateway Protocol (Version 3)", which was updated to support BGP-4 in
RFC 1657. This memo fixes errors introduced when the MIB was RFC 1657. This memo fixes errors introduced when the MIB was
converted to use the SNMPv2 SMI, as well as updates references to the converted to use the SNMPv2 SMI, as well as updates references to the
current SNMP framework documents. 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@merit.net. idr@ietf.org.
4. Introduction Table of Contents
1. Introduction ................................................... 3
2. The Internet-Standard Management Framework ..................... 3
3. Overview ....................................................... 3
4. Definitions .................................................... 4
5. Intellectual Property ......................................... 29
6. Security Considerations ....................................... 30
7. Acknowledgements .............................................. 32
8. Normative References .......................................... 33
9. Informative References ........................................ 34
10. Editors' Address .............................................. 35
11. Full Copyright Statement ...................................... 35
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, BGPAPPL]. Border Gateway Protocol Version 4 or lower [BGP, BGP4APP].
5. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
-- An overall architecture, described in RFC 2571 [RFC2571].
-- Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
-- Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
-- Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
-- A set of fundamental applications described in RFC 2573 2. The Internet-Standard Management Framework
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
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. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
6. Overview 3. Overview
These objects are used to control and manage a BGP-4 implementation. These objects are used to control and manage a BGP-4 implementation.
Apart from a few system-wide scalar objects, this MIB is broken into Apart from a few system-wide scalar objects, this MIB is broken into
three tables: the BGP Peer Table, the BGP Received Path Attribute three tables: the BGP Peer Table, the BGP Received Path Attribute
Table, and the BGP-4 Received Path Attribute Table. The BGP Peer Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
Table contains information about state and current activity of Table contains information about state and current activity of
connections with the BGP peers. The BGP Received Path Attribute connections with the BGP peers. The BGP Received Path Attribute
Table contains path attributes received from all peers running BGP Table contains path attributes received from all peers running BGP
version 3 or less. The BGP-4 Received Path Attribute Table contains version 3 or less. The BGP-4 Received Path Attribute Table contains
path attributes received from all BGP-4 peers. The actual attributes path attributes received from all BGP-4 peers. The actual attributes
used in determining a route are a subset of the received attribute used in determining a route are a subset of the received attribute
tables after local routing policy has been applied. tables after local routing policy has been applied.
7. Definitions 4. Definitions
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 "200211040000Z" LAST-UPDATED "200308180000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@merit.net CONTACT-INFO "E-mail: idr@ietf.org
Jeff Haas, Sue Hares (Editors) Jeffrey Haas, Susan Hares (Editors)
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
E-mail: jhaas@nexthop.com E-mail: jhaas@nexthop.com
skh@nexthop.com" skh@nexthop.com"
DESCRIPTION DESCRIPTION
"The MIB module for the BGP-4 protocol. "The MIB module for the BGP-4 protocol.
Changes since RFC 1657: Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200308180000Z"
DESCRIPTION
"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 for latest BGP information 3) Updated information for the values of
draft-ietf-idr-bgp4-17.txt for value of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement. bgp4PathAttrASPathSegement.
4) Added additional clarification commments where 4) Added additional clarification comments where
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."
::= { 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
skipping to change at page 9, line 19 skipping to change at page 8, line 26
cause the BGP Start Event to be generated. cause the BGP Start Event to be generated.
A transition from 'start' to 'stop' will A transition from 'start' to 'stop' will
cause the BGP Stop Event to be generated. cause the BGP Stop Event to be generated.
This parameter can be used to restart BGP This parameter can be used to restart BGP
peer connections. Care should be used in peer connections. Care should be used in
providing write access to this object providing write access to this object
without adequate authentication." without adequate authentication."
::= { bgpPeerEntry 3 } ::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer32 (0..255) 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.
This entry should be zero (0) unless the This entry should be zero (0) unless the
bgpPeerState is in the openconfirm or the bgpPeerState is in the openconfirm or the
established state." established state.
Note that legal values should be between 0
and 255."
::= { bgpPeerEntry 4 } ::= { bgpPeerEntry 4 }
bgpPeerLocalAddr OBJECT-TYPE bgpPeerLocalAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address of this entry's BGP "The local IP address of this entry's BGP
connection." connection."
::= { bgpPeerEntry 5 } ::= { bgpPeerEntry 5 }
skipping to change at page 15, line 35 skipping to change at page 14, line 44
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 obsolete, having been replaced in -- This table is deprecated, 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 obsolete STATUS deprecated
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 obsolete STATUS deprecated
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 16, line 32 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 obsolete STATUS deprecated
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 obsolete STATUS deprecated
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
STATUS obsolete STATUS deprecated
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 obsolete STATUS deprecated
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 obsolete STATUS deprecated
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 obsolete STATUS deprecated
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 22, line 20 skipping to change at page 21, line 28
Known Issues: Known Issues:
o The BGP-4 specification uses an o The BGP-4 specification uses an
unsigned 32 bit number and thus this unsigned 32 bit number and thus this
object cannot represent the full object cannot represent the full
range of the protocol." range of the protocol."
::= { bgp4PathAttrEntry 8 } ::= { bgp4PathAttrEntry 8 }
bgp4PathAttrAtomicAggregate OBJECT-TYPE bgp4PathAttrAtomicAggregate OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
lessSpecificRouteNotSelected(1), lessSpecificRouteNotSelected(1),
-- Typo corrected from RFC 1657
lessSpecificRouteSelected(2) lessSpecificRouteSelected(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The original text for this object was: "The original text for this object was:
Whether or not a system has selected Whether or not a system has selected
a less specific route without a less specific route without
selecting a more specific route. selecting a more specific route.
skipping to change at page 23, line 6 skipping to change at page 22, line 15
::= { bgp4PathAttrEntry 9 } ::= { bgp4PathAttrEntry 9 }
bgp4PathAttrAggregatorAS OBJECT-TYPE bgp4PathAttrAggregatorAS OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The AS number of the last BGP4 speaker that "The AS number of the last BGP4 speaker that
performed route aggregation. A value of performed route aggregation. A value of
zero (0) indicates the absence of this zero (0) indicates the absence of this
attribute." attribute.
Note that propagation of AS of zero is illegal
in the Internet."
::= { bgp4PathAttrEntry 10 } ::= { bgp4PathAttrEntry 10 }
bgp4PathAttrAggregatorAddr OBJECT-TYPE bgp4PathAttrAggregatorAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last BGP4 speaker "The IP address of the last BGP4 speaker
that performed route aggregation. A that performed route aggregation. A
value of 0.0.0.0 indicates the absence value of 0.0.0.0 indicates the absence
of this attribute. of this attribute."
Note propagation of AS of zero is illegal in
the Internet."
::= { bgp4PathAttrEntry 11 } ::= { bgp4PathAttrEntry 11 }
bgp4PathAttrCalcLocalPref OBJECT-TYPE bgp4PathAttrCalcLocalPref OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The degree of preference calculated by the "The degree of preference calculated by the
receiving BGP4 speaker for an advertised receiving BGP4 speaker for an advertised
route. A value of -1 indicates the route. A value of -1 indicates the
skipping to change at page 24, line 33 skipping to change at page 23, line 42
recorded by this object. recorded by this object.
Known Issues: Known Issues:
o Attributes understood by this speaker, but not o Attributes understood by this speaker, but not
represented in this MIB, are unavailable to represented in this MIB, are unavailable to
the agent." the agent."
::= { bgp4PathAttrEntry 14 } ::= { bgp4PathAttrEntry 14 }
-- Traps. -- Traps.
-- note that in RFC 1657, bgpTraps was incorrectly -- Note that in RFC 1657, bgpTraps was incorrectly
-- assigned a value of { bgp 7 }, and each of the -- assigned a value of { bgp 7 } and each of the
-- traps had the bgpPeerRemoteAddr object inappropriately -- traps had the bgpPeerRemoteAddr object inappropriately
-- removed from their OBJECTS clause. The following -- removed from their OBJECTS clause. The following
-- definitions restore the semantics of the traps as -- definitions restore the semantics of the traps as
-- they were initially defined in RFC 1269. -- they were initially defined in RFC 1269.
bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } bgpNotification OBJECT IDENTIFIER ::= { bgp 0 }
bgpEstablishedNotification NOTIFICATION-TYPE bgpEstablishedNotification NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Established event is generated when "The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state. the BGP FSM enters the ESTABLISHED state.
This object obsoletes bgpEstablished." This object deprecates bgpEstablished."
::= { bgpNotification 1 } ::= { bgpNotification 1 }
bgpBackwardTransNotification NOTIFICATION-TYPE bgpBackwardTransNotification NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGPBackwardTransNotification Event is "The BGPBackwardTransNotification Event is
generated when the BGP FSM moves from a higher generated when the BGP FSM moves from a higher
numbered state to a lower numbered state. numbered state to a lower numbered state.
This object obsoletes bgpBackwardsTransition." This object deprecates bgpBackwardsTransition."
::= { bgpNotification 2 } ::= { bgpNotification 2 }
-- { bgp 7 } is obsoleted -- { bgp 7 } is deprecated
bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } bgpTraps OBJECT IDENTIFIER ::= { bgp 7 }
bgpEstablished NOTIFICATION-TYPE bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerLastError,
bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS obsolete STATUS deprecated
DESCRIPTION DESCRIPTION
"The BGP Established event is generated when "The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state. the BGP FSM enters the ESTABLISHED state.
This object has been obsoleted in favor of This object has been deprecated in favor of
bgpEstablishedNotification." bgpEstablishedNotification."
::= { bgpTraps 1 } ::= { bgpTraps 1 }
bgpBackwardTransition NOTIFICATION-TYPE bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerLastError,
bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGPBackwardTransition Event is generated "The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered when the BGP FSM moves from a higher numbered
state to a lower numbered state. state to a lower numbered state.
This object has been obsoleted in favor of This object has been deprecated in favor of
bgpBackwardTransNotification." bgpBackwardTransNotification."
::= { bgpTraps 2 } ::= { bgpTraps 2 }
-- conformance information -- Conformance information
bgpMIBConformance OBJECT IDENTIFIER bgp4MIBConformance OBJECT IDENTIFIER
::= { bgp 8 } ::= { bgp 8 }
bgpMIBCompliances OBJECT IDENTIFIER bgp4MIBCompliances OBJECT IDENTIFIER
::= { bgpMIBConformance 1 } ::= { bgp4MIBConformance 1 }
bgpMIBGroups OBJECT IDENTIFIER bgp4MIBGroups OBJECT IDENTIFIER
::= { bgpMIBConformance 2 } ::= { bgp4MIBConformance 2 }
-- compliance statements -- Compliance statements
bgpMIBCompliance MODULE-COMPLIANCE bgp4MIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities which "The compliance statement for entities which
implement the BGP4 mib." implement the BGP4 mib."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { bgp4MIBGlobalsGroup, MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
bgp4MIBPeerGroup, bgp4MIBPeerGroup,
bgp4MIBPathAttrGroup, bgp4MIBPathAttrGroup }
bgp4MIBNotificationGroup, ::= { bgp4MIBCompliances 1 }
bgp4MIBNewNotificationGroup }
::= { bgpMIBCompliances 1 }
-- units of conformance bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement documenting deprecated
objects in the BGP4 mib."
MODULE -- this module
GROUP bgp4MIBRcvdPathAttrGroup
DESCRIPTION
"Group containing objects relevant to BGP-3
and earlier objects."
GROUP bgp4MIBTrapGroup
DESCRIPTION
"Group containing TRAP objects that were
improperly converted from SMIv1 in RFC 1657.
The proper semantics have been restored
with the objects in bgp4MIBNotificationGroup."
::= { bgp4MIBCompliances 2 }
-- 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."
::= { bgpMIBGroups 1 } ::= { bgp4MIBGroups 1 }
bgp4MIBPeerGroup OBJECT-GROUP bgp4MIBPeerGroup OBJECT-GROUP
OBJECTS { bgpPeerIdentifier, OBJECTS { bgpPeerIdentifier,
bgpPeerState, bgpPeerState,
bgpPeerAdminStatus, bgpPeerAdminStatus,
bgpPeerNegotiatedVersion, bgpPeerNegotiatedVersion,
bgpPeerLocalAddr, bgpPeerLocalAddr,
bgpPeerLocalPort, bgpPeerLocalPort,
bgpPeerRemoteAddr, bgpPeerRemoteAddr,
bgpPeerRemotePort, bgpPeerRemotePort,
skipping to change at page 27, line 35 skipping to change at page 27, line 10
bgpPeerKeepAlive, bgpPeerKeepAlive,
bgpPeerHoldTimeConfigured, bgpPeerHoldTimeConfigured,
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."
::= { bgpMIBGroups 2 } ::= { bgp4MIBGroups 2 }
bgp4MIBRcvdPathAttrGroup OBJECT-GROUP bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
OBJECTS { bgpPathAttrPeer, OBJECTS { bgpPathAttrPeer,
bgpPathAttrDestNetwork, bgpPathAttrDestNetwork,
bgpPathAttrOrigin, bgpPathAttrOrigin,
bgpPathAttrASPath, bgpPathAttrASPath,
bgpPathAttrNextHop, bgpPathAttrNextHop,
bgpPathAttrInterASMetric } bgpPathAttrInterASMetric }
STATUS obsolete STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects for managing BGP "A collection of objects for managing BGP-3 and
path entries. earlier path entries.
This conformance group is obsolete, This conformance group is deprecated."
replaced by bgp4MIBPathAttrGroup." ::= { bgp4MIBGroups 3 }
::= { bgpMIBGroups 3 }
bgp4MIBPathAttrGroup OBJECT-GROUP bgp4MIBPathAttrGroup OBJECT-GROUP
OBJECTS { bgp4PathAttrPeer, OBJECTS { bgp4PathAttrPeer,
bgp4PathAttrIpAddrPrefixLen, bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrIpAddrPrefix, bgp4PathAttrIpAddrPrefix,
bgp4PathAttrOrigin, bgp4PathAttrOrigin,
bgp4PathAttrASPathSegment, bgp4PathAttrASPathSegment,
bgp4PathAttrNextHop, bgp4PathAttrNextHop,
bgp4PathAttrMultiExitDisc, bgp4PathAttrMultiExitDisc,
bgp4PathAttrLocalPref, bgp4PathAttrLocalPref,
bgp4PathAttrAtomicAggregate, bgp4PathAttrAtomicAggregate,
bgp4PathAttrAggregatorAS, bgp4PathAttrAggregatorAS,
bgp4PathAttrAggregatorAddr, bgp4PathAttrAggregatorAddr,
bgp4PathAttrCalcLocalPref, bgp4PathAttrCalcLocalPref,
bgp4PathAttrBest, bgp4PathAttrBest,
bgp4PathAttrUnknown } bgp4PathAttrUnknown }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for managing "A collection of objects for managing
BGP path entries." BGP path entries."
::= { bgpMIBGroups 4 } ::= { bgp4MIBGroups 4 }
bgp4MIBNotificationGroup NOTIFICATION-GROUP bgp4MIBTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablished, NOTIFICATIONS { bgpEstablished,
bgpBackwardTransition } bgpBackwardTransition }
STATUS obsolete STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling "A collection of notifications for signaling
changes in BGP peer relationships. changes in BGP peer relationships.
Obsoleted by bgp4MIBNewNotificationGroup" Obsoleted by bgp4MIBNewNotificationGroup"
::= { bgpMIBGroups 5 } ::= { bgp4MIBGroups 5 }
bgp4MIBNewNotificationGroup 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 bgp4MIBNotificationGroup."
::= { bgpMIBGroups 6 } ::= { bgp4MIBGroups 6 }
END END
8. 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
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
9. Security Considerations The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
6. Security Considerations
This MIB relates to a system providing inter-domain routing. As This MIB relates to a system providing inter-domain routing. As
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 thse 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.
skipping to change at page 33, line 5 skipping to change at page 32, line 5
implementation and use of the User-based Security Model [REF] and the implementation and use of the User-based Security Model [REF] and the
View-based Access Control Model [REF] is recommended to provide View-based Access Control Model [REF] is recommended to provide
appropriate security controls. appropriate security controls.
It is then an operator/user responsibility to ensure that the SNMP It is then an operator/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
10. Acknowledgements 7. Acknowledgements
We would like to acknowledge the assistance of all the members of the We would like to acknowledge the assistance of all the members of the
Inter-Domain Routing Working Group, and particularly the following Inter-Domain Routing Working Group, and particularly the following
individuals: individuals:
Yakov Rekhter, Juniper Networks Yakov Rekhter, Juniper Networks
Rob Coltun, Redback Rob Coltun, Redback
Guy Almes, Internet2 Guy Almes, Internet2
Jeff Honig, BSDi Jeff Honig, BSDi
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
Dennis Ferguson, Juniper Networks Dennis Ferguson, Juniper Networks
Mike Mathis, PSC Matt Mathis, PSC
John Krawczyk, Bay Networks John Krawczyk, Bay Networks
Curtis Villamizar, Avici Curtis Villamizar, Avici
Dave LeRoy, Pencom Systems Dave LeRoy, Pencom Systems
Paul Traina, Juniper Networks Paul Traina, Juniper Networks
Andrew Partan, MFN Andrew Partan, MFN
Robert Snyder, cisco Systems Robert Snyder, Cisco Systems
Dimitry Haskin, Nortel Dimitry Haskin, Nortel
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
Joel Halpern, CTO Longitude Systems, Inc. Joel Halpern, CTO Longitude Systems, Inc.
Nick Thille, RedBack Networks Nick Thille, RedBack Networks
Bert Wijnen, Lucent Bert Wijnen, Lucent
Shane Wright, NextHop Shane Wright, NextHop
Mike McFadden, Riverstone Networks, Inc. Mike McFadden, Riverstone Networks, Inc.
Jon Saperia, JDS Consulting, Inc. Jon Saperia, JDS Consulting, Inc.
Wayne Tackabury, Gold Wire Technology, Inc. Wayne Tackabury, Gold Wire Technology, Inc.
Bill Fenner, AT&T Research Bill Fenner, AT&T Research
RJ Atkinson, Extreme Networks RJ Atkinson, Extreme Networks
The origin of this document is from RFC 1269 "Definitions of Managed The origin of this document is from RFC 1269 "Definitions of Managed
Objects for the Border Gateway Protocol (Version 3)" written by Steve Objects for the Border Gateway Protocol (Version 3)" written by Steve
Willis and John Burruss, which was updated by John Chu to support Willis and John Burruss, which was updated by John Chu to support
BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of
these original authors. these original authors.
11. References 8. Normative References
[BGP4] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC
1771, March 1995.
[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border Gateway [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway
Protocol in the Internet", RFC 1772, March 1995. Protocol 4 (BGP-4)", RFC yyyy, zzzz 2003.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture -- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its
for Describing SNMP Management Frameworks", RFC 2571, April -- month of publication
1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border
of Management Information for TCP/IP-based Internets", STD Gateway Protocol in the Internet", RFC 1772, March 1995.
16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD --- XXX TODO - this document has yet to be updated.
16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
SNMP", RFC 1215, March 1991. (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture
Network Management Protocol", STD 15, RFC 1157, May 1990. for Describing Simple Network Management Protocol (SNMP)
Management Frameworks", RFC 3411, December 2002.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3413] D. Levi, P. Meyer, B. Stewart, "Simple Network Management
"Introduction to Community-based SNMPv2", RFC 1901, January Protocol (SNMP) Applications", RFC 3413, December 2002.
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3415] B. Wijnen, R. Presuhn, K. McCloghrie, "View-based Access
"Transport Mappings for Version 2 of the Simple Network Control Model (VACM) for the Simple Network Management
Management Protocol (SNMPv2)", RFC 1906, January 1996. Protocol (SNMP)", RFC 3415, December 2002.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC3416] Presuhn, R., Editor, "Version 2 of the Protool Operations
Processing and Dispatching for the Simple Network Management for the Simple Network Management Protocol (SNMP)",
Protocol (SNMP)", RFC 2572, April 1999. RFC 3416, December 2002.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC3417] Presuhn, R., Editor, "Transport Mappings for the Simple
(USM) for version 3 of the Simple Network Management Network Management Protocol (SNMP)", RFC 3417, December
Protocol (SNMPv3)", RFC 2574, April 1999. 2002.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 9. Informative References
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
RFC 2573, April 1999. "Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2576] Frye, R., Levi, D., Routhier, S. and B. Wijnen,
Access Control Model (VACM) for the Simple Network "Coexistence between Version 1, Version 2, and Version
Management Protocol (SNMP)", RFC 2575, April 1999. 3 of the Internet-Standard Network Management Framework",
RFC 2576, March 2000.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction and Applicability Statements for Internet-
Management Framework", RFC 2570, April 1999. Standard Management Framework", RFC 3410, December 2002.
12. Editors Address 10. Editors' Address
Jeff Haas, Sue Hares Jeffrey Haas, Susan Hares
NextHop Technologies NextHop Technologies
825 Victor's Way, Suite 100 825 Victor's Way, Suite 100
Ann Arbor, MI 48103 Ann Arbor, MI 48103
Phone: +1 734 222-1600 Phone: +1 734 222-1600
Fax: +1 734 222-1602 Fax: +1 734 222-1602
Email: jhaas@nexthop.com Email: jhaas@nexthop.com
skh@nexthop.com skh@nexthop.com
13. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

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