draft-ietf-idr-bgp4-mib-01.txt   draft-ietf-idr-bgp4-mib-02.txt 
Network Working Group S. Willis Network Working Group S. Willis
INTERNET DRAFT BayNetworks INTERNET DRAFT BayNetworks
J. Burruss J. Burruss
BayNetworks Windata
J. Chu J. Chu
IBM Corporation IBM Corporation
J. Johnson J. Johnson
cisco Systems cisco Systems
January 1996 March 1996
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-01.txt> <draft-ietf-idr-bgp4-mib-02.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its Working Groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet-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
Internet Drafts may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is not appropriate to use Internet Drafts as time. It is inappropriate to use Internet- Drafts as reference material
reference material or to cite them other than as a "working draft" or or to cite them other than as ``work in progress.''
"work in progress."
Please check the I-D abstract listing contained in each Internet Draft To learn the current status of any Internet-Draft, please check the
directory to learn the current status of this or any other Internet ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow
Draft. Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract Abstract
This memo is an extension to the SNMP MIB. It specifies an IAB This memo is an extension to the SNMP MIB. It specifies an IAB
standards track protocol for the Internet community, and requests standards track protocol for the Internet community, and requests
discussion and suggestions for improvements. The origin of this memo is discussion and suggestions for improvements. The origin of this memo is
from RFC 1269 "Definitions of Managed Objects for the Board Gateway from RFC 1269 "Definitions of Managed Objects for the Board Gateway
Protocol (Version 3)" written by the first two authors of this memo, Protocol (Version 3)" written by the first two authors of this memo,
which was updated to support BGP-4 in RFC 1657. This memo fixes errors which was updated to support BGP-4 in RFC 1657. This memo fixes errors
introduced when the MIB was converted to use the SNMPv2 SMI. introduced when the MIB was converted to use the SNMPv2 SMI, as well as
updates references to the Draft Standard SNMPv2 SMI documents.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
bgp@ans.net. bgp@ans.net.
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing the Border Gateway Protocol Version 4 or lower [1, 2]. managing the Border Gateway Protocol Version 4 or lower [1, 2].
2. The SNMPv2 Network Management Framework 2. The SNMP Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
RFC 1442 which defines the SMI, the mechanisms used for describing
and naming objects for the purpose of management.
RFC 1213 defines MIB-II, the core set of managed objects for the
Internet suite of protocols.
RFC 1445 which defines the administrative and other architectural
aspects of the framework.
RFC 1448 which defines the protocol used for network access to The SNMP Network Management Framework consists of several components.
managed objects. For the purpose of this specification, the applicable components of the
Framework are the SMI and related documents [3, 4, 5], which define the
mechanisms used for describing and naming objects for the purpose of
management.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
3. Object Definitions 3. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
skipping to change at line 105 skipping to change at page 3, line 18
from all BGP-4 peers. The actual attributes used in determining a route from all BGP-4 peers. The actual attributes used in determining a route
are a subset of the received attribute tables after local routing policy are a subset of the received attribute tables after local routing policy
has been applied. has been applied.
5. Definitions 5. 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 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;
mib-2
FROM RFC1213-MIB;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "9512110000Z" LAST-UPDATED "9601080000Z"
ORGANIZATION "IETF BGP Working Group" ORGANIZATION "IETF BGP Working Group"
CONTACT-INFO CONTACT-INFO
" John Chu (Editor) " John Chu (Editor)
Postal: IBM Corp. Postal: IBM Corp.
P.O.Box 704 P.O.Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
US US
Tel: +1 914 784 7839 Tel: +1 914 784 7839
Fax: +1 914 784 6205 Fax: +1 914 784 6205
skipping to change at line 1011 skipping to change at page 22, line 18
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 } ::= { bgpMIBGroups 4 }
bgp4MIBNotiicationGroup NOTIFICATION-GROUP bgp4MIBNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablished, NOTIFICATIONS { bgpEstablished,
bgpBackwardTransition } bgpBackwardTransition }
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."
::= { bgpMIBGroups 4 } ::= { bgpMIBGroups 4 }
END END
6. Acknowledgements 6. 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
Interconnectivity Working Group, and particularly the following Inter-Domain Routing Working Group, and particularly the following
individuals: individuals:
Yakov Rekhter, cisco Systems Yakov Rekhter, cisco Systems
Rob Coltun, Fore Rob Coltun, Fore
Guy Almes, ANS Guy Almes, ANS
Jeff Honig, Cornell Theory Center Jeff Honig, Cornell Theory Center
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
Dennis Ferguson, Ipsilon Dennis Ferguson, Ipsilon
Mike Mathis, PSC Mike Mathis, PSC
John Krawczyk, BayNetworks John Krawczyk, BayNetworks
skipping to change at line 1049 skipping to change at page 23, line 32
Andrew Partan, UUNET Andrew Partan, UUNET
Robert Snyder, cisco Systems Robert Snyder, cisco Systems
Dimitry Haskin, BayNetworks Dimitry Haskin, BayNetworks
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
Joel Halpern, NewBridge Joel Halpern, NewBridge
Nick Thille, cisco Systems Nick Thille, cisco Systems
7. References 7. References
[1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)",
RFC1771, March 1995 RFC 1771, March 1995.
[2] Rekhter, Y., Gross, P., "Application of the Border [2] Rekhter, Y., Gross, P., "Application of the Border
Gateway Protocol in the Internet", RFC1772, March 1995 Gateway Protocol in the Internet", RFC 1772, March 1995.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Conformance Statements for Version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC 1904,
January 1996.
8. Security Considerations 8. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
Authors' Address Authors' Address
Steven Willis Steve Willis
BayNetworks Bay Networks, Inc.
15 Crosby Drive 3 Federal St
Bedford, MA 01730 Billerica, MA 01821
Phone: +1 617 275 2400 Phone: +1 508 436 3927
Email: swillis@baynetworks.com Email: swillis@BayNetworks.com
John Burruss John Burruss
BayNetworks Windata Inc.
15 Crosby Drive 543 Great Road
Bedford, MA 01730 Littleton MA 01460
Phone: +1 617 275 2400 Phone: +1 508 952 0170
Email: jburruss@baynetworks.com Email: jburruss@windata.com
John Chu John Chu
IBM Corporation IBM Corporation
P.O.Box 704 P.O.Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
Phone: +1 914 784 7839 Phone: +1 914 784 7839
Email: jychu@watson.ibm.com Email: jychu@watson.ibm.com
Jeff Johnson Jeff Johnson
 End of changes. 

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