IETF Logo Mail Archive

Re: [Acme] [Editorial Errata Reported] RFC8823 (7508)

richard@zotrus.com Fri, 05 May 2023 00:28 UTC

Return-Path: <richard@zotrus.com>
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 95022C1516E2 for <acme@ietfa.amsl.com>; Thu, 4 May 2023 17:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMVVC85EF5aM for <acme@ietfa.amsl.com>; Thu, 4 May 2023 17:28:44 -0700 (PDT)
Received: from out28-172.mail.aliyun.com (out28-172.mail.aliyun.com [115.124.28.172]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD1D2C1595FD for <acme@ietf.org>; Thu, 4 May 2023 17:28:42 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.08853253|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_system_inform|0.0231771-0.000823661-0.975999; FP=0|0|0|0|0|-1|-1|-1; HT=ay29a033018047188; MF=richard@zotrus.com; NM=1; PH=DS; RN=3; RT=3; SR=0; TI=SMTPD_---.SYGuHYn_1683246517;
Received: from CSRWDT202106(mailfrom:richard@zotrus.com fp:SMTPD_---.SYGuHYn_1683246517) by smtp.aliyun-inc.com; Fri, 05 May 2023 08:28:38 +0800
From: richard@zotrus.com
To: 'RFC Errata System' <rfc-editor@rfc-editor.org>
Cc: alexey.melnikov@isode.com, acme@ietf.org
References: <20230505000116.94627563F1@rfcpa.amsl.com>
In-Reply-To: <20230505000116.94627563F1@rfcpa.amsl.com>
Date: Fri, 05 May 2023 08:28:37 +0800
Message-ID: <004601d97ee8$891fdee0$9b5f9ca0$@zotrus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHO1WOOBs/sYOcJgaKsdavEeRq3ga9gJWmQ
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/k4Rf7P52eto7cHFKKxjs7y04MDs>
X-Mailman-Approved-At: Fri, 05 May 2023 02:25:17 -0700
Subject: Re: [Acme] [Editorial Errata Reported] RFC8823 (7508)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 May 2023 00:47:19 -0000

Sorry, missed another place in Figure 1 in the email body:
This is an automatically generated ACME challenge for email address "alexey@example.com".

It should be:

This is an automatically generated ACME challenge for email address "alexey@example.org"


Best Regards,

Richard Wang

-----Original Message-----
From: RFC Errata System <rfc-editor@rfc-editor.org> 
Sent: Friday, May 5, 2023 8:01 AM
To: rfc-editor@rfc-editor.org
Cc: richard@zotrus.com; alexey.melnikov@isode.com; acme@ietf.org
Subject: [Editorial Errata Reported] RFC8823 (7508)

The following errata report has been submitted for RFC8823, "Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates".

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

--------------------------------------
Type: Editorial
Reported by: Richard Wang <richard@zotrus.com>

Section: 3.1 and 3.2

Original Text
-------------
Figure 1:
  Message-ID: <A2299BB.FF7788@example.org>
  From: acme-generator@example.org
  To: alexey@example.com

Figure 2:
   Message-ID: <111-22222-3333333@example.com>
   In-Reply-To: <A2299BB.FF7788@example.org>
   From: alexey@example.com
   To: acme-generator@example.org

Corrected Text
--------------
Figure 1:
  Message-ID: <A2299BB.FF7788@example.com>
  From: acme-generator@example.com
  To: alexey@example.org

Figure 2:
   Message-ID: <111-22222-3333333@example.org>
   In-Reply-To: <A2299BB.FF7788@example.com>
   From: alexey@example.org
   To: acme-generator@example.com

Notes
-----
Accoording to RFC8555, the domain example.com used for ACME server, the example.org used for the Client.

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. 

--------------------------------------
RFC8823 (draft-ietf-acme-email-smime-14)
--------------------------------------
Title               : Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
Publication Date    : April 2021
Author(s)           : A. Melnikov
Category            : INFORMATIONAL
Source              : Automated Certificate Management Environment
Area                : Security
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email