UUNET Routing issues

Fri Oct 4 21:08:50 UTC 2002

>OK. I'll bite - is it feasible if you're a caspian engineer? ;)

Obviously, as most of the audience knows, it´s a function of the speed you want
to achieve, the number of flows you expect to be interested in and what you want
to do with the flows. Getting traffic split up in a few million flows and
maintaining
the flow cache and associated state and doing lookups in the the cache is not
too
hard. Doing anything more clever than switching packets (like scheduling which
one
goes next) across a large dataset has been unachievable challenge so far.
(at least at price points people want to pay)

It would have to be an earlier hour to walk trough if a design which would
combine
flow classification and CAM based scheduling would cut it, but I´m afraid of the
aliasing
contention killing the actual thing you´re trying to achieve. (service
quarantees)

Pete