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

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

Return-Path: <prvs=15775de6d8=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 B7D9E3A0E1B for <ipv6@ietfa.amsl.com>; Wed, 4 Nov 2020 01:29:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 E6iJXS1Znz5j for <ipv6@ietfa.amsl.com>; Wed, 4 Nov 2020 01:29:14 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id E3CE83A0E13 for <ipv6@ietf.org>; Wed, 4 Nov 2020 01:29:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1604482153; x=1605086953; 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; bh=zhgDYUtMqPzsuccYJ49Ky0APkYfpTsYLR3 XJDuWHZgI=; b=hJMVFOuNMFB8MDvKOjDVKsJX2zOkcuxr6VBBfCxvF5xi7NYahb qFPvzO37OyIV60OnPrsHKWBKYlwymQrSUeck22d2e/f/+Q21AEmaG478htITarzq +ZXKqvaUc7s+QrJf/TwNYmdyTgvhig6V1FljsakDI0NKKkBjh1k56yIAo=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 04 Nov 2020 10:29:12 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 04 Nov 2020 10:29:12 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000453996.msg for <ipv6@ietf.org>; Wed, 04 Nov 2020 10:29:12 +0100
X-MDRemoteIP: 2001:470:1f09:495:14a1:4e08:d912:6b56
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Wed, 04 Nov 2020 10:29:12 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=15775de6d8=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: Wed, 04 Nov 2020 10:29:07 +0100
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: 6man <ipv6@ietf.org>
Message-ID: <A95A26FC-94A9-475F-9BCC-6AD17574EA35@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> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com>
In-Reply-To: <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3687330547_810840888"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KyorxRgnE2bPc4yUAwoz3JzsJkc>
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 09:29:17 -0000

Exactly!

 

In fact, not using it is very bad when you want to offer 5G broadband to customers that may not have access to a wireline. If they aren’t able to get /48 thru the 5G “modem”, how come they can segment their network? This is just creating NAT for IPv6, as if a 5G broadband customer needs to have multiple /64 VLANs, they have no other way.

 

Regards,

Jordi

@jordipalet

 

 

 

El 4/11/20 9:52, "ipv6 en nombre de Lorenzo Colitti" <ipv6-bounces@ietf.org en nombre de lorenzo=40google.com@dmarc.ietf.org> escribió:

 

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.

-------------------------------------------------------------------- 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.