An Attribute for Statement of Possession of a Private Key
draft-ietf-lamps-private-key-stmt-attr-09

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, debcooley1@gmail.com, draft-ietf-lamps-private-key-stmt-attr@ietf.org, lamps-chairs@ietf.org, rfc-editor@rfc-editor.org, spasm@ietf.org, tim.hollebeek@digicert.com
Subject: Protocol Action: 'An Attribute for Statement of Possession of a Private Key' to Proposed Standard (draft-ietf-lamps-private-key-stmt-attr-09.txt)

The IESG has approved the following document:
- 'An Attribute for Statement of Possession of a Private Key'
  (draft-ietf-lamps-private-key-stmt-attr-09.txt) as Proposed Standard

This document is the product of the Limited Additional Mechanisms for PKIX
and SMIME Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-private-key-stmt-attr/

Ballot Text

Technical Summary

   This document specifies an attribute for a statement of possession of
   a private key by a certificate subject.  As part of X.509 certificate
   enrollment, a Certification Authority (CA) typically demands proof
   that the subject possesses the private key that corresponds to the
   to-be-certified public key.  In some cases, a CA might accept a
   signed statement from the certificate subject.  For example, when a
   certificate subject needs separate certificates for signature and key
   establishment, a statement that can be validated with the previously
   issued signature certificate for the same subject might be adequate
   for subsequent issuance of the key establishment certificate.

Working Group Summary
  There was broad agreement and little controversy.  

Document Quality

There is ASN.1:  The ASN.1 in the text was examined by eye, and the ASN.1 
module in Appendix A was compiled.

Downrefs which are already in the registry:  RFC 2986, RFC 5912

Personnel

   The Document Shepherd for this document is Tim Hollebeek. The
   Responsible Area Director is Deb Cooley.

RFC Editor Note