[Acme] [Errata Rejected] RFC8555 (5771)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 17 July 2019 17:27 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB4531207E8; Wed, 17 Jul 2019 10:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 KqPf07i9QTZM; Wed, 17 Jul 2019 10:27:11 -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 55C5A1207E7; Wed, 17 Jul 2019 10:27:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 127DAB8176E; Wed, 17 Jul 2019 10:27:07 -0700 (PDT)
To: rob@sectigo.com, rlb@ipv.sx, jsha@eff.org, cpu@letsencrypt.org, jdkasten@umich.edu
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: kaduk@mit.edu, iesg@ietf.org, acme@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190717172707.127DAB8176E@rfc-editor.org>
Date: Wed, 17 Jul 2019 10:27:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/V8EXfhDdY7rgRbIBhFeXLt5hL20>
Subject: [Acme] [Errata Rejected] RFC8555 (5771)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2019 17:27:14 -0000
The following errata report has been rejected for RFC8555, "Automatic Certificate Management Environment (ACME)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5771 -------------------------------------- Status: Rejected Type: Technical Reported by: Rob Stradling <rob@sectigo.com> Date Reported: 2019-07-02 Rejected by: Benjamin Kaduk (IESG) Section: 7.1.1 Original Text ------------- Clients access the directory by sending a GET request to the directory URL. Corrected Text -------------- Clients access the directory by sending a GET request to the directory URL. Before making a request to any URL from the directory, the client MUST evaluate whether the directory object is still fresh according to the Cache-Control header(s) received when that directory object was accessed. If no Cache-Control header(s) were received, the client MUST act as if "Cache-Control: no-cache" was received. If the directory object is no longer fresh, the client MUST access the directory again (by sending another GET request to the directory URL) and then use the updated directory object. Notes ----- The original text is underspecified, because it doesn't say how long a directory remains valid. A server should be able to update its directory (e.g., to add support for newAuthz, to update the termsOfService URL, etc) without having to worry about clients holding on to stale directory objects. Whilst in practice many clients tend to re-fetch the server's directory object frequently, I think that it's unwise to leave this to chance. --VERIFIER NOTES-- WG consensus per the thread including https://mailarchive.ietf.org/arch/msg/acme/I2oeALKJTyCwlMOp1v9BTadahyE is to reject the proposed erratum. -------------------------------------- RFC8555 (draft-ietf-acme-acme-18) -------------------------------------- Title : Automatic Certificate Management Environment (ACME) Publication Date : March 2019 Author(s) : R. Barnes, J. Hoffman-Andrews, D. McCarney, J. Kasten Category : PROPOSED STANDARD Source : Automated Certificate Management Environment Area : Security Stream : IETF Verifying Party : IESG
- [Acme] [Errata Rejected] RFC8555 (5771) RFC Errata System