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

Lisa Dusseault <lisa@osafoundation.org> Fri, 19 May 2006 00:14 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgsd5-0002yT-AB; Thu, 18 May 2006 20:14:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FgriE-0002pX-Rq for discuss@apps.ietf.org; Thu, 18 May 2006 19:15:22 -0400
Received: from laweleka.osafoundation.org ([204.152.186.98]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgriE-0005bz-4p for discuss@apps.ietf.org; Thu, 18 May 2006 19:15:22 -0400
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id BDE20142297; Thu, 18 May 2006 16:15:16 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11601-05; Thu, 18 May 2006 16:15:14 -0700 (PDT)
Received: from [192.168.1.101] (c-67-161-46-163.hsd1.ca.comcast.net [67.161.46.163]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 98F0214228A; Thu, 18 May 2006 16:15:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v749.3)
References: <E1Fgjqu-0005en-0k@stiedprstage1.ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail-20-35697861"
Message-Id: <334E15AA-7049-4A6E-AFD7-916667E67E6D@osafoundation.org>
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Fwd: Protocol Action: 'The Base16, Base32, and Base64 Data Encodings' to Proposed Standard
Date: Thu, 18 May 2006 16:15:05 -0700
To: discuss@apps.ietf.org, XMPP WG List <xmppwg@jabber.org>, Atom <atom-syntax@imc.org>, ietf-nntp@lists.eyrie.org
X-Mailer: Apple Mail (2.749.3)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
X-Mailman-Approved-At: Thu, 18 May 2006 20:14:05 -0400
Cc: simon@josefsson.org, James M Snell <jasnell@gmail.com>, clive@demon.net, doug_otis@trendmicro.com
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

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 <iesg-secretary@ietf.org>
> 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:
> http://www.ietf.org/internet-drafts/draft-josefsson-rfc3548bis-04.txt
>
> 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
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce