RE: [RRG] Consequences of no renumbering...

["Tony Li" <tony.li@tony.li>]

Hi Lixia,

|- there are multiple proposals on the RRG table that fall into the  
|general map-and-encap direction. In general they do not require  
|renumbering.


So let's try to discuss this in full generality.  If we take a m&e approach,
and have some kind of transition that doesn't include translation, how do we
improve aggregation in the underlying routing?

Dino correctly points out that sites can avoid renumbering and advertise
aggregates in the locator space.  This would represent some amount of
savings.  However, this would seem to affect the quality of routing as when
such aggregates are injected back into legacy routing, it would create
stretch/TE issues.  We've seen that folks deaggregate to address these
issues today.  Could we address this somehow?

Tony


--
to unsubscribe send a message to rrg-request@psg.com 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