>> can you please rename the production to something which is clearly not a >> base64 string.
> HTTPbis describes the production as: > > "The "b64token" syntax allows the 66 unreserved URI characters > ([RFC3986]), plus a few others, so that it can hold a base64, base64url > (URL and filename safe alphabet), base32, or base16 (hex) encoding, > with > or without padding, but excluding whitespace ([RFC4648])." -- > <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p7-auth- > 20.html#rfc.section.2.1.p.4> > > I think that's sufficiently clear, and "b64token" is actually a good > name for that ABNF production. The *text* is clear, but Alexey isn't the first (or last) person see the label "b64token" and assume it always holds a base64-encoding. How about renaming the production to "token68", reflecting the fact that it supports an alphabet of 68 characters (plus equal signs at the end)? -- James Manger _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
