Re: [Drip] drip-rid-18 - CTA 2063-A encoding changes

[Robert Moskowitz <[e-mail]>]

One vote for Base34 encoding.  And a heavy 1 vote as Adam writes code!

On 3/29/22 11:19, Adam Wiethuechter wrote:
> For whatever reason Outlook hates how you respond in these email 
> threads and it's a jumbled mess for me to view.

I always hated Outlook....


>
> But to clarify CTA encoding is broken and we need to fix it to fit the 
> new 8-bit Suite ID. 'Z' is a letter that is unusable and was a general 
> oversight that we still used it.

I should have caught my mis-use of 'Z' earlier and used 'Y' instead.  
Moving to Base34 means it can stay as 'Z'.

>
> I personally prefer the simple approach of using a Base34 encoding 
> into 14 characters so that the first character can remain in use for 
> the indicator of a DRIP Serial Number.
>
> Allocating multiple characters to signal use seems overly complex and 
> limits standard use of the Serial Number's max characters.
>
> --------
> 73,
> Adam T. Wiethuechter
> Software Engineer; AX Enterprize, LLC
> ------------------------------------------------------------------------
> *From:* Tm-rid <[e-mail]> on behalf of Robert Moskowitz 
> <[e-mail]>
> *Sent:* Tuesday, March 29, 2022 9:10 AM
> *To:* [e-mail] <[e-mail]>
> *Subject:* Re: [Drip] drip-rid-18 - CTA 2063-A encoding changes
> ARGH!!!!
>
> I need a nap....
>
> 2^5 - 2^2 = 28.
>
> Sigh.
>
> Signing off for an hour.  Too short of a night.  Us septarians 
> (speeling ? 70-year olds :) ) need our sleep....
>
> On 3/29/22 09:06, Robert Moskowitz wrote:
>> OOPs.  One small correction.
>>
>> The manufacturer can have 24 SN encodings in the Base32 approach as 
>> 2^5 - 2^3 is 24.
>>
>> On 3/29/22 08:22, Robert Moskowitz wrote:
>>>
>>>
>>> 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
>>>
>>
>
> -- 
> Robert Moskowitz
> Owner
> HTT Consulting
> C: 248-219-2059
> F: 248-968-2824
> E: [e-mail] <mailto:[e-mail]>
>
> There's no limit to what can be accomplished if it doesn't matter who 
> gets the credit
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:[e-mail]

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit