asp@uunet.uu.net (Andrew Partan) writes: * > 04/22/94 18596 * * AlterNet is currently seeing 19583 routes - looks like ANS is seeing * about 1K fewer routes. Interesting data point. Not quite sure what it * means. * Hmm. to confirm - this is the data I see from the Table-History file I am generatiing. It does seem ANS is a 1000 low ? Date Routes Paths 080494 20136 53243 090494 20139 53225 100494 20044 53333 110494 20036 53183 120494 20294 53642 130494 20326 53849 140494 20374 53822 150494 20246 53541 150494 20384 53776 160494 20099 53167 170494 19949 52708 180494 19858 52489 190494 20238 53577 200494 19327 51054 210494 19463 51341 220494 19486 51544 --Tony.

Got a list of routes which are not in the NSFnet table but some other places. Spot that one incident that the aggregate is advertised to both routing tables, but there are few specific routes within the aggregate has been advertised to the NSFNET. So in terms of connectivity, both can reach all the specific routes destination, but the path would be different. However, that cause the difference in size of the routing table. This is just the one I happen to see but there could be more such cases. This indicates reason #1 in my previous message. I also saw a lot of routes in the diff list looks like testnets but not quite sure. I do not have time to do more poking today, I will do it on Monday. --Jessica

Elise, My feeling is that there is some level of atomic aggregation, below which, you will be using igp routes. This goes back to the original definition of Autonomous System. I would like to see the home AS represent that transition from igp routing to egp routing. That is, if you inject a route into the global routing table, then you have some level of responsibility for that route and this should be documented somewhere. Don't think of it as no more A,B,C networks, but rather as 30 different sizes. Erik P.S. Would routing within a AS be sub-atomic routing? :-)

During this tranisition from the classful world to the classless, home ASs still have meaning. It does not seem clear that home ASs will be relevant when we treat all routes as classless entities, because most assignments can be further subdivided. There will be no base unit such as class A, B or C on which to hang the home AS tag. We may want to move from "one net/one home AS" to "prefix and length/ announcing AS" - since an AS downstream or upstream may aggregate a subset or superset.

I'm not commenting directly on your suggestion on how to express meaningful information about the specific nets that AS 701 has withdrawn from its announcment to AS 690, but trying to explore how we should look at keeping information about classless entities. These lists (regional-techs and bgpd) seem like the right place to discuss what information the operators need in a classless routing world. --Elise

Andrew, Is your definition of home-as the RIPE definition?

Home-AS still has meansing for a classless net; just as it does for a classfull one.

How do you designate home-as for 194.16/16 from 194.16.16/24? 194.16/16 was assigned to organizationX and indicated that the home-as was 701. Then organizationX gave 194.16.16/24 to companyY who has their own AS 702. Now the assignment registry can be updated to show these changes in home-AS.

Routing table entries should have some idea of the 'creator' of that entry. Home-AS or aggregator or some such seems to be the most useful. --asp@uunet.uu.net (Andrew Partan)

But when the classless thingy is routed, home-AS and aggregator-AS can be inconsistent or there can even be multiple creators of aggregation. So I am not sure that home-AS means the same thing for classless entities - or perhaps we need another concept which acknowledges a classless entity may be included in several supersets all of which have different aggregator-ASs. If your definition permits multiple home-as tags per classless net, then you have answered my question. Thanks. --Elise