Re: [pkix] [Technical Errata Reported] RFC7030 (5108)

Sean Turner <sean@sn3rd.com> Thu, 07 September 2017 20:40 UTC

Return-Path: <sean@sn3rd.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 CD2E61329B5 for <pkix@ietfa.amsl.com>; Thu, 7 Sep 2017 13:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 m-y0m2iz8zkn for <pkix@ietfa.amsl.com>; Thu, 7 Sep 2017 13:40:30 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D74831201F8 for <pkix@ietf.org>; Thu, 7 Sep 2017 13:40:29 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id h15so2125051qta.4 for <pkix@ietf.org>; Thu, 07 Sep 2017 13:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+ymGBnf+cxVQDW//cO/H3uUXdTrHMHoo1vy6I5ozq4U=; b=Z4Fc7a2sRfL+MF4blJEOG/Jj917xf532xcWFjY+YhYAh7MKADzJca6WYCvjDr+D3js BwznF66Id9xjRiwx4iyBLPk7ZMachHfvaqMywnm5VDSn2yM/74Oo5bv3Aym4RSq4msUj 8RhR4gS4MVPmlOz6GV8KX5/cAbGieLrbAHCzs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+ymGBnf+cxVQDW//cO/H3uUXdTrHMHoo1vy6I5ozq4U=; b=ihZwYrGmoGgGPJDhSOVYA/F5NXIZQsBEJb4UoF37gWHL+QUPA/wkHd22fooKnKRRAm ZnwhHPiyZ0UmToaWCsMthX1XP5dc2GYFFsA/QytIJ1lpF3Xos8W0PUHQ34wHjfJtgV1T hxWbnJ7Bt9kNL7peGo3yLGicOCDLxbvI94qYFQtHJ4D9nISTHZwMHCZXdjeHdFkxUXIq 4jR8Nzsm3UA+75i4FMC5Lc2zwoV+vY73t+C/vXMeIbdCwi6/YgBtP5mw950TZyiPTLSb M7ayqGQxLqwkQkuMes+0vaALNyJmEzpzqZYFVo9v9WunfPLpGv3Dmo+oOCHZJzOOfySS 0UWQ==
X-Gm-Message-State: AHPjjUieb5ZdkvY6ZBGDhxkzoK0nlF7PR1c5VOcT60AhuZiBSNlLCmBy r/vti3UmCqRmCgSef/8DcA==
X-Google-Smtp-Source: AOwi7QCxgm2r4czBa8zNBkapRPWooNXJ8TnfdV224rKRUgTFN9YRKN+nX4dFisUNEmCsx4eyV4JseA==
X-Received: by 10.237.35.238 with SMTP id k43mr964387qtc.214.1504816828676; Thu, 07 Sep 2017 13:40:28 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.223.191]) by smtp.gmail.com with ESMTPSA id s43sm162197qta.31.2017.09.07.13.40.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Sep 2017 13:40:27 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <20170907201944.D97B7B8178F@rfc-editor.org>
Date: Thu, 7 Sep 2017 16:40:26 -0400
Cc: Max Pritikin <pritikin@cisco.com>, Peter Yee <peter@akayla.com>, Daniel Harkins <dharkins@arubanetworks.com>, Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, Stephen Kent <kent@alum.mit.edu>, Stefan Santesson <stefan@aaa-sec.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C273AA78-C22F-409D-91A6-7B4E1D8A340F@sn3rd.com>
References: <20170907201944.D97B7B8178F@rfc-editor.org>
To: PKIX <pkix@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/eyXF_u1-tgHqFA6B6vB109GjC0s>
Subject: Re: [pkix] [Technical Errata Reported] RFC7030 (5108)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 07 Sep 2017 20:40:32 -0000

Note that this issue was discovered during IESG review of draft-turner-est-extensions.  Alexey, Panos, Dan, Max, and myself worked on the wording.  I’m hoping it can stew for a couple of days and then be marked as accepted.

spt

> On Sep 7, 2017, at 16:19, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC7030,
> "Enrollment over Secure Transport".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5108
> 
> --------------------------------------
> Type: Technical
> Reported by: Sean Turner <sean@sn3rd.com>
> 
> Section: 4.2.3, 4.4.2
> 
> Original Text
> -------------
> OLD from s.4.2.3:
> 
>  If the content-type is not set, the response data MUST be a plaintext
>  human-readable error message containing explanatory information
>  describing why the request was rejected (for example, indicating that
>  CSR attributes are incomplete).
> 
> OLD from s4.4.2:
> 
>  If the content-type is not set, the response data MUST be a plaintext
>  human-readable error message.
> 
> Corrected Text
> --------------
> NEW for s4.2.3:
> 
>  If the content-type is not set, the response data must be a plaintext
>  human-readable error message containing explanatory information
>  describing why the request was rejected (for example, indicating that
>  CSR attributes are incomplete).  Servers MAY use the "text/plain”
>  content-type [RFC2046] for human-readable errors.
> 
> NEW for s4.4.2:
> 
>  If the content-type is not set, the response data must be a plaintext
>  human-readable error message. Servers MAY use the "text/plain”
>  content-type [RFC2046] for human-readable errors.
> 
> Notes
> -----
> The current text is somewhat unclear as to what content-type needs to be used for the human-readable error.  There are many human-readable content-types, but "text/plain" seems to be the most sensible.
> 
> Note that the MUST was reduced to a must because no content-type is specified.
> 
> 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  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC7030 (draft-ietf-pkix-est-09)
> --------------------------------------
> Title               : Enrollment over Secure Transport
> Publication Date    : October 2013
> Author(s)           : M. Pritikin, Ed., P. Yee, Ed., D. Harkins, Ed.
> Category            : PROPOSED STANDARD
> Source              : Public-Key Infrastructure (X.509)
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG