IETF Logo Mail Archive

Re: [v6ops] Implementation Status of PREF64

Owen DeLong <owen@delong.com> Mon, 11 October 2021 00:14 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFCC53A135B for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 17:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=delong.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHgxElVj32FP for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 17:14:11 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id C716E3A1355 for <v6ops@ietf.org>; Sun, 10 Oct 2021 17:14:11 -0700 (PDT)
Received: from smtpclient.apple ([IPv6:2620:0:930:0:3d47:4290:6816:2e2f]) (authenticated bits=0) by owen.delong.com (8.16.1/8.15.2) with ESMTPSA id 19B0E9Zm2451470 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 10 Oct 2021 17:14:09 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com 19B0E9Zm2451470
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1633911249; bh=MGg3wTUZir4otjd163qtsDSv+leOezv/WtO/uZFlznU=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=Awudif+Lwpaw2lK9ekeQ6OKlz3sZBXFjA+L/r3RiT/ABqLrzz7DLDjgqffzw5ff6G JirOjWYfXP5ECVLCo3MqTQI84zSSTfljRtsKt37aPqP2MeRrcmjQygNiXR7HNLj9z+ gRbXRh089i9qGG3FaehKc/p0892yMn4TmwwuC+No=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <d0c441c6-68fa-52ef-7c60-e8f0cff80ba0@gmail.com>
Date: Sun, 10 Oct 2021 17:14:09 -0700
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <64E83A09-C4DC-428C-88D1-79FAD6AAB72E@delong.com>
References: <EFC78F4B-873B-42EE-8DC5-04C29758B0D0@consulintel.es> <YVNhdioAbeO9p2/G@Space.Net> <CAKD1Yr2+Y59v81mPBn4Y3u0LRX7TzahbnaF1hVUZ+NSf0Jj_4g@mail.gmail.com> <20210930.082006.177771395.sthaug@nethelp.no> <d0c441c6-68fa-52ef-7c60-e8f0cff80ba0@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Sun, 10 Oct 2021 17:14:09 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UCVcR4-wTobL9h40y0iRshBFiE0>
Subject: Re: [v6ops] Implementation Status of PREF64
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2021 00:14:18 -0000

Alexandre,

You’re fighting a different battle than the one most people in this thread care about.

I’m not saying it’s not a good fight, but fighting uphill with 3GPP and Lorenzo on the 3GPP interface(s) is not what is delaying
enterprise IPv6 rollout.

Support for IA_NA on the WLAN interface(s) is the key issue here.

To the best of my knowledge, everyone EXCEPT android supports that.

Owen



> On Oct 7, 2021, at 06:18 , Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> 
> 
> Le 30/09/2021 à 08:20, sthaug@nethelp.no a écrit :
>>>> As a matter of fact, I know of at least one deployment in a "fortune 500"
>>>> company that was seriously impaired due to lack of DHCPv6 support in
>>>> Android.  They want control over address assignment, tracking of address
>>>> assignments, and DHCP is the machinery they use for it (plus NAC, making
>>>> sure that only assigned IPv6 addresses can be used).
>>>> 
>>>> But they want to support Android devices.
>>>> 
>>>> So, still no IPv6 today...
>>>> 
>>> 
>>> Is there any other way to break this logjam than to implement DHCPv6 IA_NA
>>> and accept one IPv6 address per device? What about DHCPv6 PD or
>>> /64-per-host? What about resurrecting draft-ietf-dhc-addr-registration
>>> <https://datatracker.ietf.org/doc/draft-ietf-dhc-addr-registration/>, so
>>> the device can inform the network of addresses it has created?
>> We would love to use IA_PD only, and no IA_NA. Having DHCPv6 PD for
>> Android would be a significant step in that direction.
> 
> I agree, having even a limited DHCP (maybe only IA_PD, or only address registering, or other limitations) working on Android on a cellular modem would be a significant achievement.
> 
> One such limitation is 'stateless DHCP'.  It is a 'may' in 3GPP documents.  However, even that simple limited DHCPv6 is prohibited in 3GPP modems.
> 
> The problematic text in 3GPP TS 23.501 is the following:
> > /64 IPv6 prefix allocation shall be supported via IPv6 Stateless
> > Auto-configuration according to RFC 4862 [10], if IPv6 is supported.
> > The details of Stateless IPv6 Address Autoconfiguration are described
> > in clause 5.8.2.2.3. IPv6 parameter configuration via Stateless
> > DHCPv6 (according to RFC 3736 [14]) may also be supported.
> 
> Remark the 'may' in the last line.
> 
> In practice there is no DHCPv6 allowed by any 3GPP modem out there.
> 
> Alex
> 
>> Steinar Haug, AS2116
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email