Protocol Action: 'X.509 Certificate Extension for S/MIME Capabilities' to Proposed Standard

The IESG <> Mon, 27 June 2005 21:14 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1Dn0vi-0003V9-GI; Mon, 27 Jun 2005 17:14:10 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1Dn0vX-0003Ut-3b; Mon, 27 Jun 2005 17:13:59 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id RAA19726; Mon, 27 Jun 2005 17:13:56 -0400 (EDT)
Received: from [] ( by with esmtp (Exim 4.33) id 1Dn1Kl-0004n1-3E; Mon, 27 Jun 2005 17:40:03 -0400
Received: from apache by with local (Exim 4.43) id 1Dn0vV-0008Sj-Eo; Mon, 27 Jun 2005 17:13:57 -0400
X-test-idtracker: no
From: The IESG <>
To: IETF-Announce <>
Message-Id: <>
Date: Mon, 27 Jun 2005 17:13:57 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: smime chair <>, smime chair <>, Internet Architecture Board <>, smime mailing list <>, RFC Editor <>
Subject: Protocol Action: 'X.509 Certificate Extension for S/MIME Capabilities' to Proposed Standard
X-Mailman-Version: 2.1.5
Precedence: list
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

The IESG has approved the following document:

- 'X.509 Certificate Extension for S/MIME Capabilities '
   <draft-ietf-smime-certcapa-05.txt> as a Proposed Standard

This document is the product of the S/MIME Mail Security Working Group. 

The IESG contact persons are Russ Housley and Sam Hartman.

A URL of this Internet-Draft is:

Technical Summary
  This protocol provides an X.509 public key certificate extension to indicate
  the end entity's S/MIME cryptographic capabilities.  It is an optional,
  non-critical extension.
Working Group Summary
  Initially, the major discussion point was whether this mechanism, which is
  considered a "static" mechanism, is better or worse than a more "dynamic"
  mechanism, which could change without affecting the public key certificates
  contents.  The WG decided to allow for the possibility of another editor
  could step for to define the "dynamic" mechanism, but that this "static"
  mechanism should be allowed to proceed.  The other discussions on the draft
  were considered minor, mostly dealt with the security considerations
  wording, and these issues were resolved quickly.
Protocol Quality
  The protocol is implemented by one vendor already in a number of their

  This document was reviewed by Russ Housley for the IESG.

IETF-Announce mailing list