Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 09 November 2020 09:24 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 C347A3A0D87 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 01:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.17
X-Spam-Level: *
X-Spam-Status: No, score=1.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, GB_ABOUTYOU=0.5, 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 5bcv7ALxxzBw for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 01:24:23 -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 C7A7E3A0D41 for <ipv6@ietf.org>; Mon, 9 Nov 2020 01:24:22 -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 0A99OKTd021898 for <ipv6@ietf.org>; Mon, 9 Nov 2020 10:24:20 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D049A20461D for <ipv6@ietf.org>; Mon, 9 Nov 2020 10:24:20 +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 C31BA204617 for <ipv6@ietf.org>; Mon, 9 Nov 2020 10:24:20 +0100 (CET)
Received: from [10.11.240.35] ([10.11.240.35]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A99OK5G002244 for <ipv6@ietf.org>; Mon, 9 Nov 2020 10:24:20 +0100
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: ipv6@ietf.org
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CABNhwV3L7kz=cWu8s3X=djVf4MCwewzbEgx09TWaKzCULCjYUQ@mail.gmail.com> <9A9CE8E7-3552-4FD8-A50E-1BDCA2CB813F@employees.org> <CABNhwV0LxM7EuKo2wNtVacjewsVqdhrmSiVBmB_EL-mqJYdU3A@mail.gmail.com> <CD9F9F09-2CBC-4A72-99C0-4A9A470357ED@employees.org> <CABNhwV1WmnQ_vt31t0eUTiEhsi3Du+X+XPafRNv1BgvZS+TPGA@mail.gmail.com> <m1kaM2K-0000J1C@stereo.hq.phicoh.net> <CABNhwV3uODOD7_fWhZzSNrw+P8ftR5D5QAiK65FNXCs+NrmE_w@mail.gmail.com> <CABNhwV3zGLXTTRXzkUShCmnVUqdy0p+QiLHhVAa1bzr_XGJx9w@mail.gmail.com> <4ED53387-0CCB-4779-848E-EFCF6120EB66@consulintel.es> <2596ea4a-6160-e07f-0c40-96649c83f10f@gmail.com> <46D48E3F-B395-4DE2-AAD3-676086D78B34@consulintel.es> <cda97933-5935-ebd8-da38-3f9ce7fbba61@gmail.com> <3E50906D-1E09-4555-B38A-A6E283AB49DC@consulintel.es>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <94c0bdc8-3c63-2fe6-7978-94593d396b69@gmail.com>
Date: Mon, 09 Nov 2020 10:24:20 +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: <3E50906D-1E09-4555-B38A-A6E283AB49DC@consulintel.es>
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/aya2Edm0vAVOzBfV6SUEuu3SCb4>
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: Mon, 09 Nov 2020 09:24:25 -0000

I think there are many instances where one tries DHCPv6 on a computer 
connected to LTE and it appears to be working.

But there might be some details in that high level statement that might 
not be enough for what we try to achieve.

For example, executing DHCPv6 on an processor running linux did succeed 
to ask for IPv6 addresses to a modem on LTE.  But the modem itself 
transformed that DHCPv6 request into something else (a link layer 
message) that is not DHCPv6.   We too have tried such configuration - 
execute DHCPv6 on the processor - but the LTE operator did not receive 
any DHCPv6 message from us.

We have writen a draft that tries to explain, among other things, that 
difference between a processor and the modem, and the behaviour of 
DHCPv6 on them.  The file name is draft-shytyi-v6ops-danir-05 and it is 
titled "DHCPv6_PD, PDP and NDP Implementation in IoT Router (DANIR)". 
In particular, in the figure before section 8, one can see a computer 
User Equipment made of a laptop with an E329 USB Dongle.

Alex

Le 09/11/2020 à 10:09, JORDI PALET MARTINEZ a écrit :
> I tried to find the information in my notes, but it was a casual testing, not in the scope of the customer project, I just took the opportunity to test it because I saw an LTE router and a network "combination" that was supporting it. Tested and worked. I recall there were many LTE routers (kind of CPEs with SIM support), most of them were from Chinese's vendors (some well-known brands such as Huawei).
> 
>   
> 
> El 8/11/20 23:44, "ipv6 en nombre de Alexandre Petrescu" <ipv6-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:
> 
> 
> 
>      Le 08/11/2020 à 23:06, JORDI PALET MARTINEZ a écrit :
>      [...]
>      > Also, Alex insisted that chipset vendors don't support it. I don't
>      > think this is the case, I recall having used DHCPv6-PD with an LTE
>      > router long time ago.
> 
>      I asked it at that time, I will ask it again the same question of
>      whether this was on a smartphone or on a CPE, with which operator, which
>      LTE modem, was the Server in the cellular network, and other details.
> 
>      (if my assumptions about your trial is correct) The fact that a CPE
>      router has a LTE interface and that the Server is outside the network
>      operator it does not mean DHCPv6-PD works on smartphones.
> 
>      > I'm sure we have in the list folks from Apple, Broadcom, Qualcomm,
>      > maybe ARM, or somebody in the list can reach them, to ensure if this
>      > is a chipset problem, which I don't think is the case.
> 
>      It is the case.
> 
>      > It looks to me it is more a problem of the rest of the mobile network
>      > equipment, just not implementing it by default.
> 
>      No, it is a problem on the modem in the smartphone, not in the network.
> 
>      Anyways, we will not solve it here.
> 
>      One has to admit that in some environments some things are simply not
>      there and wont come.
> 
>      Alex
> 
>      >
>      >
>      > El 8/11/20 22:44, "ipv6 en nombre de Brian E Carpenter"
>      > <ipv6-bounces@ietf.org en nombre de brian.e.carpenter@gmail.com>
>      > escribió:
>      >
>      > On 09-Nov-20 09:14, JORDI PALET MARTINEZ wrote:
>      >> This is wrong. As one of the authors of that document, I can ensure
>      >> that it covers both aspects, size and persistence and it also
>      >> covers mobile. See:
>      >>
>      >>
>      >>
>      >> 4.2.4. Considerations for Cellular Operators
>      >>
>      >> There is a clear exception to the rule described above when
>      >> assigning prefixes in a cellular network. In this case, a /64 will
>      >> need to be provided for each PDP context for cellular phones,
>      >> whereas for LTE modems/routers, i.e. in the case of broadband by
>      >> means of cellular access, it will still be necessary to choose a
>      >> /48 or /56 in accordance with the aforementioned considerations.
>      >>
>      >
>      > Can you be more explicit? Are you saying that this problem is in fact
>      > solved for 5G modems? If so, and 4G is soon to be legacy, why are we
>      > even having this discussion?
>      >
>      > Regards Brian
>      >
>      >
>      > --------------------------------------------------------------------
>      > IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>      > Requests: https://www.ietf.org/mailman/listinfo/ipv6
>      > --------------------------------------------------------------------
>      >
>      >
>      >
>      > ********************************************** IPv4 is over Are you
>      > ready for the new Internet ? http://www.theipv6company.com The IPv6
>      > Company
>      >
>      > This electronic message contains information which may be privileged
>      > or confidential. The information is intended to be for the exclusive
>      > use of the individual(s) named above and further non-explicilty
>      > authorized disclosure, copying, distribution or use of the contents
>      > of this information, even if partially, including attached files, is
>      > strictly prohibited and will be considered a criminal offense. If you
>      > are not the intended recipient be aware that any disclosure, copying,
>      > distribution or use of the contents of this information, even if
>      > partially, including attached files, is strictly prohibited, will be
>      > considered a criminal offense, so you must reply to the original
>      > sender to inform about this communication and delete it.
>      >
>      >
>      >
>      > --------------------------------------------------------------------
>      > IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>      > Requests: https://www.ietf.org/mailman/listinfo/ipv6
>      > --------------------------------------------------------------------
>      >
> 
>      --------------------------------------------------------------------
>      IETF IPv6 working group mailing list
>      ipv6@ietf.org
>      Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>      --------------------------------------------------------------------
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>