Re: [pkix] Mail regarding draft-ietf-pkix-new-asn1

Paul Hoffman <phoffman@imc.org> Mon, 29 March 2010 00:08 UTC

Return-Path: <phoffman@imc.org>
X-Original-To: pkix@core3.amsl.com
Delivered-To: pkix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 948203A686B for <pkix@core3.amsl.com>; Sun, 28 Mar 2010 17:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.916
X-Spam-Level:
X-Spam-Status: No, score=-4.916 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 fpEEZmBotsgO for <pkix@core3.amsl.com>; Sun, 28 Mar 2010 17:08:33 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 6381D3A682E for <pkix@ietf.org>; Sun, 28 Mar 2010 17:08:33 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o2T08vjt070628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 28 Mar 2010 17:08:58 -0700 (MST) (envelope-from phoffman@imc.org)
Mime-Version: 1.0
Message-Id: <p0624080ac7d5a00c4ad1@[10.20.30.158]>
Date: Sun, 28 Mar 2010 17:08:54 -0700
To: "Leonberger, Pierce (US SSA)" <pierce.leonberger@baesystems.com>
From: Paul Hoffman <phoffman@imc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: pkix@ietf.org
Subject: Re: [pkix] Mail regarding draft-ietf-pkix-new-asn1
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2010 00:08:34 -0000

[[ I am Ccing the WG on this because someone has suggested a technical change to a WG consensus document in the RFC Editor's queue, and we intend to make that change. ]]

At 11:44 AM -0400 3/22/10, Leonberger, Pierce (US SSA) wrote:
>Shouldn't parameters be OPTIONAL in the SIGNED parameterized type?
>
>I believe the syntax should be:
>
>SIGNED{ToBeSigned} ::= SEQUENCE {
>     toBeSigned           ToBeSigned,
>     algorithmIdentifier  SEQUENCE {
>         algorithm        SIGNATURE-ALGORITHM.
>                              &id({SignatureAlgorithms}),
>         parameters       SIGNATURE-ALGORITHM.
>                              &Params({SignatureAlgorithms}
>                                  {@algorithmIdentifier.algorithm}) OPTIONAL
>     },
>
>     signature BIT STRING (CONTAINING SIGNATURE-ALGORITHM.&Value(
>                              {SignatureAlgorithms}
>                              {@algorithmIdentifier.algorithm}))
>  }
>
>

Good catch. Jim and I agree.