[180781] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Lorenzo Colitti)
Wed Jun 10 12:18:11 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <20150610173518.4ccfcdd3@envy.fud.no>
From: Lorenzo Colitti <lorenzo@colitti.com>
Date: Thu, 11 Jun 2015 01:17:47 +0900
To: Tore Anderson <tore@fud.no>
Cc: NANOG List <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Thu, Jun 11, 2015 at 12:35 AM, Tore Anderson <tore@fud.no> wrote:
> > 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.
>
> Of course. Hard to argue against imaginary things. :-)
>
I think "imaginary" is the wrong word here. There's a difference between
imaginary things and leaving room for for future innovation. Phone network
model vs. Internet model is the usual example that comes to mind.
> On the other hand, there exist applications *today* that do require
> DHCPv6. One such example would be MAP, which IMHO is superior to
> 464XLAT both for the network operator (statlessness ftw) as well as for
> the end user (unsolicited inbound packets work, no NAT traversal
> required). MAP is provisioned with DHCPv6 (I-D.ietf-softwire-map-dhcp),
> so without DHCPv6 support in Android, MAP support in Android is a
> non-starter.
>
Support for the DHCPv6 protocol, or support for assigning addresses from
IA_NA?
