[180753] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Lorenzo Colitti)
Wed Jun 10 08:45:16 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <20150610143103.4700248d@envy.fud.no>
From: Lorenzo Colitti <lorenzo@colitti.com>
Date: Wed, 10 Jun 2015 21:44:52 +0900
To: Tore Anderson <tore@fud.no>
Cc: NANOG List <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Jun 10, 2015 at 9:31 PM, Tore Anderson <tore@fud.no> wrote:
> In particular comment 105 is illuminating. Android is apparently fully
> on-board with mobile carriers' desire to break tethering, even going so
> far as to implement a feature whose *sole purpose* is to break
> thethering.
>
> Yet, at the same time, you refuse to implement DHCPv6 on WiFi because it
> *might*, as a *side effect*, break tethering. This does not strike me
> as very consistent.
>
Tethering is just one example that we know about today. Another example is
464xlat. And that's not counting future applications that can take
advantage of multiple IP addresses that we haven't thought of yet, and that
we will have if we get stuck with
there-are-more-IPv6-addresses-in-this-subnet-than-grains-of-sand-but-you-only-get-one-because-that's-how-we-did-it-in-IPv4
networks.
