draft-ietf-idr-bgp4-mibv2-04.txt   draft-ietf-idr-bgp4-mibv2-05.txt 
Inter-Domain Routing Working Group J. Haas Inter-Domain Routing Working Group J. Haas
Internet Draft NextHop Internet Draft NextHop
S. Hares S. Hares
NextHop NextHop
W. Tackabury W. Tackabury
Gold Wire Technology Gold Wire Technology
January 12, 2004 July 13, 2005
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),
Second Version Second Version
<draft-ietf-idr-bgp4-mibv2-04.txt> <draft-ietf-idr-bgp4-mibv2-05.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 RFC2026. all provisions of Section 10 of RFC2026.
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 38 skipping to change at page 1, line 38
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 mate- time. It is inappropriate to use Internet-Drafts as reference mate-
rial or to cite them other than as "work in progress." rial 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.
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
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 TCP/IP-based internets. for use with network management protocols in TCP/IP-based internets.
In particular, this MIB defines objects that facilitate the In particular, this MIB defines objects that facilitate the manage-
management of the Border Gateway Protocol Version 4 (BGP4). ment of the Border Gateway Protocol Version 4 (BGP4).
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
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. Border Gateway Protocol Version 4.
skipping to change at page 5, line 49 skipping to change at page 6, line 15
per-row-data requirements of bgpM2PeerTable instance retrieval so as per-row-data requirements of bgpM2PeerTable instance retrieval so as
to make such per-row retrieval unwieldy for the management applica- to make such per-row retrieval unwieldy for the management applica-
tion. tion.
3.2.1. bgpM2PeerCapabilities 3.2.1. bgpM2PeerCapabilities
bgpM2PeerCapabilitiesData has objects and tables to describe BGP bgpM2PeerCapabilitiesData has objects and tables to describe BGP
capabilities locally supported, and those reported and negotiated capabilities locally supported, and those reported and negotiated
over each peer session. For tables supporting each of these capa- over each peer session. For tables supporting each of these capa-
bility sets, capability code and data value are provided. Attention bility sets, capability code and data value are provided. Attention
must be given to the fact that multiple instances of a given must be given to the fact that multiple instances of a given capabil-
capability can be transmitted between BGP speakers. ity can be transmitted between BGP speakers.
3.2.2. bgpM2PeerCounters 3.2.2. bgpM2PeerCounters
The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol
exchanges/FSM transitions, and discrete number of NLRIs exchanged per exchanges/FSM transitions, and discrete number of NLRIs exchanged per
peering session, respectively. This is independent of actual peering session, respectively. This is independent of actual
exchanged path attributes, which are tabularized later in the MIB exchanged path attributes, which are tabularized later in the MIB
module. Note that session transitions as reflected in changes of module. Note that session transitions as reflected in changes of
instances within this table may also be reflected in issuance of instances within this table may also be reflected in issuance of
bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs. bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs.
skipping to change at page 6, line 49 skipping to change at page 7, line 16
its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg- its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg-
PeerAuthTable. These are used to facilitate direct creation of peer- PeerAuthTable. These are used to facilitate direct creation of peer-
ing sessions by the management application. The function of columnar ing sessions by the management application. The function of columnar
OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote
address, version negotiation, and various row-administrative address, version negotiation, and various row-administrative
attributes (RowStatus and StorageType SYNTAXes) are straightforward attributes (RowStatus and StorageType SYNTAXes) are straightforward
enough. The only subtlety with respect to how peering sessions are enough. The only subtlety with respect to how peering sessions are
activated from usage of this table, and how the activated sessions activated from usage of this table, and how the activated sessions
are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta- are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta-
tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar
object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two val-
values. When a peering session, as reflected through its row ues. When a peering session, as reflected through its row instance
instance in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus instance value
instance value in that row set to running(2) at the time of the SYN- in that row set to running(2) at the time of the SYNTAX RowStatus
TAX RowStatus object instance of bgpM2CfgPeerRowEntryStatus set to object instance of bgpM2CfgPeerRowEntryStatus set to active(1), the
active(1), the peering session will in fact be activated in the BGP peering session will in fact be activated in the BGP routing process
routing process (in addition to having its row instance created in (in addition to having its row instance created in the bgpM2Cfg-
the bgpM2CfgPeerTable and bgpM2CfgPeerAdminStatusTable). In this PeerTable and bgpM2CfgPeerAdminStatusTable). In this case, the asso-
case, the associated row of the bgpM2CfgPeerAdminStatusTable row ciated row of the bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdmin-
bgpM2CfgPeerAdminStatus instance would have the value of start(2). Status instance would have the value of start(2). If, in the prior
If, in the prior example, the bgpM2CfgPeerStatus is halted(1) at the example, the bgpM2CfgPeerStatus is halted(1) at the time of the
time of the bgpM2CfgPeerRowEntryStatus instance set to active(1), bgpM2CfgPeerRowEntryStatus instance set to active(1), only the peer-
only the peering table entries would be created at this time of acti- ing table entries would be created at this time of activation, with-
vation, without the peering session being automatically started. The out the peering session being automatically started. The bgpM2Cfg-
bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance PeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance associated
associated with the session would in this case reflect a value of with the session would in this case reflect a value of stop(1).
stop(1).
Since the row entries of the per-peer configuration tables which AUG- Since the row entries of the per-peer configuration tables which AUG-
MENT the bgpM2CfgPeerTable logically fate-share the row instances in MENT the bgpM2CfgPeerTable logically fate-share the row instances in
the bgpM2CfgPeerTable which they are AUGMENTing, they also share the the bgpM2CfgPeerTable which they are AUGMENTing, they also share the
same StorageType and RowStatus SYNTAX object sense of the bgpM2Cfg- same StorageType and RowStatus SYNTAX object sense of the bgpM2Cfg-
PeerTable rows which they augment. PeerTable rows which they augment.
3.3. BGP Routing Information Base Data 3.3. BGP Routing Information Base Data
An important table for providing index information for other tables An important table for providing index information for other tables
skipping to change at page 10, line 11 skipping to change at page 10, line 26
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType, TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType,
RowStatus RowStatus
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;
bgpM2 MODULE-IDENTITY bgpM2 MODULE-IDENTITY
LAST-UPDATED "200401120000Z" LAST-UPDATED "200507130000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@merit.net CONTACT-INFO "E-mail: idr@merit.net
Jeffrey Haas (Editor) Jeffrey Haas (Editor)
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Ann Arbor, MI 48108 Ann Arbor, MI 48108
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"
skipping to change at page 94, line 51 skipping to change at page 95, line 25
Creation of separate bgpM2AdjRibsOutTable. Creation of separate bgpM2AdjRibsOutTable.
Appearance of NLRI table notions such as 'opaque type'. Appearance of NLRI table notions such as 'opaque type'.
Overhaul of specification of AS Path types to accommodate eas- Overhaul of specification of AS Path types to accommodate eas-
ier management at time of route aggregation. ier management at time of route aggregation.
9. Normative References 9. Normative References
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management Proto-
Protocol (SNMPv3)", RFC 2574, April 1999. col (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 Infor- Rose, M., and S. Waldbusser, "Structure of Management Infor-
mation Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. mation Version 2 (SMIv2)", STD 58, RFC 2578, April 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.,
skipping to change at page 97, line 22 skipping to change at page 97, line 48
Wayne Tackabury Wayne Tackabury
Gold Wire Technology Gold Wire Technology
411 Waverley Oaks Rd. 411 Waverley Oaks Rd.
Waltham, MA 02452-8401 Waltham, MA 02452-8401
Phone: +1 781 398-8819 Phone: +1 781 398-8819
Fax: +1 781 398-8811 Fax: +1 781 398-8811
Email: wayne@goldwiretech.com Email: wayne@goldwiretech.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this doc-
ument itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop-
ing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as
required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be This document is subject to the rights, licenses and restrictions
revoked by the Internet Society or its successors or assigns. contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein is provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 2 2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3 2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3
2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 3
3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 3 3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 5 3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 6
3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6 3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6
3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6 3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6
3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 6 3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 6
3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 7 3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 7
3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 8 3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 8
3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 8 3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 9
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5. Intellectual Property Rights . . . . . . . . . . . . . . . . . . 91 5. Intellectual Property Rights . . . . . . . . . . . . . . . . . . 92
6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 92 6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 92
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 93 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 93
8. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 93 8. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 93
9. Normative References . . . . . . . . . . . . . . . . . . . . . . 94 9. Normative References . . . . . . . . . . . . . . . . . . . . . . 95
10. Informative References . . . . . . . . . . . . . . . . . . . . . 96 10. Informative References . . . . . . . . . . . . . . . . . . . . . 97
11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 97
12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 97 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 97
 End of changes. 

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