Re: IPv6 prefix lengths - how long?

David Farmer <farmer@umn.edu> Fri, 07 June 2019 21:23 UTC

Return-Path: <farmer@umn.edu>
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 54308120161 for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 14:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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=umn.edu
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 yCV8NU3mVZQl for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2019 14:23:33 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 338601200B2 for <ipv6@ietf.org>; Fri, 7 Jun 2019 14:23:33 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id AA4D584D for <ipv6@ietf.org>; Fri, 7 Jun 2019 21:23:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CSLzrMciIaQz for <ipv6@ietf.org>; Fri, 7 Jun 2019 16:23:32 -0500 (CDT)
Received: from mail-vk1-f197.google.com (mail-vk1-f197.google.com [209.85.221.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 6678DD1A for <ipv6@ietf.org>; Fri, 7 Jun 2019 16:23:32 -0500 (CDT)
Received: by mail-vk1-f197.google.com with SMTP id 129so1236847vkh.15 for <ipv6@ietf.org>; Fri, 07 Jun 2019 14:23:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YYhCAscAQed2LntU/9eqRLs1yU5GSKH+umnKleA3Wpc=; b=nBRL0IZnAKoaQREwl74mN7NEXfO3wrM1XFn2fOcAjNI+cNOVY/wQmkmbHqIKRU/8nX AbXzoaz1DfYplBwDgbc2kmD/8hceiYYgrLKeQGSrd6T7ZRQsh7wdRmwINMNsbfm0N3WZ hhczgHSv9oxqiKGf4ekAjDAG0t2FUvTvXTn8L1sq3Rm/JEtWFAVJ80mk7g6Xml/+WrW6 dQtFVGrtKC/vOO86Xi8nylYet0UzCf+VhPNuTXDdHdv0Yk3/5hnDNaZfo24CVVfVHDqC kIKHbbtouJw2qrMAfHvF9bPZ7EtJY/mtu2BsMpYtZWCwRqGg3ccM8QmFykV/h2HWP+lN ckNg==
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; bh=YYhCAscAQed2LntU/9eqRLs1yU5GSKH+umnKleA3Wpc=; b=AozM6R/lubKZZg4Hrs6m1Tb9Q6Rls31FdxEGIHabNddV0BDCcFdQ+hySpCStf8wSd2 nWCPNdc4sH2kyQYOrZr4uwHtSJwJDk9V9hKj9hOZluSvMz3iVj2vvSUf651QKgoAGqFK /oI6KliMwPeGlqQ+/WCIgfZpkdEbRuD9NBSbe61uhu15eG8zfusI0deZTRV3GnTwtPra AJf4WOE18Sy7AyE3XFDg5Kgg5TVTDOnmRMAXEJqjyCjMWyZ4fLpzadrSKf90UMZKS7Vx zU/prDTBjDcRc8qw15+fu9m715eRxLVVpW2Lybg6iaIIbaBFe9pUnH6odm7dNbRmaT7I UZGQ==
X-Gm-Message-State: APjAAAU7qxrgJeXC7NFeMiuFEz4gCFWikCYEKNKv+L3Sc64SW4eABcBn B/eRr0oNzRxuv+gegaJovSPoLWrolfJMaZQeB51iHQB7tQBeNRZe6JhkVsZfEEDOSTDlbFQsLTY vsBHf6MistrZZ3/4zrGktY6PV
X-Received: by 2002:a67:790d:: with SMTP id u13mr17550654vsc.86.1559942611101; Fri, 07 Jun 2019 14:23:31 -0700 (PDT)
X-Google-Smtp-Source: APXvYqyjYI0zuFfo0P/4to5MqCPAAyEUjZ6lqSB4Lf+wJ6JBjPde5UJzkHxmH/oRuxfowL8JtKAP9Jy43pXXF+BoTVY=
X-Received: by 2002:a67:790d:: with SMTP id u13mr17550632vsc.86.1559942610599; Fri, 07 Jun 2019 14:23:30 -0700 (PDT)
MIME-Version: 1.0
References: <ee811897e2d2438e9c3592012b725ac3@boeing.com> <1ce85ce8-9844-27bd-30b4-a0b07bdaaccb@gmail.com>
In-Reply-To: <1ce85ce8-9844-27bd-30b4-a0b07bdaaccb@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Fri, 07 Jun 2019 16:23:14 -0500
Message-ID: <CAN-Dau3zM6V-WzTwhAMVdZ1brx0rU0Uc9zjgg9xQfR2X=2WvGA@mail.gmail.com>
Subject: Re: IPv6 prefix lengths - how long?
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002cd563058ac2717a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HRkUV9aV1gOTdlBD0pTmLXDrcFc>
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 21:23:35 -0000

I mostly agree with Brian, other than that are many advantages to alignment
on nibble boundaries with the hexadecimal representation of IPv6 addresses.
So, any of the 16 nibble aligned options seem fine with me; /64, /68, /72,
/76, /80, /84, /88, /92, /96, /100, /104, /108, /112, /116, /120, /124. So,
personally, I would argue against /118 on that principle.

Thanks.

On Fri, Jun 7, 2019 at 3:53 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> I can't speak for the other authors of draft-bourbaki-6man-classless-ipv6,
> but my answer is: this question isn't our business. If we disestablish
> the /64 boundary, we surely don't replace it with a new one.
>
> Privacy considerations are probably a determining factor, as we
> hinted in https://tools.ietf.org/html/rfc7421#section-4.5
>
> Regards
>    Brian
>
> On 08-Jun-19 05:43, Templin (US), Fred L 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
> > --------------------------------------------------------------------
> >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================