Re: IPv6 prefix lengths - how long?

Fred Baker <fredbaker.ietf@gmail.com> Fri, 07 June 2019 18:10 UTC

Return-Path: <fredbaker.ietf@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 E6C8D1201ED for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 11:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 n2m2Yb8i7_KR for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 11:10:13 -0700 (PDT)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 8B3AD1201A2 for <ipv6@ietf.org>; Fri, 7 Jun 2019 11:10:13 -0700 (PDT)
Received: by mail-pf1-x42b.google.com with SMTP id t16so1609394pfe.11 for <ipv6@ietf.org>; Fri, 07 Jun 2019 11:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=BXzFrjegYOpaNKVpazRA0goSKbG/km1Qr8z6GW/mxew=; b=RXaCD5XNNU6hyuEeH70mY29KTPTdLI4vLtQAfE9/Op5SuwGohQaYVzhmy4OsYyERTc quMyIq/wiRT8fxMhx29GQ9stPowTFdFAWgKdz52eiG0pV0p9ATHte/Moz3eWzzlv/ZOM SOvHPspbinDogE1w8qb6Dtrz1MiOW9o6vovYfATLTMRcjUmjfExgeB7Fb0QcnpNP8xpX u9RLXnTcPXbXhY/O/urO9SkuZb+/wk8leUog2+YDK7r8MtNBKGbcZj4hVvBB8q6ZuqPo URgH4kP1VlKCHTO7QDqnDhgeYE8MsyFTP3KHYLxlKHq0Fzd79y+dTtshVwUSXgQgOtkJ Q8UQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=BXzFrjegYOpaNKVpazRA0goSKbG/km1Qr8z6GW/mxew=; b=OS2stcCcapRdipsTR9EzoUaRek9iDBSzNE7qeaxSpuOYi78UTTsEU5KgbAmB0+pjvo TbrBRAqmddT++DVRF14Z7RxtTDh/4JxoVR/gJiNX8hbhoIcvhqDPjIV+PH4XZ2eQpYVH CkIszG4mRs7VD5sxHCtr/QmDoLefrnp5XMLtujrZxYXcEp0KvhsiZLXadS5q+Kbt0xz/ WB2DDVKQPhRxmSWgboqcUlZoVP++699y2QJkD2gJ4bCuhbAqiy38VQZCkGzQLFC4AH5j /u3yxQg9aMAj59ZYj2MfgiPgBoWbvzkxgBIbdI2y7vKtwydLkrO1hIG6mvFkdG6dhlY1 qozg==
X-Gm-Message-State: APjAAAUuov92vLPUtmI9LSKVS1XFcWcjOLt93RaOzuK0LvAGfHnGodPI 9guqznFl8MKo+vTJgnjRbgk=
X-Google-Smtp-Source: APXvYqyMxB77E6umYMS5X9EQeEJDqP7VjJZT/DbJTmRWJQ2ZWfBiy5cGbAhHrGQt/9kO9YwyXyG4xQ==
X-Received: by 2002:aa7:9190:: with SMTP id x16mr47623239pfa.86.1559931013024; Fri, 07 Jun 2019 11:10:13 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::1006? ([2600:8802:5903:df16::1006]) by smtp.gmail.com with ESMTPSA id t187sm3274785pfb.64.2019.06.07.11.10.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 11:10:12 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <F971D5DA-9523-4B9A-A34C-161A73FB2B50@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_EB73C4E0-C396-45BF-82C1-6C6C54B413EB"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: IPv6 prefix lengths - how long?
Date: Fri, 07 Jun 2019 11:10:11 -0700
In-Reply-To: <ee811897e2d2438e9c3592012b725ac3@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
To: Fred Templin <Fred.L.Templin@boeing.com>
References: <ee811897e2d2438e9c3592012b725ac3@boeing.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AeMWWDacJSyqv0jLwTZ9i96viGQ>
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: Fri, 07 Jun 2019 18:10:29 -0000

From my perspective, there is no requirement that there be a single prefix. You could have 128 prefixes, each with 8 addresses in use. I'm not sure why you would, but I don't see an architectural reason that you couldn't. You just wouldn't be using SLAAC to assign them.

From my perspective, if a platform contains some number of internal objects (VMs, containers, applications, whatever) that each get one or more addresses, I'd be hard pressed to make a general statement about the platform. If it needs to support 10,000 VMs-or-whatever, I guess it needs to support at least 10,000 addresses. If they are all packaged up into one prefix, that's going to be a /112 prefix at least, and the platform had best support it.

It's not really a technical requirement that all platforms have to support. It's a market requirement, and the platform in question is being designed to meet that market.

> On Jun 7, 2019, at 10:43 AM, 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”?
> 
> We all know about /127 for point to point links, but I am not talking about those. I am
> talking about prefixes that are assigned to nodes that might be acting either as routers
> or as multi-addressed hosts.
> 
> 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.
> 
> Thoughts?
> 
> Fred
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------------------
The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume...