[
Lists Home |
Date Index |
Thread Index
]
Why not base 32K, for effeciently encoding binary data into UTF-16?
.micah
-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]
Sent: Tuesday, July 08, 2003 7:26 PM
To: xml-Dev
Subject: [xml-dev] Fwd: RFC 3548 on The Base16, Base32, and Base64 Data
Encodings
Base64 encoding has a new home.
>To: IETF-Announce: ;
>Subject: RFC 3548 on The Base16, Base32, and Base64 Data Encodings
>From: rfc-editor@rfc-editor.org
>Date: Tue, 08 Jul 2003 16:35:59 -0700
>
>
>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.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-Type: text/plain
>Content-ID: <030708163442.RFC@RFC-EDITOR.ORG>
>
>RETRIEVE: rfc
>DOC-ID: rfc3548
>
><ftp://ftp.isi.edu/in-notes/rfc3548.txt>
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
|
