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

Gyan Mishra <hayabusagsm@gmail.com> Wed, 04 November 2020 15:54 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 873D23A1322; Wed, 4 Nov 2020 07:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 eygpk3YlVhkh; Wed, 4 Nov 2020 07:54:34 -0800 (PST)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (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 983173A0D58; Wed, 4 Nov 2020 07:54:34 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id q20so6184825uar.7; Wed, 04 Nov 2020 07:54:34 -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=kLIgdtJQ+RIyrAwMTjBdnIoj/b0nQT5Cxu9ChC6WClU=; b=bgltWbmxy4BeLDdw3Y43frhxlySnJzABuBxyPyVAzQk9vPVx3dMy87bXqUN6NJmSGt dttRvf+Z+LmRFAOSjZ6R0uN+GgdRF2WATaQKgCYT0JCnAhJmgh6zgn+osqZ2ZqzD7QjO tanBVXdu6o6T6JvD1KIHJEvoYsUClye+GR9IlRNDHVQEZgqfcv1Dv5VqEKncxaFxR8RQ CK8y71RqSVMECEDT3fuQ1rnwhShUT4k0+no1WIjuKBk8NYGnUiTkWRHCalwf61b5FzNp ZEXBvIkhmss02Jy/lJOvcjFCtaFw2LleqZ7KS/PYuq7hqG+2GEB5GKug8xOgxX5K47O0 +xmw==
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=kLIgdtJQ+RIyrAwMTjBdnIoj/b0nQT5Cxu9ChC6WClU=; b=d9ToaUeumbUdVCzmeJ5XFxlvUUfnZSGwElq8/Oz72WCY2xXFEfETADtahvEkDEJFIw kKkW2K5L4UQ7VNttzzZ1f6W6RpvzzSFs2Y8FOG3Qd+omit400N4KSrzsvssQgAd/sIkV DMYEcB7I/ADqW3dwTC8ZNjmzftAjoGEmIYdxQpO8r45m2QZq609DOXMFi3yKpBeVU1dR BV5cvEYyBQfKU8HEAYGYpa0NmaGQ/yaVa9d1/sUwJJwlfCfntxh4OmyezDQoRvbIfpER wUJy/00IjGVy+IvwLGCSo/Yw9FAWaHc2UyouBXl0tvRWUqczDjXXXLE00tM30J9+d+B2 aIpQ==
X-Gm-Message-State: AOAM530jQWAM98N4nBt8kC3kp/sQGNcalYqc+Y2MADKG4Hvxbwpjh8VJ S3SOt7mYvtcGdVMuAUgL3Fhxtf/isiBmyrmNbP7AL1fF3J8HNA==
X-Google-Smtp-Source: ABdhPJx+Oc2jsv/pAmpA8QPeeUIdua1DkD40vbzcHFxXmFmHI+cwj43Isvstqjs9iqjsFmEJfiTkG0U5JcNBsEcvgsU=
X-Received: by 2002:a9f:2067:: with SMTP id 94mr13450741uam.141.1604505273662; Wed, 04 Nov 2020 07:54:33 -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>
In-Reply-To: <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 04 Nov 2020 10:54:22 -0500
Message-ID: <CABNhwV13gggo9XfRvrR31bCUptZuAiosK5ebMmnzDdinKqmrBw@mail.gmail.com>
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: Lorenzo Colitti <lorenzo@google.com>
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, draft-mishra-6man-variable-slaac@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e082fa05b349fe76"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zNh_3Qdvy7Vru7ehrB_iZRUoz-A>
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: Wed, 04 Nov 2020 15:54:38 -0000

On Wed, Nov 4, 2020 at 3:51 AM Lorenzo Colitti <lorenzo@google.com> wrote:

> On Tue, Nov 3, 2020 at 4:27 PM Gyan Mishra <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.
>

   Agreed.  Fixed 5G broadband agreed would use the current wired broadband
DHCPv6 PD and would follow the BSOP RIPE-690 and I think would use the
recommended shorter prefix like a /56.  As fixed 5G would take advantage of
the value added at a premium network slicing capabilities for the front
haul and backhaul I can see Broadband 5G getting even a /48.  The issue
mentioned in the draft is related to 4G as well as 5G “mobile handsets” and
getting a /64 allocation which has been the standard which cannot be
segmented by the Subscriber customer end.  I don’t see the mobile handset
/64 prefix being going any shorter even for 5G.  For 5G the business driver
for larger allocation is for the value added network slicing capabilities
and the is relevant only for fixed broadband 5G which will replace wired
broadband.  Mobile handset 5G will not get network slicing capabilities as
it would use the front hall handset to tower backhaul tower to core Normal
RAN Radio VPN.  Compared to Fixed 5G broadband which would have
capabilities of being provisioned for high priority network slice Enhanced
VPN with resource isolation and dedicated resource characteristics.

> --

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

*Gyan Mishra*

*Network Solutions A**rchitect *



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