RE: Making private IPv4 addresses public

2006-06-01 Thread Remi Denis-Courmont
Selon Manfredi, Albert E [EMAIL PROTECTED]: I'm not sure what different the intermediate routers would have to do, if anything. Nothing. But policy boxes and firewalls would be slower because of the IHL difference. It's a way of tackling the address space problem without depending on a new

Re: Making private IPv4 addresses public

2006-06-01 Thread Ignatios Souvatzis
On Wed, May 31, 2006 at 01:10:12PM -0400, Manfredi, Albert E wrote: Not sure if this is the right wg for this idea, or for that matter if I'm suggesting anything new. [...] Wouldn't it be nice if we could have NAPT without the TCP/UDP Port ID trick? You're reinventing source routing. [...] To

RE: Making private IPv4 addresses public

2006-06-01 Thread Pascal Thubert \(pthubert\)
So we can see that as a migration technique too: when you have a plurality of IPv4 networks that you do not want to migrate immediately, this might actually provide a way to migrate at your own rhythm. As you point out it is easy to define the double-mapped format using a mix of mapped address and

Re: Making private IPv4 addresses public

2006-06-01 Thread Bob Hinden
Hi, While this is an interesting topic, it's not appropriate for the the IPv6 mailing list. There is lots of prior work on schemes to expand the IPv4 address space using various forms of source routing and/or encapsulation. Even one written by me, namely RFC1955. The community decided

The IPv6 Day: Registration of free IPv6 Services open

2006-06-01 Thread JORDI PALET MARTINEZ
(posted with permission of the IPv6 WG co-chairs) If you have any free IPv6 connectivity service or other publicly available services, see below and register them at the IPv6 Day website (http://www.ipv6day.org). Contributors to translate the main web site pages to other languages are welcome