Tony Li wrote:
Kevin,I've been thinking about how a new address format definition would help a scenario like this. Scalable Address Format (SAF): 0001[ASN 5-15]:[ASN 16-31]:[inter-ASN topology 0-31]:[routing hint 0-63]In this scheme, is there any hope for aggregation above a /32? IMHO, 4 billion routes is a tad too many. ;-)
If you are a transit provider, you only need the routes for your customers and routes for other transit providers. You do not
need the routes of other transit providers customers, the routing hint points you to one of their providers. Of course it would be possible to leak customer routes to other providers if the participants preferred that for some routes. If you were a multihomed end site, you would probably get a feed of all global transit provider routes, minus remote customer routes, plus your own providers customer's routes. The minimum set of routes is all transit providers (the address space used for hints). - Kevin -- 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