* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Lamps Status Pages

Limited Additional Mechanisms for PKIX and SMIME (Active WG)
Sec Area: Roman Danyliw, Benjamin Kaduk | 2016-Jul-01 —  

2021-03-31 charter

Limited Additional Mechanisms for PKIX and SMIME (lamps)


 Current Status: Active

     Russ Housley <housley@vigilsec.com>
     Tim Hollebeek <tim.hollebeek@digicert.com>

 Security Area Directors:
     Roman Danyliw <rdd@cert.org>
     Benjamin Kaduk <kaduk@mit.edu>

 Security Area Advisor:
     Roman Danyliw <rdd@cert.org>

 Mailing Lists:
     General Discussion: spasm@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/spasm
     Archive:            https://mailarchive.ietf.org/arch/browse/spasm/

Description of 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 LAMPS WG is now tackling these topics:

  1. Specify the use of short-lived X.509 certificates for which no
  revocation information is made available by the Certification Authority.
  Short-lived certificates have a lifespan that is shorter than the time
  needed to detect, report, and distribute revocation information.  As a
  result, revoking short-lived certificates is unnecessary and pointless.

  2. Update the specification for the cryptographic protection of email
  headers -- both for signatures and encryption -- to improve the
  implementation situation with respect to privacy, security, usability
  and interoperability in cryptographically-protected electronic mail.
  Most current implementations of cryptographically-protected electronic
  mail protect only the body of the message, which leaves significant
  room for attacks against otherwise-protected messages.

  3. The Certificate Management Protocol (CMP) is specified in RFC 4210,
  and it offers a vast range of certificate management options.  CMP is
  currently being used in many different industrial environments, but it
  needs to be tailored to the specific needs of such machine-to-machine
  scenarios and communication among PKI management entities.  The LAMPS
  WG will develop a "lightweight" profile of CMP to more efficiently
  support of these environments and better facilitate interoperable
  implementation, while preserving cryptographic algorithm agility.  In
  addition, necessary updates and clarifications to CMP will be
  specified in a separate document.  This work will be coordinated with
  the LWIG WG.

  In addition, the LAMPS WG may investigate other updates to documents
  produced by the PKIX and S/MIME WG. The LAMPS WG may produce
  clarifications where needed, but the LAMPS WG shall not adopt
  anything beyond clarifications without rechartering.

Goals and Milestones:
  Jul 2021 - Adopt a draft for short-lived certificate conventions
  Nov 2021 - Header protection conventions sent to IESG for standards track publication
  Dec 2021 - CMP updates sent to IESG for  standards track publication
  Dec 2021 - Lightweight CMP profile sent to IESG for informational publication
  Mar 2022 - Short-lived certificate conventions sent to IESG for BCP publication
  Done     - Adopt a draft for header protection conventions
  Done     - Adopt a draft for CMP updates
  Done     - Adopt a draft for Lightweight CMP profile

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/lamps/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -