Re: DHCPv6-PD is fine
Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 10 November 2020 10:21 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE2D3A0EB4 for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 02:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 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_H3=0.001, RCVD_IN_MSPIKE_WL=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 1s0iqOrDTN6P for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 02:21:19 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 2EECE3A0EA8 for <ipv6@ietf.org>; Tue, 10 Nov 2020 02:21:18 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AAALHuU027187 for <ipv6@ietf.org>; Tue, 10 Nov 2020 11:21:17 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 18E5720467A for <ipv6@ietf.org>; Tue, 10 Nov 2020 11:21:17 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0E9872046B7 for <ipv6@ietf.org>; Tue, 10 Nov 2020 11:21:17 +0100 (CET)
Received: from [10.11.242.43] ([10.11.242.43]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AAALFkC008764 for <ipv6@ietf.org>; Tue, 10 Nov 2020 11:21:16 +0100
Subject: Re: DHCPv6-PD is fine
To: ipv6@ietf.org
References: <350919b2-fe50-a3b8-3f15-4ce32124d495@gmail.com> <3377F3AE-BDFE-4AAC-ACA3-0F3D1A4D8854@thehobsons.co.uk> <SN6PR02MB4512DE7BF31D8758BE15D899C3EA0@SN6PR02MB4512.namprd02.prod.outlook.com> <20201109.220035.1460667476695106090.he@uninett.no> <06002E16-10CF-4C39-80A7-4EF2B1DFF4CA@fugue.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <92f3c592-ac15-1e9a-640b-86f5e090e57a@gmail.com>
Date: Tue, 10 Nov 2020 11:21:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.1
MIME-Version: 1.0
In-Reply-To: <06002E16-10CF-4C39-80A7-4EF2B1DFF4CA@fugue.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SB8f9idPsbwArhYJyWCZjUvP6H0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2020 10:21:21 -0000
This is a personal point of view, I am not employed at manufacturer or operator. Le 09/11/2020 à 22:23, Ted Lemon a écrit : > On Nov 9, 2020, at 4:00 PM, Havard Eidnes > <he=40uninett.no@dmarc.ietf.org > <mailto:he=40uninett.no@dmarc.ietf.org>> wrote: >>>> From what I've been reading in this thread, in the mobile >>>> world the problem isn't DHCPv6-PD, but the cellular world >>>> having not adopted it, or even blocked it (ref discussion of >>>> mobile modems blocking DHCP packets). >> >> Is this lack of flexibility for all intents and purposes imprinted >> into silicon? That would ... be an extremely effective road-block >> for practical deployment if one wanted to make a change where DHCP >> should additionally be used. > > I’m having trouble envisioning how this would even be possible. Is > there an IP stack on the chip that has a firewall in it that blocks > DHCP? Yes. > This woud be surprising. YEs to me too it was surprising to see how many things these modems do. I was surprised first when my laptop sent a DHCP request, received an answer, but the operator told me they did not receive such a request and they did not generate an answer either. It's because there was a DHCP proxy in between that I could not see. It's on the modem. There is a whole operating system running in modern modems of smartphones. They have their own IP addresses inside. Some times they even run DHCP servers inside. Looking at the open source efforts to make an OS for these modems it is possible to get a hint of how advanced they are. IIRC one is called Hexagon MiniVM. > Why would they go to that effort? In order to protect (some humans at some computers at some) operator. The legislation requests that the owner of a smartphone has access to that smartphone, i.e. to log in and install whatever s/he wishes; as a side note this is different than CPEs where the legislation only requests the GPLed source codes of CPE to be made available upon request. On these smartphones, a malicious user might install malicious software that could attack the (~) operator. Other than outright vicious attacks some programmers might want to play with a home made DHCP client on the ARM part of the smartphone (not the modem). That client would disrupt functioning of the already exisitng DHCP server running in the modem. I suspect that is why smartphone manufacturer, under guidance of modem manufacturer and in agreement with (~) operator, effectively block UDP port numbers of DHCPv6. They block other people's DHCP and let only their own non-documented variant of DHCP proxy through. That is my supposition, or rather a speculation. It means that I might be wrong. But that does not improve the situation of absence of DHCPv6-PD in smartphones. Alex > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list ipv6@ietf.org Administrative > Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- DHCPv6-PD is fine Templin (US), Fred L
- Re: DHCPv6-PD is fine Alexandre Petrescu
- Re: DHCPv6-PD is fine Templin (US), Fred L
- Re: DHCPv6-PD is fine Simon Hobson
- RE: [EXTERNAL] Re: DHCPv6-PD is fine Templin (US), Fred L
- RE: DHCPv6-PD is fine STARK, BARBARA H
- Re: DHCPv6-PD is fine Philip Homburg
- Re: DHCPv6-PD is fine tony.whyman
- RE: [EXTERNAL] Re: DHCPv6-PD is fine Templin (US), Fred L
- Re: DHCPv6-PD is fine Havard Eidnes
- Re: DHCPv6-PD is fine Templin (US), Fred L
- Re: DHCPv6-PD is fine Ted Lemon
- Re: DHCPv6-PD is fine Havard Eidnes
- Re: DHCPv6-PD is fine Brian E Carpenter
- Re: DHCPv6-PD is fine Alexandre Petrescu
- RE: DHCPv6-PD is fine Vasilenko Eduard
- Re: DHCPv6-PD is fine Alexandre Petrescu