RE: proposed update to XML Encryption 1.1

Why not do this the other way around? We're close to publication, Eastlake's document is still just a draft. He could easily switch.

-- Magnus

> -----Original Message-----
> From: Frederick.Hirsch@nokia.com [mailto:Frederick.Hirsch@nokia.com]
> Sent: 7 February, 2013 12:33
> To: public-xmlsec@w3.org
> Cc: Frederick.Hirsch@nokia.com
> Subject: proposed update to XML Encryption 1.1
> 
> The PR draft of XML Encryption 1.1 defines informative URIs for AES Key
> Wrap with Padding in Appendix A [1]. The update to RFC 4051 defines these
> as well using different URIs [2].
> 
> I propose the URIs in XML Encryption 1.1 be updated to use those defined in
> the RFC - as this is an informative appendix I see no harm in doing so to the
> PR draft as we go to REC.
> 
> Specifically, I propose changing
> 
> http://www.w3.org/2009/xmlenc11#kw-aes-128-pad
> 
> http://www.w3.org/2009/xmlenc11#kw-aes-192-pad
> 
> http://www.w3.org/2009/xmlenc11#kw-aes-256-pad
> 
> to
> 
> http://www.w3.org/2007/05/xmldsig-more#kw-aes128-pad
> 
> http://www.w3.org/2007/05/xmldsig-more#kw-aes192-pad
> 
> http://www.w3.org/2007/05/xmldsig-more#kw-aes256-pad
> 
> Comment or suggestions?
> 
> regards, Frederick
> 
> Frederick Hirsch, Nokia
> Chair, W3C DAP Working Group
> 
> [1]  [http://www.w3.org/TR/xmlenc-core1/#sec-kw-aes-with-pad
> 
> [2] http://datatracker.ietf.org/doc/draft-eastlake-additional-xmlsec-uris/
> 
> 
> 
> 
> 
> 

Received on Thursday, 7 February 2013 21:09:58 UTC