Implementations MUST include appropriate pad characters at the end ofĮncoded data unless the specification referring to this documentĢ.3. Size of transported data cannot be made, padding is required to yield In some circumstances, the use of padding ("=") in base encoded data RFC 3548 The Base16, Base32, and Base64 Data Encodings July 2003 2.2. Unless the specification referring to this document explicitlyĭirects base encoders to add line feeds after a specific number of Implementations MUST NOT not add line feeds to base encoded data The MIME and PEM limits are both due to limits within "virtually identical", however PEM uses a line length of 64Ĭharacters. MIME inherits the encoding from PEM stating it is As such, MIMEĮnforces a limit on line length of base 64 encoded data to 76Ĭharacters.
MIME does not define "base 64" per se, but rather a "base 64Ĭontent-Transfer-Encoding" for use within MIME. MIME is often used as a reference for base 64 encoding. Specific recommended behavior for the future. Implementations in the past, and where appropriate, mandate a Here we discuss the discrepancies between base encoding "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in RFC 2119. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", This will hopefully reduceĪmbiguity in other documents, leading to better interoperability. The purpose of this specification is to establish commonĪlphabet and encoding considerations. MIME is often used as a reference for base64 withoutĬonsidering the consequences for line-wrapping or non-alphabetĬharacters. General, and "base64" in particular, without a precise description or Today, protocol specifications sometimes use base encodings in In the past, different applications have had different requirementsĪnd thus sometimes implemented base encodings in slightly different Makes it possible to manipulate objects with text editors. Base encoding can also be used in newĪpplications that do not have legacy restrictions, simply because it Introductionīase encoding of data is used in many situations to store or transferĭata in environments that, perhaps for legacy reasons, are restricted RFC 3548 The Base16, Base32, and Base64 Data Encodings July 2003 1. Base 64 Encoding with URL and Filename Safe Alphabet. Interpretation of non-alphabet characters in encodedĭata. It also discusses the use of line-feeds inĮncoded data, use of padding in encoded data, use of non-alphabetĬharacters in encoded data, and use of different encoding alphabets.ġ. This document describes the commonly used base 64, base 32, and baseġ6 encoding schemes. Distribution of thisĬopyright (C) The Internet Society (2003).
Not specify an Internet standard of any kind. This memo provides information for the Internet community. The Base16, Base32, and Base64 Data Encodings
0 kommentar(er)
