Closed cabo closed 4 months ago
I’d like to ask that the draft explicitly say that .b4u and .b4c accept only their respective alphabets. RFC 4648 only really says how to encode, not what decoders should do B64 decoders out there widely accept both; What .b64u and .b64c do here is far from the norm (but I like it) This draft is a specification that we expect other cddl tool implementors to follow so it should be clear It would also be helpful for CDDL-using document authors like me to not have to go read and interpret RFC 4648.
I’d like to ask that the draft explicitly say that .b4u and .b4c accept only their respective alphabets.
It would also be helpful for CDDL-using document authors like me to not have to go read and interpret RFC 4648.
(Laurence Lundblade in https://mailarchive.ietf.org/arch/msg/cbor/u5JGioIgCdtxEKs8k2MtSgCIH9w.)
(Laurence Lundblade in https://mailarchive.ietf.org/arch/msg/cbor/u5JGioIgCdtxEKs8k2MtSgCIH9w.)