[14268] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Traffic Engineering

daemon@ATHENA.MIT.EDU (Curtis Villamizar)
Tue Dec 16 20:44:32 1997

To: curtis@ans.net
cc: "James R Grinter" <jrg@watching.org>, nanog@merit.edu
Reply-To: curtis@ans.net
In-reply-to: Your message of "Tue, 16 Dec 1997 15:08:39 EST."
             <199712162008.PAA15876@brookfield.ans.net> 
Date: Tue, 16 Dec 1997 20:31:34 -0500
From: Curtis Villamizar <curtis@brookfield.ans.net>


In message <199712162008.PAA15876@brookfield.ans.net>, Curtis Villamizar writes
:
> 
> The only real problem you can run into is if someone is boneheaded
> enough to misconfigure their routing to do per prefix load splitting
					     ^^^^^^^^^^
					     per packet
> across WAN links or worse yet across providers.  Again, such people
> don't deserve to stay in business (since *all* TCP traffic from their
network will suck), but they do exist.  The common newbie mistake is
> to configure per prefix load split among two default routes.  Westnet
> used to do this many years ago.  Some small network in Florida did
> this more recently.
> 
> Curtis


Minor correction but big difference in meaning.  Per prefix is fine.
It is per packet load split that causes trouble.,

Curtis


home help back first fref pref prev next nref lref last post