2011/11/7 Hadriel Kaplan <[email protected]>:
> But this S/MIME discussion is like arguing about the length of horn a unicorn 
> must have. ;)

Oh, I cannot believe what I read... !!!

S/MIME is, for sure, very extended in SIP devices. If not, why does
every SIP related RFC include a section recommending usage of S/MIME?
I'm pretty sure that S/MIME will become a revolution in SIP within
next 2 years!
S/MIME for all !!!


Security Considerations

  This mail has been sent using plain HTTP and plain SMTP. In order
  to protect the content of the mail from network intruders, the email
  client could encrypt it by using S/MIME mechanism.

     Note: How the user gets his own S/MIME certificate is out of the
     scope of this document, but I was mandated to mention S/MIME
     in order the IETF to approve this draft as RFC.




-- 
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to