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

Simon Hobson <linux@thehobsons.co.uk> Mon, 09 November 2020 12:10 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 D1E823A0D14; Mon, 9 Nov 2020 04:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 XoepKaKwWpiH; Mon, 9 Nov 2020 04:10:43 -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 CB5383A0FF2; Mon, 9 Nov 2020 04:10:42 -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 DCD011A073; Mon, 9 Nov 2020 12:10:36 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
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: <alpine.DEB.2.20.2011091220500.15604@uplift.swm.pp.se>
Date: Mon, 09 Nov 2020 12:10:35 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2347DA8-5935-4BE8-B82A-FB7B5D0B86C9@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> <alpine.DEB.2.20.2011091220500.15604@uplift.swm.pp.se>
To: draft-mishra-6man-variable-slaac@ietf.org, 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wMOA5g5dOHfzk2s0s4AtymdJ4Dk>
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 12:10:45 -0000

Mikael Abrahamsson <swmike=40swm.pp.se@dmarc.ietf.org> wrote:

> We've discussed this before. Let's go that route and give people larger prefixes instead of trying to carve up that poor /64 into smaller pieces.

Perhaps we're simply looking at the problem from the wrong angle ?

Perhaps the right question to be considering is "HOW do we persuade that subset of ISPs that they need to allocate a /56 or /48 ?" It seems to me, that if we can solve that one, then all the rest of the discussion becomes moot.

That's already in the various best practice guides, and has been since ... like forever. But some are either not seeing it, not understanding it, not acting on it as it conflicts with everything they "know" about networking, or just don't see any reason to act on it as it conflicts with their commercial priorities.


I'll put a magic wand on my ${festive_season} list :D