[Acme] [Errata Held for Document Update] RFC8555 (5979)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 24 February 2020 17:45 UTC

To: jonathan@findmeon.com, rlb@ipv.sx, jsha@eff.org, cpu@letsencrypt.org, jdkasten@umich.edu
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: <20200224174520.49102F4071A@rfc-editor.org>
Date: Mon, 24 Feb 2020 09:45:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/Ne9Gmkl2xyfnb8rZngg9YedY0SU>
Subject: [Acme] [Errata Held for Document Update] RFC8555 (5979)
Precedence: list

The following errata report has been held for document update
for RFC8555, "Automatic Certificate Management Environment (ACME)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5979

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: jonathan vanasco <jonathan@findmeon.com>
Date Reported: 2020-02-11
Held by: Benjamin Kaduk (IESG)

Section: 7.4

Original Text
-------------
If the server is willing to issue the requested certificate, it
responds with a 201 (Created) response. The body of this response is
an order object reflecting the client's request and any
authorizations the client must complete before the certificate will
be issued.

Corrected Text
--------------
If the server is willing to issue the requested certificate, it
responds with a 201 (Created) response. The body of this response is
an order object reflecting the client's request and any
authorizations the client must complete before the certificate will
be issued. The server returns an order URL in a Location header field.

Notes
-----
The RFC does not specify/require where the "order URL" is presented. The RFC is very explicit about where other URLs are obtained, and the common understanding is that the URL appears in a Location header after a new-order.

For example:

In 7.3; 7.3.1; 7.3.5, the RFC explicitly declares the account URL is in the Location header field.

In 7.4.1 the RFC is explicit that authorization URLs in pre-authorization appear in the Location header field.

But the order URL is only mentioned by example:

In 7.4, the RFC illustrates the order URL appearing in the Location header field (All clients seem to implement this). In 7.1, the RFC shows a table with "a typical sequence of requests" that note the "account" and "order" URLs appear in the location header field.

The specification should state something to the effect of "The server returns an order URL in a Location header field." making this functionality explicit.

--------------------------------------
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 Held for Document Update] RFC8555 … RFC Errata System