Re: IPv6 prefix lengths - how long?

Fred Baker <fredbaker.ietf@gmail.com> Tue, 11 June 2019 04:51 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 03D33120086 for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 21:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 NLRv1HAybTto for <ipv6@ietfa.amsl.com>; Mon, 10 Jun 2019 21:51:40 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 35EB312002E for <ipv6@ietf.org>; Mon, 10 Jun 2019 21:51:40 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id t16so6593845pfe.11 for <ipv6@ietf.org>; Mon, 10 Jun 2019 21:51:40 -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=YXyZUUdDqCZDEt9qi5rWpsYivmYCj4L8GnxlELq63Vw=; b=n7Zp0u01CI6JYmxoMHy9pd/kOSWce5WBg/F9qffhw7grMwBtLtMBMwwoajQ3rwEatZ KUzJomnPFcj6ZNZ1QWwpp56oHdUNkfEh/IeAA82FyRuxL8SJHP3vNrSYSN4Pu7OiRKgT fZ21VUTroDfp9ynIVXGW8aT7oB/fEjtXofU/wHpRnH8fz6SIDAVNStZsPH4AtzZN9az/ GhrGSqNAkcVBnD1SkF0CfbgzTImaffC3jR0bHBTQCX2KS4HbjBUELQggFpeRYwUNyRQx G1ofnJLmsJ7rYoFwEhRxmUOdhu+RVtZNbqKYNUdYb7YLVs+mc356ElvZg5ggKB+gDpzC 8ODQ==
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=YXyZUUdDqCZDEt9qi5rWpsYivmYCj4L8GnxlELq63Vw=; b=j1fadmjqNW9FItHgDfCUnYlDtIkF8Pog0TbITwJqT3EP3cSOBgPzvmmP1Paka5RmVw IdJPD2fM01JPval6a9K/uT7u5MXHiQdMftTFX3l51iNOXXV0k3qB7N7fuG4q4/Vj/XjW DRcUGi481w1BwIwe+B5839M1L91rh2BOgPlVqrYRuDYVGe2kue15ehBL8edWk6whTrsH y02Q++EZ3NUDXezLdNeqkuibLtc4uvaml/bvhynuPH9HhkLdBpXPT16zqPtvzrFhWjKj ONxEI8Fj7s+WQlix1+sPkZvTjB06UzoJX/ttjzOs7Ly9ZG2pB1e8h/4O27mf27gqihMy Tg3A==
X-Gm-Message-State: APjAAAUl6yOykQfQ94hdfl43bfeXPA8fV6fckCN1NV1NJdG2ZJXtakwx usrNgB9lbyQ2zmFFEzXx1iA=
X-Google-Smtp-Source: APXvYqyMfxulfFEe76jumkBPvrNWx+4YHyI+MXtUCrVMijSscniiBSEzS8SfKt+banLF+XyLOSN4gw==
X-Received: by 2002:a63:306:: with SMTP id 6mr5306152pgd.263.1560228699618; Mon, 10 Jun 2019 21:51:39 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::1008? ([2600:8802:5903:df16::1008]) by smtp.gmail.com with ESMTPSA id c9sm16033596pfn.3.2019.06.10.21.51.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Jun 2019 21:51:38 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <96BC6316-424C-49E5-89FF-1631831E97CC@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1E4D5D2A-27F9-4894-B311-50BAA56F743E"; 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: Mon, 10 Jun 2019 21:51:37 -0700
In-Reply-To: <2df5b0bb7e8e43c594de501b38e9cfef@boeing.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>
To: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
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>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ebNZWcAiTD6LWeo_xBd_zgQnBps>
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:51:42 -0000


> On Jun 10, 2019, at 6:20 PM, 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. 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.

My understanding, from a number of ISP sources, is that the ISP gives the user what s/he asks for. In many cases, that is a /64.

--------------------------------------------------------------------------------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu