3 ms·
So... there's a specification that has barely any text, which feels way too premature for me to care. But I also wonder why people should expect this to be any
by jcranmer 11y ago
So... there's a specification that has barely any text, which feels way too premature for me to care.
But I also wonder why people should expect this to be any more successful in deployment than S/MIME 3.1's use of an encrypted/signed message/rfc822 blob to protect headers. Officially standardized for 11 years and in use by exactly 0 email clients as far as I am aware.
- jakeogh 11y agoS/MIME 3.1: https://tools.ietf.org/html/rfc3851#page-14 https://tools.ietf.org/html/rfc3851#page-14