Mobile TCP socket for secure applications

A TCP session uses IP addresses (+ IP port) of both end points as identifiers. Therefore when a mobile handover to a new AP that belong to a different subnet/domain, the IP address will changes and ongoing TCP connections are reset. Several approaches have been proposed to solve this problem, and one of which was to modified the TCP/IP stack to update the changes of the IP address for the ongoing connections. However, these proposals causes unnecessary processing when TCP is used in applications which have already employed some kinds of security measures, such as SIP. This paper proposes the Mobi Socket, which specifically supports TCP mobility for intrinsic secure applications without unnecessary overhead.