Hi Lorenzo,
On Tue, Aug 11, 2015 at 8:47 PM, Lorenzo Colitti <lore...@google.com> wrote:
> On Wed, Aug 12, 2015 at 2:47 AM, Alia Atlas <akat...@gmail.com> wrote:
>
>> ECMP is critical in the data-center and backbone, but I'm interested in
>> seeing what the reasoning is as to why it isn't or is needed in the homenet
>> scenarios.
>>
>
> ECMP is critical in the datacenter and backbone because those networks are
> designed to provide the E ("equal") in ECMP. Because the links are equal,
> it's easy to load-balance over them without needing to do complicated stuff
> like traffic engineering - you just treat an N-way ECMP bundle as a link N
> times bigger, and hash across it. That does not happen in home networks,
> which are more grown than designed.
>
ECMP applies beyond link bundles. Of course, equal-cost can be hard to do
- and one can safely use downstream paths. The relevant question is
whether traffic is expected to be able to take multiple paths to allow
load-balancing.
> Having a homenet load-balance Internet-bound across multiple provides is a
> non-starter because it is presumed that said providers will employ BCP38
> filtering. It's possible for the *hosts* to load-balance across different
> providers by simply sending their packets with different source addresses
> (and, in some cases, different routers).
>
Yes, of course if one is doing src-dest routing, the multiple paths would
have to be valid for the route.
Regards,
Alia
_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
