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

Ca By <cb.list6@gmail.com> Thu, 05 November 2020 00:15 UTC

Return-Path: <cb.list6@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 DE6B83A1193; Wed, 4 Nov 2020 16:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level:
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 vf8Tra6XXr1X; Wed, 4 Nov 2020 16:15:25 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 A4D803A1191; Wed, 4 Nov 2020 16:15:25 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id u21so387830iol.12; Wed, 04 Nov 2020 16:15:25 -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=Jme9y+zVsJDTFHARBrcFHfV1Ly5j51xZzhyQl5JvkEg=; b=nS5xMLUXv7bsth+7Mm3ieqPrJVAmhjObeQqkSWTVIIrnkUgWAnIk2tgXIYZVwXMctO 1gmuTWwOnnSKPSCbiyXgP9hqIwF1GO6EVEXVDiCRXXPNOomeii6pLH2D2/hRHAfq0KiG l6yx74kNSnIEI6vGXdKuvFMgdzmtTBYufpszSe/Bz59Nt+uu/LINWO3l4JgtS+3ZQ4BR ThdbxoPuRCuzyDSxFXhzl+VNkF0AKqQil1JUJ+UWIWywvFg+RgYtSOZem9s/2fHrN6JM rF0b22HdYe1Fr0ZQhzqmG/vGpDnGDhAIUppxClVx7hZunIUZfUM6GCc5TXoW9K/A0ZYI lwQg==
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=Jme9y+zVsJDTFHARBrcFHfV1Ly5j51xZzhyQl5JvkEg=; b=FKEsiq94mAenuUUnw2yljrvjpsJpVWpaewTDtAaCA+DFaCkftGuUhw27pB1Xnvu4lS Jc7zWbkeEBBJoHPfvVxE3EBW8Qbv98SiVObqBwfc5RFuV8LE9+oc7uL30EPGuAGA5kaa ZRxAuVskuIM1UriwAz5jwkESSEGRaC0RJYCN36buiQ1UClMbIZkzeS69IGO00xTdfzsI IaehSASyJQl3kFm2zjnWKV2r6k5l37vy+WbZwZMZngwDtoTd+60k2KMZLZRhPhQZapzo EhLjDMgbsdZri1xcB9tYMxQtje701KEtgTfYeqEkfxhCKHQYWxtouj/DDWiEGcSw7fYh U5CQ==
X-Gm-Message-State: AOAM532m3xWDBawDLsTpmH+EHD28b4yissnX7fLqXkqJJR+jEptGwUJe zuN6LuY1ajeLEKyNTfqfPFnh6ShhtpxcaLjntwQ=
X-Google-Smtp-Source: ABdhPJyP1rtNxRNHnc7oBasENNUdefWdFryou63g385k+Sj+2ErsNHeYj1ve7F1fG2mcQJ4vDFbMiEIGE9C4D9Fsh54=
X-Received: by 2002:a5d:9813:: with SMTP id a19mr434155iol.194.1604535324906; Wed, 04 Nov 2020 16:15:24 -0800 (PST)
MIME-Version: 1.0
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CAD6AjGQPatbg5=OaMzxJXy5mGZai1bqLfg8f+9SUnfg=s1kADg@mail.gmail.com> <e55a9fbf-a93c-a96f-7991-f0c3aad8ce16@gmail.com>
In-Reply-To: <e55a9fbf-a93c-a96f-7991-f0c3aad8ce16@gmail.com>
From: Ca By <cb.list6@gmail.com>
Date: Wed, 04 Nov 2020 16:15:14 -0800
Message-ID: <CAD6AjGSTQjKQuY1+0DNm5NRgTRkWUQ=eRhnvyKCXvKc3Kvy9TQ@mail.gmail.com>
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6man <ipv6@ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, draft-mishra-6man-variable-slaac@ietf.org
Content-Type: multipart/alternative; boundary="000000000000121bd405b350fe32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9-8QCcEa5FxgihjHqpoLBeAU5hQ>
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: Thu, 05 Nov 2020 00:15:27 -0000

On Wed, Nov 4, 2020 at 2:37 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 05-Nov-20 04:45, Ca By wrote:
> >
> >
> > On Wed, Nov 4, 2020 at 12:52 AM Lorenzo Colitti <lorenzo=
> 40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> wrote:
> >
> >     On Tue, Nov 3, 2020 at 4:27 PM Gyan Mishra <hayabusagsm@gmail.com
> <mailto:hayabusagsm@gmail.com>> wrote:
> >
> >         It's hard to see why this draft is needed anyway. All that is
> needed
> >
> >             is to remove the "64 bit" statement from the addressing
> architecture,
> >             which the WG has consistently failed to reach consensus
> about.
> >
> >
> >             Gyan>  This topic has come up many times over the years in
> heated debate and this is another instance of that.  Agreed.  However, what
> makes this instance different is that we have a major problem to be solved
> with 4G  &  now as 5G is rolled out, segmentation is of utmost importance.
> I think in the past we have not had a major problem to be solved and so
> this change being proposed did not gain traction,  but now as 5G becomes
> the "norm" as it will compete directly with broadband that customers will
> start using 5G in SOHO as well as other environments.   This is a major
> issue that has come up with the ramp up for 5G IPv6 only deployments.
> >
> >
> >     There is already a solution to this: use DHCPv6 PD on 5G networks.
> It's been supported since 3GPP release 10 several years ago.
> >
> >
> > Has any mobile provider deployed dhcpv6 pd?
> >
> > Perhaps the mobile providers have seen what an operational nightmare
> dhcpv6 pd is and... are like nope.
>
> Perhaps that needs to be documented over in v6ops.
>
> > I am in favor of the ietf opening their eyes to a better solution.
> >
> > Rfc7278 is universally deployed because it is easy.
>
> As far as I can tell that is no use for the case of routed network
> connected to a hotspot, since there is still only one /64 prefix.
>
> > Can we do better (more /64s) and easy ?
>
> You mean multiple /64s for a single mobile device? Rather than fixing 3GPP
> to support shorter prefixes, which seems simpler.
>
>     Brian


Mobile providers have not deployed dhcp pd in the last 10 years.

As a mobile provider, my bet is the next 10 years may be no better.

Yet, rfc 7278 is deployed in many places in mobile


>
>