[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Android (lack of) support for DHCPv6
- Subject: Android (lack of) support for DHCPv6
- From: kauer at biplane.com.au (Karl Auer)
- Date: Wed, 10 Jun 2015 17:13:13 +1000
- In-reply-to: <CAKGbBmkE_AbZcmWhtWS68a=t9QmuccLdarhaN=m+9QEmJxOcJg@mail.gmail.com>
- References: <[email protected]> <CAKGbBm=dCDpeFJe4f0_KM6pjdvpeHrL4t7fyczOj2D3y=_07pg@mail.gmail.com> <1433905187.11511.25.camel@karl> <[email protected]> <1433907422.11511.30.camel@karl> <CAKGbBmkE_AbZcmWhtWS68a=t9QmuccLdarhaN=m+9QEmJxOcJg@mail.gmail.com>
On Wed, 2015-06-10 at 15:32 +0900, Lorenzo Colitti wrote:
> It's certainly possible to make Android request N IPv6 addresses via
> DHCPv6, and not accept the offer if it is offered fewer than N addresses.
> But that only really makes sense if there's a generally-agreed upon minimum
> value of N. I'd be happy to work with people on an Internet draft or other
> standard to define a minimum value for N, but I fear that it may not
> possible to gain consensus on that.
You need as many as you need. Request them. Worry about it if you don't
get them. This is exactly what happens when N=1, BTW. A DHCPv6 server is
almost certainly not going to have an upper limit that significantly
crimps your style...
Regards, K.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389
GPG fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4
Old fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882