W3C home > Mailing lists > Public > public-xmlsec@w3.org > January 2010

Reverting RFC 2231 change (Re: WWW/2008/xmlsec/Drafts/xmldsig-core-11 Overview.src.html,1.24,1.25 Overview.htm,1.110,1.111)

From: Thomas Roessler <tlr@w3.org>
Date: Tue, 12 Jan 2010 13:41:32 +0100
Cc: Thomas Roessler <tlr@w3.org>
Message-Id: <9201E900-6120-4113-A109-8483C50AB858@w3.org>
To: XML Security Working Group WG <public-xmlsec@w3.org>, Frederick Hirsch <Frederick.Hirsch@nokia.com>
On 11 Jan 2010, at 22:00, Frederick Hirsch via cvs-syncmail wrote:

> add normative references for RFC 2231 and RFC 4055. Add link for IEEE 1363 reference. Fix URN reference format. Remove additional spurious NFC-Corrigendum referrals.

Seems like I missed that commit when I started making similar edits.  I don't think we've created any conflicts.

However, I've reverted the following change:

>   <p>Some <code>Transform</code>s may require explicit MIME type, charset (IANA 
> -  registered "character set"), or other such information concerning the data 
> +  registered "character set") [[!RFC2231]], or other such information
> +  concerning the data  
>   they are receiving from an earlier <code>Transform</code> or the source data, 
>   although no
>   <code>Transform</code> algorithm specified in this document needs such 

RFC 2231 defines a (relatively obscure) encoding for content type *parameters* that are non-ASCII.  That reference doesn't fit here, and frankly, I don't think it adds anything useful to Signature.
Received on Tuesday, 12 January 2010 12:41:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:13 UTC