Re: Request change in son-of-rfc2633
pgut001@cs.auckland.ac.nz (Peter Gutmann) Wed, 17 September 2003 13:50 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 JAA11257 for <smime-archive@lists.ietf.org>; Wed, 17 Sep 2003 09:50:57 -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 h8HDJ7eo099415 for <ietf-smime-bks@above.proper.com>; Wed, 17 Sep 2003 06:19:07 -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 h8HDJ7eC099414 for ietf-smime-bks; Wed, 17 Sep 2003 06:19:07 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from hermes.cs.auckland.ac.nz (hermes.cs.auckland.ac.nz [130.216.35.151]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h8HDJ5eo099408 for <ietf-smime@imc.org>; Wed, 17 Sep 2003 06:19:05 -0700 (PDT) (envelope-from pgut001@cs.auckland.ac.nz)
Received: from cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33]) by hermes.cs.auckland.ac.nz (8.12.9/8.12.9) with ESMTP id h8HDIqQA006897; Thu, 18 Sep 2003 01:18:52 +1200
Received: (from pgut001@localhost) by cs.auckland.ac.nz (8.11.6/8.11.6) id h8HDLTM11854; Thu, 18 Sep 2003 01:21:29 +1200
Date: Thu, 18 Sep 2003 01:21:29 +1200
Message-Id: <200309171321.h8HDLTM11854@cs.auckland.ac.nz>
From: pgut001@cs.auckland.ac.nz
To: jimsch@exmsft.com
Subject: Re: Request change in son-of-rfc2633
Cc: ietf-smime@imc.org
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>
"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? Peter.
- Request change in son-of-rfc2633 Jim Schaad
- Re: Request change in son-of-rfc2633 Russ Housley
- Re: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Blake Ramsdell
- RE: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Blake Ramsdell
- RE: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Blake Ramsdell
- RE: Request change in son-of-rfc2633 Russ Housley
- RE: Request change in son-of-rfc2633 Blake Ramsdell
- RE: Request change in son-of-rfc2633 Russ Housley
- RE: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Peter Gutmann
- RE: Request change in son-of-rfc2633 Russ Housley
- RE: Request change in son-of-rfc2633 Peter Gutmann
- Re: Request change in son-of-rfc2633 Steve Hanna
- RE: Request change in son-of-rfc2633 Santosh Chokhani
- Re: Request change in son-of-rfc2633 Peter Gutmann
- Re: Request change in son-of-rfc2633 Peter Gutmann