IETF Logo Mail Archive

RE: Request change in son-of-rfc2633

"Blake Ramsdell" <blake@brutesquadlabs.com> Mon, 27 October 2003 02:25 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 VAA08497 for <smime-archive@lists.ietf.org>; Sun, 26 Oct 2003 21:25:25 -0500 (EST)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9R1rlI7049319 for <ietf-smime-bks@above.proper.com>; Sun, 26 Oct 2003 17:53:47 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id h9R1rl52049318 for ietf-smime-bks; Sun, 26 Oct 2003 17:53:47 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from brutesquadlabs.com (gtec136-m.isomedia.com [207.115.67.136] (may be forged)) by above.proper.com (8.12.10/8.12.8) with ESMTP id h9R1rkI7049310 for <ietf-smime@imc.org>; Sun, 26 Oct 2003 17:53:46 -0800 (PST) (envelope-from blake@brutesquadlabs.com)
Received: from DEXTER ([192.168.0.12]) by brutesquadlabs.com with ESMTP ; Sun, 26 Oct 2003 17:53:43 -0800
From: Blake Ramsdell <blake@brutesquadlabs.com>
To: 'Peter Gutmann' <pgut001@cs.aucKland.ac.nz>, jimsch@exmsft.com
Cc: ietf-smime@imc.org
Subject: RE: Request change in son-of-rfc2633
Date: Sun, 26 Oct 2003 17:53:42 -0800
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAAz5qwJQBbUqJpT0dUDuYkgEAAAAA@brutesquadlabs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <200309171321.h8HDLTM11854@cs.auckland.ac.nz>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
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

> -----Original Message-----
> From: owner-ietf-smime@mail.imc.org 
> [mailto:owner-ietf-smime@mail.imc.org] On Behalf Of Peter Gutmann
> Sent: Wednesday, September 17, 2003 6:21 AM
> To: jimsch@exmsft.com
> Cc: ietf-smime@imc.org
> Subject: Re: Request change in son-of-rfc2633
> 
> "Jim Schaad" <jimsch@nwlink.com> writes:
> 
> >Messages that use this choice cannot be read by S/MIME v2 
> clients, but are
> >not to cause crashes in S/MIME v3.1 clients."
> 
> I'm having some trouble parsing this... does this mean the 
> RFC is specifying
> that S/MIME clients aren't allowed to crash?   How is this enforced?

The language that has been added is as follows:

S/MIME v3.1 implementations MUST allow for the use of the choice of
subjectKeyIdentifier in messages. Messages that use this choice cannot
be read by S/MIME v2 clients, and MUST be handled gracefully in S/MIME
v3.1 clients.

So I imagine that we're now chartered with enforcing them to be graceful
vs. enforcing them to not crash ;).

Blake

v2.28.0 | Report a Bug | By Email | System Status