Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: RFC Editor <email@example.com> Cc: The IESG <firstname.lastname@example.org>, <email@example.com>, firstname.lastname@example.org Subject: Re: Informational RFC to be: draft-lochter-pkix-brainpool-ecc-03.txt The IESG has no problem with the publication of 'ECC Brainpool Standard Curves and Curve Generation' <draft-lochter-pkix-brainpool-ecc-03.txt> as an Informational RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16140&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Tim Polk. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lochter-pkix-brainpool-ecc-03.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary This document specifies a suite of elliptic curves with parameters that were generated in a verifiably pseudo-random way. Working Group Summary This document is an independent submission. Document Quality The brainpool curves (v1.0) were published in October 2005. Personnel Tim Polk is the Responsible Area Director. RFC Editor Note The IESG has not found any conflict between this document and IETF work. This document specifies an ASN.1 arc, ecStdCurvesAndGeneration, in section 4.1. The IESG believes the document would benefit from adding a section analogous to IANA considerations describing how new OIDs will be registered in the future. IESG Note Please include the following IESG note immediately following the "Status of this Memo" section of the finished RFC: This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information.