In an IPv6 future, how will you solve IPv4 connectivity?

Drake Wilson drake at
Mon Oct 11 07:31:19 CEST 2010

Quoth Ted Mittelstaedt <tedm at>, on 2010-10-10 22:15:40 -0700:
> 1) Public IPv4 only
> 2) dual stack public IPv4/IPv6
> 3) Private (natted) IPv4 only
> 4) Dual stack public IPv6 / private (natted) IPv4
> #1 will be 5% higher than rack rate.  #2 will be 4% higher
> than rack rate. #3 1%-2% higher than rack rate  #4 will be
> rack rate.

I'm curious whether and how you plan to enforce the distinctions
between (1) and (2), and (3) and (4). It seems to me that unless you
do some moderately intrusive checks to ensure that they're responsive
on both addresses, a customer could simply disable their IPv6 stack
and go "haha, now I don't have to contribute to the environment, but I
still get the lower price".  (Here I'm assuming you're talking about
either home users or colo, since it's not totally clear to me which of
your services you're describing above.)

   ---> Drake Wilson

More information about the ipv6-ops mailing list