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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sun, 08 November 2020 22:06 UTC

Return-Path: <prvs=1581810f94=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 762AB3A0E7D for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 14:06:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=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=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 DxBg7tGGyIhe for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 14:06:37 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 69D2A3A0E7C for <ipv6@ietf.org>; Sun, 8 Nov 2020 14:06:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1604873192; x=1605477992; 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=cJJFGLjL IfUND7DXXGD3DE3pSQ5q9ZjgxpH9NO7mXbc=; b=QuTxRXd66XCmwdWFfCHVbHDO IF98spTu8ypEmp0epEqTEpNSBdmnN+DJHuIPBKhLf0rLlxWc2GyQaii/C/tOK1GJ gYooj+SxNBsIpKSu8/LqOmv5EnrxRUNkowv7guIzu77RJUl1iudTfczS2Fj8QM0x IvMdInm93L/J/X0nJHs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sun, 08 Nov 2020 23:06:32 +0100
X-Spam-Processed: mail.consulintel.es, Sun, 08 Nov 2020 23:06:29 +0100
Received: from [10.10.10.141] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000458163.msg for <ipv6@ietf.org>; Sun, 08 Nov 2020 23:06:29 +0100
X-MDRemoteIP: 2001:470:1f09:495:88f0:28ca:9d5e:dbcd
X-MDHelo: [10.10.10.141]
X-MDArrival-Date: Sun, 08 Nov 2020 23:06:29 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1581810f94=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: Sun, 08 Nov 2020 23:06:29 +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: <46D48E3F-B395-4DE2-AAD3-676086D78B34@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>
In-Reply-To: <2596ea4a-6160-e07f-0c40-96649c83f10f@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/-NBh_urUCrOC8vHzN1ZkozrGt8Q>
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: Sun, 08 Nov 2020 22:06:38 -0000

We drafted this text knowing that according to standards, a smartphone can use several PDP context, and each one obtain a /64, but that the standards (already in 3G release 10, I think around 2011) also support DHCPv6-PD, so it is expected that if it is not a smartphone, but a router, it will support a shorter prefix (/48, /56, etc.).

I think Cameron confirmed that in a previous email in this thread.

The problem seems to be that either vendors didn't implemented it, or operators didn't deployed it.

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'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 looks to me it is more a problem of the rest of the mobile network equipment, just not implementing it by default.


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.