Re: IPv6 prefix lengths - how long?

Mark Smith <markzzzsmith@gmail.com> Tue, 11 June 2019 04:02 UTC

Return-Path: <markzzzsmith@gmail.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 5A9881200F4 for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 21:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pzKLlz5SKGRd for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 21:02:12 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 44CC712007C for <ipv6@ietf.org>; Mon, 10 Jun 2019 21:02:12 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id x24so10494640otp.7 for <ipv6@ietf.org>; Mon, 10 Jun 2019 21:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Mmbv4r1W+mFVc6WWiVce8822Z+L8ossKF18ByeEkQwg=; b=ZEk063VQ5aQo7CgDqQVjFgeGjKoJq9D7Zz3dYJ+e2A5s+k+ue1vGJ23mT6BFSac8ir wNo5nmRzodIcf1YU0CpqcTgxwdHcRphJqD707z4FJJBhQSotN8nbzbOvci4eDLVuz3A9 +qB3UCBk90bN+K2dZQHJa5p+0yzh2ZU0hV5cXfR+nVuFt96abFEC815UHbAZrUhGtinU jJfG6iXC1XYcSPz9cqUBQNlfs9ULogexTRZDw+S4gVYG+9+uomBvRt9oD0FO6iaedFlv ia3v7u57yJwbBz1tpVB0TKYFlGxvBpc6VEMh3HpczfxJyD8L3RAiLO2qCQfTGkDb66/V 9/KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Mmbv4r1W+mFVc6WWiVce8822Z+L8ossKF18ByeEkQwg=; b=qtL6lWIYWJXkAltDkuKMKHvmK2UdzmViyRyN7vwnfBxkWUx26KQQZdPTL3hHsmi9Mg NabX52+iPesyKXyLRStR4LXiulNI8HFbn75P5H3Txtijz+hLNdKzLBOzDKZR4DqFjTw8 HOcsNHZ7Dwfru9cldlAX+NZYXbQKAbh3Ld9bm7tz/OLmC2NwcrYknZqnyST5Cd21pC2J lFl/SVQ4iv5Sd+LGDhQat1z9EseHfkK8MFD5MDjT9JaiiDpCLEbtvU6UKCNAIS75eTM5 ahpMVRR5RkjuUUSRZ1MOEkR0Vf6akSZzhc2IYSEFpvSQ4KkIJOPjitKqCm5MpmFnENkP e91A==
X-Gm-Message-State: APjAAAVCgn/E3ROKzaHsSeXr9x7raDklAiFybjVcaLlqW5/ATrCBGqBK qa5lwiudT5uBwKXwsBC/t9nxdniMSmgdq3CzwWg=
X-Google-Smtp-Source: APXvYqylQM44Y+ZghSld0CZp9KTfgwA3Cv7Geg3B2Ik7mj0XJE6n2R0nHAOc2eZvOgcasLmZKhkSluZ5GBzHk5H5Stc=
X-Received: by 2002:a9d:65da:: with SMTP id z26mr7229536oth.257.1560225731547; Mon, 10 Jun 2019 21:02:11 -0700 (PDT)
MIME-Version: 1.0
References: <ee811897e2d2438e9c3592012b725ac3@boeing.com> <CAO42Z2xyenxV+z58VW_h4skbWz14hyVt2pUd32tLZ826UoZKZA@mail.gmail.com> <9826C993-3670-4D7B-8709-B3FDE2A79359@gmail.com> <EEBC9697-18A1-41DF-95FB-33D0F5098620@consultant.com> <CABNhwV2fX9LrwzuJX297CoF1XNNM2U=m22QSVWEtaS9PQkM3Dg@mail.gmail.com> <CABNhwV3hA27hmdi4+WfK5ZhNPvta_d9anZA0+TJ2Uuj78kx4Cg@mail.gmail.com> <CABNhwV0rOT461e2Oc0S6e_fK_2zaLQ7Wk5sCFJCFO3xqeH2a9g@mail.gmail.com> <bd98b965334c43969b9f29662e7993b8@boeing.com> <CAO42Z2yz1vZGz0bnhfyOuoqNGcP8RFfgYV0P0LGXW7of5SSzBA@mail.gmail.com> <2df5b0bb7e8e43c594de501b38e9cfef@boeing.com>
In-Reply-To: <2df5b0bb7e8e43c594de501b38e9cfef@boeing.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 11 Jun 2019 14:01:44 +1000
Message-ID: <CAO42Z2wsvS0vOL0s3x60-RS4R3L-3ALvp8=1+5v1RcnkPiZ0Ew@mail.gmail.com>
Subject: Re: IPv6 prefix lengths - how long?
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SY3rSeR1_bkfR6cyE_FEFwtJxyI>
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: Tue, 11 Jun 2019 04:02:14 -0000

On Tue, 11 Jun 2019 at 11:20, Manfredi (US), Albert E
<albert.e.manfredi@boeing.com> wrote:
>
> We’ve been around and around on this. Today’s reality is that households and devices are being provided, in many cases, with only a /64.


It's 33%. Multiple /64s is 57% and the majority. 33% is "many" but not
the majority.

"With regards to what prefix is allocated for customers’ LANs, 22% of
the respondents indicated that they are using a /48, 35% indicated
they are using a /56, 33% a /64 and 10% other sizes (among them, a
/60, a /62, a /57, a /127 and a /128). "

https://blog.apnic.net/2016/11/14/ipv6-deployment-survey-results/


> Therefore, unless the households or devices are happy with a flat address space inside their /64, prefix, they would need to be assigned more /64 prefixes.
>

Customers are going to mostly be happy with a single /64, because most
residential customers have a single Wifi SSID that they plug
everything into. It provides a reliable and mostly error free "plug
in, switch on and it works" experience.

That doesn't mean I think it is okay for ISPs to only give a customer
a single /64. I advocate /48 for all customers for its simplicity - a
single size is much easier to manage and is either right or wrong in
all contexts.

We don't solve the problem of ISPs not giving out multiple /64s by
allowing them to continue to give customers a single /64 and then
allowing it to be further subdivided.

Doing so would be penalising those who've followed the multiple /64s
per site advice - the 57% above - and rewarding those that haven't.

Fundamentally, due to maths, we'd also be spending time solving a
problem that has no objective reason to exist in the first place.


>
>
> In many cases, I’d say universally actually, users prefer to architect their systems as they see fit,

I think you're projecting what you want and like to do onto the
majority of residential users. You're interested in technical things
and a network engineer. You'll enjoy spending your own time on
architecting your home network.

The majority of residential users aren't like you and I.



> without having to involve new requests to their ISPs. IPv4 taught us to appreciate the flexibility of CIDR. IMO, I’d leave it wide open, the prefix length, and many RFCs not related to ULA, link local, or SLAAC already allow this. In fact, even SLAAC can easily be made to accommodate various prefix/IID lengths, if it should ever come to that.
>
>
>
> (Sorry for top posting.)
>
>
>
> Bert
>
>
>
>
>
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Mark Smith
> Sent: Monday, June 10, 2019 20:32
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: 6man WG <ipv6@ietf.org>
> Subject: Re: IPv6 prefix lengths - how long?
>
>
>
>
>
> On Tue., 11 Jun. 2019, 02:54 Templin (US), Fred L, <Fred.L.Templin@boeing.com> wrote:
>
> Two points I pulled out of the many points that were made were that 1) prefixes that are
> overly long can be trivially enumerated by an attacker, and 2) prefixes should be aligned
> on nibble boundaries.
>
> I really resonate with point 1), and with Host Address Availability (RFC7934) we see that
> it is good to allow hosts (nodes) to configure many IPv6 addresses - perhaps even very
> many. I agree with the points that there are already vast numbers of /64s available for
> delegation, and /64 has many nice properties including RFC7934 support and intractable
> address enumeration. But, if we want to go longer than /64
>
>
>
>
>
> Why do we want to go longer than /64?
>
>
>
> The IPv6 address space is 2^96 times, or about 73 billion billion times larger than IPv4s.
>
>
>
> Plenty of people have done the maths to show that we are not going to run out of IPv6 addresses.
>
>
>
> Just a few months ago Brian worked out that every grain of sand on Earth could have its own /64, and from memory, that was just within 2000::/3.
>
>
>
> For a technical field, I'm becoming more and more amazed at how many people trust their intuition completely ("IPv4 ran out in a few decades so IPv6 will too"), rather than saying to themselves, "my intuition may be correct, do the facts support it?".
>
>
>
> It's not engineering if people rely on intuition, because ever now and then things are counter-intuitive.
>
>
>
>
>
> and still satisfy those
> properties, how long would that be - /96?
>
> Point 2) I am not as sure on. Why is it important for prefixes to land on even nibble
> boundaries? I can easily delegate a /63 today for example, and I don't see anything
> wrong with that. Are we saying that that should be disallowed?
>
> Fred
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------