[lamps] Last Call: <draft-ietf-lamps-cmp-updates-18.txt> (Certificate Management Protocol (CMP) Updates) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 27 April 2022 13:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-lamps-cmp-updates@ietf.org, housley@vigilsec.com, lamps-chairs@ietf.org, rdd@cert.org, spasm@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165106565480.1880.92473946301485098@ietfa.amsl.com>
Date: Wed, 27 Apr 2022 06:20:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/6XYmxdJChrG5PZYEh2bbyxJgCmI>
Subject: [lamps] Last Call: <draft-ietf-lamps-cmp-updates-18.txt> (Certificate Management Protocol (CMP) Updates) to Proposed Standard

The IESG has received a request from the Limited Additional Mechanisms for
PKIX and SMIME WG (lamps) to consider the following document: - 'Certificate
Management Protocol (CMP) Updates'
  <draft-ietf-lamps-cmp-updates-18.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-05-11. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document contains a set of updates to the syntax and transfer of
   Certificate Management Protocol (CMP) version 2.  This document
   updates RFC 4210, RFC 5912, and RFC 6712.

   The aspects of CMP updated in this document are using EnvelopedData
   instead of EncryptedValue, clarifying the handling of p10cr messages,
   improving the crypto agility, as well as adding new general message
   types, extended key usages to identify certificates for use with CMP,
   and well-known URI path segments.

   To properly differentiate the support of EnvelopedData instead of
   EncryptedValue, the CMP version 3 is introduced in case a transaction
   is supposed to use EnvelopedData.

   CMP version 3 is introduced to enable signaling support of
   EnvelopedData instead of EncryptedValue and signaling the use of an
   explicit hash AlgorithmIdentifier in certConf messages, as far as
   needed.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lamps-cmp-updates/



No IPR declarations have been submitted directly on this I-D.

[lamps] Last Call: <draft-ietf-lamps-cmp-updates-… The IESG