Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
There's something I don't understand about your model. You assert that the DFZ only contains routes for RLOCs. But today the DFZ only contains routes for EIDs, in reality. Don't you need to either operate with two co-existing DFZs (DFZ-old with EID routes, and DFZ-new with RLOC routes), or distinguish the two kinds of routes within a single DFZ?
Since currently IP addresses are both, that's only one potential way of looking at it. The other is that the DFZ currently only contains RLOCs which are also abused into being EIDs. If something LISPy is implemented, the new EID space (except perhaps in highly aggregated form) will never show up in the DFZ.
There is an outstanding question whether there's any way to get leaf ASes currently putting their RLOCs in the DFZ to remove them from BGP, turn them into EIDs, and map them to RLOCs they get from their upstreams.
S Stephen Sprunk "God does not play dice." --Albert Einstein CCIE #3723 "God is an inveterate gambler, and He throws theK5SSS dice at every possible opportunity." --Stephen Hawking
-- to unsubscribe send a message to rrg-request@psg.com 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