Anton Tveretin wrote:
Dear All,
Here is my contribution to the problem list. I hope this might help.
1. "Hanging TCP" problem: if, at the time of handover, there is a TCP
connection between nodes, this might cause sending packets to the wrong
host (i.e. IP address of the MH changes, and previous IP is assigned to
that host). This is also a security hole.
Just a clarification. SIP-based terminal mobility could be most useful
for SIP-based sessions, where media is mostly RTP/UDP (e.g., Interactive
VoIP, RTP-based streaming). There are additional complexities to support
TCP-based application (e.g., tcpchat) using SIP-based terminal mobility,
although not impossible. However, SIP-based terminal mobility cannot be
used for applications that are not initiated using SIP signaling (e.g.,
FTP, Telnet).
We had a draft discussing this issue a while back in 2001.
http://www.argreenhouse.com/SIP-mobile/sip_draft4.
One can potentially use any MIP-based solution to avoid such complexity
to support terminal mobility for TCP-based application.
2. (Related to the previous): How can the CH find out that it is
connected to the same host (MH), but with different IP address, and not
something else? This is especially important for TLS connections.
3. Handover collision problem, i.e. during handover process, the CH also
changes its IP address. I don't see any solution for this problem. IMO
the connection will be lost.
Simultaneous mobility problem is a good one. There is currently a draft
in MEXT discussing this specific issue in addition to few papers that
have addressed this specific issue. It also lists some of the solutions.
We should add this one as a requirement.
http://tools.ietf.org/html/draft-wong-mext-simultaneous-ps-01
Since we are discussing the requirement draft, we should not be
discussing possible solutions yet.
Thanks
Ashutosh
Sincerely yours.
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
