Re: IPv6 prefix lengths - how long?

James R Cutler <james.cutler@consultant.com> Sat, 08 June 2019 17:02 UTC

Return-Path: <james.cutler@consultant.com>
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 30F24120131 for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 10:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mail.com
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 ZvfkkcRPV5oZ for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 10:02:55 -0700 (PDT)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAB70120073 for <ipv6@ietf.org>; Sat, 8 Jun 2019 10:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.com; s=dbd5af2cbaf7; t=1560013364; bh=iSQq4g+FNLBUJBi4Gg+e5JcUH+jQ+1FClcG/xePwvRQ=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=fLxiJxcEJkV4kGNX62hSt6YfFVXCezRxdKyUW2jpDjWVLVQFJ+ols5eM4QMrFEJAK 84UmI7/HCTLjbtyq60jpQNOK4RX0B468V7EfO099hguTnBsbNstwn6kH/wgAQ/IfIh NqmZpC0WrJwaNIViTCSXycGRuet9bgtTq7lSp5bE=
X-UI-Sender-Class: 214d933f-fd2f-45c7-a636-f5d79ae31a79
Received: from maxijim.local ([68.55.30.51]) by mail.gmx.com (mrgmxus001 [74.208.5.15]) with ESMTPSA (Nemesis) id 0McVXi-1hHzMa1IX2-00Hgqy; Sat, 08 Jun 2019 19:02:44 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: IPv6 prefix lengths - how long?
From: James R Cutler <james.cutler@consultant.com>
In-Reply-To: <m1hZeCz-0000HkC@stereo.hq.phicoh.net>
Date: Sat, 08 Jun 2019 13:02:36 -0400
Cc: ipv6@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <849AC762-6570-4557-92A4-795B6637332F@consultant.com>
References: <ee811897e2d2438e9c3592012b725ac3@boeing.com> <1ce85ce8-9844-27bd-30b4-a0b07bdaaccb@gmail.com> <CAN-Dau3zM6V-WzTwhAMVdZ1brx0rU0Uc9zjgg9xQfR2X=2WvGA@mail.gmail.com> <2153986C-8580-4D18-8916-9A2B045BC779@gmail.com> <m1hZeCz-0000HkC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Provags-ID: V03:K1:MvjWJjkiDOT5pAlHZL5X7Txc1GxPbI6A320LdNX37gRnHjrhnO7 tvmL2qdH61QdWYNCjDDrBmgkyQxfxEqKMofR3Hy1dNuF/xBHkAOw1rLc6ztOSQvkLlHC6NA rkD7toZGYnUG4uP7sa+gzEfuwt49aAwVH2TuAp5mpU8lqMueS6WN1c9O3LBSZZYyq3l2y+r qZo6SyzOS69Z5hJLom39A==
X-UI-Out-Filterresults: notjunk:1;V03:K0:hgfV+1mc3FU=:UDFpe7bxQAPudOgc3tRvbr Ms6goOLICvukBIkHxQZlMNup9T4YJfjL9JxM1iv7dJEzvW55+zv+GeMtAYd6P69sb2kJVkFsX jmTT2IYTnuLBAmxP/wPcY3EFplKoSPavb1ODwKRWRFZz/Pg9xZoURakXbQMmWVSexv2VCajVl QoI0Xa8gZ4LjvdIjjrcKT0WAEbE8h386EqwcjDQd1wQdlw2nhruxCDZwofWEUKbhXUQnIhzOo lK2cAWXvGZnh33scccSaR0ndKve1ycQENWYlpHIrVda/bcjRDQnt13Pd8P8Kf892opRMpbGHl 9Cd7rcevRh2zlSmaC52Iw05jSExab0Nrc33A1vHcTp5Sj3ZwM1R6PvBjpAlkechcAu8oEXVWb 9B099tlDmAwBjByXbGDyNnEOkK8pECBwMb3KBYXCmzYkh5O0btPowv0BTEo7uR9JX4epuw+Rz WykeZBiA2JAeu2S2PkZkK9J+NbdU6HlFGLUQFW5l43Y8S6LTiOTWNyOv58sTtPrebktLrcV8E DZbDbBw2mDSfyPz8216HedGP7tGbfVM7YxfvCCpmHMQtnctc/ktB26vj1AQ2WCc3VtqeBWTtN N4n3urwopokRmiO9BiUI+RqVm+SDhulk9uX5e80i6n2GaDn/cij/UNXuloKTC3iG7biigAIXX /xBf31tL/kGu10UsdG72ZneHql9bGRq1jlPOlU+O5+oGnAcLdZfcwwq38R6yXdFdwCDCl8yzb 0pflIEGfe4nyfoPVf4xfGm38PnQn23wUmP8zpQK2/JkyUxQpXGnyIQu/5zeCLQuU6KrdXirQ6 SzRjUm5M1bpRAS1WHrGmBabrrVJelr9m/iMY8jtFS6RP9Nbm+U5pgKDqChrZNIqItJACTHQdA CRvd3sxry9MHInhfTzVkUr1S7rjZfIF/9kVDbl5kCbt3UWw7ran3JjsXAszdArRSviF8N2xuN TokY4FdAeaHXi0lS8iMtFLlc6ypmWNz3TeitAXe3i/Orjty9zPSpG
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tkeyHVXwzJ7XlkP2CBMnRbDm1Qc>
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: Sat, 08 Jun 2019 17:02:57 -0000

> On Jun 8, 2019, at 12:28 PM, Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> wrote:
> 
>> The RFC 4291 IPv6 addressing and the original stance on 64bit boundary was bas
>> ed on the EUI64 format for the Mac generated FFFE bit stiff between the 3rd an
>> d 4th octet of the station id or random station id.
>> 
>> I agree that a 64bit station id was overkill and was made 20 years ago thinkin
>> g futuristically that every physical device you can think of would have an IP 
>> but now in reality large in my opinion that would never be used and really was
>> ted valuable bits on a station Id that could have been used more wisely to exp
>> and the prefix length.
> 
> With SLAAC, EUI64 has to some extent been replaced with pseudo-random 
> numbers.
> 
> For that to work, the number of bits needs to be sufficient to avoid
> collisions. The exact number of bits you need depends on the number of
> addresses on a subnet and how much you care about the damage done by
> collisions.
> 
> The problem is that we know that a 64 bit pseudo-random number is safe,
> but there is no sensible way to set a lower bound. There certainly is
> no consensus on a lower bound.
> 
> At the same time, we are not running out /64 prefixes. We have prefix
> allocation problem. We have enough /64s to give every virtual subnet its
> own /64.
> 
> So the obvious thing to do is to leave the 64 bit boundary in place for SLAAC.
> 
> If you really need longer prefixes, then just use static configuration or
> DHCPv6.
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> ——————————————————————————————————


I have difficulty considering the use of a 64 bit as a “waste" because it:
1. Has not been shown to create a resource shortage in the foreseeable future.
2. It is a “safe” size for a pseudo-random space as far as we know.
3. As Philip Homburg stated, we have no proof for a minimum size space.

I consider the effort and confusion involved in modification away from 64 bit Station IDs to be a waste (SLAAC, anyone?). 

I would rather see the effort put into better solutions security problems, including name to address resolution and routing.