draft-ietf-smime-certcapa-02.txt   draft-ietf-smime-certcapa-03.txt 
Stefan Santesson
Microsoft Security Center of Excellence (SCOE)
S/MIME Working Group S. Santesson (Microsoft) S/MIME Working Group S. Santesson (Microsoft)
INTERNET-DRAFT INTERNET-DRAFT
Expires June 2005 Expires August 2005
December 2004 February 2005
Certificate extension for S/MIME Capabilities Certificate extension for S/MIME Capabilities
<draft-ietf-smime-certcapa-02.txt> <draft-ietf-smime-certcapa-03.txt>
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668 disclosed, in accordance with RFC 3668
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 8 skipping to change at page 2, line 8
capabilities in public key certificates defined by RFC 3280. capabilities in public key certificates defined by RFC 3280.
S/MIME Capabilities provides an optional method to communicate S/MIME Capabilities provides an optional method to communicate
cryptographic capabilities of the certified subject as a complement cryptographic capabilities of the certified subject as a complement
to use of the S/MIME Capabilities signed attribute in S/MIME messages to use of the S/MIME Capabilities signed attribute in S/MIME messages
according to RFC 3851. according to RFC 3851.
Table of Contents Table of Contents
1 Introduction ................................................ 2 1 Introduction ................................................ 2
1.1 Terminology ............................................... 3
2 S/MIME Capabilities Extension ............................... 3 2 S/MIME Capabilities Extension ............................... 3
3 Use in applications ......................................... 3 3 Use in applications ......................................... 3
4 Security Considerations ..................................... 3 4 Security Considerations ..................................... 4
5 References .................................................. 4 5 References .................................................. 4
Authors' Addresses ............................................. 4 Authors' Addresses ............................................. 5
Disclaimer ..................................................... 5 Disclaimer ..................................................... 5
Copyright Statement ............................................ 5 Copyright Statement ............................................ 5
1. Introduction 1 Introduction
The purpose of this specification is to specify a simple approach to This document defines a certificate extension for inclusion of S/MIME
store cryptographic capabilities in public key certificates. capabilities in public key certificates defined by RFC 3280 [RFC
3280].
The S/MIME Capabilities attribute is defined in RFC 3851 for The S/MIME Capabilities attribute is defined in RFC 3851 for
specifying cryptographic capabilities of the sender of a signed specifying cryptographic capabilities of the sender of a signed
S/MIME message. This information can be used by the recipient in S/MIME message. This information can be used by the recipient in
subsequent S/MIME secured exchanges to select appropriate subsequent S/MIME secured exchanges to select appropriate
cryptographic properties for future exchange with the opponent. cryptographic properties for future exchange with the opponent.
The use of S/MIME does however introduce the scenario where e.g. a The use of S/MIME does however introduce the scenario where e.g. a
sender of an encrypted message has no prior established knowledge of sender of an encrypted message has no prior established knowledge of
the recipient's cryptographic capabilities through recent S/MIME the recipient's cryptographic capabilities through recent S/MIME
skipping to change at page 3, line 5 skipping to change at page 3, line 7
cryptographic capabilities for use with S/MIME, to be used as an cryptographic capabilities for use with S/MIME, to be used as an
optional additional information resource when knowledge about the optional additional information resource when knowledge about the
subject capabilities is considered insufficient. subject capabilities is considered insufficient.
This document is limited to the "static" approach where asserted This document is limited to the "static" approach where asserted
cryptographic capabilities remain unchanged until the certificate cryptographic capabilities remain unchanged until the certificate
expires or is revoked. Other "dynamic" approaches which allow expires or is revoked. Other "dynamic" approaches which allow
retrieval of certified dynamically updatable capabilities during the retrieval of certified dynamically updatable capabilities during the
lifetime of a certificate are out of scope of this document. lifetime of a certificate are out of scope of this document.
2. S/MIME Capabilities Extension 1.1 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [STDWORDS].
2 S/MIME Capabilities Extension
This section defines the S/MIME Capabilities extension. This section defines the S/MIME Capabilities extension.
The S/MIME capabilities extension data structure used in this The S/MIME capabilities extension data structure used in this
specification is identical to the data structure of the S/MIME specification is identical to the data structure of the
capabilities attribute defined in RFC 3851. SMIMECapabilities attribute defined in RFC 3851 [RFC 3851].
The S/MIME Capabilities extension MUST follow the definition defined The S/MIME Capabilities extension MUST follow the requirements and
in RFC 3851. (The ASN.1 structure of smimeCapabilities is included definitions defined in RFC 3851. (The ASN.1 structure of
below for illustrative purposes only) smimeCapabilities is included below for illustrative purposes only)
smimeCapabilities OBJECT IDENTIFIER ::= smimeCapabilities OBJECT IDENTIFIER ::=
{iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) 15} pkcs-9(9) 15}
sMIMECapabilitiesExt EXTENSION ::= { sMIMECapabilitiesExt EXTENSION ::= {
SYNTAX SMIMECapabilities SYNTAX SMIMECapabilities
IDENTIFIED BY smimeCapabilities } IDENTIFIED BY smimeCapabilities }
SMIMECapabilities ::= SEQUENCE OF SMIMECapability SMIMECapabilities ::= SEQUENCE OF SMIMECapability
SMIMECapability ::= SEQUENCE { SMIMECapability ::= SEQUENCE {
capabilityID OBJECT IDENTIFIER, capabilityID OBJECT IDENTIFIER,
parameters ANY DEFINED BY capabilityID OPTIONAL } parameters ANY DEFINED BY capabilityID OPTIONAL }
Algorithms should be ordered by preference. This extension is expected to hold the same type of capability data
as the SMIMECapabilities attribute defined in RFC 3851.
This extension MUST NOT be marked critical. This extension MUST NOT be marked critical.
3. Use in applications 3 Use in applications
Applications using the S/MIME Capabilities extension SHOULD NOT use Applications using the S/MIME Capabilities extension SHOULD NOT use
information in the extension if more reliable and relevant information in the extension if more reliable and relevant
authenticated capabilities information are available to the authenticated capabilities information are available to the
application. application.
It is outside the scope of this specification to define what is, or It is outside the scope of this specification to define what is, or
is not, regarded as more reliable source of information by the is not, regarded as more reliable source of information by the
encrypting application. encrypting application.
skipping to change at page 4, line 22 skipping to change at page 4, line 32
Implementers should take into account that the use of this extension Implementers should take into account that the use of this extension
does not change the fact that it is always the responsibility of the does not change the fact that it is always the responsibility of the
sender to choose sufficiently strong encryption for its information sender to choose sufficiently strong encryption for its information
disclosure. disclosure.
5 References 5 References
Normative references: Normative references:
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate [STDWORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC 3280] R. Housley, W. Polk, W. Ford, and D. Solo, "Internet [RFC 3280] R. Housley, W. Polk, W. Ford, and D. Solo, "Internet
X.509 Public Key Infrastructure: Certificate and X.509 Public Key Infrastructure: Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280, Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002. April 2002.
[RFC 3851] B. Ramsdell, "Secure/Multipurpose Internet Mail [RFC 3851] B. Ramsdell, "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.1 Message Specification", Extensions (S/MIME) Version 3.1 Message Specification",
RFC 3851, July 2004 RFC 3851, July 2004
skipping to change at page 5, line 21 skipping to change at page 5, line 31
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Expires June 2005 Expires August 2005
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/