[180811] in North American Network Operators' Group
Re: Android (lack of) support for DHCPv6
daemon@ATHENA.MIT.EDU (Ted Hardie)
Wed Jun 10 17:33:24 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <5578A933.8090504@dougbarton.us>
Date: Wed, 10 Jun 2015 14:27:12 -0700
From: Ted Hardie <ted.ietf@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On Wed, Jun 10, 2015 at 2:16 PM, Doug Barton <dougb@dougbarton.us> wrote:
> On 6/10/15 2:00 PM, Ted Hardie wrote:
>
>> Lorenzo has detailed why N=3D1 doesn't work for devices that need to use
>> xlat
>>
>
> ... and it's been well demonstrated that this is a red herring argument
> since the provider has to configure xlat for it to have any chance of
> working.
>
> or which might want to tether other devices;
>>
>
> ... and this argument has been refuted by the word "bridging."
>
>
=E2=80=8BTo repeat Valdis' question:=E2=80=8B
=E2=80=8BAnd the router knows to send to the "front" address to reach the "=
back"
> address, how, exactly? Seems like somebody should invent a way to assign =
a
> prefix to the front address that it can delegate to things behind it. :)=
=E2=80=8B
>
=E2=80=8BThe other option would, of course, be "bridging" plus IPv6 "NAT", =
and I
assume you see the issues there.=E2=80=8B
=E2=80=8BBack to the question I asked before: does "static" solve the stat=
ed
problems without "single"?
regards,
Ted=E2=80=8B
