Re: WG next steps

[Andrew Partan <post-multi6@partan.com>]

On Mon, Nov 18, 2002 at 08:45:33PM +0100, Iljitsch van Beijnum wrote:
> It's very simple. If you use a hierarchical addressing mechanism, you
> get to aggregate. If you aggregate, traffic flows become less optimal.
> Making the hierarchy geographically relevant gives you the _potential_
> to get around the traffic flow problem. That's all. No creative physics.

I'll try to explain this again.

I'm a large provider; I'm connected to two geo areas - A and B.
Not everyone in area A is my customer.
At B I connect to another provider.
What routes to I announce to that other provider about area A?
If I announce just my customers' routes, then aggregation is dead.
If I announce just the area A aggregate, then I am giving free transit
to everyone in area A.
Neither one flys.

You have the smae problem with exchange addressing as well.
	--asp