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

Simon Hobson <linux@thehobsons.co.uk> Mon, 09 November 2020 17:31 UTC

Return-Path: <linux@thehobsons.co.uk>
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 95BA43A128A for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 S5ULoz8jsjux for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 09:31:26 -0800 (PST)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F01013A1289 for <ipv6@ietf.org>; Mon, 9 Nov 2020 09:31:03 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.137.104] (unknown [192.168.137.104]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id C2C5C1A073 for <ipv6@ietf.org>; Mon, 9 Nov 2020 17:30:59 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAD6AjGTLdFPSmUKUHUSS6rf4ewiteoa27D-zK3amyGvo7sWswQ@mail.gmail.com>
Date: Mon, 09 Nov 2020 17:30:58 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA2D0B4E-EF9D-41D8-B127-599A6ADF9855@thehobsons.co.uk>
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>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/IkX0UiszRjbfN2vBxPzvL7-HKAg>
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:31:28 -0000

Ca By <cb.list6@gmail.com> wrote:

> Dhcpv6 is not. Has not. Will not.

That's a bold statement. "is not, has not" may well be correct, but I fail to see why "will not" is a valid statement other than for vested interests deciding to nobble it. Reading some bits of the discussion, it sounds a bit like locking a horse in it's stable and then complaining that it didn't finish the race !

> I am a mobile operator and i want the ietf’s help to provide < /64 prefixes to my users. I want to give them more ipv6 space. Help me focus the conversation on how to engineer better methods to deploy larger blocks of space. 

OK, that probably deserves a new thread - it's almost completely orthogonal to the original question of splitting a single /64 to make multiple networks.
What specifically is stopping you from doing that now, with the tools available ?

TBH, the technicalities have gone beyond what I've learned, but I've seen talk in this thread (thread of threads) suggesting that it's supported by the mobile standards (3GPP ?) but it's just that some operators are stuck in an "everything is a /64" mindset. I get the impression that there are people in here that do have the in depth knowledge of how to do it. I do suspect that it may also depend on what kit you currently have in your network.

Simon