Re: Allocation of a Global Prefix (Re: I-D Action: draft-ietf-6man-sids-01.txt)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 19 May 2022 12:56 UTC

Return-Path: <mcr@sandelman.ca>
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 4ABACC16550F for <ipv6@ietfa.amsl.com>; Thu, 19 May 2022 05:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIF0NMLCCbKV for <ipv6@ietfa.amsl.com>; Thu, 19 May 2022 05:56:45 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BC8DC16550B for <ipv6@ietf.org>; Thu, 19 May 2022 05:56:45 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [5.148.108.162]) by relay.sandelman.ca (Postfix) with ESMTPS id 213FE1F479; Thu, 19 May 2022 12:56:41 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 189A51A01EE; Thu, 19 May 2022 08:41:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Erik Kline <ek.ietf@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: Re: Allocation of a Global Prefix (Re: I-D Action: draft-ietf-6man-sids-01.txt)
In-reply-to: <CAMGpriWaXnZbt_oyVm+-mdtDFbPNORa4Ms32EOSJ5zztajnt5g@mail.gmail.com>
References: <165284367846.30321.7356413318207645578@ietfa.amsl.com> <4A75A06F-A65B-40C0-AE17-6BD6B841F9C3@gmail.com> <CA+9kkMCbjSyTx+oNJ9U0HnRkJjCM1JOt+KVh8TSwO67enW5qCQ@mail.gmail.com> <adf6b119-97b7-48de-b03d-5ac96b97b81c@gmail.com> <7C814936-BD91-4A4D-8424-9BB46CA42FDE@gmail.com> <CAMGpriWaXnZbt_oyVm+-mdtDFbPNORa4Ms32EOSJ5zztajnt5g@mail.gmail.com>
Comments: In-reply-to Erik Kline <ek.ietf@gmail.com> message dated "Wed, 18 May 2022 21:13:22 -0700."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 19 May 2022 08:41:43 -0400
Message-ID: <720694.1652964103@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wh4yMsjKVGxAOba7RPwqlJ32OF4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 19 May 2022 12:56:47 -0000

I also think that we should use a new prefix, not try to smash ULA-C into a
different shaped hole.

Erik Kline <ek.ietf@gmail.com> wrote:
    > (no hats) fwiw, I believe the next unicast /16 (for example) working
    > "down" from ULA space would be fbff::/16 (although my reckoning might
    > be wrong).

I think your math is correct.

I can see reasons why asking IANA to allocate out of 2000::/3 could be wrong,
but OTH, the HIP/DRIP people would also like a non-2000::/3 allocation, and
have been pushed into 2001::/23.

from draft-ietf-drip-rid-28

   Address Block:
      IANA is requested to allocate a new 28-bit prefix out of the IANA
      IPv6 Special Purpose Address Block, namely 2001::/23, as per
      [RFC6890] (TBD6, suggested: 2001:30::/28).

So I wonder what would make SIDs different than DRIP RIDs.
Both are unroutable... SIDs are perhaps less aggregatable.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-