[180715] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Mark Andrews)
Wed Jun 10 01:44:20 2015
X-Original-To: nanog@nanog.org
To: Michael Thomas <mike@mtcc.com>
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Tue, 09 Jun 2015 22:10:22 -0700."
<5577C6BE.6020905@mtcc.com>
Date: Wed, 10 Jun 2015 15:42:14 +1000
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
In message <5577C6BE.6020905@mtcc.com>, Michael Thomas writes:
> On 06/09/2015 08:37 PM, Karl Auer wrote:
> > On Tue, 2015-06-09 at 23:09 -0400, Valdis.Kletnieks@vt.edu wrote:
> >> How does the device ask for a *second* DHCPv6'ed address for tethering or
> >> whatever?
> > RFC 3315 says you just chuck in multiple IA_NA (or IA_TA) options. The
> > server will respond with multiple addresses.
> >
> > And if a device makes a second (, third, fourth, ..) request with a
> > different DUID, it'll get a second (,third, fourth,...) address oo, I
> > guess.
>
> Wouldn't the right thing to do is have the provider support dhcp prefix
> delegation, and the tether can run
> dhcp for its clients? (or even slaac?)
Yes. Providers should support both IA_NA and PD.
Tethering could have been done properly with PD at the time but it
was decided to leave PD to the next round of the phone spec. as as
a result there was all the prefix sharing kludges.
> Mike
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
