The Base16, Base32, and Base64 Data Encodings
draft-josefsson-base-encoding-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3548.
Author Simon Josefsson
Last updated 2020-01-21 (Latest revision 2002-05-13)
RFC stream Independent Submission
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Stream ISE state (None)
Consensus boilerplate Unknown
Document shepherd (None)
IESG IESG state Became RFC 3548 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Ned Freed
IESG note
Send notices to <sjosefsson@rsasecurity.com>
Email authors IPR References Referenced by Nits Search email archive
draft-josefsson-base-encoding-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3548

        Title:      The Base16, Base32, and Base64 Data Encodings
        Author(s):  S. Josefsson, Ed.
        Status:     Informational
        Date:       July 2003
        Mailbox:    simon@josefsson.org
        Pages:      13
        Characters: 26363
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-josefsson-base-encoding-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3548.txt

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.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.