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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 09 November 2020 17:00 UTC

Return-Path: <prvs=158289e994=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 DB95D3A1255 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:00:09 -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 C-9ARORWMmHO for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:00:07 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 226EC3A120A for <ipv6@ietf.org>; Mon, 9 Nov 2020 09:00:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1604941205; x=1605546005; 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=ns5ivr/AMbfjqRh4EE9+5BzexBmIw8QtGQ ekDJ0MojY=; b=k7Qi7PAvQngVi68rfFG9OPobX7B7fi1bIwX2IUF0GOL0wSz/bS merlxxP3zdgIRbLG+vCCEH1vjtaXBrXhqWPllKrdfYIu9XmJs65Iy+J09/TxibsY yXSIGuA4C4hOxGU+L+6Xwrn4yHHrdSv+kHyqQg1vQh5RQeTx6VwHAIXXs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 09 Nov 2020 18:00:05 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 09 Nov 2020 18:00:04 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000458975.msg for <ipv6@ietf.org>; Mon, 09 Nov 2020 18:00:03 +0100
X-MDRemoteIP: 2001:470:1f09:495:881d:3bca:4069:cd37
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Mon, 09 Nov 2020 18:00:03 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=158289e994=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: Mon, 09 Nov 2020 17:59:59 +0100
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: 6man WG <ipv6@ietf.org>
Message-ID: <96D1A0F4-0AAD-4400-9C3E-A952E5908B5C@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> <CAD6AjGQPatbg5=OaMzxJXy5mGZai1bqLfg8f+9SUnfg=s1kADg@mail.gmail.com> <FE260932-A064-493E-8CD5-D92B2725F9E6@employees.org> <CAD6AjGRXYqJhXL6ipbS_cWkE2mg3sU4tM5XCCvgiGvSALGfeeg@mail.gmail.com> <e7938c0f-758c-1f90-814a-46f8b262a134@gmail.com> <3298C400-E393-4588-A703-BA9B4B09587F@consulintel.es> <CAD6AjGTLdFPSmUKUHUSS6rf4ewiteoa27D-zK3amyGvo7sWswQ@mail.gmail.com>
In-Reply-To: <CAD6AjGTLdFPSmUKUHUSS6rf4ewiteoa27D-zK3amyGvo7sWswQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3687789599_1721567562"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Gb5fCNEqja4JHKzBfH-samTBj8Q>
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, 09 Nov 2020 17:00:10 -0000

Hi Cameron,

 

You know that I’ve been defending 464XLAT in broadband as well … so your comment is not fair in my own case.

 

Let me clarify my point.

 

I know that authentication, billing, dpi, etc., are working for even the bigger cellular providers. What I’m saying is that if those have been able to scale in a safe way for you, DHCPv6-PD should be as well.

 

I’m just trying (and I think many folks in this discussion), why the 3GPP incorporated DHCPv6-PD in the standards, and however, is not being used. We are missing facts, reasons, why it doesn’t work.

 

Regards,

Jordi

@jordipalet

 

 

 

El 9/11/20 17:13, "ipv6 en nombre de Ca By" <ipv6-bounces@ietf.org en nombre de cb.list6@gmail.com> escribió:

 

 

 

On Mon, Nov 9, 2020 at 1:39 AM JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:

I think there is some performance testing done in ISC KEA, which allows distributed DHCPv6 (including PD) servers, HA features, etc. I don't think this should be a different problem than the fact that they need to run many APNs, authentications servers, billing, DPI, firewalling, etc., for the same number of hundreds of millions of customers (in the bigger cases of cellular networks).

Regards,
Jordi
@jordipalet

 

All those things you mentioned above (billing,  dpi, ...)  are working today

 

Dhcpv6 is not. Has not. Will not. 

 

Just like the story of 464xlat, we can deploy ipv6 if we listen to what mobile operators in the ietf are saying. 

 

Just like back then, the ietf simply said use dual-stack, no need for 464xlat. Same story now, folks say use dhcpv6. Not helpful. 

 



El 9/11/20 2:26, "ipv6 en nombre de Brian E Carpenter" <ipv6-bounces@ietf.org en nombre de brian.e.carpenter@gmail.com> escribió:

    On 09-Nov-20 13:00, Ca By wrote:
    > 
    > 
    > On Fri, Nov 6, 2020 at 1:05 AM <otroan@employees.org <mailto:otroan@employees.org>> wrote:
    > 
    >     Cameron,
    > 
    >     >     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.
    >     >
    >     > I am in favor of the ietf opening their eyes to a better solution.
    >     >
    >     > Rfc7278 is universally deployed because it is easy.
    >     >
    >     > Can we do better (more /64s) and easy ?
    > 
    >     It's difficult to design a better solution without understanding what "operational nightmares" mean.
    >     Would you mind elaborating?
    > 
    > 
    > I believe running a dhcp server supporting 120M mobile subscribers would be a nightmare.  I believe dhcpv6 is a larger stateful database and a not very forgiving protocol... and client implementations are ... heterogeneous. ... and server failover.. messy

    Of course. You would have to run thousands of DHCPv6 servers out in the wild. Certainly there would need to be some distributed address pool management too. Just handing out a /56 to each PDP context would be so much better.

        Brian

    > 
    > None of that exists today in mobile. I feel the effort and scale are daunting, so i am not going to do it. 
    > 
    > But, getting a knob in the gateway to set the RA to be 60 (or other) instead of 64 would be easy. And, that knob could be constrained to only compatible device type (chef’s kisses!)... it can be done
    > 
    > 
    > 
    >     Best regards,
    >     Ole
    > 
    > 
    > --------------------------------------------------------------------
    > IETF IPv6 working group mailing list
    > ipv6@ietf.org
    > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    > --------------------------------------------------------------------
    > 

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



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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