Re: IPv6 prefix lengths - how long?

Mark Smith <markzzzsmith@gmail.com> Sun, 09 June 2019 03:20 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 2DE411200EC for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 20:20:49 -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 AaItSBfbSYKy for <ipv6@ietfa.amsl.com>; Sat, 8 Jun 2019 20:20:47 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 82C8112004D for <ipv6@ietf.org>; Sat, 8 Jun 2019 20:20:47 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id q186so4079242oia.0 for <ipv6@ietf.org>; Sat, 08 Jun 2019 20:20:47 -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=vjvoUSmsc5ypMCmx0OeK6mLsVl1qSeyDmO6KCb7Jkck=; b=hletRIGRI/WE6BAZRbagXhwclRHS5VgkurtPXRdgtsWjaU6xa7T0I9sUsAbEDzjqu4 wDUMBMXc9DwyQOiMd3uEvtWKXH2x34Iqug49Ol38wrzW+jnW6COYLDRV3mQaeAvbLwrz FLyhX0GORphONaqqeEit5qcRAVAR8eCk0twwtOf9Bgdt35hz8lPO28wkksIxCDcCm3eu 8xZH1LmcObD/h08JJSsWE9XB8ZYeJQh6yedqFnot5n91jivE/IMLvMaEXWGg+hwt5fHv RbkWV4ADzozKTcZV4MkDfkJiBLkU4JwQeO6EHw3nj5l7U3Cznhz30p05gK74tLb7fnoA pzzA==
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=vjvoUSmsc5ypMCmx0OeK6mLsVl1qSeyDmO6KCb7Jkck=; b=bP7zvTCD34yiCz59KiDXjMqW6dSez7/dIjs2Um9XANUEiqdewLwr43gwfjGGP/4Ufg e/s/gWjgg78R21ZxUKbABp/IZjTn54cB3u6fr5BzgWfkpjA2D2VNpkokKjSDOEi3EyU6 u9rwPRa9E38b4X0mE26R4FGkAduBRWzccLFI/xDTN48i/6l0gn48Ui3r2oE58/20DHf8 cnoYPhIBekg4ETLRapYYj83XqHFdAENNmf/WXi5oD0nvbHXu0+4b2TjGFUBwdbp6h/IN NUeB0u8rBvQiwFQdsr4VusqysXiYZTgq3ehBZhu3HrVjt4UmkBWRDQWpUP8yfPYM21Gj FvsQ==
X-Gm-Message-State: APjAAAV8HZRTD1UPFwkya7ikZjNcgsqINxGifyepmlyQU6uOt8C3GndX zgjty8XXAaJ/epB7D9EiSMkxX0TIZVgeco3VjAQ=
X-Google-Smtp-Source: APXvYqyn/VsZZAC3k19prWAPE0HMrG2jPOaSdG1PVn/uYC7/6PEpY3URjaE/lsf0HKRoP/MfW1Fn15DhQEBQtwGd9MA=
X-Received: by 2002:aca:c584:: with SMTP id v126mr7337733oif.60.1560050446716; Sat, 08 Jun 2019 20:20:46 -0700 (PDT)
MIME-Version: 1.0
References: <ee811897e2d2438e9c3592012b725ac3@boeing.com>
In-Reply-To: <ee811897e2d2438e9c3592012b725ac3@boeing.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 09 Jun 2019 13:20:20 +1000
Message-ID: <CAO42Z2xyenxV+z58VW_h4skbWz14hyVt2pUd32tLZ826UoZKZA@mail.gmail.com>
Subject: Re: IPv6 prefix lengths - how long?
To: "Templin (US), Fred L" <Fred.L.Templin@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/j0-uaamGkyVDsf7by7pMiOTn9jQ>
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 03:20:49 -0000

Hi Fred,

On Sat, 8 Jun 2019 at 03:44, Templin (US), Fred L
<Fred.L.Templin@boeing.com> wrote:
>
> Hi, we all know about the tussle regarding the /64 boundary for IPv6 prefixes but
>
> assuming that we will one day want to allow longer prefixes the question is “how long”?
>
>
>

<snip>

>
>
> Because of RFC7934, we see the value of Host Address Availability Recommendations.
>
> It makes the point that, due to the nature of multi-addressing supported by IPv6, it
>
> would be useful for each node to be able to configure multiple (perhaps even many)
>
> IPv6 addresses from an IPv6 prefix. But, “how many”?
>
>
>
> My assertion is that a multi-addressed host (or, an End User Network router) should
>
> support numbering for at least 1K IPv6 addresses. This would imply that (assuming
>
> at some point the /64 boundary is relaxed) the longest IPv6 prefix should be a /118.
>
>

I think we really need to work out what a host is first.

Is it the physical device? Virtual hosts within a physical device?
Individual applications? Threads or processes within applications?


"On Many Addresses per Host", S. Bellovin
https://tools.ietf.org/html/rfc1681


"Transient Addressing for Related Processes: Improved Firewalling by
Using IPV6 and Multiple Addresses per Host", Peter M. Gleitz, Steven
M. Bellovin
https://www.cs.columbia.edu/~smb/papers/tarp/tarp.html


"node" is probably better to use to describe a network attached entity
that needs one or more addresses to be able to send or receive
packets.

The number of addresses a node needs depends on what it is, what it is
doing and how it is going to use its addresses. In some cases 1K would
be excessive for a node, for others it could be far too little.

As others have said, there can be other properties of addresses, such
as privacy, security, and plug-and-play operation. As an example, the
choice in 1980 of 48 bit Ethernet addresses, rather than just 10 bit
addresses as originally required to suit a maximum of 1024 nodes on a
link, has paid off immensely for nearly 40 years.

"Too many" addresses for a node, to the point where the unit of
allocation starts to cost something where the cost is worth worrying
about, is a much better answer than not enough.

I'd say that cost threshold is at /64 today (e.g. RFC 8273, "Unique
IPv6 Prefix per Host"), also placing value on it being the minimum
link allocation convention we've had for more than 20 years (since RFC
2373), and that there is more than approximately 3/4 of the total IPv6
address space unallocated for any purpose at all.


Regards,
Mark.










>
> Thoughts?
>
>
>
> Fred
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------