proposed addition to application/pkcs7-mime smime parameter

Rohan Mahy <rohan@cisco.com> Sat, 07 June 2003 03:28 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22987 for <smime-archive@lists.ietf.org>; Fri, 6 Jun 2003 23:28:44 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h572wYAF044816 for <ietf-smime-bks@above.proper.com>; Fri, 6 Jun 2003 19:58:34 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h572wYcq044815 for ietf-smime-bks; Fri, 6 Jun 2003 19:58:34 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h572wWAF044807 for <ietf-smime@imc.org>; Fri, 6 Jun 2003 19:58:33 -0700 (PDT) (envelope-from rohan@cisco.com)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h572wSjc028705; Fri, 6 Jun 2003 19:58:28 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AHW76812; Fri, 6 Jun 2003 19:54:14 -0700 (PDT)
Date: Fri, 06 Jun 2003 19:59:22 -0700
Subject: proposed addition to application/pkcs7-mime smime parameter
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf-smime@imc.org, rohan@cisco.com
To: Blake Ramsdell <blake@brutesquadlabs.com>
From: Rohan Mahy <rohan@cisco.com>
Content-Transfer-Encoding: 7bit
Message-Id: <0A426B56-9894-11D7-861A-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.552)
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

At IETF 56, I presented about SIP's use of S/MIME and CMS. One of the 
suggestions that I received from the group was that SIP should use raw 
CMS instead of S/MIME.  In order to convey CMS types not used by S/MIME 
(especially AuthenticatedData), it would be very convenient to have a 
MIME type registration for CMS which incorporated these types.

When draft-ietf-smime-2633bis progresses, it will hold the MIME type 
registration for application/pkcs7-mime.  Today, we could represent 
authenticated data by using the smime-type parameter with the complete 
oid for authentcated data but that is very cumbersome.  It would be 
very convenient for future uses of CMS if the types were already 
defined with the application/pkcs7-mime MIME type.

I have included some proposed text to add the other CMS types to the 
smime-type mime parameter.  Alternatively a new cms-type mime parameter 
could be defined, but this seems a but pedantic to me.

thanks,
-rohan


from 2633bis:
> 3.2.2 The smime-type parameter
>
> The application/pkcs7-mime content type defines the optional "smime-
> type" parameter. The intent of this parameter is to convey details
> about the security applied (signed or enveloped) along with infomation
> about the contained content. This specification defines the following
> smime-types.
>
> Name                   CMS type                Inner Content
>
> enveloped-data         EnvelopedData           id-data
>
> signed-data            SignedData              id-data
>
> certs-only             SignedData              none
>
> compressed-data        CompressedData          id-data


Proposed replacement text follows:

3.2.2 The smime-type parameter

The application/pkcs7-mime content type defines the optional "smime-
type" parameter. The intent of this parameter is to convey details
about the security applied (signed or enveloped) along with infomation
about the contained content. This specification defines the following
smime-types. (For completeness all CMS types are defined, even
those not used by S/MIME)

Name                   CMS type                Inner Content

enveloped-data         EnvelopedData           id-data

signed-data            SignedData              id-data

certs-only             SignedData              none

compressed-data        CompressedData          id-data

authenticated-data     AuthenticatedData  *    id-data

digested-data          DigestedData       *    id-data

encrypted-data         EncryptedData      *    id-data

*Note that these CMS types are not used by S/MIME