Re: [Gen-art] Gen-art review of draft-ietf-smime-multisig-04.txt

"Turner, Sean P." <turners@ieca.com> Mon, 10 March 2008 15:54 UTC

Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: ietfarch-gen-art-archive@core3.amsl.com
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D144228C5BB; Mon, 10 Mar 2008 08:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.311
X-Spam-Level:
X-Spam-Status: No, score=-100.311 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZhtmfJXaySF; Mon, 10 Mar 2008 08:54:22 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65FAA28C69B; Mon, 10 Mar 2008 08:34:14 -0700 (PDT)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E64328C41A for <gen-art@core3.amsl.com>; Mon, 10 Mar 2008 08:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqWf5Ari4pJR for <gen-art@core3.amsl.com>; Mon, 10 Mar 2008 08:34:11 -0700 (PDT)
Received: from smtp109.biz.mail.mud.yahoo.com (smtp109.biz.mail.mud.yahoo.com [68.142.201.178]) by core3.amsl.com (Postfix) with SMTP id 8ACFF28D974 for <gen-art@ietf.org>; Mon, 10 Mar 2008 08:08:18 -0700 (PDT)
Received: (qmail 75345 invoked from network); 10 Mar 2008 15:05:58 -0000
Received: from unknown (HELO Wylie) (turners@ieca.com@130.129.18.223 with login) by smtp109.biz.mail.mud.yahoo.com with SMTP; 10 Mar 2008 15:05:57 -0000
X-YMail-OSG: ewDYfbAVM1lHAF_2tMzfEdFNZsDMdWYSGrXlkaYBJqhxXOdUEozdy6A0w8LH19Ftdxp.6zgqRg--
X-Yahoo-Newman-Property: ymail-3
From: "Turner, Sean P." <turners@ieca.com>
To: 'Elwyn Davies' <elwynd@dial.pipex.com>, 'General Area Review Team' <gen-art@ietf.org>
References: <47D18547.4050905@dial.pipex.com>
Date: Mon, 10 Mar 2008 10:58:16 -0400
Organization: IECA, Inc.
Message-ID: <005501c882bf$2ca8bf00$df128182@Wylie>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AciAfrkdeq24XAdrRDGrLe6YnKAauACPPCfQ
In-Reply-To: <47D18547.4050905@dial.pipex.com>
Cc: 'IETF Discussion' <ietf@ietf.org>, jimsch@exmsft.com, smime-chairs@tools.ietf.org, smime-ads@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-smime-multisig-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Elwyn,

Thanks for the review. Responses inline... 

spt

>-----Original Message-----
>Comments:
>s3:  The first part of the specification for MultipleSignatures is :
>
>>    The fields in MultipleSignatures have the following meaning:
>>
>>      - bodyHashAlg includes the digest algorithmIdentifier for the
>>      referenced multiple-signatures attribute.
>>
>>      - signAlg includes the signature algorithmIdentifier for the
>>      referenced multiple-signatures attribute.
>>
>I am confused by the use of 'includes' here: Do these specs 
>imply that the values of these fields are comma separated 
>lists of all relevant alg identifiers for the signatures?  An 
>example with three signatures might clarify what is going on, 
>but the spec should be clarified in any case, I think (but I 
>may just not be sufficiently knowledgable about this sort of spec).

The attribute is multivalued (discussed before the ASN.1) so there is a set
of values for each signature applied. The reason for only using two in the
example was purely based on page real estate.

>Editorial:
>idnits reports a clean bill of health.
>
>Abstract: Expand CMS acronym.

fixed

>s5: s/in a singled/in a single/

fixed

>s5.2: s/the rquire application/the required application/

fixed

>s5.3, para 5: The first sentence
>>
>> If signatures are added for the support of [ESS] features, then the
>>    fact that an outer layer signature can be treated as a non-
>>    significant failure.
>>
>does not parse.  Probably missing 'is invalid' or some such 
>relating to outer layer signature.

fixed

>Appendix B: 'hashes CMS'??? Does not parse!

fixed (reword)

>B.1: s/is needed/are needed/

fixed (reword)

>B.2 1/a/ii: s/Reistance/Resistance/

fixed

>B.2 1/c/iii: s/success/successful/

fixed

>B.2 2: Expand DER acronym.

fixed

>B.2: is not normative but uses SHOULD NOT.

fixed

>B.2 (2nd para on p18): s/that the attack/than the attack/

fixed

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art