Hi, Simon,
ABSOLUTELY no one asked my opinion about this, but
I was expecting a short, pithy name for each alphabet that would allow
them to be distinguished. I didn't feel that the whole of the section
title constituted a 'name', whereas some of them have (nearly) got
names: "base32", etc. I think an explicit name like this would help
future protocol designers to refer very precisely to the alphabet in
use.
Oh, I see. I agree. I have added sentences like:
This encoding may be referred to as "base64".
This encoding may be referred to as "base64url".
This encoding may be referred to as "base32".
This encoding may be referred to as "base32hex"
...
See the updated URLs above.
Is this OK?
I really appreciate spec authors who do stuff like this to improve the
usability of our specs. Don't you wish everyone did?
Thanks!
Spencer
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art