[Dance] Encoding of the certificate

["Stange, Wolf" <[e-mail]>]

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 :-)


________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com