Skip to main content

Last Call Review of draft-merkle-tls-brainpool-02

Request Review of draft-merkle-tls-brainpool
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2013-07-16
Requested 2013-06-27
Authors Johannes Merkle , Manfred Lochter
I-D last updated 2013-07-12
Completed reviews Genart Last Call review of -02 by Roni Even (diff)
Genart Telechat review of -04 by Roni Even
Secdir Last Call review of -02 by Simon Josefsson (diff)
Secdir Telechat review of -04 by Simon Josefsson
Assignment Reviewer Simon Josefsson
State Completed
Request Last Call review on draft-merkle-tls-brainpool by Security Area Directorate Assigned
Reviewed revision 02 (document currently at 04)
Result Has nits
Completed 2013-07-12
I have reviewed draft-merkle-tls-brainpool-03 and consider the document
to be "Ready with nits".  I support its publication.

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

I haven't verified the test vectors, but as an implementer I'm happy
that they are present and they improve the credibility of the draft.

I believe the document would be improved by addressing the suggestions
below, but these comments are not critical.


When I read the document, it seems to be missing its "gut".  There is
one section "Introduction" and then you would expect the actual
specification.  But instead comes the Security Considerations and the
rest of the usual IETF boiler plate.  The contribution of this document
is hidden in the IANA Considerations.

In particular, there is no TLS presentation language of the new fields.

Adding new TLS enum types is done by several other documents, and they
usually contain a bit more detail.  Compare how RFC5878 introduces new
enum types in section 2.  For an alternative approach, look at how
rfc6042 introduces new enum types.

Further, I feel it is more appropriate to put the comment about DTLS
compatibility in this new section rather than in the IANA

I would propose to add a new section after "Introduction":

2. Brainpool NamedCurve Types

This document adds three new NamedCurve types as follows.

        enum {
        } NamedCurve;

These curves are suitable for use with DTLS [RFC6347].


In section 1, remove a whitespace after the RFC5480 citation.  It
causes a comma to appear standalone.

   certificates according to [RFC3279] and [RFC5480] , their negotiation
   certificates according to [RFC3279] and [RFC5480], their negotiation