Re: [Dance] Encoding of the certificate

[Shreyas Zare <[e-mail]>]

Hi,

On 2/8/2023 1:55 PM, Stange, Wolf wrote:
>
> Hello,
>
> I've just discovered DANCE and am really excited about it, because I 
> really like and use DANE already.
>
> However, I've a question:
>
> DANE is using Base16 (hex) for storing the certificate/subpubkey data 
> in the TLSA record - Have there been any thoughts about using base64 
> as the encoding for the data, or even more compact encodings?
>
> You would always need two bytes to represent a byte in base16 (= 
> doubling it), whereas base64 maps every 3 bytes of data to 4 
> characters/bytes. For example, encoding 32 bytes: b16 => 64 bytes; b64 
> => 44 bytes.
>
> I see, that it could make hash comparisons more difficult in some 
> cases (when using a hash matching type (1, 2) and the representation 
> IS already in hex). But for the matching type 0 (full), it COULD still 
> bring an advantage when storing large information in the record, 
> especially in the case of selector 0 (full cert).
>
> Best
>
> Wolf :-)
>
>
The Certificate Associated Data in the TLSA record is in binary when its 
serialized to wire format and only represented in hex form in its text 
presentation format in zone files.

Regards,
*Shreyas Zare*
Technitium <https://technitium.com/>