This one came is as Editorial and was changed to Technical. I think we should make it Editorial.
There needs to be a complete list of places where .com and .org are swapped. At that point it can be 'Verified'. Deb On Tue, Oct 10, 2023 at 7:52 PM Chris Smiley <[email protected]> wrote: > > Hi Roman, > > We are unable to verify this erratum that the submitter marked as > editorial. > Please note that we have changed the “Type” of the following errata > report to “Technical”. As Stream Approver, please review and set the > Status and Type accordingly (see the definitions at > https://www.rfc-editor.org/errata-definitions/). > > You may review the report at: > https://www.rfc-editor.org/errata/eid7508 > > Please see https://www.rfc-editor.org/how-to-verify/ for further > information on how to verify errata reports. > > Further information on errata can be found at: > https://www.rfc-editor.org/errata.php. > > Thank you. > > RFC Editor/cs > > > > > On May 4, 2023, at 5:01 PM, RFC Errata System <[email protected]> > wrote: > > > > 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 <[email protected]> > > > > Section: 3.1 and 3.2 > > > > Original Text > > ------------- > > Figure 1: > > Message-ID: <[email protected]> > > From: [email protected] > > To: [email protected] > > > > Figure 2: > > Message-ID: <[email protected]> > > In-Reply-To: <[email protected]> > > From: [email protected] > > To: [email protected] > > > > Corrected Text > > -------------- > > Figure 1: > > Message-ID: <[email protected]> > > From: [email protected] > > To: [email protected] > > > > Figure 2: > > Message-ID: <[email protected]> > > In-Reply-To: <[email protected]> > > From: [email protected] > > To: [email protected] > > > > 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 > > > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
