Re: [BEHAVE] v6 content for IPv4-only clients

[Dan Wing <[e-mail]>]

On Jul 1, 2013, at 12:59 AM, Branimir Rajtar <[e-mail]> wrote:

> Hello everybody,
>  
> Just wanted to let you know my colleagues and me just posted a new draft describing how IPv4-only clients can access content available only on IPv6. Please take a look and comment:
> http://datatracker.ietf.org/doc/draft-rfvlb-behave-v6-content-for-v4-clients/

The document says:

  1.2.  Covered Scenarios

   As described in [RFC6144], there are multiple scenarios for IPv4/IPv6
   translation.  This document covers mainly Scenario 4: An IPv4 Network
   to the IPv6 Internet, but is not limited to be used for the following
   scenarios as well:

   o  Scenario 2: The IPv4 Internet to an IPv6 Network

   o  Scenario 6: An IPv4 Network to an IPv6 Network

   These scenarios are not subject of this draft and can be elaborated
   in future documents, if deemed necessary.


I don't think Scenario 2 is solvable with the approach described in draft-rfvlb-behave-v6-content-for-v4-clients, because draft-rfvlb-behave-v6-content-for-v4-clients describes assigning IPv4 addresses from RFC1918 space.  If public space were to be assigned instead of RFC1918 space, public IPv4 space would be consumed at the same rate as running a normal dual-stack server, so nothing is gained compared to operating a normal dual-stack server.

It would be helpful to include a network diagram showing the location of the DNS proxy (which is a new function), the NAT46 function, and the Internet. I have a topology in my head, and I believe my topology is accurate, but I can't be sure until I see a diagram of where these elements would be located.  Thanks.

-d