On Tue, Feb 2, 2010 at 8:14 PM, Florin Coras <fco...@ac.upc.edu> wrote: > > Maybe I'm missing something but what happens when a mobile endpoint changes > its point of attachment in the hierarchical address space to a new location > that might just be using the same "edge space address" to identify another > endpoint? > > Florin > When you are changing location and you are moving from one network to another MP-TCP takes care of your issue. At the new location you get a new edge-address and if this happens on the fly, e.g. from WiFi to 3G the MP-TCP token keeps the session alive - during roaming you have two edge space addresses in use and if you are really unlucky you get two exactly similar addresses. Don't know how the MP-TCP stack would react to this, it could happen already today with RFC 1918 addresses. The mobile device is not identified with something in the IP layer, so when you are changing location you can receive whatever IP address from the service provider - MP-TCP token keeps your session alive. I.e. the mobile device doesn't take with it a given IP address from one service provider to another service provider
-- patte _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
