Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

Simon Hobson <linux@thehobsons.co.uk> Wed, 16 August 2017 19:47 UTC

Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBC0132350 for <v6ops@ietfa.amsl.com>; Wed, 16 Aug 2017 12:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 gPTlkKsBD-Hp for <v6ops@ietfa.amsl.com>; Wed, 16 Aug 2017 12:47:22 -0700 (PDT)
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 5D6A3132143 for <v6ops@ietf.org>; Wed, 16 Aug 2017 12:47:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.137.111] (unknown [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 8B1C31BC37 for <v6ops@ietf.org>; Wed, 16 Aug 2017 19:47:02 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAKD1Yr0uBU-LczaZJ5SdNpb_FpB0qfZJ0kNnr=gEviD+F3DTZw@mail.gmail.com>
Date: Wed, 16 Aug 2017 20:47:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B13F6A0A-BF0A-404B-A332-5A228F4AFC07@thehobsons.co.uk>
References: <CAO42Z2wJBCo1yjguWSy-jzSvndeZTPgtN71FfdEhvqrVAUhZUA@mail.gmail.com> <9bd9f886-f53b-109f-d998-1d4c7adaf3b1@gmail.com> <B6A257C9-7E8A-452D-9C0F-0B10A31990CB@thehobsons.co.uk> <796A0ED0-0F58-43FA-9F81-D4D736A35F3B@steffann.nl> <BD3B4153-2EEF-4BFB-832D-D126A75AEC11@thehobsons.co.uk> <CAN-Dau2jzbQPuE5diEz-XzfRBHY=O1znE8hfy8P-Eee=MVwC_w@mail.gmail.com> <7C6C4FCC-26B9-493D-9992-4663DE6EB9CE@jisc.ac.uk> <3A69468C-98E4-4631-A52F-3D8772646EEE@consulintel.es> <20170807110746.GG45648@Space.Net> <CAO42Z2xXXjKUZ8qQY+b1NgDagX2ZJkqL5gieD+_js59ucp0EMw@mail.gmail.com> <20170810055819.GQ45648@Space.Net> <CAO42Z2xtfsYbw+Wf=ZjyFCmnDbhL17QCkWWRJ7F1+BgGCRiipg@mail.gmail.com> <51268C23-40F4-4476-9025-A1DD3BA37BC3@thehobsons.co.uk> <CAKD1Yr0uBU-LczaZJ5SdNpb_FpB0qfZJ0kNnr=gEviD+F3DTZw@mail.gmail.com>
To: v6ops list <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZMvJNWcdNckeY0uLR0ov_nbpMp8>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 19:47:25 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:


> /64 gives you something that no longer prefix does: the ability to run SLAAC and connect unlimited devices behind the host. 

From previous discussions, I am led to believe that SLAAC will work with other (longer or shorter) prefixes. It is only the deprecated EUI64 method that *needs* 64 bits.


> No. Someone wrote code that gets a prefix via DHCPv6 PD, and blindly announces it in an RA.

Are you suggesting that someone who realises that not everything is a /64 would do that ? You've not really done anything to counter this being a case of "everything is /64" thinking and thus ignoring the potential for anything else. It may be a simple case of blindly re-announcing the prefix you got delegated - but it still comes down to not understanding that the prefix may be other than /64.


> That doesn't work because SLAAC only works with 64-bit IIDs, and for good reason.

As above, I've seen comments here stating that this isn't the case.


> Already? 64 everywhere has been the standard for 20 almost years now. It predates pretty much every IPv6 network and every IPv6 implementation out there today.

And that hardcodes in a restriction which IN THE REAL WORLD is known to cause issues. For example, you (incorrectly) only get a single /64 from upstream, but want to something other than a single host or very simple network. I agree that it shouldn't happen, but in the real world it does - you either stick with a simple basic network, or you run prefixes smaller than a /64.