Document:   draft-ietf-tls-ecc-12.txt 
Reviewer: Joel M. Halpern [joel@stevecrocker.com]
Review Date:  Sunday 1/15/2006 9:11 AM CST
IESG Telechat Date:  Thursday, 19 January 2006

Summary: This document is not quite ready for publication as an informational RFC.

My concern is the status of the document.  It is normal for Cipher Suites 
(algorithm definitions) to be informational RFCs.  I have no argument with 
that.
However, this document is not an algorithm definition.
Rather, it is the definition of a set of TLS extensions and the format of 
the information in those TLS extensions.
As such, it is a definition for bits on a wire, not for a computational 
algorithm.
(I was curious to see how the algorithm would be described, having only 
seen exponential algorithms described in RFCs before.   The algorithm is 
not described in this document.)

Note: I will take as given that the descriptions of enums and structures 
here is sufficient that in conjunction with the base TLS documents and the 
extension description document an implementor can determine how to form the 
proper messages.    The description consisting  of the words "structure of 
the message" followed by the definition of an enum (to be used somewhere?) 
followed sometimes by a struct defintion (presumably to be included in a 
message somewhere, with some context identifier, if the values of the enum 
are used somewhere?) is not clear to one who is not immersed in TLS 
extension work.  (Presumably, this definition structure is used because 
giving the rest of the information would be both long and duplicative.)
I also presume that the definition of the lagnuage used for the structure 
definition, and the mapping of that definition to bits on the wire, is 
included in the TLS extensions document?

nit: idnits notes that the Copyright statement is not verbatim as specified.