[pkix] [Errata Held for Document Update] RFC7030 (5108)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 19 August 2020 20:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 970403A0A65; Wed, 19 Aug 2020 13:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level:
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 DJ3NXzQqpx4s; Wed, 19 Aug 2020 13:00:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E9A73A0A64; Wed, 19 Aug 2020 13:00:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C29B4F4078B; Wed, 19 Aug 2020 13:00:37 -0700 (PDT)
To: sean@sn3rd.com, pritikin@cisco.com, peter@akayla.com, dharkins@arubanetworks.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rdd@cert.org, iesg@ietf.org, pkix@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200819200037.C29B4F4078B@rfc-editor.org>
Date: Wed, 19 Aug 2020 13:00:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/06cgaRAQw2sk5qPZzD3WxdcRRXc>
Subject: [pkix] [Errata Held for Document Update] RFC7030 (5108)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Aug 2020 20:00:57 -0000
The following errata report has been held for document update for RFC7030, "Enrollment over Secure Transport". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5108 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Sean Turner <sean@sn3rd.com> Date Reported: 2017-09-07 Held by: Roman Danyliw (IESG) 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. -------------------------------------- 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
- [pkix] [Errata Held for Document Update] RFC7030 … RFC Errata System