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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 09 November 2020 09:09 UTC

Return-Path: <prvs=158289e994=jordi.palet@consulintel.es>
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 D87413A0D52 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 01:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_ABOUTYOU=0.5, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 D2aAaTC8Ucbt for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 01:09:06 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 75C973A0D65 for <ipv6@ietf.org>; Mon, 9 Nov 2020 01:09:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1604912944; x=1605517744; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=npWySHvo Vl8ryzupWJI9VEePL+tNgTRu/+ehmlC+oOM=; b=sEhCtaolUZ7u9+29k98gLOH5 b6mj8lBf2600/MwCkE9rVzd4ORzOYjvM0L+mR9X8n6K1IshUrhXtaHbUSvw0aGrL sODV94Xs5w36w8GBPsZoKav5q06rUakQuY8yxXQXsp8QDeVsNKmTZD/v3ckktBsd tT3IqkNDbmNjJAqksG8=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 09 Nov 2020 10:09:04 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 09 Nov 2020 10:09:03 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000458548.msg for <ipv6@ietf.org>; Mon, 09 Nov 2020 10:09:03 +0100
X-MDRemoteIP: 2001:470:1f09:495:d41d:ff88:9a6d:5019
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Mon, 09 Nov 2020 10:09:03 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=158289e994=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
User-Agent: Microsoft-MacOutlook/16.42.20101102
Date: Mon, 09 Nov 2020 10:09:01 +0100
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ipv6@ietf.org
Message-ID: <3E50906D-1E09-4555-B38A-A6E283AB49DC@consulintel.es>
Thread-Topic: I-D Action: draft-mishra-6man-variable-slaac-01.txt
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>
In-Reply-To: <cda97933-5935-ebd8-da38-3f9ce7fbba61@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KpnokSmhMtwikoDKQkrvposkkHw>
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:09:08 -0000

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.