Doug Ewell via Unicode wrote in <2A67B4F082F74F8AADF34BA11D885554_at_DougEwell>:
|Steffen Nurpmeso wrote:
|> Base64 is defined in RFC 2045 (Multipurpose Internet Mail Extensions
|> (MIME) Part One: Format of Internet Message Bodies).
|
|Base64 is defined in RFC 4648, "The Base16, Base32, and Base64 Data
|Encodings." RFC 2045 defines a particular implementation of base64,
|specific to transporting Internet mail in a 7-bit environment.
|
|RFC 4648 discusses many of the "higher-level protocol" topics that some
|people are focusing on, such as separating the base64-encoded output
|into lines of length 72 (or other), alternative target code unit sets or
|"alphabets," and padding characters. It would be helpful for everyone to
|read this particular RFC before concluding that these topics have not
|been considered, or that they compromise round-tripping or other
|characteristics of base64.
|
|I had assumed that when Roger asked about "base64 encoding," he was
|asking about the basic definition of base64.
Sure; i have only followed the discussion superficially, and even
though everybody can read RFCs, i felt the necessity to polemicize
against the false however i look at it "MIME actually splits
a binary object into multiple fragments at random positions".
Solely my fault.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
Received on Mon Oct 15 2018 - 11:55:12 CDT
This archive was generated by hypermail 2.2.0 : Mon Oct 15 2018 - 11:55:12 CDT