The current encoding depends on the issuers public key algorithm which may not be known when processing the CBOR certificate. I will change the encoding to say that r and s are padded so they have equal length instead. This is actually simpler to implement as well. No practical affects on size of the encoding. With a probablility of 2^-16 it will save a couple of bytes or more.
emanjon
commented
3 years ago
The current encoding depends on the issuers public key algorithm which may not be known when processing the CBOR certificate. I will change the encoding to say that r and s are padded so they have equal length instead. This is actually simpler to implement as well. No practical affects on size of the encoding. With a probablility of 2^-16 it will save a couple of bytes or more.