Fwd: Protocol Action: 'The Base16, Base32, and Base64 Data Encodings' to Proposed Standard

Thu, 18 May 2006 16:32:14 -0700

This announcement is for a document that will obsolete RFC3548, which is referenced by a couple APPS area RFCs:  XMPP (RFC3920) and Atom Syntax (RFC4287).

There are also a few drafts that reference RFC3548 that caught my eye:

 - draft-ietf-nntpext-base, which is in RFC ED queue
 -  draft-josefsson-sasl-gs2-00
 - draft-otis-dkim-options-00
 - draft-snell-atompub-author-extensions-00 

thanks,
Lisa

Begin forwarded message:

From: The IESG <[EMAIL PROTECTED]>
Date: May 18, 2006 7:51:48 AM PDT
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'The Base16, Base32, and Base64 Data  Encodings' to Proposed Standard 

The IESG has approved the following document:

- 'The Base16, Base32, and Base64 Data Encodings '
   <draft-josefsson-rfc3548bis-04.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Ted Hardie.

A URL of this Internet-Draft is:

Technical Summary

  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.
   It obsoletes the descriptions in RFC 3548.

Working Group Summary

 This work is the product of an individual submitter.  There were significant
 IETF Last Call comments, and the draft was updated to respond to them.

Protocol Quality

 This document was reviewed for the IESG by Ted Hardie.


_______________________________________________
IETF-Announce mailing list

Reply via email to