Re: IPv6 prefix lengths - how long?
Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Sat, 08 June 2019 16:28 UTC
Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 B8641120123 for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 09:28:51 -0700 (PDT)
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 sn_-0ZGsXII7 for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 09:28:49 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EE88120058 for <ipv6@ietf.org>; Sat, 8 Jun 2019 09:28:49 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1hZeCz-0000HkC; Sat, 8 Jun 2019 18:28:45 +0200
Message-Id: <m1hZeCz-0000HkC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: IPv6 prefix lengths - how long?
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.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>
In-reply-to: Your message of "Sat, 8 Jun 2019 11:51:48 -0400 ." <2153986C-8580-4D18-8916-9A2B045BC779@gmail.com>
Date: Sat, 08 Jun 2019 18:28:44 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KAsbfIN13cwEf_E42aAKMuvNTj0>
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 16:28:52 -0000
>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.
- IPv6 prefix lengths - how long? Templin (US), Fred L
- Re: IPv6 prefix lengths - how long? Fred Baker
- Re: IPv6 prefix lengths - how long? Michael Richardson
- Re: IPv6 prefix lengths - how long? Michael Richardson
- Re: IPv6 prefix lengths - how long? Nick Hilliard
- Re: IPv6 prefix lengths - how long? Michael Richardson
- Re: IPv6 prefix lengths - how long? Brian E Carpenter
- Re: IPv6 prefix lengths - how long? David Farmer
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? Philip Homburg
- Re: IPv6 prefix lengths - how long? James R Cutler
- Re: IPv6 prefix lengths - how long? Mark Smith
- Re: IPv6 prefix lengths - how long? Mark Smith
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? James R Cutler
- Re: IPv6 prefix lengths - how long? Mark Smith
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- RE: IPv6 prefix lengths - how long? Templin (US), Fred L
- Re: IPv6 prefix lengths - how long? Yucel Guven
- Re: IPv6 prefix lengths - how long? David Farmer
- Re: IPv6 prefix lengths - how long? Mark Smith
- RE: IPv6 prefix lengths - how long? Manfredi (US), Albert E
- Re: IPv6 prefix lengths - how long? Mark Smith
- Re: IPv6 prefix lengths - how long? Fred Baker
- Re: IPv6 prefix lengths - how long? JORDI PALET MARTINEZ
- Re: IPv6 prefix lengths - how long? JORDI PALET MARTINEZ
- Re: IPv6 prefix lengths - how long? Alexandre Petrescu
- Re: IPv6 prefix lengths - how long? Alexandre Petrescu
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? Gyan Mishra
- Re: IPv6 prefix lengths - how long? Mark Smith
- Re: IPv6 prefix lengths - how long? Mudric, Dusan (Dusan)
- Re: IPv6 prefix lengths - how long? Gyan Mishra