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

"Card, Stu" <stu.card@axenterprize.com> Thu, 21 November 2019 09:55 UTC

Return-Path: <stu.card@axenterprize.com>
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 0B565120A40 for <tm-rid@ietfa.amsl.com>; Thu, 21 Nov 2019 01:55:19 -0800 (PST)
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, HTML_MESSAGE=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 (1024-bit key) header.d=axenterprize.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 ovYVAUXcJaW9 for <tm-rid@ietfa.amsl.com>; Thu, 21 Nov 2019 01:55:17 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 34D4812086B for <tm-rid@ietf.org>; Thu, 21 Nov 2019 01:55:17 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id m5so2703174ilq.0 for <tm-rid@ietf.org>; Thu, 21 Nov 2019 01:55:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axenterprize.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=060uKe0qP7jr4sFImxFLmmeGeoovJYlcl5L8OThi2bA=; b=V+B3gQ7pnutH3kmys7oY8EGQIvTcedQ3YrUWDoCosgO8UL26qmTQs23Mvsi762rOx0 Y1CWmuGgCzCHH1Az/p7G1iW362v7sfod1vqAX4WYgXARfnIhM/stcd4MwZ2L9OgnMUVs yPsj4pazF+luKVeYybn4gAsfrgUVHRyOnMwao=
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=060uKe0qP7jr4sFImxFLmmeGeoovJYlcl5L8OThi2bA=; b=uCtO6mvXVOIuuVeGADeq6bUhd/cOTu7rhiyDUD+PNt4WV/pRktzxP8rBA+mxkTihUB gDwdJdfHJ5XBvQASD3PsLKSxxeGjzpYwRGr7zrOUBjDVxBMsMwLnaOilxi/2bPddpIVn 4xYbHVv6tmYuasJFfd4/i0Ze/xV6mByZNrJGaK0S3XAHaWoQsPJVT8mQHh87PuqMbV+S SAkGXQgM08bCYCV1rnBmNnxKGDNlEsvL2N+WvFgb2BLJIT7YSd4H4S7cu8m0JoB5VzPn mhfRnXRHjM++bRgg6IyTfLtHUvEuXCzeKdWUMqoJkCNUzlfI4SxXZRZwthN2m/w74LLz qawQ==
X-Gm-Message-State: APjAAAWxaiQISJOBC+WyPvBcWhu5BJqGyqdRGDPxOd5rMQ6TXfa60o7T kAZv00y96NRjabfWV3loZDMKuazdMjXFzY7cyUEx5JWo
X-Google-Smtp-Source: APXvYqzTa3+5u8UawhP7PSdKZ7p/2/oHL6R3J5ygqiJRSfj/qJwreMGg5tVDmBI3JUbt8u8V2BgsBS7VArJ+uQRljGg=
X-Received: by 2002:a92:bf0e:: with SMTP id z14mr9081115ilh.80.1574330116322; Thu, 21 Nov 2019 01:55:16 -0800 (PST)
MIME-Version: 1.0
References: <501e2093-a370-b527-8309-6a42b099123f@labs.htt-consult.com> <24022.14776.836622.11887@fireball.acr.fi> <52d38537-5c17-e7de-c684-b2a4719700ae@labs.htt-consult.com>
In-Reply-To: <52d38537-5c17-e7de-c684-b2a4719700ae@labs.htt-consult.com>
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Thu, 21 Nov 2019 17:55:08 +0800
Message-ID: <CAKM0pYPbMg-Lu4fZ5+BCn7m8an8WJQ75QmU3Prh0eUvMycK-uA@mail.gmail.com>
To: Robert Moskowitz <rgm@labs.htt-consult.com>
Cc: Tero Kivinen <kivinen@iki.fi>, tm-rid@ietf.org
Content-Type: multipart/alternative; boundary="00000000000057cb2c0597d84b49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/TpDcfpjQ-F6QeYDU165V2FyC5Lg>
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: Thu, 21 Nov 2019 09:55:19 -0000

I think we need to assume that many commercial UAS operators will use 1
HHIT per flight. Given the large number of UAS & frequency of flights, this
will rapidly consume enough of even a large space that collisions will
rise. So HHITs will need lifetimes & to be reclaimed for re-use.

I know many will pillory me for saying this: maybe claim a HHIT by
appending it in a blinded form to a blockchain? For blinding, I'm thinking
back before Satoshi Nakamoto, to David Chaum's & Stefan Brands' work...
also more recently Jan Camenisch & Anna Lyskayana...

On Thu, Nov 21, 2019, 5:09 PM Robert Moskowitz <rgm@labs.htt-consult.com>
wrote:

>
>
> On 11/21/19 3:16 PM, Tero Kivinen wrote:
>
> Robert Moskowitz writes:
>
> 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.
>
> If it just one RAA getting very large, we can of course give him
> 2nd RAA number.
>
>
> Another item to toss into the mix is an HDA requesting a second or so
> number.  After registering so many HHITs, the collision rate becomes
> 'unacceptable' and the move to a new HDA number for new registrations.
>
> How many deliveries might UPS make a day via UAs?  A new HHIT per delivery
> or only per day?  This could run through a lot of HHITs.
>
> Will some HDAs deprecate expired HHITs and allow reuse or keep the numbers
> around even after they are released by the owner?
>
> All policy issues that will impact the hierarchy space.
>
>
>
> The IPv4 addresses just showed that we can never get the split right
> on the first time...
>
>
> Oh, and the 32bit space will be represented in DNS as nibbles.
>
>
> --
> Robert Moskowitz
> Owner
> HTT Consulting
> C:      248-219-2059
> F:      248-968-2824
> E:      rgm@labs.htt-consult.com
>
> There's no limit to what can be accomplished if it doesn't matter who gets
> the credit
> --
> Tm-rid mailing list
> Tm-rid@ietf.org
> https://www.ietf.org/mailman/listinfo/tm-rid
>