Subject: base encoding implementation report

From: Simon Josefsson <[email-masked]>
Date: Thu, 28 May 2009 18:31:36 +0200

All,

I'm attempting to move RFC 4648 (on base64, base32, base16) to Draft
Standard.  Any thoughts on this?  I started working on a implementation
report, guided by Lisa and Robert's document.  It surely needs work, but
I'm unsure what improvements to make at this point.  So I have posted a
-00 document for review.

If someone has implemented base encoding, especially the more exotic
variants like base64url, base32 or base32hex, and wants to help testing,
please contact me.

I'm slightly concerned that the base64url alphabet may not be widely
implemented.  But it isn't clear to me that this would prevent the
document from moving to Draft Status, confidence in interoperability can
be inferred from the normal base64 alphabet.  Any thoughts on this?

Thanks,
/Simon

[email-masked] writes:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
> 	Title           : RFC 4648 Implementation Report
> 	Author(s)       : S. Josefsson
> 	Filename        : draft-josefsson-rfc4648-impl-report-00.txt
> 	Pages           : 5
> 	Date            : 2009-05-28
>
> This is an implementation report of RFC4648, for the purpose of
> advancing the document to Draft Standard.
> See <http://josefsson.org/base-encoding/> for more information.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-josefsson-rfc4648-impl-report-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt