Hello there, On Wednesday 24 December 2008, William Herrin wrote: > Draft #6 of the Summary of Routing Architectures discussed in the RRG > is now available at: > > http://bill.herrin.us/network/rrgarchitectures.html
I'm new to this list/area (so be gentle :-) and I've just read the above page. I find it weird that while the title is "Routing table size problem" there is a lot of talk about mobility (plus other things like PMTUD (?)). Even though those are real-world problems, I see that you're trying to address them at the same time. AFAICT from the document, this complicates things a lot. For example, criticism #1 for strategy B seems only related to mobility and I see it as a problem no matter how routing works (except perhaps from an unknown-yet very-special case). >From what I understand from the document, if there is ever a GUID/SID/LOC breakup, the core routing will only deal with LOC, while the TCP (strategy B, criticism 1) will have to do with SID. Also, shouldn't firewalls have to work with GUIDs instead of LOCs ? (strategy B, criticism 2) Finally, some comments: for Strategy E: Assuming that managers, politics and economy will efficiently solve a technical issue that IETF and technicians can't, seems somehow... well... wrong... :-) for Strategy F: 6000$ per year per prefix seems like a small amount. Some spam/chain letters cost a lot more per day or even per hour. A 2002 study [1] showed that for that year, spam costed 8.9 billion dollars in US only [1]. Many TCP implementations send 4 bytes of NOPs in every packet, which should add to a lot more than the 6000$ per year. Not very efficient compression of the google logo at its main page may cost more. The list of examples can grow really long. Most probably the cost of whatever transition is decided will be more than those 6000$ may sum for the next 30+ years. So, I propose that cost isn't considered as the main reason to make such a change and thus assume strategy F as correct but not adequate. Hope the above helps. [1] http://www.d-silence.com/feature.php?id=257 _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
