> This is correct. Once we have loc/id and renumbering, then we can do things > like ask folks to stop using PI because we have made PA almost as good. > Again, avoiding the multi-homing usage for PI route injection is the goal.
What about traffic engineering? Will a loc/id split "solve" traffic engineering (which is normally done by leaking longer prefixes today), and if so, how? I understand you can "map" the id to the locator you'd prefer to bring the traffic in through, but does that truly solve the traffic engineering problem unless you also have one locator per possible exit point (customer/edge pair) for every (transit) network in the world, and does this actually scale better than what we have today? IE, what's the incentive to aggregate locators, vs the incentive for de-aggregating locators, or even assigning tons of locators because, "well, it's free to advertise a locator, and the table is really small, so..." It seems to me the locator table will end up just where the routing table is today--there's no cost to advertise the things, so, hey, why not? You could, I suppose, constrain the locator space so its very small, but that doesn't seem like a very good solution, either. So, IMHO, this is all neat and everything, but until the economic problem is addressed, there's not much hope of doing anything other than kicking the can down the road a couple of years or so. :-) Russ
signature.asc
Description: OpenPGP digital signature
_______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
