IETF Logo Mail Archive

Re: [v6ops] Implementation Status of PREF64

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 07 October 2021 13:18 UTC

Return-Path: <alexandre.petrescu@gmail.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 D95063A102B for <v6ops@ietfa.amsl.com>; Thu, 7 Oct 2021 06:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 TS1ReVDynRzk for <v6ops@ietfa.amsl.com>; Thu, 7 Oct 2021 06:18:42 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36DF23A1029 for <v6ops@ietf.org>; Thu, 7 Oct 2021 06:18:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 197DIdTv027703 for <v6ops@ietf.org>; Thu, 7 Oct 2021 15:18:39 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7F3C42052E8 for <v6ops@ietf.org>; Thu, 7 Oct 2021 15:18:39 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 75C812052C6 for <v6ops@ietf.org>; Thu, 7 Oct 2021 15:18:39 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 197DId34005661 for <v6ops@ietf.org>; Thu, 7 Oct 2021 15:18:39 +0200
To: v6ops@ietf.org
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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d0c441c6-68fa-52ef-7c60-e8f0cff80ba0@gmail.com>
Date: Thu, 07 Oct 2021 15:18:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <20210930.082006.177771395.sthaug@nethelp.no>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PXfdrPPRv4duAlmjMkFANkBXMA0>
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: Thu, 07 Oct 2021 13:18:47 -0000


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
>

v2.23.0 | Report a Bug | By Email