idnits 2.17.1 draft-josefsson-base-encoding-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3548 5 Title: The Base16, Base32, and Base64 Data Encodings 6 Author(s): S. Josefsson, Ed. 7 Status: Informational 8 Date: July 2003 9 Mailbox: simon@josefsson.org 10 Pages: 13 11 Characters: 26363 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-josefsson-base-encoding-04.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3548.txt 18 This document describes the commonly used base 64, base 32, and base 19 16 encoding schemes. It also discusses the use of line-feeds in 20 encoded data, use of padding in encoded data, use of non-alphabet 21 characters in encoded data, and use of different encoding alphabets. 23 This memo provides information for the Internet community. It does 24 not specify an Internet standard of any kind. Distribution of this 25 memo is unlimited. 27 This announcement is sent to the IETF list and the RFC-DIST list. 28 Requests to be added to or deleted from the IETF distribution list 29 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 30 added to or deleted from the RFC-DIST distribution list should 31 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 33 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 34 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 35 help: ways_to_get_rfcs. For example: 37 To: rfc-info@RFC-EDITOR.ORG 38 Subject: getting rfcs 40 help: ways_to_get_rfcs 42 Requests for special distribution should be addressed to either the 43 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 44 specifically noted otherwise on the RFC itself, all RFCs are for 45 unlimited distribution.echo 46 Submissions for Requests for Comments should be sent to 47 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 48 Authors, for further information.