metasystema.org
ObsoletedINFORMATIONALINDEPENDENT stream

RFC 3548: The Base16, Base32, and Base64 Data Encodings

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4648.

Current version: 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, and use of different encoding alphabets. This memo provides information for the Internet community.

Document record

Document ID
RFC3548
Published
July 2003
Authors
S. Josefsson
Status
INFORMATIONAL
Stream
INDEPENDENT
Area
—
Pages
13
Also known as
—
Obsoleted by:
RFC 4648

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3548-the-base16-base32-and-base64-data-encodings