--- 1/draft-ietf-idr-bgp4-mib-04.txt 2006-02-04 23:30:42.000000000 +0100 +++ 2/draft-ietf-idr-bgp4-mib-05.txt 2006-02-04 23:30:43.000000000 +0100 @@ -1,46 +1,46 @@ Network Working Group S. Hares -INTERNET DRAFT Merit - J. Johnson - RedBack Networks +INTERNET DRAFT NextHop + J. Haas + NextHop S. Willis Argon Networks J. Burruss WinData J. Chu - IBM Corporation - February 1999 + Cosine + December 2000 Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) - + Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." 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. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract @@ -63,21 +63,21 @@ In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. 2. The SNMP Network Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2271 [3]. - o Mechanisms for describing and naming objects and events for + o bgp 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 RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The second version, called SMIv2, is described in RFC 1902 [7], RFC 1903 [8] and RFC 1904 [9]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [10]. A second version of the SNMP message protocol, which is not an Internet standards @@ -142,56 +142,53 @@ BGP4-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress, Integer32, Counter32, Gauge32, mib-2 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; bgp MODULE-IDENTITY - LAST-UPDATED "9902100000Z" + LAST-UPDATED "0012100000Z" ORGANIZATION "IETF IDR Working Group" CONTACT-INFO "E-mail: idr@merit.net Susan Hares (Editor) - Merit Network - 4251 Plymouth Road - Suite C - Ann Arbor, MI 48105-2785 + 517 W. William Street + Ann Arbor, MI 48103-4943 Tel: +1 734 936 2095 - Fax: +1 734 647 3185 - E-mail: skh@merit.edu + Fax: +1 734 615-3241 + E-mail: skh@nexthop.com" - Jeff Johnson (Editor) - RedBack Networks, Inc. - 1389 Moffett Park Drive - Sunnyvale, CA 94089-1134 - Tel: +1 408 548 3516 - Fax: +1 408 548 3599 - E-mail: jeff@redback.com" DESCRIPTION "The MIB module for BGP-4." - REVISION "9902100000Z" + REVISION "0012100000Z" DESCRIPTION "Corrected duplicate OBJECT IDENTIFIER assignment in the conformance information." REVISION "9601080000Z" DESCRIPTION "1) Fixed the definitions of the traps to make them equivalent to their initial definition in RFC 1269. - 2) Added compliance and conformance info." + 2) Added compliance and conformance info. + 3) Updated for latest BGP information + draft-ietf-idr-bgp4-10.txt for value of + bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, + bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, + bgp4PathAttrASPathSegement." + ::= { mib-2 15 } bgpVersion OBJECT-TYPE - SYNTAX OCTET STRING (SIZE (1..255)) + SYNTAX OCTET STRING (SIZE (1..32)) --- change to match draft MAX-ACCESS read-only STATUS current DESCRIPTION "Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit @@ -320,21 +317,21 @@ the BGP Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication." ::= { bgpPeerEntry 3 } bgpPeerNegotiatedVersion OBJECT-TYPE - SYNTAX Integer32 + SYNTAX Integer[1..255] --- change to match draft MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated version of BGP running between the two peers." ::= { bgpPeerEntry 4 } bgpPeerLocalAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only @@ -779,21 +776,21 @@ egp(2),-- networks learned via EGP incomplete(3) -- undetermined } MAX-ACCESS read-only STATUS current DESCRIPTION "The ultimate origin of the path information." ::= { bgp4PathAttrEntry 4 } bgp4PathAttrASPathSegment OBJECT-TYPE - SYNTAX OCTET STRING (SIZE (2..255)) + SYNTAX OCTET STRING (SIZE (2..500)) --- [change 3 possible to have 500*4 bytes of aSpath] MAX-ACCESS read-only STATUS current DESCRIPTION "The sequence of AS path segments. Each AS path segment is represented by a triple . The type is a 1-octet field which has two possible values: 1 AS_SET: unordered set of ASs a @@ -814,42 +811,44 @@ first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;" ::= { bgp4PathAttrEntry 5 } bgp4PathAttrNextHop OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The address of the border router that should - be used for the destination network." + be used for the destination network. This + address is the nexthop address received in + the UPDATE packet." ::= { bgp4PathAttrEntry 6 } bgp4PathAttrMultiExitDisc OBJECT-TYPE - SYNTAX INTEGER (-1..2147483647) + SYNTAX INTEGER (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This metric is used to discriminate between multiple exit points to an adjacent autonomous - system. A value of -1 indicates the absence of + system. A value of -1 (4294967295) indicates the absence of this attribute." ::= { bgp4PathAttrEntry 7 } bgp4PathAttrLocalPref OBJECT-TYPE - SYNTAX INTEGER (-1..2147483647) + SYNTAX INTEGER (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The originating BGP4 speaker's degree of preference for an advertised route. A value of - -1 indicates the absence of this attribute." + -1 (4294967295) indicates the absence of this attribute." ::= { bgp4PathAttrEntry 8 } bgp4PathAttrAtomicAggregate OBJECT-TYPE SYNTAX INTEGER { lessSpecificRrouteNotSelected(1), lessSpecificRouteSelected(2) } MAX-ACCESS read-only STATUS current DESCRIPTION @@ -862,59 +861,64 @@ SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute." ::= { bgp4PathAttrEntry 10 } bgp4PathAttrAggregatorAddr OBJECT-TYPE - SYNTAX IpAddress + SYNTAX IpAddress propagation of AS path zero] MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the last BGP4 speaker that performed route aggregation. A value of - 0.0.0.0 indicates the absence of this attribute." + 0.0.0.0 indicates the absence of this attribute. + Note propagation of AS of zero is illegal in internet." ::= { bgp4PathAttrEntry 11 } bgp4PathAttrCalcLocalPref OBJECT-TYPE - SYNTAX INTEGER (-1..2147483647) + SYNTAX INTEGER (0 ..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The degree of preference calculated by the receiving BGP4 speaker for an advertised route. - A value of -1 indicates the absence of this + A value of -1 (4294967295) indicates the absence of this attribute." ::= { bgp4PathAttrEntry 12 } bgp4PathAttrBest OBJECT-TYPE SYNTAX INTEGER { false(1),-- not chosen as best route true(2) -- chosen as best route } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of whether or not this route was chosen as the best BGP4 route." ::= { bgp4PathAttrEntry 13 } - bgp4PathAttrUnknown OBJECT-TYPE + bgp4PathAttrUnknown OBJECT-TYPE [format not specific enough + [switch to path format + type length value] SYNTAX OCTET STRING (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "One or more path attributes not understood - by this BGP4 speaker. Size zero (0) indicates + by this BGP4 speaker. Path attributes are + recorded in the Update Path attribute format + of type, length, value. Size zero (0) indicates the absence of such attribute(s). Octets beyond the maximum size, if any, are not recorded by this object." ::= { bgp4PathAttrEntry 14 } -- Traps. -- note that in RFC 1657, bgpTraps was incorrectly -- assigned a value of { bgp 7 }, and each of the -- traps had the bgpPeerRemoteAddr object inappropriately @@ -1074,37 +1078,38 @@ proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. 7. Acknowledgements We would like to acknowledge the assistance of all the members of the Inter-Domain Routing Working Group, and particularly the following individuals: Yakov Rekhter, cisco Systems - Rob Coltun, Fore - Guy Almes, ANS + Rob Coltun, Redback + Guy Almes, Internet2 Jeff Honig, Cornell Theory Center Marshall T. Rose, Dover Beach Consulting, Inc. Dennis Ferguson, Juniper Networks Mike Mathis, PSC John Krawczyk, Bay Networks - Curtis Villamizar, ANS + Curtis Villamizar, Avici Dave LeRoy, Pencom Systems Paul Traina, Juniper Networks - Andrew Partan, UUNET + Andrew Partan, MFS Robert Snyder, cisco Systems - Dimitry Haskin, Bay Networks + Dimitry Haskin, Nortel Peder Chr Norgaard, Telebit Communications A/S - Joel Halpern, NewBridge + Joel Halpern, CTO Longitude Systems, Inc. Nick Thille, RedBack Networks Bert Wijnen, IBM + Shane Wright, NextHop The origin of this document is from RFC 1269 "Definitions of Managed Objects for the Border Gateway Protocol (Version 3)" written by Steve Willis and John Burruss, which was updated by John Chu to support BGP-4 in RFC 1657. The editors wishes to acknowledge the fine work of these original authors. 8. References [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC @@ -1230,27 +1235,26 @@ It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 10. Authors' Address Susan Hares - Merit Network, Inc. - 4251 Plymouth Road - Suite C - Ann Arbor, MI 48105-2785 + NextHop Technologies + 517 Williams + Ann Arbor, MI 48103-4943 Phone: +1 734 936 2095 - Fax: +1 734 647 3185 - Email: skh@merit.edu + Fax: +1 734 615-3241 + Email: skh@nexthop.com Jeff Johnson RedBack Networks, Inc. 1389 Moffett Park Drive Sunnyvale, CA 94089 Phone: +1 408 548 3516 Email: jeff@redback.com Steve Willis Argon Networks @@ -1261,25 +1265,25 @@ Email: swills@argon.com John Burruss Windata Inc. 543 Great Road Littleton MA 01460 Phone: +1 508 952 0170 Email: jburruss@windata.com John Chu - IBM Corporation - P.O.Box 704 - Yorktown Heights, NY 10598 - Phone: +1 914 784 7839 - Email: jychu@watson.ibm.com + Cosine Communications + 1200 Bridge Parkway + Redwood City, CA 94065 + Phone: 650-637-4780 + Email: jchu@cosinecom.com 11. Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. 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