RFC 4648: The Base16, Base32, and Base64 Data Encodings
In plain English — editorial summary, not part of the RFC
This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4648
- Published
- October 2006
- Authors
- S. Josefsson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 18
- Also known as
- —
- Obsoletes:
- RFC 3548
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5126CMS Advanced Electronic Signatures (CAdES)Current
March 2008
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3965A Simple Mode of Facsimile Using Internet MailCurrent
December 2004
- RFC 5341The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter RegistryCurrent
September 2008
- RFC 3861Address Resolution for Instant Messaging and PresenceCurrent
August 2004
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 3593Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
September 2003
- RFC 3470Guidelines for the Use of Extensible Markup Language (XML) within IETF ProtocolsUpdated
January 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?