Re: [pkix] [Technical Errata Reported] RFC4211 (4797)

Megan Ferguson <mferguson@amsl.com> Tue, 13 September 2016 22:29 UTC

Return-Path: <mferguson@amsl.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F417912B0AC for <pkix@ietfa.amsl.com>; Tue, 13 Sep 2016 15:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.129
X-Spam-Level:
X-Spam-Status: No, score=-4.129 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-Zr-25VZKUd for <pkix@ietfa.amsl.com>; Tue, 13 Sep 2016 15:29:37 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0FAC12B0CD for <pkix@ietf.org>; Tue, 13 Sep 2016 15:29:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 33A781E5A0B; Tue, 13 Sep 2016 15:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHhYmI2Jd415; Tue, 13 Sep 2016 15:24:04 -0700 (PDT)
Received: from [192.168.0.5] (cpe-76-174-176-44.socal.res.rr.com [76.174.176.44]) by c8a.amsl.com (Postfix) with ESMTPA id D9E6C1E5A07; Tue, 13 Sep 2016 15:24:03 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <CANNx7D_NPPYOekz4yOv7N-dE9Fa5VBkWKay2ADNQdS91YwP=GA@mail.gmail.com>
Date: Tue, 13 Sep 2016 15:29:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9BA9F51-76DC-4B6D-88A7-684B50A942A7@amsl.com>
References: <20160908140059.7EF20B80BD6@rfc-editor.org> <CANNx7D_NPPYOekz4yOv7N-dE9Fa5VBkWKay2ADNQdS91YwP=GA@mail.gmail.com>
To: Lijun Liao <lijun.liao@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/m-phZqhY_R4vqR56jhAjhLV-2Vs>
Cc: Stefan Santesson <stefan@aaa-sec.com>, jimsch@exmsft.com, pkix@ietf.org, RFC System <rfc-editor@rfc-editor.org>
Subject: Re: [pkix] [Technical Errata Reported] RFC4211 (4797)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Sep 2016 22:29:40 -0000

Lijun,

We have edited this report to contain your correction in the Notes field as requested.

Thank you.

RFC Editor/mf

On Sep 8, 2016, at 7:16 AM, Lijun Liao <lijun.liao@gmail.com> wrote:

> Just correction:
> 
> The Notes should be as follows:
> ------------------------------------------
> 
> The original text conflicts with the following text block (just several lines later).
> 
> "     The fields of POPOSigningKey have the following meaning:
>       ...
>  
>       signature contains the POP value produce.  If poposkInput is
>       present, the signature is computed over the DER-encoded value of
>       poposkInput.  If poposkInput is absent, the signature is computed
>       over the DER-encoded value of certReq."
> 
> 
> On Thu, Sep 8, 2016 at 4:00 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> The following errata report has been submitted for RFC4211,
> "Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4211&eid=4797
> 
> --------------------------------------
> Type: Technical
> Reported by: Lijun Liao <lijun.liao@gmail.com>
> 
> Section: 4.1
> 
> Original Text
> -------------
>    3.  The certificate subject places its name in the Certificate
>        Template structure along with the public key.  In this case the
>        poposkInput field is omitted from the POPOSigningKey structure.
>        The signature field is computed over the DER-encoded certificate
>        template structure.
> 
> Corrected Text
> --------------
>    3.  The certificate subject places its name in the Certificate
>        Template structure along with the public key.  In this case the
>        poposkInput field is omitted from the POPOSigningKey structure.
>        The signature field is computed over the DER-encoded value of
>        certReq
> 
> Notes
> -----
> The original text conflicts with the following text block (just several lines later).
> 
> "   The fields of POPOSigningKeyInput have the following meaning:
> 
>       sender contains an authenticated identity that has been previously
>       established for the subject.
> 
>       publicKeyMAC contains a computed value that uses a shared secret
>       between the CA/RA and the certificate requestor.
> 
>       publicKey contains a copy of the public key from the certificate
>       template.  This MUST be exactly the same value as is contained in
>       the certificate template."
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC4211 (draft-ietf-pkix-rfc2511bis-08)
> --------------------------------------
> Title               : Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)
> Publication Date    : September 2005
> Author(s)           : J. Schaad
> Category            : PROPOSED STANDARD
> Source              : Public-Key Infrastructure (X.509)
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 
> 
> 
> 
> -- 
> Lijun Liao