IPv6 Deployment for Mobile Subscribers
Ryan, Spencer
sryan at arbor.net
Fri Jul 22 16:59:44 UTC 2016
As far as I'm aware Android still today does not support DHCPv6.
https://en.wikipedia.org/wiki/Comparison_of_IPv6_support_in_operating_systems
________________________________
From: NANOG <nanog-bounces at nanog.org> on behalf of james machado <hvgeekwtrvl at gmail.com>
Sent: Friday, July 22, 2016 12:57:58 PM
To: Ricardo Ferreira
Cc: NANOG
Subject: Re: IPv6 Deployment for Mobile Subscribers
Ricardo,
I know from previous discussions on this list that Android phones are
looking for DHCPD leases and not /128's or /64's. From what I remember
this is due to the current requirement for multiple ipv6 subnets for
various applications (vpns among others) to function correctly. As a
result Google has disabled Android from receiving a DHCP lease as it wasn't
long enough.
if you look back about 6 months there is probably 100+ posts on the subject.
All I really know is that I can not provide an ipv6 dhcp lease to an
android phone and have it receive the address.
james
On Fri, Jul 22, 2016 at 1:54 AM, Ricardo Ferreira <
ricardofbferreira at gmail.com> wrote:
> Is there anyone here working in an ISP where IPv6 is deployed?
> We are starting to plan the roll-out IPv6 to mobile subscribers (phones) I
> am interesting in knowing the mask you use for the assignment; whether it
> is /64 or /128.
>
> In RFC 3177, it says:
> 3. Address Delegation Recommendations
>
> The IESG and the IAB recommend the allocations for the boundary
> between the public and the private topology to follow those general
> rules:
>
> - /48 in the general case, except for very large subscribers.
> - /64 when it is known that one and only one subnet is needed by
> design.
> - /128 when it is absolutely known that one and only one device
> is connecting.
>
> Basically a sole device will be connecting to the internet so I am
> wondering if this rule is follwed.
>
> Cheers
>
> --
> Ricardo Ferreira
>
More information about the NANOG
mailing list