Simon St.Laurent wrote:
> Base64 encoding has a new home.
> URL: ftp://ftp.rfc-editor.org/in-notes/rfc3548.txt
Unfortunately that document is pretty crappy, and we are better off with
the current practice of referencing MIME.
1. It defines an "alternate" base 64 mechanism with similar name but a
different character set. This will be confusing, especially since it
says "should not" and not "SHOULD not" (or even better "MUST NOT") be
represented as base64.
2. It should have said "ignore whitespace", rather than encouraging
output to be a single long line by default.
/r$
--
Rich Salz, Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
