draft-ietf-idr-bgp4-mib-09.txt		draft-ietf-idr-bgp4-mib-10.txt
	skipping to change at page 1, line 20		skipping to change at page 1, line 20
	Argon Networks		Argon Networks
	J. Burruss		J. Burruss
	WinData		WinData
	Editor of previous version:		Editor of previous version:
	J. Chu		J. Chu
	Cosine		Cosine
	March 2002		March 2002
	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-09.txt>		<draft-ietf-idr-bgp4-mib-10.txt>
	1. Status of this Memo		1. 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 RFC 2026.		all provisions of Section 10 of RFC 2026.
	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 3, line 49		skipping to change at page 3, line 49
	MIB.		MIB.
	6. Overview		6. Overview
	These objects are used to control and manage a BGP-4 implementation.		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		Apart from a few system-wide scalar objects, this MIB is broken into
	three tables: the BGP Peer Table, the BGP Received Path Attribute		three tables: the BGP Peer Table, the BGP Received Path Attribute
	Table, and the BGP-4 Received Path Attribute Table. The BGP Peer		Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
	Table contains information about state and current activity of		Table contains information about state and current activity of
	connections with the BGP peers. The Received Path Attribute Table		connections with the BGP peers. The BGP Received Path Attribute
	contains path attributes received from all peers running BGP version		Table contains path attributes received from all peers running BGP
	3 or less. The BGP-4 Received Path Attribute Table contains path		version 3 or less. The BGP-4 Received Path Attribute Table contains
	attributes received from all BGP-4 peers. The actual attributes used		path attributes received from all BGP-4 peers. The actual attributes
	in determining a route are a subset of the received attribute tables		used in determining a route are a subset of the received attribute
	after local routing policy has been applied.		tables after local routing policy has been applied.
	7. Definitions		7. 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, mib-2		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;
	bgp MODULE-IDENTITY		bgp MODULE-IDENTITY
	LAST-UPDATED "200203010000Z"		LAST-UPDATED "200211040000Z"
	ORGANIZATION "IETF IDR Working Group"		ORGANIZATION "IETF IDR Working Group"
	CONTACT-INFO "E-mail: idr@merit.net		CONTACT-INFO "E-mail: idr@merit.net
	Jeff Haas, Sue Hares (Editors)		Jeff Haas, Sue Hares (Editors)
	825 Victors Way		825 Victors Way
	Suite 100		Suite 100
	Ann Arbor, MI 48108-2738		Ann Arbor, MI 48108-2738
	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 5, line 47		skipping to change at page 5, line 47
	definition in RFC 1269.		definition in RFC 1269.
	2) Added compliance and conformance info.		2) Added compliance and conformance info.
	3) Updated for latest BGP information		3) Updated for latest BGP information
	draft-ietf-idr-bgp4-17.txt for value of		draft-ietf-idr-bgp4-17.txt for value of
	bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,		bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
	bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,		bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,
	bgp4PathAttrASPathSegement.		bgp4PathAttrASPathSegement.
	4) Added additional clarification commments where		4) Added additional clarification commments where
	needed.		needed.
	5) Noted where objects do not fully reflect		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 }		::= { mib-2 15 }
	bgpVersion OBJECT-TYPE		bgpVersion OBJECT-TYPE
	SYNTAX OCTET STRING (SIZE (1..255))		SYNTAX OCTET STRING (SIZE (1..255))
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Vector of supported BGP protocol version		"Vector of supported BGP protocol version
	numbers. Each peer negotiates the version		numbers. Each peer negotiates the version
	from this vector. Versions are identified		from this vector. Versions are identified
	via the string of bits contained within this		via the string of bits contained within this
	object. The first octet contains bits 0 to		object. The first octet contains bits 0 to
	skipping to change at page 13, line 9		skipping to change at page 13, line 12
	SYNTAX Integer32 ( 0 | 3..65535 )		SYNTAX Integer32 ( 0 | 3..65535 )
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Time interval in seconds for the Hold		"Time interval in seconds for the Hold
	Timer established with the peer. The		Timer established with the peer. The
	value of this object is calculated by this		value of this object is calculated by this
	BGP speaker by using the smaller of the		BGP speaker by using the smaller of the
	value in bgpPeerHoldTimeConfigured and the		value in bgpPeerHoldTimeConfigured and the
	Hold Time received in the OPEN message.		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		if it is not zero (0). If the value is
	zero (0), the Hold Timer has either not been		zero (0), the Hold Timer has either not been
	established with the peer, or, the value of		established with the peer, or, the value of
	bgpPeerHoldTimeConfigured is zero (0)."		bgpPeerHoldTimeConfigured is zero (0)."
	::= { bgpPeerEntry 18 }		::= { bgpPeerEntry 18 }
	bgpPeerKeepAlive OBJECT-TYPE		bgpPeerKeepAlive OBJECT-TYPE
	SYNTAX Integer32 ( 0 | 1..21845 )		SYNTAX Integer32 ( 0 | 1..21845 )
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	skipping to change at page 15, line 29		skipping to change at page 15, line 32
	::= { bgpPeerEntry 24 }		::= { bgpPeerEntry 24 }
	bgpIdentifier OBJECT-TYPE		bgpIdentifier OBJECT-TYPE
	SYNTAX IpAddress		SYNTAX IpAddress
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The BGP Identifier of local system."		"The BGP Identifier of local system."
	::= { bgp 4 }		::= { 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		-- one entry per path to a network, path attributes
	-- received from all peers running BGP version 3 or less.		-- received from all peers running BGP version 3 or less.
	-- This table is obsolete, having been replaced in		-- This table is obsolete, having been replaced in
	-- functionality with the bgp4PathAttrTable.		-- functionality with the bgp4PathAttrTable.
	bgpRcvdPathAttrTable OBJECT-TYPE		bgpRcvdPathAttrTable OBJECT-TYPE
	SYNTAX SEQUENCE OF BgpPathAttrEntry		SYNTAX SEQUENCE OF BgpPathAttrEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS obsolete		STATUS obsolete
	DESCRIPTION		DESCRIPTION
	skipping to change at page 22, line 23		skipping to change at page 22, line 25
	::= { bgp4PathAttrEntry 8 }		::= { bgp4PathAttrEntry 8 }
	bgp4PathAttrAtomicAggregate OBJECT-TYPE		bgp4PathAttrAtomicAggregate OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	lessSpecificRouteNotSelected(1),		lessSpecificRouteNotSelected(1),
	lessSpecificRouteSelected(2)		lessSpecificRouteSelected(2)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		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		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 }		::= { bgp4PathAttrEntry 9 }
	bgp4PathAttrAggregatorAS OBJECT-TYPE		bgp4PathAttrAggregatorAS OBJECT-TYPE
	SYNTAX Integer32 (0..65535)		SYNTAX Integer32 (0..65535)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The AS number of the last BGP4 speaker that		"The AS number of the last BGP4 speaker that
	performed route aggregation. A value of		performed route aggregation. A value of
	zero (0) indicates the absence of this		zero (0) indicates the absence of this
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/