New SMime Capabilities item

"Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com> Wed, 12 May 1999 04:04 UTC

Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08638 for <smime-archive@odin.ietf.org>; Wed, 12 May 1999 00:04:55 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id TAA08511 for ietf-smime-bks; Tue, 11 May 1999 19:57:32 -0700 (PDT)
Received: from doggate.exchange.microsoft.com (doggate.exchange.microsoft.com [131.107.88.55]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA08497; Tue, 11 May 1999 19:57:28 -0700 (PDT)
Received: by doggate.exchange.microsoft.com with Internet Mail Service (5.5.2232.9) id <JYW3AHYS>; Tue, 11 May 1999 19:59:46 -0700
Message-ID: <2FBF98FC7852CF11912A0000000000010ECB5F4A@DINO>
From: "Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com>
To: "Russ Housley (E-mail)" <housley@spyrus.com>
Cc: "Ietf-Smime (E-mail)" <ietf-smime@imc.org>, "Paul Hoffman (E-mail)" <phoffman@imc.org>
Subject: New SMime Capabilities item
Date: Tue, 11 May 1999 19:59:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>

Please add the following to the SMimeCapabilities section of the OIDs
document on IMC.ORG.

sMIMECapabilitiesVersions ::= {sMIMECapabilities 3}
SMIMECapabilitiesVersions ::= SEQUENCE OF INTEGER
--     SMime Capabilities Versions holds the sequence of S/MIME V3
specifications
--     understood by the client.   Currently the only two items legal values
are
--     v2 (S/MIME version 2) and v3 (S/MIME version 3).   If the item is
missing from a
--     capabilities list then V2 only should be assumed.


The current justification for this is that S/MIME V2 clients will probably
not understand the CMS encrypted data objects.  Specifically receipient
infos other than key transport and may not be able to decrypt the message at
all if other key managment algorithms are used in the message.

jim