Skip to main content

Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation
RFC 5639

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: RFC Editor <>
Cc: The IESG <>, <>,
Subject: Re: Informational RFC to be: 

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 
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:

The process for such documents is described at

Thank you,

The IESG Secretary

Ballot Text

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.


   Tim Polk is the Responsible Area Director.

RFC Editor Note

    The IESG has not found any conflict between this document and IETF

    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.


   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.

RFC Editor Note