[Acme] [Editorial Errata Reported] RFC8555 (6276)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 03 September 2020 04:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 876CE3A044A for <acme@ietfa.amsl.com>; Wed, 2 Sep 2020 21:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xFgLKMEwQ4Mx for <acme@ietfa.amsl.com>; Wed, 2 Sep 2020 21:29:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08DB33A043A for <acme@ietf.org>; Wed, 2 Sep 2020 21:29:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3CD75F40776; Wed, 2 Sep 2020 21:29:05 -0700 (PDT)
To: rlb@ipv.sx, jsha@eff.org, cpu@letsencrypt.org, jdkasten@umich.edu, rdd@cert.org, kaduk@mit.edu, rsalz@akamai.com, ynir.ietf@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: james@manger.com.au, acme@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200903042905.3CD75F40776@rfc-editor.org>
Date: Wed, 02 Sep 2020 21:29:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/zN1sGuF85gJqVOVRtf7SsQ3Q4Fg>
X-Mailman-Approved-At: Thu, 03 Sep 2020 06:46:07 -0700
Subject: [Acme] [Editorial Errata Reported] RFC8555 (6276)
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: Thu, 03 Sep 2020 04:29:21 -0000

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

You may review the report below and at:

Type: Editorial
Reported by: James Manger <james@manger.com.au>

Section: 2

Original Text
For example, the CA might require a client requesting example.com to provision a DNS record under example.com or an HTTP resource under http://example.com.

Corrected Text
For example, the CA might require a client requesting example.org to provision a DNS record under example.org or an HTTP resource under http://example.org.

The spec consistently uses example.com for an ACME CA server, and example.org for a site requesting a certificate -- except in this sentence.

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. 

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