Re: IPv6 prefix lengths - how long?

Mark Smith <markzzzsmith@gmail.com> Sun, 09 June 2019 04:00 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 73B2912004D for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 21:00:55 -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 EBjxO-HSlvrn for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 21:00:54 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 10693120136 for <ipv6@ietf.org>; Sat, 8 Jun 2019 21:00:53 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id w196so4072520oie.7 for <ipv6@ietf.org>; Sat, 08 Jun 2019 21:00:53 -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=Jy3N6ZyswJQ/8OIz96Ad+uTMTqwV1qXe9Dk7/gDi5Qc=; b=u63JSszMR8xJkXb+7KqNHjBZA0xWPJRKMTdMKuvD4AOzXpWj0Gis5unRCdfAvJDNU6 VIn9m+mMSPevmLwUko6NbGS67ojgPzqjes1zhWC8aW7ty3AVGevPVjXQ2YUnSv7vs8po 1K0Y8A+dn8kFXPu1x3K3xBVbYUwxWt1rrMaHcUI48vnnhDB0r7zGd9/UHxiy0lRpCLRM dVGyRhg7JREg+8atQs/K7b9rLsQygulvxLvzColufi25AF+KU326eXjlliQpsaiXFVWz 1H8QRUBlme0YI3kQh3fk96YVfdDJ0tNDUPpBv50tAt7p9juuBnxJGME05dF7cZQRvfGt WAmQ==
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=Jy3N6ZyswJQ/8OIz96Ad+uTMTqwV1qXe9Dk7/gDi5Qc=; b=S4i33t9eknB/HAX6HOyQ9JM04BRwMQFN5t4JPCIq4a4/o6jqusg140TEEkFAKFQCne GxwIUrqxHSK5vkiSsFSpRUtKDv1J8IrbLiX8G1+yWI6aHTgD3gHpEnHYTSiMr9XgGdbq TIm5Dj8WJJJ/TEJOT1SMP34iT5WsctW9rBM1gu96wRVESTEa/evEEL67ysKEdvdfmFh/ vHp0WtDce56k5CNUdHzwaMXQma4b1uufksXdlNys3Zt+zXCvfohhDEic9hEDnwlL7tM2 5b/Yver1oaUQMxMjepyOa7Qw0uVvLI3GQPhcjFgzI/B2YbfC6bSxTkmSh0PcrnMo9eXo O5lQ==
X-Gm-Message-State: APjAAAV0PPCdGxkSEnFw30rKLJdYzLtHQ0BnV184VT+5s7Ddk+xN+Y5+ 0xH2OQzDOSDB8U+Sd2dBfuZeXs9HFRGvcpPJIdI=
X-Google-Smtp-Source: APXvYqzJrNDQpdyj8H1CcGgQN2e9NAWg3XT92sqxBCP9ubNm82tlQEXI+xHYIYlyGI78G1HJAB5J3Py5FLkefj1tmHQ=
X-Received: by 2002:aca:c584:: with SMTP id v126mr7399368oif.60.1560052853111; Sat, 08 Jun 2019 21:00:53 -0700 (PDT)
MIME-Version: 1.0
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> <849AC762-6570-4557-92A4-795B6637332F@consultant.com>
In-Reply-To: <849AC762-6570-4557-92A4-795B6637332F@consultant.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 09 Jun 2019 14:00:26 +1000
Message-ID: <CAO42Z2yagfk4ab4Jrd9dMwCqiJRXGNut3GNTQvQWp-ZEVzTwTg@mail.gmail.com>
Subject: Re: IPv6 prefix lengths - how long?
To: James R Cutler <james.cutler@consultant.com>
Cc: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, 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/PfQ7xUYsg-rlBqLNDyaqINtg1vU>
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: Sun, 09 Jun 2019 04:00:56 -0000

On Sun, 9 Jun 2019 at 03:03, James R Cutler <james.cutler@consultant.com> wrote:
>
<snip>
>
> 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.
>

Waste occurs when you get no useful value from something.

As a relevant example, Ethernet addresses are 48 bits, yet when
Ethernet was designed, there was a limit of 1024 nodes on a link. That
means only 10 bits were required to uniquely identify a node.

So what value have those other 38 bits provided in the past 39 years,
and has that been useful value? Or does everybody think those other 38
bits are a waste, because they're strictly not necessary for the
protocol to work?


> 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.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------