Question Re: best practices
martin at millnert.se
Mon May 9 21:30:11 CEST 2011
On Mon, 2011-05-09 at 20:40 +0200, Gert Doering wrote:
> NAT64/DNS64 isn't actually going to help much here, if the client
> network is IPv4 and the server doesn't have IPv4 available - the SSL
> service has to be given an IPv4 address, be it proxy or
> IPv4-side-of-NAT64, and if you have none, you can't solve this without
> the help of an intermediary that's dual-stacked...
The intermediary can be operated by another party however, with whom you
talk IPv6 over the public internet.
Not saying this is a preferred way for a content provider to host its
data, but it may be a way out for access networks who are OK with using
NAT to reach out to the IPv4 Internet, and by extension (are OK with NAT
after all) don't care much about external IPv4 clients being able to
connect to your network.
With such an external service, there's no need for a network to have any
IPv4 at all "on-net" (or some other term).
More information about the ipv6-ops