Hi Brian, you are entirely correct. I believe I read the paragraph not carefully enough. For some reason I read octal rather than octet and that makes, of course, a huge difference.
Sorry. My fault. Ciao Hannes On 04/25/2014 04:22 PM, Brian Campbell wrote: > Note that the draft is showing an *octet sequence* with each individual > octet being shown as decimal value. It doesn't state anything about > using octal, the base-8 number system. Those octets also show > unambiguously what is being base64url encoded (including the line > endings via "13, 10") - no matter how the unencoded headers or bodies > are shown in the draft, there's going to be potential confusion about > what white space and line breaks is or is not to be included in the > encoding and serialization so giving the octet sequence alleviates that. > It's maybe also worth noting that the JOSE suite of specs all use the > same notation and text in their examples.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
