IETF-96 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Limited Additional Mechanisms for PKIX and SMIME (lamps) (WG)

Minutes   |   Jabber Logs  |   Mailing List Archives

Additional information is available at


Security Area Area Director(s):

Assigned Area Director

Status Update (provided 2016-07-22)

This was the first meeting of the LAMPS WG.  The group covered three topics:

1) Adding authenticated-encryption algorithms with S/MIME.  The WG adopted draft-schaad-rfc5651-bis, and once it is published as an RFC, it will obsolete RFC 5751.  It was observed that a corresponding document to obsolete RFC 5750 will also be needed.

2) Email Address Internationalization (EAI) and Certificates.  The WG adopted draft-melnikov-spasm-eai-addresses, which suggests carrying smtputf8Name as an OtherName in the Certificate.  Once this document is published as an RFC, it will update RFC 5280.

3) The CURDLE WG asked this WG for a recommendation regarding CFRG Elliptic Curve algorithm identification in certificates.  The people in the room unanimously recommended that the same object identifiers be used for SubjectPublicKeyInfo.algorithm and Certificate.signatureAlgorithm and SignerInfo.signatureAlgorithm, and that this is used to identify the curve as well as the operation (signature, pre-hash signature, or key agreement).


Meeting Slides:

Blue Sheets:


No Request for Comments

Charter (as of 2016-07-01):

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
editor queue.