Limited Additional Mechanisms for PKIX and SMIME (lamps)
|WG||Name||Limited Additional Mechanisms for PKIX and SMIME|
|Area||Security Area (sec)|
|Status Update||Show update (last changed 2016-07-22)|
|Dependencies||Document dependency graph (SVG)|
|Jabber chat||Room address||xmpp:firstname.lastname@example.org?join|
Charter for Working Group
The PKIX and S/MIME Working Groups have been closed for some time. Some
updates have been proposed to the X.509 certificate documents produced
by the PKIX Working Group and the electronic mail security documents
produced by the S/MIME Working Group.
The LAMPS (Limited Additional Mechanisms for PKIX and SMIME) Working
Group is chartered to make updates where there is a known constituency
interested in real deployment and there is at least one sufficiently
well specified approach to the update so that the working group can
sensibly evaluate whether to adopt a proposal. The current charter
encompasses updates to satisfy the following needs:
1. Specify the way to include an i18n email address as a subject
alternative name and an issuer alternative name.
draft-melnikov-spasm-eai-addresses is a proposal in this space.
2. Specify the way to use authenticated encryption in S/MIME.
draft-schaad-rfc5751-bis is a proposal in this space.
In addition, the LAMPS Working Group may investigate other updates to
the documents produced by the PKIX and S/MIME Working Groups, but the
LAMPS Working Group shall not adopt any of these potential work items
without rechartering. No such re-chartering is envisaged until one or
more of the above work items have been successfully delivered to the RFC
|Apr 2017||WGLC for draft to specify the way to use authenticated encryption in S/MIME|
|Jan 2017||WGLC for a draft to specify the way to include an i18n email address as a subject alternative name and an issuer alternative name|
WG adoption of a draft to specify the way to include an i18n email address as a subject alternative name and an issuer alternative name
WG adoption of a draft to specify the way to use authenticated encryption in S/MIME