[p2p-hackers] Official IETF behavior recommendations for NAT relevant to P2P

[Justin Cormack]

On 18 May 2005, at 19:59, Bryan Ford wrote:

> Dear p2p-hackers,
>
> A discussion is currently taking place on the IETF BEHAVE working  
> group
> mailing list (see http://www1.ietf.org/html.charters/behave- 
> charter.html)


(snip)

How current is this? These are the people who loooked at STUn and  
decided it wasnt that much use, and are due to wind up next January.

(not on the list but just asking)

Not sure what the issue is with TCP - surely it just doesnt work, you  
cant get the sequence numbers to work.

For UDP, well its easy to spoof anyway, The main problem with not  
using full cone is that it restricts the number of connections that  
you can NAT (and given the lack of timeouts on UDP this does impact  
many applications). Asking for non full cone to be default is thus a  
bit broken. But all the makers of dumb boxes are doing it anyway.  
Since when have NAT vendors cared about the IETF? Isnt it only Linux/ 
BSD based boxes that do full cone anyway?

Given that l33t hackers are already giving owned machines ipv6  
addresses anyway I am not ure it is an issue...

j