[Cbor] Cutting down base64 (b64'....') in diagnostic notation examples, before elision

[Carsten Bormann <[e-mail]>]

(1) Random observation, most relevant until we have elision: 

If you randomly truncate a base64 string (no padding), there is only a 1 out of 3 chance (actually 21/64) that the result will still be a base64 string (no padding).  
If you cut it down to a multiple of 4 characters, the result will always be valid.

(2) The current implementation of cbor-diag does not allow comments in b64’…' (https://github.com/cabo/cbor-diag/issues/22).
However, they already work in h’…’ byte strings, so…

h’47110815/.../‘

…or more verbosely…

h’47110815/... (rest of CWT omitted)/‘

…leaves your diagnostic notation parsable (but with truncated values, of course).

Note that an apostroph terminates the byte string prematurely, so don’t use something like...

h’47110815/... (rest of client’s key omitted)/‘

…in your h’…’ comments.

Because of the abovementioned bug, I’d use

b64’A7ii08iS'/... (rest of CWT omitted)/

…for now if b64 is needed (but see note about truncation above).

(Apologies for smartquotes.)

Grüße, Carsten