draft-ietf-idr-bgp4-09.txt		draft-ietf-idr-bgp4-10.txt
	Network Working Group Y. Rekhter		Network Working Group Y. Rekhter
	INTERNET DRAFT cisco Systems		INTERNET DRAFT cisco Systems
	T. Li		T. Li
	Juniper Networks		Procket Networks, Inc.
	Editors		Editors
	A Border Gateway Protocol 4 (BGP-4)		A Border Gateway Protocol 4 (BGP-4)
	<draft-ietf-idr-bgp4-09.txt>		<draft-ietf-idr-bgp4-10.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 RFC2026.		all provisions of Section 10 of RFC2026.
	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 40, line 36		skipping to change at page 40, line 36
	a) Remove from consideration routes with less-preferred		a) Remove from consideration routes with less-preferred
	MULTI_EXIT_DISC attributes. MULTI_EXIT_DISC is only comparable		MULTI_EXIT_DISC attributes. MULTI_EXIT_DISC is only comparable
	between routes learned from the same neighboring AS. Routes which		between routes learned from the same neighboring AS. Routes which
	do not have the MULTI_EXIT_DISC attribute are considered to have		do not have the MULTI_EXIT_DISC attribute are considered to have
	the highest possible MULTI_EXIT_DISC value.		the highest possible MULTI_EXIT_DISC value.
	This is also described in the following procedure:		This is also described in the following procedure:
	for m = all routes still under consideration		for m = all routes still under consideration
	for n = all routes still under consideration		for n = all routes still under consideration
	if (neighborAS(m) == neighborAS(n)) and (MED(n) <		if (neighborAS(m) == neighborAS(n)) and (MED(n) < MED(m))
	MED(m))
	remove route m from consideration		remove route m from consideration
	In the pseudo-code above, MED(n) is a function which returns the		In the pseudo-code above, MED(n) is a function which returns the
	value of route n's MULTI_EXIT_DISC attribute. If route n has no		value of route n's MULTI_EXIT_DISC attribute. If route n has no
	MULTI_EXIT_DISC attribute, the function returns the highest		MULTI_EXIT_DISC attribute, the function returns the highest
	possible MULTI_EXIT_DISC value, i.e. 2^32-1.		possible MULTI_EXIT_DISC value, i.e. 2^32-1.
	Similarly, neighborAS(n) is a function which returns the neighbor		Similarly, neighborAS(n) is a function which returns the neighbor
	AS from which the route was received.		AS from which the route was received.
	skipping to change at page 60, line 10		skipping to change at page 60, line 10
	Editors' Addresses		Editors' Addresses
	Yakov Rekhter		Yakov Rekhter
	cisco Systems, Inc.		cisco Systems, Inc.
	170 W. Tasman Dr.		170 W. Tasman Dr.
	San Jose, CA 95134		San Jose, CA 95134
	email: yakov@cisco.com		email: yakov@cisco.com
	Tony Li		Tony Li
	Juniper Networks, Inc.		Procket Networks
	385 Ravendale Dr.		3910 Freedom Circle, Ste. 102A
	Mountain View, CA 94043		Santa Clara CA 95054
	email: tli@juniper.net		Email: tli@procket.com
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/