Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?

Gyan Mishra <hayabusagsm@gmail.com> Mon, 23 November 2020 17:05 UTC

Return-Path: <hayabusagsm@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 199253A0B1C; Mon, 23 Nov 2020 09:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level:
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kVEXx6FuFFzt; Mon, 23 Nov 2020 09:05:50 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FCF23A0B18; Mon, 23 Nov 2020 09:05:50 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id s2so9141243plr.9; Mon, 23 Nov 2020 09:05:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9IpAu/GbRWQEeLs/05ExUvxSKAymrp1bYWgp5gifPrg=; b=hO+EwiTg79un+E7FsRl8zZf7dpE2QaXqlGSUbcjjRxOs+i0JXsSjT3uge49Kywh7X/ huWrSImv3thyYWL2gjzwLxVZHGdIPWs9PdcQGEO0KiTArEqVstGOofCxkEbu9o7D1AEH lDqFHHajiaryXZnzGv7+maMGbib22nKjgn9zA67QciteYJ/J7ggORrrti1yts2L5Cl5E L/vP+UB0pRH1dG63QU9doyBWmO1QiqPGWEL94aKRIHnkkAkcj5ll+5V4zJOcMGna/oxu p+bcNg68Pm+QTTFkSnIMqECWe8ZtsOrSU+9rkRxjK/uevqojeAwdfTT/79o+i0Euw0cI uhLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9IpAu/GbRWQEeLs/05ExUvxSKAymrp1bYWgp5gifPrg=; b=WZ3py08SLP977JuhwVR9/rdRtLhCt6WC87QikT8RFikSA/9274RQmWzkO5PXmfiRI4 FsiqVr83rJIjbVH8tVTXCju3b7Bq/G1F4JwOttA4+Y9f6pbhoxUNNtZXynzb12CBVKY5 6azE6cUWkJDgiy7HngC4ciGvijvqwEJAZvzZpYtHsYWwkcvZ6+j0xWdiX017CvxeROFp NiPoX4Xr8emYYtVGWCQCt/B4wAiWrMIsex+smYVMx4e1yU5zi1t1SvQu5+19H9pNeyea e+0HURIou25NnUXbwzGlPkkLBTzXQxj7kKuEQWZQe9uNqAZd1f46qTuzAJ0i5BlLVfSp qEtw==
X-Gm-Message-State: AOAM531HWV1fCkLkHAE0j+wFH5Q4BfPBK4ggCbnqPv+Yo8vyY4hg2ZOf sjfBWewtPyStg5AAgtI5F7ZKcdHMMaqe6aOoZVY=
X-Google-Smtp-Source: ABdhPJwXlpgxOAS+Il0Y+6lVQ6uktSEAcpW2uf3GlukSu6aDvoInUwbDWduDoq+op+ffJygLxWRVt5bEqQXHNzfDlF8=
X-Received: by 2002:a17:902:7c01:b029:d8:ee2a:ce88 with SMTP id x1-20020a1709027c01b02900d8ee2ace88mr401636pll.22.1606151149581; Mon, 23 Nov 2020 09:05:49 -0800 (PST)
MIME-Version: 1.0
References: <CABNhwV2-dH81CY4wSisV8BU-7H9m5a1xYMqTMecRxhNqZe=ApQ@mail.gmail.com> <alpine.DEB.2.20.2011231317420.26384@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.2011231317420.26384@uplift.swm.pp.se>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 23 Nov 2020 12:05:39 -0500
Message-ID: <CABNhwV0xuzJwYhic9+eDcMzs-Lgt3grtSC_YkTrR6QNQs3zqAg@mail.gmail.com>
Subject: Re: [v6ops] How do you solve 3GPP issue if neither operator nor handset supports PD?
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Cc: 6MAN <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>, "draft-mishra-6man-variable-slaac@ietf.org" <draft-mishra-6man-variable-slaac@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b9f85f05b4c934d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aZf1BTbi_1oyFZfAOYPPjWPqtW4>
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, 23 Nov 2020 17:05:52 -0000

On Mon, Nov 23, 2020 at 7:24 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Mon, 23 Nov 2020, Gyan Mishra wrote:
>
> > How do we propose to solve this problem if operators don’t support PD
> even
> > though the  3GPP standard has supported PD for over 10 years.
> >
> > Another twist to this puzzle is Android has 90% of the mobile handset
> > marketplace worldwide and adamantly states they will NOT support DHCPv6
> or
> > PD.
> >
> > I researched Apple which has 10% of the market and they also do not
> support
> > PD.
> >
> > Whats the solution now?
>
> The obvious use-case for PD is the "LTE router" fixed-wireless use-case.
> There the problem of getting a DHCPv6-PD client into the UE isn't the same
> as on handsets. A lot of those platforms already support DHCPv6-PD for
> their wired versions (some have both LTE and wired WAN).


    Gyan>Agreed the obvious PD use case is for wired LTE but this
particular use case brought up in slaac problem statement draft is for
handsets.

>
>
> So this brings us back to the mobile core. Why doesn't this today, 8 years
> after DHCPv6-PD was introduced in 3GPP standards, still not support PD?


>
> I don't know but I know staff at operators who claim to have tried (more
> than 5 years ago). I do not know why their efforts failed. Perhaps the
> mobile core vendors successfully managed to divide the customer base so
> there was no critical mass. I can only speculate. I just find it weird
> that there are now demands to change *everything* downstream from the 3GPP
> bearer to handle smaller subnets instead of enabling PD in mobile core.


    Gyan> I have to research technical reasons why

>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD