[Catching up...] | > I think the RRG has only focused on loc/id split and |really hasn't gone | > into greater depth with other routing architectures. | |Ah, I don't consider the location/identity split a 'routing |architecture'. |It's an ancillary aspect of the overall system architecture, |one which has at |best some influence on particular desired operational goals |having to do with |routing (e.g. provider independence). | |To me, routing architectures are about things like 'what |entity choses the |path the packets flow along', and 'how are those paths |computed', 'what data |does that computation need', 'how is that data distributed', etc. |network-sized-mapping-database.
As has been remarked before, routing and addressing are fundamentally inseparable, and indeed our charter is to explore both routing and addressing architectures. To my mind, a locator/identifier split is a major change in the addressing architecture that will fundamentally change the scalability of the routing subsystem. If folks have other tricks up their sleeve that result in improved routing scalability, that's certainly most welcome. Tony -- to unsubscribe send a message to [EMAIL PROTECTED] 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
