And the router changes to do a different type of longest match?And in the ETR case, the forwarding algorithm is different as well. Because you have to tell your FIB to match on high-order bits only to determine the packet needs to be translated.I'm not sure I see the need for different longest matches. After all, this is a translation box and you're allowed to know which interfaces are 'inside' and which are 'outside'.
Well, until there is a clearly written spec, everyone is going to speculate how it works and make different assumptions.
So I am not going to respond because I think an "ETR-based GSE" works a certain way. A way I think I can implement. That is probably a lot different from what other people think.
And I wanted it to look roughly like the LISP architecture so you can implement one architecture in the ETR for IPv4 and IPv6. We will need to have both coexist at the same time and people will want multi- homing to work for both protocol families.
So I'm going to stop here.Can someone write a spec! I hear there is a lot of interest and people are keen on GSE but no one is doing detailed work.
I have said publicly many times, I will implement a GSE design if someone can write it down. I don't have cycles to do LISP design and GSE design but am willing to contribute.
Dino -- 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