Re: [Drip] drip-rid-18 - CTA 2063-A encoding changes
Robert Moskowitz <rgm@labs.htt-consult.com> Tue, 29 March 2022 12:22 UTC
Return-Path: <rgm@labs.htt-consult.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 C2D993A1858
for <tm-rid@ietfa.amsl.com>; Tue, 29 Mar 2022 05:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01]
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 83ZEpf4F6MRp for <tm-rid@ietfa.amsl.com>;
Tue, 29 Mar 2022 05:22:29 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147])
(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 3C7973A143D
for <tm-rid@ietf.org>; Tue, 29 Mar 2022 05:22:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by z9m9z.htt-consult.com (Postfix) with ESMTP id 01A9A6256E
for <tm-rid@ietf.org>; Tue, 29 Mar 2022 08:21:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1])
by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024)
with LMTP id 36HQvEhTfh2F for <tm-rid@ietf.org>;
Tue, 29 Mar 2022 08:21:31 -0400 (EDT)
Received: from [192.168.160.11] (unknown [192.168.160.11])
(using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 99D0D6247F
for <tm-rid@ietf.org>; Tue, 29 Mar 2022 08:21:31 -0400 (EDT)
Message-ID: <fa2166e9-927c-3c1b-d96c-1eafb965f198@labs.htt-consult.com>
Date: Tue, 29 Mar 2022 08:22:17 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Content-Language: en-US
From: Robert Moskowitz <rgm@labs.htt-consult.com>
To: "tm-rid@ietf.org" <tm-rid@ietf.org>
References: <bf1e4ef0-66a6-1779-638f-74dd50f7cf31@labs.htt-consult.com>
In-Reply-To: <bf1e4ef0-66a6-1779-638f-74dd50f7cf31@labs.htt-consult.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/1cChsjgjG5Xig3-5k_LbyvbC9BA>
Subject: Re: [Drip] drip-rid-18 - CTA 2063-A encoding changes
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <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: Tue, 29 Mar 2022 12:22:31 -0000
On 3/28/22 08:33, Robert Moskowitz wrote: > I am going through the changes I missed needed since decreasing the > HID to 28 bits. > > Just caught that sec 4.2, CTA 2063-A needs to be reworked. Need 4 > more bits, it MAY be easy, I have not done the work yet, but heads up > on this one... I have time to think more on this. If I stay with the Base32 encoding, I will have to use 2 bits from the 1st character in the Serial Number field. This would work if we reserve values of W,X,Y, and Z (first 3 bits 1s) for that encoding. This approach would allow manufactures to still have 7 possible 14 character encodings under their manufacturing code. (0 - V) I do note, now one 'error' in this section. I say to avoid using 'Z' as it is too similar to '2': "Thus, here a Base32 encoding will be used by also excluding the letters Z and S (too similar to the digits 2 and 5)." Yet then I go and use it to identify HHIT encoded in 2063! "The first character after the Length Code MUST be 'Z', followed by the 14 characters of the encoded HIT Suite ID and ORCHID hash." Argh. Suggestions? Should I thus use V, W, X, and Y to encode 11100, 11101, 11110, and 11111? Or I can use the Base34 encoding and then there is plenty of space in 14 characters for 72 bits. Comments please. I would like to get this done by end of week, and Friday I have 3 grandchildren (and their parents :) ) descending on the house! Won't get too much writing done then as the youngest (5 mo) uses my office for her bedroom. Bob
- [Drip] drip-rid-18 items Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Adam Wiethuechter
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Robert Moskowitz
- Re: [Drip] drip-rid-18 - CTA 2063-A encoding chan… Adam Wiethuechter