draft-ietf-smime-cms-mult-sign-01.txt   draft-ietf-smime-cms-mult-sign-02.txt 
S/MIME Working Group R. Housley (Vigil Security) S/MIME Working Group R. Housley
Updates: 3852 (once approved) Vigil Security
Expires January 2007 Expires June 2007 November 2006
Cryptographic Message Syntax (CMS) Cryptographic Message Syntax (CMS)
Multiple Signer Clarification Multiple Signer Clarification
<draft-ietf-smime-cms-mult-sign-01.txt> <draft-ietf-smime-cms-mult-sign-02.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 12 skipping to change at page 2, line 12
handling of the SignedData protected content type when more than one handling of the SignedData protected content type when more than one
digital signature is present. digital signature is present.
1. Introduction 1. Introduction
This document updates the Cryptographic Message Syntax (CMS) [CMS]. This document updates the Cryptographic Message Syntax (CMS) [CMS].
The CMS SignedData protected content type allows multiple digital The CMS SignedData protected content type allows multiple digital
signatures, but the specification is unclear about the appropriate signatures, but the specification is unclear about the appropriate
processing by a recipient of such a signed content. This document processing by a recipient of such a signed content. This document
provides replacement text for a few paragraphs, making it clear that provides replacement text for a few paragraphs, making it clear that
the protected content is valid if any of the digital signatures is the protected content is valid if any of the digital signatures for a
valid. particular signer is valid.
This property is especially important in two cases. First, when the This property is especially important in two cases. First, when the
recipients do not all implement the same digital signature algorithm, recipients do not all implement the same digital signature algorithm,
the signer can sign the content with several different digital a signer can sign the content with several different digital
signature algorithms so that each of the recipients can find an signature algorithms so that each of the recipients can find an
acceptable signature. For example, if some recipients support RSA acceptable signature. For example, if some recipients support RSA
and some recipients support ECDSA, then the signer can generate two and some recipients support ECDSA, then the signer can generate two
signatures, one with RSA and one with ECDSA, so that each recipient signatures, one with RSA and one with ECDSA, so that each recipient
will be able to validate one of the signature. Second, when a will be able to validate one of the signature. Second, when a
community is transitioning one-way hash functions or digital community is transitioning one-way hash functions or digital
signature algorithms, the signer can sign the content with the older signature algorithms, a signer can sign the content with the older
and the newer signature algorithms so that each recipient can find an and the newer signature algorithms so that each recipient can find an
acceptable signature, regardless of their state in the transition. acceptable signature, regardless of their state in the transition.
For example, consider a transition from RSA with SHA-1 to RSA with For example, consider a transition from RSA with SHA-1 to RSA with
SHA-256. The signer can generate two signatures, one with SHA-1 and SHA-256. The signer can generate two signatures, one with SHA-1 and
one with SHA-256, so that each recipient will be able to validate at one with SHA-256, so that each recipient will be able to validate at
least one of the RSA signatures. least one of the RSA signatures.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 3, line 16 skipping to change at page 3, line 16
| A recipient independently computes the message digest. This message | A recipient independently computes the message digest. This message
| digest and the signer's public key are used to verify the signature | digest and the signer's public key are used to verify the signature
| value. The signer's public key is referenced either by an issuer | value. The signer's public key is referenced either by an issuer
| distinguished name along with an issuer-specific serial number or by | distinguished name along with an issuer-specific serial number or by
| a subject key identifier that uniquely identifies the certificate | a subject key identifier that uniquely identifies the certificate
| containing the public key. The signer's certificate can be included | containing the public key. The signer's certificate can be included
| in the SignedData certificates field. | in the SignedData certificates field.
| |
| When more than one signature is present, the successful validation | When more than one signature is present, the successful validation
| of one of signature associated with each signer is usually treated | of one signature associated with each signer is usually treated
| as a successful validation of the signed-data content type. However, | as a successful validation of the signed-data content type. However,
| there are some application environments where other rules are needed. | there are some application environments where other rules are needed.
| An application that employs a rule other than one valid signature for | An application that employs a rule other than one valid signature for
| each signer must specify those rules. Also, where simple matching of | each signer must specify those rules. Also, where simple matching of
| the signer identifier is not sufficient to determine whether the | the signer identifier is not sufficient to determine whether the
| signatures were generated by the same signer, then the application | signatures were generated by the same signer, the application
| specification must describe how to determine which signatures were | specification must describe how to determine which signatures were
| generated by the same signer. Support of different communities of | generated by the same signer. Support of different communities of
| recipients is the primary reason that signers choose to include more | recipients is the primary reason that signers choose to include more
| than one signature. For example, the signed-data content type might | than one signature. For example, the signed-data content type might
| include signatures generated with the RSA signature algorithm and | include signatures generated with the RSA signature algorithm and
| with the ECDSA signature algorithm. This allows recipients to | with the ECDSA signature algorithm. This allows recipients to
| verify one algorithm or the other. | verify the signature associated with one algorithm or the other.
4. Update to RFC 3852, Section 5.1: SignedData Type 4. Update to RFC 3852, Section 5.1: SignedData Type
RFC 3852, section 5.1, the next to the last paragraph says: RFC 3852, section 5.1, the next to the last paragraph says:
| signerInfos is a collection of per-signer information. There MAY | signerInfos is a collection of per-signer information. There MAY
| be any number of elements in the collection, including zero. The | be any number of elements in the collection, including zero. The
| details of the SignerInfo type are discussed in section 5.3. | details of the SignerInfo type are discussed in section 5.3.
| Since each signer can employ a digital signature technique and | Since each signer can employ a digital signature technique and
| future specifications could update the syntax, all implementations | future specifications could update the syntax, all implementations
 End of changes. 8 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/