On Mon, Mar 7, 2016 at 10:58 PM, Russ Housley <housley(_at_)vigilsec(_dot_)com>
wrote:
I am hearing interest in these topics (a combination of things on this
list and side conversations).
(1) Specify the way to use authenticated encryption in S/MIME. Note that
it is already done for CMS.
(2) Specify conventions for AES-CCM, AES-GCM, and ChaCha20 with Poly1305
authenticated encryption algorithms.
(3) Specify conventions for using Curve25519 and Curve448 for key
agreement.
(4) Specify conventions for using the CFRG chosen curves for elliptic
curve digital signature.
(5) Specify a way to use PGP public keys in addition to PKIX certificates.
Anything else?
While I'm afraid of scope creep as resolving the above would be very
useful, could also mail header integrity and privacy be considered?
Perhaps the WG scope be split into near and long term work to help
prioritize. The above five items be categorize as near term and the mail
header work considered longer term?
-Wei
(PS yes there is RFC7508 which is experimental, and does not keep private
the sender and recipient. Still it is an improvement...)
Is this enough to re-charter the S/MIME WG?
Russ
_______________________________________________
smime mailing list
smime(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime
_______________________________________________
smime mailing list
smime(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime