- From: Frederick Hirsch <frederick.hirsch@nokia.com>
- Date: Wed, 12 May 2010 11:53:29 -0400
- To: Makoto MURATA <eb2m-mrt@asahi-net.or.jp>
- Cc: Frederick Hirsch <frederick.hirsch@nokia.com>, XMLSec WG Public List <public-xmlsec@w3.org>
(corrected confirmation request) Makoto As Last Call comments on XML Signature 1.1 you noted an ambiguity related to the SHA384 URI [1] [2]. This was noted as WG issues ISSUE-190 and ISSUE-191 [3] and also recorded as a single Last Call issue (LC-2376) [4]. In order to maintain backward compatibility the WG resolved the issue by updating the document to consistently use http://www.w3.org/2001/04/xmldsig-more#sha384 as proposed [5] and minuted [6]. We included you in a message on March noting the resolution, but I have not heard any response [7]. I assume this means this resolution is acceptable, but for the record, can you please confirm that the resolution is acceptable to you? The latest Editors Draft has this correction [8]. Thank you. regards, Frederick Frederick Hirsch, Nokia Chair XML Security WG [1] http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0052.html [2] http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0029.html [3] http://www.w3.org/2008/xmlsec/track/issues/190 and http://www.w3.org/2008/xmlsec/track/issues/191 [4] http://www.w3.org/2006/02/lc-comments-tracker/42458/WD-xmldsig-core1-20100204/2376 [5] http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0074.html [6] http://www.w3.org/2010/03/09-xmlsec-minutes.html#item03 [7] http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0081.html [8] http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.html#sec-SHA-384
Received on Wednesday, 12 May 2010 15:54:38 UTC