Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 In your previous mail you wrote:

   I'm OK with this text.  I tried to come up with a way to briefly discuss
   how error detection is very related to things like protecting against
   substitution of content (the internet mirror case) but failed to come up
   with something brief.
   So, I'm fine with what you have.
   
=> can I conclude you are in the "they are security considerations so
don't talk about not-security uses" side?

Thanks

Francis.Dupont@xxxxxxxxxx

PS: to summary the issue, we can do 3 things about new not-security uses:
 - not discourage them as they don't raise any security problems
 - discourage them as they can raise operational problems because
  some crypto regulations banish MD5 by itself
 - write nothing
Note the last option solves the issue only for this document,
i.e., each time a document will propose a new use of MD5 the issue
will be re-opened.
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]