rfc8704v3.txt		rfc8704.txt
	skipping to change at line 224 ¶		skipping to change at line 224 ¶
	one transit provider (ISP-a) and a different prefix (P2) to another		one transit provider (ISP-a) and a different prefix (P2) to another
	transit provider (ISP-b) but routes data packets with source		transit provider (ISP-b) but routes data packets with source
	addresses in the second prefix (P2) to the first transit provider		addresses in the second prefix (P2) to the first transit provider
	(ISP-a) or vice versa. Then, data packets with a source address in		(ISP-a) or vice versa. Then, data packets with a source address in
	prefix P2 that are received at AS2 directly from AS1 will get		prefix P2 that are received at AS2 directly from AS1 will get
	dropped. Further, data packets with a source address in prefix P1		dropped. Further, data packets with a source address in prefix P1
	that originate from AS1 and traverse via AS3 to AS2 will also get		that originate from AS1 and traverse via AS3 to AS2 will also get
	dropped at AS2.		dropped at AS2.
	+------------+ ---- P1[AS2 AS1] ---> +------------+		+------------+ ---- P1[AS2 AS1] ---> +------------+
	| AS2(ISP-a) | <----P2[AS3 AS1] ---- | AS3(ISP-b)|		| AS2(ISP-a) | <----P2[AS3 AS1] ---- | AS3(ISP-b) |
	+------------+ +------------+		+------------+ +------------+
	/\ /\		/\ /\
	\ /		\ /
	\ /		\ /
	\ /		\ /
	P1[AS1]\ /P2[AS1]		P1[AS1]\ /P2[AS1]
	\ /		\ /
	+-----------------------+		+-----------------------+
	| AS1(customer) |		| AS1(customer) |
	+-----------------------+		+-----------------------+
	skipping to change at line 285 ¶		skipping to change at line 285 ¶
	second transit provider (ISP-b or AS3) does not propagate the		second transit provider (ISP-b or AS3) does not propagate the
	prepended route for prefix P1 to the first transit provider (ISP-a or		prepended route for prefix P1 to the first transit provider (ISP-a or
	AS2). This is because AS3's decision policy permits giving priority		AS2). This is because AS3's decision policy permits giving priority
	to a shorter route to prefix P1 via a lateral peer (AS2) over a		to a shorter route to prefix P1 via a lateral peer (AS2) over a
	longer route learned directly from the customer (AS1). In such a		longer route learned directly from the customer (AS1). In such a
	scenario, AS3 would not send any route announcement for prefix P1 to		scenario, AS3 would not send any route announcement for prefix P1 to
	AS2 (over the P2P link). Then, a data packet with a source address		AS2 (over the P2P link). Then, a data packet with a source address
	in prefix P1 that originates from AS1 and traverses via AS3 to AS2		in prefix P1 that originates from AS1 and traverses via AS3 to AS2
	will get dropped at AS2.		will get dropped at AS2.
	+------------+ routes for P1, P2 +-----------+		+------------+ routes for P1, P2 +------------+
	| AS2(ISP-a) |<-------------------->| AS3(ISP-b)|		| AS2(ISP-a) |<-------------------->| AS3(ISP-b) |
	+------------+ (P2P) +-----------+		+------------+ (P2P) +------------+
	/\ /\		/\ /\
	\ /		\ /
	P1[AS1]\ /P2[AS1]		P1[AS1]\ /P2[AS1]
	\ /		\ /
	P2[AS1 AS1 AS1]\ /P1[AS1 AS1 AS1]		P2[AS1 AS1 AS1]\ /P1[AS1 AS1 AS1]
	\ /		\ /
	+-----------------------+		+-----------------------+
	| AS1(customer) |		| AS1(customer) |
	+-----------------------+		+-----------------------+
	P1, P2 (prefixes originated)		P1, P2 (prefixes originated)
End of changes. 2 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/