Document: draft-turner-md5-seccon-update-07.txt
Reviewer: Francis Dupont
Review Date: 2010-12-06
IETF LC End Date: 2010-12-22
IESG Telechat date: unknown

Summary: Not Ready

Major issues:
 - IANA action is to change a field which doesn't exist

 - there is no consensus if the document should stress not-security uses
  of MD5 are perfectly fine or at the opposite the security label attached
  to MD5 raises practical issues so new uses of MD5 should be strongly
  discouraged or both are out of scope...

Minor issues: None

Nits/editorial comments:
 - 2.1 page 2: Psuedo -> Pseudo

 - 2.1 page 3: 1.6 GHz. -> 1.6GHz (note: suggestion for removing the space,
  fix for the spurious '.' after an unit)

 - 2.3 page 3: (suggestion) H(IV,M). -> H(IV, M).

Regards

Francis.Dupont@fdupont.fr

PS: about 3:

   IANA is requested to update the md5 usage entry in the Hash Function 
   Textual Names registry by replacing "COMMON" with "DEPRECATED". 

I understand why the md5 is in lower case (it is the name of the entry)
but I can't find the usage field in the registry at:

http://www.iana.org/assignments/hash-function-text-names/
hash-function-text-names.xhtml

PPS: my proposal for solving the two issues is:
 - give the first one to IANA (IANA has to address it anyway)
  (PS: in fact IANA already raised a question about this point!)
 - use the standard Last Call process for the second