On 02 Oct 2014, at 09:22, Carsten Bormann <[email protected]> wrote: > 6.3.2.x: > The constant repetition of »It is represented as the base64url encoding of > the value's unsigned big endian representation as an octet sequence. > The octet sequence MUST utilize the minimum number of octets to > represent the value.« almost ensures that an implementer will stop > reading the details (well, I did, and I did not write a program to > verify the same phrase is used everywhere; if any parameter were using a > different encoding, that sure would be missed). Why not define > another abstraction like base64url and use this?
Just read Richard’s DISCUSS: > Section 6.3.2.6. > This section defines the wrong parameter. Priceless corroboration. Grüße, Carsten _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
