Re: [Tm-rid] RAA/HDA - drawing the line in 32 bits

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 22 November 2019 02:42 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220C012012A for <tm-rid@ietfa.amsl.com>; Thu, 21 Nov 2019 18:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 y0U5MKlx8MQ7 for <tm-rid@ietfa.amsl.com>; Thu, 21 Nov 2019 18:42:22 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EE1D12010F for <tm-rid@ietf.org>; Thu, 21 Nov 2019 18:42:21 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:c410:81ff:fe5c:906b]) by relay.sandelman.ca (Postfix) with ESMTPS id 216DD1F450; Fri, 22 Nov 2019 02:42:19 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id BF38DC19; Fri, 22 Nov 2019 10:42:20 +0800 (+08)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tero Kivinen <kivinen@iki.fi>
cc: Robert Moskowitz <rgm@labs.htt-consult.com>, "tm-rid@ietf.org" <tm-rid@ietf.org>
In-reply-to: <24022.14776.836622.11887@fireball.acr.fi>
References: <501e2093-a370-b527-8309-6a42b099123f@labs.htt-consult.com> <24022.14776.836622.11887@fireball.acr.fi>
Comments: In-reply-to Tero Kivinen <kivinen@iki.fi> message dated "Thu, 21 Nov 2019 09:16:08 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 22 Nov 2019 10:42:20 +0800
Message-ID: <18803.1574390540@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/AFPjfvj9Nqu3b43QqBG6EukqBcc>
Subject: Re: [Tm-rid] RAA/HDA - drawing the line in 32 bits
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 02:42:24 -0000

Tero Kivinen <kivinen@iki.fi> wrote:
    >> In draft-moskowitz-hip-hierarchical-hit-01.txt, I use 14 bits (16,384)
    >> for the RAA space and 18 bits (262,144) for HDA within each RAA.  Seems
    >> reasonable enough for me.  Good as any guess about the future.
    >>
    >> Tero Kivinen suggested a soft separation with the HDA in little endian
    >> order.  This way we might have time to figure out where we need more,
    >> RAAs or HDAs.
    >>
    >> Sounds interesting, but I see potential problem(s) if one RAA really
    >> runs up its number of HDAs and thus limits the number of RAAs in total
    >> as a result.

    > I think we should be strict hard limit for RAAs for how many HDAs it
    > can before it needs to come back for asking changing. For example say
    > 12-bits for HDAs and if it looks like there are going to be multiple
    > RAAs running out of 12-bit space, then we can expand it to 16-bit etc.

Given that we don't have to bake this split into end-user software (which was
the problem with IPv4 before CIDR), then I am in favour of this split.
(Clearly the allocation agency needs to know the split)

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