Re: Request change in son-of-rfc2633
Russ Housley <housley@vigilsec.com> Tue, 16 September 2003 14:15 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 KAA15639 for <smime-archive@lists.ietf.org>; Tue, 16 Sep 2003 10:15:12 -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 h8GDPLeo083937 for <ietf-smime-bks@above.proper.com>; Tue, 16 Sep 2003 06:25:21 -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 h8GDPL8W083936 for ietf-smime-bks; Tue, 16 Sep 2003 06:25:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [207.228.252.5]) by above.proper.com (8.12.9/8.12.8) with SMTP id h8GDPJeo083930 for <ietf-smime@imc.org>; Tue, 16 Sep 2003 06:25:20 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 25145 invoked by uid 0); 16 Sep 2003 13:25:07 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (141.156.181.78) by woodstock.binhost.com with SMTP; 16 Sep 2003 13:25:07 -0000
Message-Id: <5.2.0.9.2.20030916092428.031421a0@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 16 Sep 2003 09:25:18 -0400
To: jimsch@exmsft.com, blake@brutesquadlabs.com
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Request change in son-of-rfc2633
Cc: ietf-smime@imc.org
In-Reply-To: <001501c37c1b$705f4980$1400a8c0@augustcellars.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Good suggestion. Please incorporate this change. Russ At 11:26 PM 9/15/2003 -0700, Jim Schaad wrote: >In section 2.6, the text states that the choice must be >issuerAndSerialNumber. I don't have a problem with this, however I >think that text needs to be added as follows: > >"S/MIME v3.1 implemenations 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, but are not to cause crashes in S/MIME >v3.1 clients." > >jim
- 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