ACTION-227: Draft text encryption algorithms regarding ECC algorithms and what curves should be used

Draft text encryption algorithms regarding ECC algorithms and what curves should be used

State:
closed
Person:
Brian LaMacchia
Due on:
March 10, 2009
Created on:
March 3, 2009
Related emails:
  1. 2009-03-31 Minutes for Approval (from edsimon@xmlsec.com on 2009-04-03)
  2. Agenda: Distributed Meeting 2009-03-31 (from frederick.hirsch@nokia.com on 2009-03-30)
  3. Agenda: Distributed Meeting 2009-03-24 v2 (resend) (from frederick.hirsch@nokia.com on 2009-03-23)
  4. Agenda: Distributed Meeting 2009-03-24 v2 (from Frederick.Hirsch@nokia.com on 2009-03-23)
  5. Agenda: Distributed Meeting 2009-03-24 (resend) (from Frederick.Hirsch@nokia.com on 2009-03-22)
  6. Agenda: Distributed Meeting 2009-03-24 (from Frederick.Hirsch@nokia.com on 2009-03-22)
  7. ACTION-227: text specifying ECC curves in XMLENC (from bal@exchange.microsoft.com on 2009-03-17)
  8. Agenda: Distributed Meeting 2009-03-17 (resend) (from frederick.hirsch@nokia.com on 2009-03-11)
  9. Agenda: Distributed meeting 2009-03-17 (from Frederick.Hirsch@nokia.com on 2009-03-11)
  10. Updated minutes for 3 March 2009 (from frederick.hirsch@nokia.com on 2009-03-06)

Related notes:

OK, I think all this needs is for the following paragraph to be added as the second paragraph of Section 5.5.4 in XMLENC:

Compliant implementations are REQUIRED to support ECDH-ES key
agreement using the P-256 prime curve specified in Section D.2.3 of
FIPS 186-3 [FIPS186-3]. (This is the same curve that is REQUIRED in
XMLDSIG 1.1 to be supported for the ECDSAwithSHA256 algorithm.) It is
further RECOMMENDED that implementations also support the P-384 and
P-521 prime curves for ECDH-ES; these curves are defined in Sections
D.2.4 and D.2.5 of FIPS 186-3, respectively.

And we'll also have to add a reference to FIPS 186-3 when it's finalized.

Brian LaMacchia, 17 Mar 2009, 07:07:28

Display change log.


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 227.html,v 1.1 2017/01/10 16:23:36 carine Exp $