Re: RFC4051 [Fwd: Add #ecdsa-ripemd160, #rsa-whirlpool, #ecdsa-whirlpool to XML Security Algorithm Cross-Reference [ACTION-222 restating ISSUE-83]]

Dear Donald,

Could you please let me know what the status of
http://tools.ietf.org/html/draft-eastlake-additional-xmlsec-uris-00  is?

BR
Konrad

forwarding to d3e3e3@gmail.com found here
http://tools.ietf.org/html/draft-ietf-trill-rbridge-vlan-mapping-00#page-10

-------- Original-Nachricht --------
Betreff: 	Add #ecdsa-ripemd160, #rsa-whirlpool, #ecdsa-whirlpool to XML
Security Algorithm Cross-Reference [ACTION-222 restating ISSUE-83]
Datum: 	Tue, 24 Feb 2009 18:27:12 +0100
Von: 	Konrad Lanz <Konrad.Lanz@iaik.tugraz.at>
An: 	XMLSec WG Public List <public-xmlsec@w3.org>, Thomas Roessler
<tlr@w3.org>, Frederick Hirsch <frederick.hirsch@nokia.com>
CC: 	Eastlake III Donald <Donald.Eastlake@motorola.com>



Dear all,

Restating and summarizing the proposal from ISSUE-83 to add the
following to the algorithms note (aka. XML Security Algorithm
Cross-Reference ??, aka. Product xmlsec-algorithms ??):

* ECDSA-RIPEMD Identifier:

http://www.w3.org/2007/05/xmldsig-more#ecdsa-ripemd160

#ecdsa-ripemd160 fragment of the new namespace identifies a signature
method processed in the same way as specified by the #ecdsa-sha1
fragment of this namespace with the exception that RIPEMD160 is used
instead of SHA-1.

* RSA-WHIRLPOOL Identifier:
http://www.w3.org/2007/05/xmldsig-more#rsa-whirlpool

This implies the PKCS#1 v1.5 padding algorithm [RFC3447] as described
in section 2.3.1 but with the ASN.1 BER WHIRLPOOL algorithm
designator prefix. An example of use is

<SignatureMethod
Algorithm=http://www.w3.org/2007/05/xmldsig-more#rsa-whirlpool"/>

* ECDSA-WHIRLPOOL Identifiers:
http://www.w3.org/2007/05/xmldsig-more#ecdsa-whirlpool

The #ecdsa-whirlpool fragment of the new namespace identifies a
signature method processed in the same way as specified by the
#ecdsa-sha512 fragment of this namespace
(http://www.w3.org/2001/04/xmldsig-more) with the exception that
WHIRLPOOL is used instead of SHA-512.


BR
Konrad

P.S.: I associated http://www.w3.org/2008/xmlsec/track/issues/83 with
http://www.w3.org/2008/xmlsec/track/products/21

Is Product "xmlsec-algorithms" really XML Security Algorithm
Cross-Reference?
If so can I rename it?
http://www.w3.org/2008/xmlsec/track/products/21/edit

P.S.: ECDSA-RIPEMD Identifier had made it into the RFC 4051 successor
draft ... from
http://tools.ietf.org/html/draft-eastlake-additional-xmlsec-uris-00#section-2.3.6
anyone knows it's status?



-- 
Konrad Lanz, IAIK/SIC - Graz University of Technology
Inffeldgasse 16a, 8010 Graz, Austria
Tel: +43 316 873 5547
Fax: +43 316 873 5520
http://www.iaik.tugraz.at/content/about_iaik/people/lanz_konrad/
http://jce.iaik.tugraz.at/sic/products/xml_security/

Downlaod certificate chain (including the EuroPKI root certificate):
http://ca.iaik.tugraz.at/capso/certs.jsp






-- 
Konrad Lanz, IAIK/SIC - Graz University of Technology
Inffeldgasse 16a, 8010 Graz, Austria
Tel: +43 316 873 5547
Fax: +43 316 873 5520
http://www.iaik.tugraz.at/content/about_iaik/people/lanz_konrad/
http://jce.iaik.tugraz.at/sic/products/xml_security/

Downlaod certificate chain (including the EuroPKI root certificate):
http://ca.iaik.tugraz.at/capso/certs.jsp