OK, but that does not solve the problem where the NATs are mostly deployed -- home and SOHO -- until all internet servers of interest to those users speak IPv6. "Can be upgraded to do so" is great if you control the server, but these users don't. So Yahoo, Google, etc can be pursuaded to upgrade, maybe... and the home/SOHO user using the setup below does a search. Many of the hits will be IPv4 only sites, and we are back to NAT. Don't get me wrong, this is a good migration path and should be pushed as much as possible, but it is not as fast as your message implies. --On Tuesday, March 19, 2002 11:37 -0500 Keith Moore <moore@cs.utk.edu> wrote: >> Maybe IPv6 will fix all that . . . . we can only pray . . . > > easily fixed. > > get a single IPv4 address, assign it to a 6to4 router that's installed > at your border, and put up to 2**80 hosts (okay, 2**16 hosts if > you use stateless autoconfig) behind it. you can then get to any of > those hosts from any another machine that speaks IPv6. if those > machines don't speak IPv6, they can often be upgraded to do so. > if they don't have IPv6 connectity, they can get it using 6to4. Hans Kruse, Associate Professor J. Warren McClure School of Communication Systems Management Ohio University, Athens, OH, 45701 740-593-4891 voice, 740-593-4889 fax