ISSUE-83: Ecdsa-ripemd160 and ecdsa-whirlpool need identifiers, rfc4051?
Ecdsa-ripemd160 and ecdsa-whirlpool need identifiers, rfc4051?
- State:
- CLOSED
- Product:
- XML Signature Streaming Profile of XPath 1.0
- Raised by:
- Konrad Lanz
- Opened on:
- 2009-01-13
- Description:
- Related Actions Items:
ACTION-222 on Konrad Lanz to Make proposal RIPE algorithms - due 2009-03-03, closed- Related emails:
- F2F Minutes updated - revision for approval (from frederick.hirsch@nokia.com on 2009-06-02)
- Draft minutes from May 13 (from pratik.datta@oracle.com on 2009-05-21)
- Agenda: Distributed Meeting 2009-03-17 (resend) (from frederick.hirsch@nokia.com on 2009-03-11)
- Agenda: Distributed meeting 2009-03-17 (from Frederick.Hirsch@nokia.com on 2009-03-11)
- Re: RFC4051 [Fwd: Add #ecdsa-ripemd160, #rsa-whirlpool, #ecdsa-whirlpool to XML Security Algorithm Cross-Reference [ACTION-222 restating ISSUE-83]] (from Konrad.Lanz@iaik.tugraz.at on 2009-02-24)
- Add #ecdsa-ripemd160, #rsa-whirlpool, #ecdsa-whirlpool to XML Security Algorithm Cross-Reference [ACTION-222 restating ISSUE-83] (from Konrad.Lanz@iaik.tugraz.at on 2009-02-24)
- Draft Minutes: xmlsec face-to-face 13 January 2009 (from tlr@w3.org on 2009-01-22)
- Re: ISSUE-90 (addtluris): Define algorithm URIs for ecdsa-ripemd160 and ecdsa-whirlpool? [v11] (from tlr@w3.org on 2009-01-22)
Related notes:
the expired Easlake drafts for the RFC4051 replacement can be found here http://tools.ietf.org/html/draft-eastlake-additional-xmlsec-uris-00#section-2.3.6 may be associate this with the issue surrounding http://www.w3.org/2007/05/xmldsig-more#ecdsa-ripemd160
ecdsa-ripemd160:
http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2007Oct/0032.html
http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2007Nov/0010.html
Whirlpool:
http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2008Mar/0002.html
From http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2008Mar/0002.html
Konrad Lanz, 13 Jan 2009, 18:57:18From http://tools.ietf.org/html/draft-eastlake-additional-xmlsec-uris-00#section-2.3.6 :
#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.
Proposed text for RSA-WHIRLPOOL:
> * 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"/>
Proposed addition to section-2.3.6 for RSA-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.
[fjh2]: see RFC draft
13 May 2009, 21:03:01Display change log