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

"Sean P. Turner" <turners@ieca.com> Tue, 02 March 2004 03:02 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 WAA25664 for <smime-archive@lists.ietf.org>; Mon, 1 Mar 2004 22:02:16 -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 i222k8YN069681; Mon, 1 Mar 2004 18:46:08 -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 i222k8vZ069680; Mon, 1 Mar 2004 18:46:08 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from smtp001.bizmail.yahoo.com (smtp001.bizmail.yahoo.com [216.136.172.125]) by above.proper.com (8.12.11/8.12.8) with SMTP id i222k788069674 for <ietf-smime@imc.org>; Mon, 1 Mar 2004 18:46:07 -0800 (PST) (envelope-from turners@ieca.com)
Received: from unknown (HELO ieca.com) (turners@ieca.com@218.37.226.73 with plain) by smtp001.bizmail.yahoo.com with SMTP; 2 Mar 2004 02:46:13 -0000
Message-ID: <4044BA02.3070207@ieca.com>
Date: Tue, 02 Mar 2004 11:44:50 -0500
From: "Sean P. Turner" <turners@ieca.com>
Organization: IECA, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Blake Ramsdell <blake@brutesquadlabs.com>
CC: ietf-smime@imc.org
Subject: Re: WG LAST CALL: draft-ietf-smime-rfc2633bis-07.txt
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAAAi98FZ4k0O8A68DLlOuMwEAAAAA@brutesquadlabs.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAARMPfbnbp50SwK3EZjypY2MKAAAAQAAAAAAi98FZ4k0O8A68DLlOuMwEAAAAA@brutesquadlabs.com>
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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

Only minor editorial comments (read NO show stoppers):
  1. Para 1.3, Certificate definition: Replace "distinguished name" with "name" the names are not always "distinguished."
  2. Para 1.3, Receiving agent, Sending agent, and S/MIME agent definitions: Capitalize 1st word "software" and "user."
  3. Para 2.2, Last paragraph last sentence: replace "and may not implement id-dsa-with-sha1 at all" with "and may not implement id-dsa-with-sha1 or id-sha at all."
  4. Para 2.4.2, SignedData Content Type: Can we add a sentence that says "Applying a signature to message provides authentication, message integrity, and non-repudiation of origin."  The other content types indicate what "services" they support or don't support.
  5. Para 2.4.4, 2nd sentence: Replace "This content type does not provide authentication or privacy" with "This content type does not provide authentication, message integrity, non-repudiation, or data confidentiality".  Just making it match the "services" listed in the introduction.
  6. Para 3.1, Steps 1-4: Add periods to end of sentences.
  7. Para 3.1.3, 3rd Para 2nd sentence: Replace "8-bit clear" with "8-bit clean" to match terminology in 3.1.2 2nd paragraph 4 sentence.
  8. Para 3.3, Step 2, last sentence: Replace "(see CMS Section 6)" with (see [CMS] Section 6).
  9. Para 3.4.2, Steps 1&2: Add periods to end of sentences.
  10. Compressed data text in 3.5 points to 3.1 but there's no mention in 3.1 of compression.  You should either add a sentence to say that in 3.1 enveloped = compression in this section or make the following changes (or others to clarify that you also mean to refer to compression data):
    1. Para 3.1, Title: Replace "Signing or Enveloping" with "Signing, Enveloping, or Compressing" because para 3.5 says perform message as in 3.1 but there's not mention of compressing in 3.1.
    2. Para 3.1, 1st para 1st sentence: Replace "S/MIME is used to secure MIME entities" with "S/MIME is used to secure and optionally compress MIME entities."
    3. Para 3.1, 2nd para 1st sentence: Replace "The MIME entity that is secured and ..." with "The MIME entity that is secured or compressed and ..."
    4. Para 3.1, 4th para 1st sentence: Replace "A single procedure is used for creating MIME entities that are to be signed, enveloped, or both signed and enveloped" with "A single procedure is used for creating MIME entities that are to be signed, enveloped, compressed and both signed and enveloped, signed and compressed, compressed and enveloped, and compressed, signed, and enveloped, etc." (or whatever # of combinations you feel like listing)
    5. Para 3.1, 4th para 3rd sentence: Replace "It is recommended that these additional steps be performed on enveloped messages, or signed and enveloped messages" with "It is recommended that these additional steps be performed on enveloped and compressed messages, or signed and enveloped messages or compressed, signed and enveloped messages."
    6. Para 3.1, 1st para after Step 3: Replace "the security services on the message are processed" with "the security services or compression on the message are processed"
    7. Para 3.5, Step 1: Replace "to be enveloped" with "to be compressed".
  11. Para 3.7, Step 3: Add period to end of sentence.
  12. Annex F, Remove prior to submission to IESG (?)