RE: New SMime Capabilities item
"Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com> Wed, 26 May 1999 00:31 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 UAA01729 for <smime-archive@odin.ietf.org>; Tue, 25 May 1999 20:31:24 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id QAA04563 for ietf-smime-bks; Tue, 25 May 1999 16:38:58 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA04559 for <ietf-smime@imc.org>; Tue, 25 May 1999 16:38:57 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0) id <K5PL82GM>; Tue, 25 May 1999 16:39:29 -0700
Message-ID: <2FBF98FC7852CF11912A0000000000010ECB5F96@DINO>
From: "Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com>
To: 'Russ Housley' <housley@spyrus.com>, "Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com>
Cc: "Ietf-Smime (E-mail)" <ietf-smime@imc.org>
Subject: RE: New SMime Capabilities item
Date: Tue, 25 May 1999 16:39:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="windows-1252"
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>
Russ,
I think the question you are asking is what is the OID for
sMIMECapabilities? It is already defined as:
sMIMECapabilities OBJECT IDENTIFIER ::= {iso(1) member-body(2)
-- us(840) rsadsi(113549) pkcs(1) pkcs-9(9) 15} -- -- [MSG]
If this is not the question you are asking, please be more explicit.
jim
-----Original Message-----
From: Russ Housley [mailto:housley@spyrus.com]
Sent: Tuesday, May 25, 1999 1:52 PM
To: Jim Schaad (Exchange)
Cc: Ietf-Smime (E-mail)
Subject: Re: New SMime Capabilities item
Jim:
What OID are you using?
Russ
At 07:59 PM 5/11/99 -0700, Jim Schaad (Exchange) wrote:
>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
>
- New SMime Capabilities item Jim Schaad (Exchange)
- Re: New SMime Capabilities item Russ Housley
- RE: New SMime Capabilities item Jim Schaad (Exchange)
- RE: New SMime Capabilities item Russ Housley
- RE: New SMime Capabilities item Blake Ramsdell