--- 1/draft-ietf-idr-bgp4-mib-09.txt 2006-02-04 23:30:47.000000000 +0100 +++ 2/draft-ietf-idr-bgp4-mib-10.txt 2006-02-04 23:30:47.000000000 +0100 @@ -9,21 +9,21 @@ Argon Networks J. Burruss WinData Editor of previous version: J. Chu Cosine March 2002 Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) - + 1. 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. @@ -121,40 +121,40 @@ MIB. 6. Overview 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 three tables: the BGP Peer Table, the BGP Received Path Attribute Table, and the BGP-4 Received Path Attribute Table. The BGP Peer Table contains information about state and current activity of - connections with the BGP peers. The Received Path Attribute Table - contains path attributes received from all peers running BGP version - 3 or less. The BGP-4 Received Path Attribute Table contains path - attributes received 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 has been applied. + connections with the BGP peers. The BGP Received Path Attribute + Table contains path attributes received from all peers running BGP + version 3 or less. The BGP-4 Received Path Attribute Table contains + path attributes received 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 has been applied. 7. Definitions 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 "200203010000Z" + LAST-UPDATED "200211040000Z" ORGANIZATION "IETF IDR Working Group" CONTACT-INFO "E-mail: idr@merit.net Jeff Haas, Sue Hares (Editors) 825 Victors Way Suite 100 Ann Arbor, MI 48108-2738 Tel: +1 734 222-1600 Fax: +1 734 222-1602 E-mail: jhaas@nexthop.com @@ -170,22 +170,25 @@ definition in RFC 1269. 2) Added compliance and conformance info. 3) Updated for latest BGP information draft-ietf-idr-bgp4-17.txt for value of bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrASPathSegement. 4) Added additional clarification commments where needed. 5) Noted where objects do not fully reflect - the protocol as Known Issues." + the protocol as Known Issues. + 6) Updated the DESCRIPTION for the + bgp4PathAttrAtomicAggregate object." ::= { mib-2 15 } + bgpVersion OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..255)) 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 @@ -491,21 +490,21 @@ SYNTAX Integer32 ( 0 | 3..65535 ) MAX-ACCESS read-only STATUS current DESCRIPTION "Time interval in seconds for the Hold Timer established with the peer. The value of this object is calculated by this BGP speaker by using the smaller of the value in bgpPeerHoldTimeConfigured and the Hold Time received in the OPEN message. - This value must be at lease three seconds + This value must be at least three seconds if it is not zero (0). If the value is zero (0), the Hold Timer has either not been established with the peer, or, the value of bgpPeerHoldTimeConfigured is zero (0)." ::= { bgpPeerEntry 18 } bgpPeerKeepAlive OBJECT-TYPE SYNTAX Integer32 ( 0 | 1..21845 ) MAX-ACCESS read-only STATUS current @@ -602,21 +602,21 @@ ::= { bgpPeerEntry 24 } bgpIdentifier OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The BGP Identifier of local system." ::= { bgp 4 } - -- Received Path Attribute Table. This table contains, + -- BGP Received Path Attribute Table. This table contains, -- one entry per path to a network, path attributes -- received from all peers running BGP version 3 or less. -- This table is obsolete, having been replaced in -- functionality with the bgp4PathAttrTable. bgpRcvdPathAttrTable OBJECT-TYPE SYNTAX SEQUENCE OF BgpPathAttrEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION @@ -909,23 +907,37 @@ ::= { bgp4PathAttrEntry 8 } bgp4PathAttrAtomicAggregate OBJECT-TYPE SYNTAX INTEGER { lessSpecificRouteNotSelected(1), lessSpecificRouteSelected(2) } MAX-ACCESS read-only STATUS current DESCRIPTION - "Whether or not a system has selected + "The original text for this object was: + + Whether or not a system has selected a less specific route without - selecting a more specific route." + selecting a more specific route. + + However, as of the current version of the BGP + specification, ATOMIC_AGGREGATE has been + deprecated. In this MIB, the value of this + object will be lessSpecificRouteNotSelected + if the ATOMIC_AGGREGATE attribute is present + in the Path Attributes and indicates that + the NLRI MUST NOT be made more specific. + + The value should be lessSpecificRouteSelected + if the ATOMIC_AGGREGATE attribute is missing + in the Path Attributes." ::= { bgp4PathAttrEntry 9 } bgp4PathAttrAggregatorAS OBJECT-TYPE SYNTAX Integer32 (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