It sounds suspiciously like ITU for me (ie, bad). It imposes previously non-existent architectural limits and constraints on Internet routing (given there is some form of routing police, of course :-)): How would you multi-home across region boundaries?
Good point. Only way is ending up with a kludge I guess where for those parties that connect over multiple summarization boundries you do not only carry a summary but also the more specific. Hence you loose effect towards less routes in the table for these parties.
What will happen with other inter-region connectivity? All AS:es who peer over a region-boundary, they will have to stop? (Who can enforce that?) Or will they have to get space from each regions RIR and do prefix translation in their routers? (This will amplify space usage by number of regions, roughly, for operators with presence in more than one region.)
That can hardly be a correct way to go down. Sounds like this is for sure one of those items coming in the way of simple aggregation.
Jasper, how did you conclude that RIR region boundaries is a good place to draw the line in the sand by the way? Why, for example, didn't you suggest nation state borders? (Ie, Denmark could have 0045::, Sweden 0046:: and so on)
Just picked a boundry - I guess there are multiple boundries where aggregation can take place. For the moment I kinda stuck by the delegations known to me already (RIR/LIR/etc). Depending on how RIRs assign prefixes today you could implement summaries in between the RIR and LIR level. But in light of your point made above - it does seem to me that the more summaries are made on a smaller scale the more exceptions are required. In a way I also felt that it aligns well with what we for instance do - we do IP transit and peering. All peerings are mainly with parties inside Europe. Transit carries all the other traffic which is mainly US/Asia/etc. Jasper Op dit e-mailbericht is een disclaimer van toepassing, welke te vinden is op http://www.espritxb.nl/disclaimer