<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff size=2>If
your protocol supports IP address mobility (preferably with protection against
using that against an endpoint for session hijacking, and preferably protecting
that against replay as well), then existing peers wouldn't need to "re-connect",
they'd just be able to keep their connections up through the change in
address,... though you would want to re-determine your external address/port so
any new peers could connect to that. Conveniently, knowledge that your address
had undergone a mobility event would be exactly how you'd know when you needed
to do that re-determination.</FONT></SPAN></DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff size=2>I
happen to have designed, published the specification for, and implemented a
protocol that does just this.</FONT></SPAN></DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff
size=2>Matthew Kaufman</FONT></SPAN></DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff size=2><A
href="mailto:matthew@matthew.at">matthew@matthew.at</A></FONT></SPAN></DIV>
<DIV><SPAN class=891270403-03032006><FONT face=Arial color=#0000ff size=2><A
href="http://www.amicima.com">http://www.amicima.com</A></FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> p2p-hackers-bounces@zgp.org
[mailto:p2p-hackers-bounces@zgp.org] <B>On Behalf Of </B>Lemon
Obrien<BR><B>Sent:</B> Thursday, March 02, 2006 1:45 PM<BR><B>To:</B>
Peer-to-peer development.<BR><B>Subject:</B> [p2p-hackers] NATs reconfiguring
IPs and Port Numbers<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT style="BACKGROUND-COLOR: #c7ffb7">It seems port numbers change
after a certain amount of time due to the local NAT or local ISP, and the peer
to peer application has to re-configure itself to find out what its new global
address is...and broadcast that to others so they can re-connect; does anyone
know what the average time is a port number is good for? I'm getting up to 24
hours testing through Comcast and SBC; but i have to sleep so...i'm not sure
on this number.</FONT></DIV>
<DIV><FONT style="BACKGROUND-COLOR: #c7ffb7"></FONT> </DIV>
<DIV><FONT style="BACKGROUND-COLOR: #c7ffb7">thanks</FONT></DIV>
<DIV><FONT style="BACKGROUND-COLOR: #c7ffb7">lemon</FONT></DIV><BR><BR>You
don't get no juice unless you squeeze<BR>Lemon Obrien, the
Third.</BLOCKQUOTE></BODY></HTML>