[Jool-list] RFC: Limiting EAM algorithm to specific header fields

[Michael Richardson]

Tore Anderson <tore at fud.no> wrote:
    > That doesn't necessarily mean "too large", though. Those operators must
    > necessarily have identical-sized tables of Elastic/Floating IP
    > addresses already today, so if they can scale those they ought to be
    > able to scale an EAMT with a similar number of entries too. Another
    > thing worth noting is that the IPv4 routing table carried by most core
    > routers on the internet contains ~525k routes, and that seems to work
    > fine too, so...

And... we can use IPv4 routing (OSPF) to split the load across many devices I
think, and we can probably also invent a way to distribute EAMT entries into
OSPF.
Probably we'd have to argue for a few months if it's an OSPFv2 (IPv4) or
OSPFv3 (IPv6) TLV.  

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [