Depends on how you do it. i think geo aggregation has been
consistently associated w/ bad design because of the bad examples
proposed in the past, that negleted the fact that the first thing to
route by is policy (local_pref is the first thing to check in bgp
decision process). after fixing this, it can look good both in paper
and in the real world ;), e.g.
http://www.cs.ucla.edu/~rveloso/papers/giro.pdf
besides aggregation, geoinfo is usefull for fault detection, TE,...
e.g. some isps tag routes with geographical info in entry points so
customers(and isps themselves) can improve their route selection
cheers,
--Ricardo
Geographical aggregation is the sort of thing which looks good on
paper, but will never be acceptable in the real world.
- Robin
--
to unsubscribe send a message to [EMAIL PROTECTED] with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
--
to unsubscribe send a message to [EMAIL PROTECTED] with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
