draft-ietf-idr-bgp4-mib-13.txt		draft-ietf-idr-bgp4-mib-14.txt
	Network Working Group Editors of this version:		Network Working Group Editors of this version:
	INTERNET DRAFT J. Haas		INTERNET DRAFT J. Haas
	S. Hares		S. Hares
	NextHop Technologies		NextHop Technologies
	October 2003		April 2004
	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-13.txt>		<draft-ietf-idr-bgp4-mib-14.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 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 1, line 36		skipping to change at page 1, line 36
	material or to cite them other than as "work in progress."		material 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.		http://www.ietf.org/ietf/1id-abstracts.
	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.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2003). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	This memo is an extension to the SNMP MIB. It obsoletes RFC 1657 and		This memo is an extension to the SNMP MIB. It obsoletes RFC 1657 and
	RFC 1269.		RFC 1269.
	The origin of this memo is from RFC 1269 "Definitions of Managed		The origin of this memo is from RFC 1269 "Definitions of Managed
	Objects for the Border Gateway Protocol (Version 3)", which was		Objects for the Border Gateway Protocol (Version 3)", which was
	updated to support BGP-4 in RFC 1657. This memo fixes errors		updated to support BGP-4 in RFC 1657. This memo fixes errors
	introduced when the MIB was converted to use the SNMPv2 SMI, as well		introduced when the MIB was converted to use the SNMPv2 SMI, as well
	skipping to change at page 2, line 18		skipping to change at page 2, line 18
	also note errors where the MIB fails to fully represent the BGP		also note errors where the MIB fails to fully represent the BGP
	protocol. Work is currently in progress to replace this MIB with a		protocol. Work is currently in progress to replace this MIB with a
	new one representing the current state of the BGP protocol and its		new one representing the current state of the BGP protocol and its
	extensions.		extensions.
	Distribution of this memo is unlimited. Please forward comments to		Distribution of this memo is unlimited. Please forward comments to
	idr@ietf.org.		idr@ietf.org.
	Table of Contents		Table of Contents
	1. Introduction .................................................. 3		1. Introduction ................................................. 3
	2. The Internet-Standard Management Framework .................... 3		2. The Internet-Standard Management Framework ................... 3
	3. Overview ...................................................... 3		3. Overview ..................................................... 3
	4. Definitions ................................................... 4		4. Definitions .................................................. 4
	5. Intellectual Property ........................................ 29		5. Intellectual Property ....................................... 30
	6. Security Considerations ...................................... 30		6. Security Considerations ..................................... 31
	7. Acknowledgements ............................................. 32		7. Acknowledgements ............................................ 33
	8. Normative References ......................................... 33		8. Normative References ........................................ 34
	9. Informative References ....................................... 34		9. Editors' Address ............................................ 35
	10. Editors' Address ............................................. 35		10. Full Copyright Statement .................................... 35
	11. Full Copyright Statement ..................................... 35
	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 or lower [BGP, BGP4APP].		Border Gateway Protocol Version 4 or lower [BGP, BGP4APP].
	This memo obsoletes RFC 1657 and RFC 1269.		This memo obsoletes RFC 1657 and RFC 1269.
	skipping to change at page 4, line 17		skipping to change at page 4, line 17
	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 "200310090000Z"		LAST-UPDATED "200404220000Z"
	ORGANIZATION "IETF IDR Working Group"		ORGANIZATION "IETF IDR Working Group"
	CONTACT-INFO "E-mail: idr@ietf.org		CONTACT-INFO "E-mail: idr@ietf.org
	Jeffrey Haas, Susan Hares (Editors)		Jeffrey Haas, Susan Hares (Editors)
	NextHop Technologies		NextHop Technologies
	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
	skh@nexthop.com"		skh@nexthop.com"
	DESCRIPTION		DESCRIPTION
	"The MIB module for the BGP-4 protocol.		"The MIB module for the BGP-4 protocol.
	Copyright (C) The Internet Society (2003). This version		Copyright (C) The Internet Society (2004). This version
	of this MIB module is part of RFC yyyy; see the RFC		of this MIB module is part of RFC yyyy; see the RFC
	itself for full legal notices."		itself for full legal notices."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this note		-- RFC Ed.: replace yyyy with actual RFC number & remove this note
	REVISION "200310090000Z"		REVISION "200404220000Z"
	DESCRIPTION		DESCRIPTION
	"Changes from RFC 1657:		"Changes from RFC 1657:
	1) Fixed the definitions of the traps to		1) Fixed the definitions of the traps to
	make them equivalent to their initial		make them equivalent to their initial
	definition in RFC 1269.		definition in RFC 1269.
	2) Added compliance and conformance info.		2) Added compliance and conformance info.
	3) Updated information for the values of		3) Updated information for the values of
	bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,		bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
	bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,		bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,
	bgp4PathAttrASPathSegement.		bgp4PathAttrASPathSegement.
	4) Added additional clarification comments where		4) Added additional clarification comments 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		6) Updated the DESCRIPTION for the
	bgp4PathAttrAtomicAggregate object.		bgp4PathAttrAtomicAggregate object.
	7) The following objects have had their DESCRIPTION		7) The following objects have had their DESCRIPTION
	clause modified to remove the requirement to		clause modified to remove the text that suggested
	reset the counter to zero on a transition to		(using "should" verb) to initialize the counter
	the established state:		to zero on a transition to the established state:
	bgpPeerInUpdates, bgpPeerOutUpdates,		bgpPeerInUpdates, bgpPeerOutUpdates,
	bgpPeerInTotalMessages, bgpPeerOutTotalMessages		bgpPeerInTotalMessages, bgpPeerOutTotalMessages
			Those implementations that still do this are
			still compliant with this new wording.
			Appliciations should not assume counters to have
			started at zero.
	Published as RFC yyyy."		Published as RFC yyyy."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this note		-- RFC Ed.: replace yyyy with actual RFC number & remove this note
	REVISION "199405050000Z"		REVISION "199405050000Z"
	DESCRIPTION		DESCRIPTION
	"Translated to SMIv2 and published as RFC 1657."		"Translated to SMIv2 and published as RFC 1657."
	REVISION "199110261839Z"		REVISION "199110261839Z"
	DESCRIPTION		DESCRIPTION
	skipping to change at page 7, line 48		skipping to change at page 8, line 7
	bgpPeerInUpdateElapsedTime		bgpPeerInUpdateElapsedTime
	Gauge32		Gauge32
	}		}
	bgpPeerIdentifier OBJECT-TYPE		bgpPeerIdentifier OBJECT-TYPE
	SYNTAX IpAddress		SYNTAX IpAddress
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The BGP Identifier of this entry's BGP peer.		"The BGP Identifier of this entry's BGP peer.
	This entry should be 0.0.0.0 unless the		This entry MUST be 0.0.0.0 unless the
	bgpPeerState is in the openconfirm or the		bgpPeerState is in the openconfirm or the
	established state."		established state."
	::= { bgpPeerEntry 1 }		::= { bgpPeerEntry 1 }
	bgpPeerState OBJECT-TYPE		bgpPeerState OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	idle(1),		idle(1),
	connect(2),		connect(2),
	active(3),		active(3),
	opensent(4),		opensent(4),
	skipping to change at page 8, line 48		skipping to change at page 9, line 9
	::= { bgpPeerEntry 3 }		::= { bgpPeerEntry 3 }
	bgpPeerNegotiatedVersion OBJECT-TYPE		bgpPeerNegotiatedVersion OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The negotiated version of BGP running between		"The negotiated version of BGP running between
	the two peers.		the two peers.
	This entry should be zero (0) unless the		This entry MUST be zero (0) unless the
	bgpPeerState is in the openconfirm or the		bgpPeerState is in the openconfirm or the
	established state.		established state.
	Note that legal values should be between 0		Note that legal values for this object are
	and 255."		between 0 and 255."
			REFERENCE
			"RFC yyyy, section 4.2."
	::= { bgpPeerEntry 4 }		::= { bgpPeerEntry 4 }
			-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
	bgpPeerLocalAddr OBJECT-TYPE		bgpPeerLocalAddr OBJECT-TYPE
	SYNTAX IpAddress		SYNTAX IpAddress
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The local IP address of this entry's BGP		"The local IP address of this entry's BGP
	connection."		connection."
	::= { bgpPeerEntry 5 }		::= { bgpPeerEntry 5 }
	bgpPeerLocalPort OBJECT-TYPE		bgpPeerLocalPort OBJECT-TYPE
	skipping to change at page 12, line 23		skipping to change at page 12, line 31
	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 least 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).
	zero (0), the Hold Timer has either not been
	established with the peer, or, the value of		If the Hold Timer has not been established
	bgpPeerHoldTimeConfigured is zero (0)."		with the peer this object MUST have a value
			of zero (0).
			If the bgpPeerHoldTimeConfigured object has
			a value of (0), then this object MUST have a
			value of (0)."
			REFERENCE
			"RFC yyyy, Section 4.2"
			-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
	::= { 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
	DESCRIPTION		DESCRIPTION
	"Time interval in seconds for the KeepAlive		"Time interval in seconds for the KeepAlive
	timer established with the peer. The value		timer established with the peer. The value
	of this object is calculated by this BGP		of this object is calculated by this BGP
	speaker such that, when compared with		speaker such that, when compared with
	bgpPeerHoldTime, it has the same proportion		bgpPeerHoldTime, it has the same proportion
	as what bgpPeerKeepAliveConfigured has when		as what bgpPeerKeepAliveConfigured has when
	compared with bgpPeerHoldTimeConfigured. If		compared with bgpPeerHoldTimeConfigured.
	the value of this object is zero (0), it
	indicates that the KeepAlive timer has not		If the KeepAlive timer has not been established
	been established with the peer, or, the value		with the peer this object MUST have a value
	of bgpPeerKeepAliveConfigured is zero (0)."		of zero (0).
			If the of bgpPeerKeepAliveConfigured object
			has a value of (0), then this object MUST have
			a value of (0)."
			REFERENCE
			"RFC yyyy, Section 4.4"
			-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
	::= { bgpPeerEntry 19 }		::= { bgpPeerEntry 19 }
	bgpPeerHoldTimeConfigured OBJECT-TYPE		bgpPeerHoldTimeConfigured OBJECT-TYPE
	SYNTAX Integer32 ( 0 | 3..65535 )		SYNTAX Integer32 ( 0 | 3..65535 )
	MAX-ACCESS read-write		MAX-ACCESS read-write
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Time interval in seconds for the Hold Time		"Time interval in seconds for the Hold Time
	configured for this BGP speaker with this		configured for this BGP speaker with this
	peer. This value is placed in an OPEN		peer. This value is placed in an OPEN
	skipping to change at page 21, line 34		skipping to change at page 22, line 15
	bgp4PathAttrAtomicAggregate OBJECT-TYPE		bgp4PathAttrAtomicAggregate OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	lessSpecificRouteNotSelected(1),		lessSpecificRouteNotSelected(1),
	-- Typo corrected from RFC 1657		-- Typo corrected from RFC 1657
	lessSpecificRouteSelected(2)		lessSpecificRouteSelected(2)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The original text for this object was:		"If the ATOMIC_AGGREGATE attribute is present
			in the Path Attributes then this object MUST
	Whether or not a system has selected		have a value of 'lessSpecificRouteNotSelected'.
	a less specific route without
	selecting a more specific route.
	However, as of the current version of the BGP		If the ATOMIC_AGGREGATE attribute is missing
	specification, ATOMIC_AGGREGATE has been		in the Path Attributes then this object MUST
	deprecated. In this MIB, the value of this		have a value of 'lessSpecificRouteSelected'.
	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		Note that ATOMIC_AGGREGATE has been deprecated
	if the ATOMIC_AGGREGATE attribute is missing		in the BGP specification."
	in the Path Attributes."		REFERENCE
			"RFC yyyy, Sections 5.1.6 and 9.1.4."
			-- RFC Ed.: Replace yyyy with latest BGP RFC
	::= { 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
	skipping to change at page 23, line 22		skipping to change at page 23, line 45
	"An indication of whether or not this route		"An indication of whether or not this route
	was chosen as the best BGP4 route for this		was chosen as the best BGP4 route for this
	destination."		destination."
	::= { bgp4PathAttrEntry 13 }		::= { bgp4PathAttrEntry 13 }
	bgp4PathAttrUnknown OBJECT-TYPE		bgp4PathAttrUnknown OBJECT-TYPE
	SYNTAX OCTET STRING (SIZE(0..255))		SYNTAX OCTET STRING (SIZE(0..255))
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"One or more path attributes not understood		"One or more path attributes not understood by
	this BGP4 speaker.		this BGP4 speaker.
	Path attributes are recorded in the Update Path		Path attributes are recorded in the Update Path
	attribute format of type, length, value.		attribute format of type, length, value.
	Size zero (0) indicates the absence of such		Size zero (0) indicates the absence of such
	attributes.		attributes.
	Octets beyond the maximum size, if any, are not		Octets beyond the maximum size, if any, are not
	recorded by this object.		recorded by this object.
	skipping to change at page 24, line 16		skipping to change at page 24, line 38
	bgpEstablishedNotification NOTIFICATION-TYPE		bgpEstablishedNotification NOTIFICATION-TYPE
	OBJECTS { bgpPeerRemoteAddr,		OBJECTS { bgpPeerRemoteAddr,
	bgpPeerLastError,		bgpPeerLastError,
	bgpPeerState }		bgpPeerState }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The BGP Established event is generated when		"The BGP Established event is generated when
	the BGP FSM enters the ESTABLISHED state.		the BGP FSM enters the ESTABLISHED state.
	This object deprecates bgpEstablished."		This Notification replaces the bgpEstablished
			Notification."
	::= { bgpNotification 1 }		::= { bgpNotification 1 }
	bgpBackwardTransNotification NOTIFICATION-TYPE		bgpBackwardTransNotification NOTIFICATION-TYPE
	OBJECTS { bgpPeerRemoteAddr,		OBJECTS { bgpPeerRemoteAddr,
	bgpPeerLastError,		bgpPeerLastError,
	bgpPeerState }		bgpPeerState }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The BGPBackwardTransNotification Event is		"The BGPBackwardTransNotification Event is
	generated when the BGP FSM moves from a higher		generated when the BGP FSM moves from a higher
	numbered state to a lower numbered state.		numbered state to a lower numbered state.
	This object deprecates bgpBackwardsTransition."		This Notification replaces the
			bgpBackwardsTransition Notification."
	::= { bgpNotification 2 }		::= { bgpNotification 2 }
	-- { bgp 7 } is deprecated		-- { bgp 7 } is obsoleted
	bgpTraps OBJECT IDENTIFIER ::= { bgp 7 }		bgpTraps OBJECT IDENTIFIER ::= { bgp 7 }
	bgpEstablished NOTIFICATION-TYPE		bgpEstablished NOTIFICATION-TYPE
	OBJECTS { bgpPeerLastError,		OBJECTS { bgpPeerLastError,
	bgpPeerState }		bgpPeerState }
	STATUS deprecated		STATUS deprecated
	DESCRIPTION		DESCRIPTION
	"The BGP Established event is generated when		"The BGP Established event is generated when
	the BGP FSM enters the ESTABLISHED state.		the BGP FSM enters the ESTABLISHED state.
	This object has been deprecated in favor of		This Notification has been replaced by the
	bgpEstablishedNotification."		bgpEstablishedNotification Notification."
	::= { bgpTraps 1 }		::= { bgpTraps 1 }
	bgpBackwardTransition NOTIFICATION-TYPE		bgpBackwardTransition NOTIFICATION-TYPE
	OBJECTS { bgpPeerLastError,		OBJECTS { bgpPeerLastError,
	bgpPeerState }		bgpPeerState }
	STATUS deprecated		STATUS deprecated
	DESCRIPTION		DESCRIPTION
	"The BGPBackwardTransition Event is generated		"The BGPBackwardTransition Event is generated
	when the BGP FSM moves from a higher numbered		when the BGP FSM moves from a higher numbered
	state to a lower numbered state.		state to a lower numbered state.
	This object has been deprecated in favor of		This Notification has been replaced by the
	bgpBackwardTransNotification."		bgpBackwardTransNotification Notification."
	::= { bgpTraps 2 }		::= { bgpTraps 2 }
	-- Conformance information		-- Conformance information
	bgp4MIBConformance OBJECT IDENTIFIER		bgp4MIBConformance OBJECT IDENTIFIER
	::= { bgp 8 }		::= { bgp 8 }
	bgp4MIBCompliances OBJECT IDENTIFIER		bgp4MIBCompliances OBJECT IDENTIFIER
	::= { bgp4MIBConformance 1 }		::= { bgp4MIBConformance 1 }
	bgp4MIBGroups OBJECT IDENTIFIER		bgp4MIBGroups OBJECT IDENTIFIER
	::= { bgp4MIBConformance 2 }		::= { bgp4MIBConformance 2 }
	skipping to change at page 32, line 29		skipping to change at page 33, line 29
	Curtis Villamizar, Avici		Curtis Villamizar, Avici
	Dave LeRoy, Pencom Systems		Dave LeRoy, Pencom Systems
	Paul Traina, Juniper Networks		Paul Traina, Juniper Networks
	Andrew Partan, MFN		Andrew Partan, MFN
	Robert Snyder, Cisco Systems		Robert Snyder, Cisco Systems
	Dimitry Haskin, Nortel		Dimitry Haskin, Nortel
	Peder Chr Norgaard, Telebit Communications A/S		Peder Chr Norgaard, Telebit Communications A/S
	Joel Halpern, CTO Longitude Systems, Inc.		Joel Halpern, CTO Longitude Systems, Inc.
	Nick Thille, RedBack Networks		Nick Thille, RedBack Networks
	Bert Wijnen, Lucent		Bert Wijnen, Lucent
	Shane Wright, NextHop		Shane Wright, NextHop Technologies
	Mike McFadden, Riverstone Networks, Inc.		Mike McFadden, Riverstone Networks, Inc.
	Jon Saperia, JDS Consulting, Inc.		Jon Saperia, JDS Consulting, Inc.
	Wayne Tackabury, Gold Wire Technology, Inc.		Wayne Tackabury, Gold Wire Technology, Inc.
	Bill Fenner, AT&T Research		Bill Fenner, AT&T Research
	RJ Atkinson, Extreme Networks		RJ Atkinson, Extreme Networks
	The origin of this document is from RFC 1269 "Definitions of Managed		The origin of this document is from RFC 1269 "Definitions of Managed
	Objects for the Border Gateway Protocol (Version 3)" written by Steve		Objects for the Border Gateway Protocol (Version 3)" written by Steve
	Willis and John Burruss, which was updated by John Chu to support		Willis and John Burruss, which was updated by John Chu to support
	BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of		BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of
	skipping to change at page 33, line 16		skipping to change at page 34, line 16
	[BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway		[BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway
	Protocol 4 (BGP-4)", RFC yyyy, zzzz 2003.		Protocol 4 (BGP-4)", RFC yyyy, zzzz 2003.
	-- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its		-- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its
	-- month of publication		-- month of publication
	[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border		[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border
	Gateway Protocol in the Internet", RFC 1772, March 1995.		Gateway Protocol in the Internet", RFC 1772, March 1995.
	[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
	(USM) for version 3 of the Simple Network Management
	Protocol (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		Rose, M., and S. Waldbusser, "Structure of Management
	Information Version 2 (SMIv2)", STD 58, RFC 2578, April		Information Version 2 (SMIv2)", STD 58, RFC 2578, April
	1999.		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.,
	Rose, M., and S. Waldbusser, "Conformance Statements for		Rose, M., and S. Waldbusser, "Conformance Statements for
	SMIv2", STD 58, RFC 2580, April 1999.		SMIv2", STD 58, RFC 2580, April 1999.
	[RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture		9. Editors' Address
	for Describing Simple Network Management Protocol (SNMP)
	Management Frameworks", RFC 3411, December 2002.
	[RFC3413] D. Levi, P. Meyer, B. Stewart, "Simple Network Management
	Protocol (SNMP) Applications", RFC 3413, December 2002.
	[RFC3415] B. Wijnen, R. Presuhn, K. McCloghrie, "View-based Access
	Control Model (VACM) for the Simple Network Management
	Protocol (SNMP)", RFC 3415, December 2002.
	[RFC3416] Presuhn, R., Editor, "Version 2 of the Protool Operations
	for the Simple Network Management Protocol (SNMP)",
	RFC 3416, December 2002.
	[RFC3417] Presuhn, R., Editor, "Transport Mappings for the Simple
	Network Management Protocol (SNMP)", RFC 3417, December
	2002.
	9. Informative References
	[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
	"Introduction to Community-based SNMPv2", RFC 1901,
	January 1996.
	[RFC2576] Frye, R., Levi, D., Routhier, S. and B. Wijnen,
	"Coexistence between Version 1, Version 2, and Version
	3 of the Internet-Standard Network Management Framework",
	RFC 2576, March 2000.
	[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
	"Introduction and Applicability Statements for Internet-
	Standard Management Framework", RFC 3410, December 2002.
	10. Editors' Address
	Jeffrey Haas, Susan Hares		Jeffrey Haas, Susan Hares
	NextHop Technologies		NextHop Technologies
	825 Victor's Way, Suite 100		825 Victor's Way, Suite 100
	Ann Arbor, MI 48103		Ann Arbor, MI 48103
	Phone: +1 734 222-1600		Phone: +1 734 222-1600
	Fax: +1 734 222-1602		Fax: +1 734 222-1602
	Email: jhaas@nexthop.com		Email: jhaas@nexthop.com
	skh@nexthop.com		skh@nexthop.com
	11. Full Copyright Statement		10. Full Copyright Statement
	Copyright (C) The Internet Society (2003). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/