V. CONCLUSION
In this paper we propose the MobiSocket to support TCP
mobility for secure application such as SIP. This socket causes
no overhead if handover does not take place like previous
proposal, and moreover it still works when both side handover
simultaneously.
In this socket, there is no need for per-TCP connection
authentication, because the authentication is left to application.
Depending on the real situation, the application can also control
whether to keep the TCP session or not, which is more
appropriate for application which is applied with other
application level constrains such as security and QoS policy .. .
In the future, we would like to carry out the implementation
of the MobiSocket to confirm the design of the system, as well
as to measure the delay and throughput parameter when the
reset'Iimen) function is (1) called and (2) not called, and
compare the results with that of [5] and [6]. We also would like
to measure the delay in the case of SIP application, when we
send the INFO message before and after re-Registration, as
well as when two end hosts handofftogether
We also plan to update the proposal in [1] with this new
MobiSocket.