IETF Logo Mail Archive

RE: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt

"Blake Ramsdell" <blake@brutesquadlabs.com> Fri, 26 March 2004 05:06 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 AAA15721 for <smime-archive@lists.ietf.org>; Fri, 26 Mar 2004 00:06:24 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.8) with ESMTP id i2Q4i1ob003350; Thu, 25 Mar 2004 20:44:01 -0800 (PST) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i2Q4i1XI003349; Thu, 25 Mar 2004 20:44:01 -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.11/8.12.8) with ESMTP id i2Q4i0rs003338 for <ietf-smime@imc.org>; Thu, 25 Mar 2004 20:44:00 -0800 (PST) (envelope-from blake@brutesquadlabs.com)
Received: from DEXTER ([192.168.0.6]) by brutesquadlabs.com with ESMTP ; Thu, 25 Mar 2004 20:44:00 -0800
From: Blake Ramsdell <blake@brutesquadlabs.com>
To: 'Russ Housley' <housley@vigilsec.com>, ietf-smime@imc.org
Subject: RE: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt
Date: Thu, 25 Mar 2004 20:44:00 -0800
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAtUAoCMhcQEOzgMbKmsO8XQEAAAAA@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
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <5.2.0.9.2.20040229235313.01f8f318@mail.binhost.com>
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: Russ Housley [mailto:housley@vigilsec.com] 
> Sent: Sunday, February 29, 2004 9:16 PM
> To: Blake Ramsdell; ietf-smime@imc.org
> Subject: Re: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt
> 
> 1.  Should Section 1.4 reference RFC 3369?

This section just describes where "prior practice of S/MIME" is located.
I think that RFC 3369 is "current practice of S/MIME".

> 2.  Delete section 1.6 before the document is sent to the IESG.

Deleted.

> 3.  Section 2.4 probably should point out that ContentInfo is 
> needed to 
> encapsulate each of the protection content types.

Hmm. I don't agree. This is meant to describe the subset of types that
are supported by S/MIME, independent of their encoding.

> 4.  What compression algorithm MUST be implemented if 
> CompressedData is 
> supported?

Has this train finished wrecking or is it still in progress?

> 5.  Section 2.5.2: s/SMIMECapabilities attribute 
> should/SMIMECapabilities 
> attribute SHOULD/

Fixed.

> 6.  Section 2.6:  the first two paragraphs are not clear.  
> S/MIME v3.1 MUST 
> support both issuerAndSerialNumber and subjectKeyIdentifier 
> for sending and 
> receiving.

S/MIME v3.1 implementations MUST support both issuerAndSerialNumber as
well as subjectKeyIdentifier. Messages that use the
subjectKeyIdentifier choice cannot be read by S/MIME v2 clients.

> 7.  Section 3.4.3.2: s/not currently supported in S/MIME/not 
> currently 
> recommended in S/MIME/

Fixed.

Blake

v2.23.0 | Report a Bug | By Email