[jdev] base64 line endings

Peter Saint-Andre stpeter at jabber.org
Mon Apr 17 11:32:37 CDT 2006

Hash: SHA1

Peter Saint-Andre wrote:
> I'll add this to my open issues list for JEP-0084...
> Norman Rasmussen wrote:
>>> It seems that JEP-0084 is inadvertently conflicting with itself by
>>> saying that data must be encoded the RFC 3548 way, and not explicitly
>>> allowing line feeds.
>>> So something to add to JEP-0084 v0.8 would be to explicitly allow line feeds.
>>> JEP-0084: User Avatar refers to RFC 3548 (The Base16, Base32, and
>>> Base64 Data Encodings), and in Section 2.1 it says:
>>>    Implementations MUST NOT not add line feeds to base encoded data
>>>    unless the specification referring to this document explicitly
>>>    directs base encoders to add line feeds after a specific number of
>>>    characters.
>>> In  XML Schemas (http://www.w3.org/TR/xmlschema-2/#base64Binary) it says:
>>>    For compatibility with older mail gateways, [RFC 2045] suggests
>>> that base64 data should have lines limited to at most 76 characters in
>>> length. This line-length limitation is not mandated in the lexical
>>> forms of base64Binary data and must not be enforced by XML Schema
>>> processors.

Oh, and BTW, we are not interacting with older email gateways... :-)


- --
Peter Saint-Andre
Jabber Software Foundation

Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20060417/36aef57c/attachment-0002.bin>

More information about the JDev mailing list