RFC 1521:MIME (Multipurpose Internet Mail Extensio...
RFC-Ref

algorithm


Click on the red underlined text to get to the source

... field imply nothing about the Content-Type other than the algorithm by which it was encoded or the transport system requirements ...
... encodings, in which data are passed through an encoding algorithm multiple times, and must be decoded multiple times in order to be properly viewed. Nested encodings add considerable ...
... arbitrary sequences of octets in a form that need not be humanly readable. The encoding and decoding algorithms are simple, but the encoded data are consistently only about 33 percent larger than the unencoded data. This encoding ...


... user agent must exercise care to choose a unique boundary. The boundary in the example above could have been the result of an algorithm designed to produce boundaries with a very low probability of already existing in the ...
... data to be encapsulated without having to prescan the data. Alternate algorithms might result in more 'readable' boundaries for a recipient with an old user agent, but would require more ...


... character set, and finally transformed via the base64 algorithm into a mail-safe form. ...



Google
Web
RFC-Ref