draft-ietf-idr-bgp4-mibv2-08.txt   draft-ietf-idr-bgp4-mibv2-09.txt 
Inter-Domain Routing Working Group J. Haas Inter-Domain Routing Working Group J. Haas
Internet-Draft Arbor Networks Internet-Draft Arbor Networks
Intended status: Standards Track November 2, 2008 Intended status: Standards Track February 18, 2009
Expires: May 6, 2009 Expires: August 22, 2009
Definitions of Managed Objects for the Fourth Version of Border Gateway Definitions of Managed Objects for the Fourth Version of Border Gateway
Protocol (BGP-4), Second Version Protocol (BGP-4), Second Version
draft-ietf-idr-bgp4-mibv2-08 draft-ietf-idr-bgp4-mibv2-09
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 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.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 6, 2009. This Internet-Draft will expire on August 22, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
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 particular it defines for use with network management protocols. In particular it defines
objects for managing the Border Gateway Protocol, Version 4. objects for managing the Border Gateway Protocol, Version 4.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 6, line 21 skipping to change at page 6, line 21
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
Bgp4V2IdentifierTC, Bgp4V2AddressFamilyIdentifierTC, Bgp4V2IdentifierTC, Bgp4V2AddressFamilyIdentifierTC,
Bgp4V2SubsequentAddressFamilyIdentifierTC Bgp4V2SubsequentAddressFamilyIdentifierTC
FROM BGP4V2-TC-MIB; FROM BGP4V2-TC-MIB;
bgp4V2 MODULE-IDENTITY bgp4V2 MODULE-IDENTITY
LAST-UPDATED "200811020000Z" LAST-UPDATED "200902180000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@ietf.org" CONTACT-INFO "E-mail: idr@ietf.org"
DESCRIPTION DESCRIPTION
"The MIB module for the BGP-4 protocol. "The MIB module for the BGP-4 protocol.
Copyright (C) The IETF Trust (2008). This Copyright (C) The IETF Trust (2009). This
version of this MIB module is part of RFC XXX; version of this MIB module is part of RFC XXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Editor - replace XXX with RFC number -- RFC Editor - replace XXX with RFC number
REVISION "200811020000Z" REVISION "200902180000Z"
DESCRIPTION DESCRIPTION
"This MIB updates and replaces the BGP MIB defined in "This MIB updates and replaces the BGP MIB defined in
RFC 4273." RFC 4273."
::= { mib-2 XXX } ::= { mib-2 XXX }
-- Top level components of this MIB module -- Top level components of this MIB module
-- Notifications -- Notifications
bgp4V2Notifications OBJECT IDENTIFIER ::= { bgp4V2 0 } bgp4V2Notifications OBJECT IDENTIFIER ::= { bgp4V2 0 }
skipping to change at page 8, line 19 skipping to change at page 8, line 19
bgp4V2PeerEntry OBJECT-TYPE bgp4V2PeerEntry OBJECT-TYPE
SYNTAX Bgp4V2PeerEntry SYNTAX Bgp4V2PeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about the connection with "Entry containing information about the connection with
a remote BGP peer." a remote BGP peer."
INDEX { INDEX {
bgp4V2PeerInstance, bgp4V2PeerInstance,
bgp4V2PeerLocalAddrType,
bgp4V2PeerLocalAddr,
bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddrType,
bgp4V2PeerRemoteAddr bgp4V2PeerRemoteAddr
} }
::= { bgp4V2PeerTable 1 } ::= { bgp4V2PeerTable 1 }
Bgp4V2PeerEntry ::= SEQUENCE { Bgp4V2PeerEntry ::= SEQUENCE {
-- INDEX information -- INDEX information
bgp4V2PeerInstance bgp4V2PeerInstance
Unsigned32, Unsigned32,
bgp4V2PeerLocalAddrType bgp4V2PeerLocalAddrType
skipping to change at page 13, line 28 skipping to change at page 13, line 26
DESCRIPTION DESCRIPTION
"Each entry contains information about errors sent "Each entry contains information about errors sent
and received for a particular BGP peer." and received for a particular BGP peer."
AUGMENTS { AUGMENTS {
bgp4V2PeerEntry bgp4V2PeerEntry
} }
::= { bgp4V2PeerErrorsTable 1 } ::= { bgp4V2PeerErrorsTable 1 }
Bgp4V2PeerErrorsEntry ::= SEQUENCE { Bgp4V2PeerErrorsEntry ::= SEQUENCE {
bgp4V2PeerLastErrorCodeReceived bgp4V2PeerLastErrorCodeReceived
OCTET STRING, Unsigned32,
bgp4V2PeerLastErrorSubCodeReceived bgp4V2PeerLastErrorSubCodeReceived
OCTET STRING, Unsigned32,
bgp4V2PeerLastErrorReceivedTime bgp4V2PeerLastErrorReceivedTime
TimeStamp, TimeStamp,
bgp4V2PeerLastErrorReceivedText bgp4V2PeerLastErrorReceivedText
SnmpAdminString, SnmpAdminString,
bgp4V2PeerLastErrorReceivedData bgp4V2PeerLastErrorReceivedData
OCTET STRING, OCTET STRING,
bgp4V2PeerLastErrorCodeSent bgp4V2PeerLastErrorCodeSent
OCTET STRING, Unsigned32,
bgp4V2PeerLastErrorSubCodeSent bgp4V2PeerLastErrorSubCodeSent
OCTET STRING, Unsigned32,
bgp4V2PeerLastErrorSentTime bgp4V2PeerLastErrorSentTime
TimeStamp, TimeStamp,
bgp4V2PeerLastErrorSentText bgp4V2PeerLastErrorSentText
SnmpAdminString, SnmpAdminString,
bgp4V2PeerLastErrorSentData bgp4V2PeerLastErrorSentData
OCTET STRING OCTET STRING
} }
bgp4V2PeerLastErrorCodeReceived OBJECT-TYPE bgp4V2PeerLastErrorCodeReceived OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last error code received from this peer via "The last error code received from this peer via
NOTIFICATION message on this connection. If no error has NOTIFICATION message on this connection. If no error has
occurred, this field is zero." occurred, this field is zero."
REFERENCE REFERENCE
"RFC 4271, Section 4.5. "RFC 4271, Section 4.5.
RFC 4486 optionally supported. RFC 4486 optionally supported.
RFC 3362, Section 5 optionally supported." RFC 3362, Section 5 optionally supported."
::= { bgp4V2PeerErrorsEntry 1 } ::= { bgp4V2PeerErrorsEntry 1 }
bgp4V2PeerLastErrorSubCodeReceived OBJECT-TYPE bgp4V2PeerLastErrorSubCodeReceived OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last subcode received from this peer via NOTIFICATION "The last subcode received from this peer via NOTIFICATION
message on this connection. If no error has occurred, this message on this connection. If no error has occurred, this
field is zero." field is zero."
REFERENCE REFERENCE
"RFC 4271, Section 4.5. "RFC 4271, Section 4.5.
RFC 4486 optionally supported. RFC 4486 optionally supported.
RFC 3362, Section 5 optionally supported." RFC 3362, Section 5 optionally supported."
skipping to change at page 15, line 19 skipping to change at page 15, line 17
dealing with OCTET STRINGS larger than 255. Thus, this dealing with OCTET STRINGS larger than 255. Thus, this
data may be truncated." data may be truncated."
REFERENCE REFERENCE
"RFC 4271, Section 4.5, "RFC 4271, Section 4.5,
RFC 2578, Section 7.1.2, RFC 2578, Section 7.1.2,
RFC 4486 optionally supported. RFC 4486 optionally supported.
RFC 3362, Section 5 optionally supported." RFC 3362, Section 5 optionally supported."
::= { bgp4V2PeerErrorsEntry 5 } ::= { bgp4V2PeerErrorsEntry 5 }
bgp4V2PeerLastErrorCodeSent OBJECT-TYPE bgp4V2PeerLastErrorCodeSent OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last error code sent to this peer via NOTIFICATION "The last error code sent to this peer via NOTIFICATION
message on this connection. If no error has occurred, this message on this connection. If no error has occurred, this
field is zero." field is zero."
REFERENCE REFERENCE
"RFC 4271, Section 4.5. "RFC 4271, Section 4.5.
RFC 4486 optionally supported. RFC 4486 optionally supported.
RFC 3362, Section 5 optionally supported." RFC 3362, Section 5 optionally supported."
::= { bgp4V2PeerErrorsEntry 6 } ::= { bgp4V2PeerErrorsEntry 6 }
bgp4V2PeerLastErrorSubCodeSent OBJECT-TYPE bgp4V2PeerLastErrorSubCodeSent OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last subcode sent to this peer via NOTIFICATION "The last subcode sent to this peer via NOTIFICATION
message on this connection. If no error has occurred, this message on this connection. If no error has occurred, this
field is zero." field is zero."
REFERENCE REFERENCE
"RFC 4271, Section 4.5. "RFC 4271, Section 4.5.
RFC 4486 optionally supported. RFC 4486 optionally supported.
RFC 3362, Section 5 optionally supported." RFC 3362, Section 5 optionally supported."
skipping to change at page 18, line 4 skipping to change at page 17, line 49
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Elapsed time (in seconds) since the last BGP UPDATE "Elapsed time (in seconds) since the last BGP UPDATE
message was received from the peer. Each time message was received from the peer. Each time
bgpPeerInUpdates is incremented, the value of this bgpPeerInUpdates is incremented, the value of this
object is set to zero (0)." object is set to zero (0)."
REFERENCE REFERENCE
"RFC 4271, Section 4.3. "RFC 4271, Section 4.3.
RFC 4271, Section 8.2.2, Established state." RFC 4271, Section 8.2.2, Established state."
::= { bgp4V2PeerEventTimesEntry 2 }
::= { bgp4V2PeerEventTimesEntry 2 }
-- --
-- Per-Peer Configured Timers -- Per-Peer Configured Timers
-- --
bgp4V2PeerConfiguredTimersTable OBJECT-TYPE bgp4V2PeerConfiguredTimersTable OBJECT-TYPE
SYNTAX SEQUENCE OF Bgp4V2PeerConfiguredTimersEntry SYNTAX SEQUENCE OF Bgp4V2PeerConfiguredTimersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Per peer management data on BGP session timers." "Per peer management data on BGP session timers."
skipping to change at page 21, line 48 skipping to change at page 21, line 45
zero (0) - if this was the value sent by the peer and zero (0) - if this was the value sent by the peer and
this value is permitted by this BGP Speaker. In this this value is permitted by this BGP Speaker. In this
case, no keepalive messages are sent and the Hold Timer case, no keepalive messages are sent and the Hold Timer
is not set. is not set.
At least three (3). This value is the smaller of At least three (3). This value is the smaller of
the value sent by this peer in the OPEN message and the value sent by this peer in the OPEN message and
bgp4V2PeerHoldTimeConfigured for this peer. bgp4V2PeerHoldTimeConfigured for this peer.
This value is only defined when the peering session is If the peer is not in the established state, the value
in the Established state." of this object is zero (0)."
REFERENCE REFERENCE
"RFC 4271, Section 4.2." "RFC 4271, Section 4.2."
::= { bgp4V2PeerNegotiatedTimersEntry 1 } ::= { bgp4V2PeerNegotiatedTimersEntry 1 }
bgp4V2PeerKeepAlive OBJECT-TYPE bgp4V2PeerKeepAlive OBJECT-TYPE
SYNTAX Unsigned32 ( 0 | 1..21845 ) SYNTAX Unsigned32 ( 0 | 1..21845 )
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the KeepAlive timer "Time interval in seconds for the KeepAlive timer
established with the peer. The value of this object established with the peer. The value of this object
is calculated by this BGP speaker such that, when is calculated by this BGP speaker such that, when
compared with bgp4V2PeerHoldTime, it has the same compared with bgp4V2PeerHoldTime, it has the same
skipping to change at page 22, line 21 skipping to change at page 22, line 20
established with the peer. The value of this object established with the peer. The value of this object
is calculated by this BGP speaker such that, when is calculated by this BGP speaker such that, when
compared with bgp4V2PeerHoldTime, it has the same compared with bgp4V2PeerHoldTime, it has the same
proportion as what bgp4V2PeerKeepAliveConfigured has proportion as what bgp4V2PeerKeepAliveConfigured has
when compared with bgp4V2PeerHoldTimeConfigured. If when compared with bgp4V2PeerHoldTimeConfigured. If
the value of this object is zero (0), it indicates the value of this object is zero (0), it indicates
that the KeepAlive timer has not been established that the KeepAlive timer has not been established
with the peer, or, the value of with the peer, or, the value of
bgp4V2PeerKeepAliveConfigured is zero (0). bgp4V2PeerKeepAliveConfigured is zero (0).
This value is only defined when the peering session is If the peer is not in the established state, the value
in the Established state." of this object is zero (0)."
REFERENCE REFERENCE
"RFC 4271, Section 4.4." "RFC 4271, Section 4.4."
::= { bgp4V2PeerNegotiatedTimersEntry 2 } ::= { bgp4V2PeerNegotiatedTimersEntry 2 }
-- --
-- Per-peer counters -- Per-peer counters
-- --
bgp4V2PeerCountersTable OBJECT-TYPE bgp4V2PeerCountersTable OBJECT-TYPE
SYNTAX SEQUENCE OF Bgp4V2PeerCountersEntry SYNTAX SEQUENCE OF Bgp4V2PeerCountersEntry
skipping to change at page 24, line 35 skipping to change at page 24, line 34
bgp4V2PrefixGaugesEntry OBJECT-TYPE bgp4V2PrefixGaugesEntry OBJECT-TYPE
SYNTAX Bgp4V2PrefixCountersEntry SYNTAX Bgp4V2PrefixCountersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about a bgp-peers prefix "Entry containing information about a bgp-peers prefix
counters." counters."
INDEX { INDEX {
bgp4V2PeerInstance, bgp4V2PeerInstance,
bgp4V2PeerLocalAddrType,
bgp4V2PeerLocalAddr,
bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddrType,
bgp4V2PeerRemoteAddr, bgp4V2PeerRemoteAddr,
bgp4V2PrefixGaugesAfi, bgp4V2PrefixGaugesAfi,
bgp4V2PrefixGaugesSafi bgp4V2PrefixGaugesSafi
} }
::= { bgp4V2PrefixGaugesTable 1 } ::= { bgp4V2PrefixGaugesTable 1 }
Bgp4V2PrefixCountersEntry ::= SEQUENCE { Bgp4V2PrefixCountersEntry ::= SEQUENCE {
bgp4V2PrefixGaugesAfi bgp4V2PrefixGaugesAfi
Bgp4V2AddressFamilyIdentifierTC, Bgp4V2AddressFamilyIdentifierTC,
skipping to change at page 26, line 44 skipping to change at page 26, line 41
bgp4V2NlriEntry OBJECT-TYPE bgp4V2NlriEntry OBJECT-TYPE
SYNTAX Bgp4V2NlriEntry SYNTAX Bgp4V2NlriEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a path to a network." "Information about a path to a network."
INDEX { INDEX {
bgp4V2PeerInstance, bgp4V2PeerInstance,
bgp4V2NlriAfi, bgp4V2NlriAfi,
bgp4V2NlriSafi, bgp4V2NlriSafi,
bgp4V2NlriPrefixType,
bgp4V2NlriPrefix, bgp4V2NlriPrefix,
bgp4V2NlriPrefixLen, bgp4V2NlriPrefixLen,
bgp4V2PeerLocalAddrType,
bgp4V2PeerLocalAddr,
bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddrType,
bgp4V2PeerRemoteAddr, bgp4V2PeerRemoteAddr,
bgp4V2NlriIndex bgp4V2NlriIndex
} }
::= { bgp4V2NlriTable 1 } ::= { bgp4V2NlriTable 1 }
Bgp4V2NlriEntry ::= SEQUENCE { Bgp4V2NlriEntry ::= SEQUENCE {
bgp4V2NlriIndex bgp4V2NlriIndex
Unsigned32, Unsigned32,
bgp4V2NlriAfi bgp4V2NlriAfi
skipping to change at page 29, line 4 skipping to change at page 28, line 48
bgp4V2NlriSafi OBJECT-TYPE bgp4V2NlriSafi OBJECT-TYPE
SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subsequent address family of the prefix for "The subsequent address family of the prefix for
this NLRI" this NLRI"
REFERENCE REFERENCE
"RFC 4760 - Multiprotocol Extensions for BGP-4" "RFC 4760 - Multiprotocol Extensions for BGP-4"
::= { bgp4V2NlriEntry 3 } ::= { bgp4V2NlriEntry 3 }
bgp4V2NlriPrefixType OBJECT-TYPE bgp4V2NlriPrefixType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the IP address prefix in the "The type of the IP address prefix in the
Network Layer Reachability Information field. Network Layer Reachability Information field.
The value of this object is derived from the The value of this object is derived from the
appropriate value from the bgp4V2NlriAfi field. appropriate value from the bgp4V2NlriAfi field.
Where an appropriate InetAddressType is not Where an appropriate InetAddressType is not
available, the value of the object must be available, the value of the object must be
unknown(0)." unknown(0)."
::= { bgp4V2NlriEntry 4 } ::= { bgp4V2NlriEntry 4 }
skipping to change at page 37, line 10 skipping to change at page 37, line 6
SYNTAX Bgp4V2AdjRibsOutEntry SYNTAX Bgp4V2AdjRibsOutEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"List of BGP routes that have been placed into a "List of BGP routes that have been placed into a
peer's Adj-Ribs-Out." peer's Adj-Ribs-Out."
INDEX { INDEX {
bgp4V2PeerInstance, bgp4V2PeerInstance,
bgp4V2NlriAfi, bgp4V2NlriAfi,
bgp4V2NlriSafi, bgp4V2NlriSafi,
bgp4V2NlriPrefixType,
bgp4V2NlriPrefix, bgp4V2NlriPrefix,
bgp4V2NlriPrefixLen, bgp4V2NlriPrefixLen,
bgp4V2PeerLocalAddrType,
bgp4V2PeerLocalAddr,
bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddrType,
bgp4V2PeerRemoteAddr, bgp4V2PeerRemoteAddr,
bgp4V2AdjRibsOutIndex bgp4V2AdjRibsOutIndex
} }
::= { bgp4V2AdjRibsOutTable 1 } ::= { bgp4V2AdjRibsOutTable 1 }
Bgp4V2AdjRibsOutEntry ::= SEQUENCE { Bgp4V2AdjRibsOutEntry ::= SEQUENCE {
bgp4V2AdjRibsOutIndex bgp4V2AdjRibsOutIndex
Unsigned32, Unsigned32,
bgp4V2AdjRibsOutRoute bgp4V2AdjRibsOutRoute
skipping to change at page 44, line 15 skipping to change at page 44, line 10
the sheer messiness of representing the BGP protocol in SMIv2. the sheer messiness of representing the BGP protocol in SMIv2.
I owe particular thanks to Susan Hares as a mentor who let me dive I owe particular thanks to Susan Hares as a mentor who let me dive
head-first into the world of Internet standards work by saying, "We head-first into the world of Internet standards work by saying, "We
have this MIB that just needs a little cleanup to advance in the have this MIB that just needs a little cleanup to advance in the
standards process." standards process."
11. Acknowledgements 11. 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, all individuals you contributed Inter-Domain Routing Working Group and individuals who contributed to
to RFCs 1269, 1657 and 4273. RFCs 1269, 1657 and 4273.
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 author wishes to acknowledge the fine work of BGP-4 in RFC 1657. The author wishes to acknowledge the fine work of
these original authors. these original authors.
12. References 12. References
12.1. Normative References 12.1. Normative References
skipping to change at page 46, line 4 skipping to change at line 2123
Reflection: An Alternative to Full Mesh Internal BGP Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, April 2006. (IBGP)", RFC 4456, April 2006.
Author's Address Author's Address
Jeffrey Haas Jeffrey Haas
Arbor Networks Arbor Networks
Phone: Phone:
EMail: jhaas@arbor.net EMail: jhaas@arbor.net
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 31 change blocks. 
36 lines changed or deleted 38 lines changed or added

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