This I-D does not even mention IPv6 -- any particular reason for not to? :-) Until now, it seems there have been at least 5-10 different NAT traversing/reversing techniques, designed for about every application requiring it. But doing NAT traversal to get IPv6 connectivity would have provided a unified solution to every application... On Fri, 26 Mar 2004 Internet-Drafts@xxxxxxxx wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Establishing Reachability Behind NATs > Author(s) : M. Shore > Filename : draft-shore-nat-reachability-00.txt > Pages : 14 > Date : 2004-3-26 > > One of the most persistent, difficult problems introduced with NATs > is voluntary reachability -- a NATted device making itself avail- > able to the public internet. This paper is an overview of the cur- > rent status of reachability, a decomposition of the problem and a > proposal for going forward. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-shore-nat-reachability-00.txt -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings