Re: [Acme] [Editorial Errata Reported] RFC8555 (6104)

Aaron Gable <aaron@letsencrypt.org> Wed, 03 January 2024 17:07 UTC

Return-Path: <aaron@letsencrypt.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 A3C79C00A6B8 for <acme@ietfa.amsl.com>; Wed, 3 Jan 2024 09:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.org
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 eSD84bJILMIU for <acme@ietfa.amsl.com>; Wed, 3 Jan 2024 09:07:35 -0800 (PST)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 0D676C337C69 for <acme@ietf.org>; Wed, 3 Jan 2024 09:07:20 -0800 (PST)
Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3bbbd4d2b4aso5492828b6e.0 for <acme@ietf.org>; Wed, 03 Jan 2024 09:07:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; t=1704301639; x=1704906439; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/Yb3Tuqk7YtFUtzIRqhFpoQdatEmdbAkZPdx2CzHFXo=; b=QUiN5e7BiJKRO00IxfQ1M9ixV0Xw8lqJaUPIhofFVZStSvKQsG680vF5KmKwLu4fzw RsQ576Y6jaRdD19DsZU5WAWRx7mSJbvQ5PfkySnqNwjbLVoLV11sIRLjbLpY2h7lodDr hfT8acNXfCfVcLiwseaOeL2MbB0ZghOxe2Ki0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704301639; x=1704906439; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/Yb3Tuqk7YtFUtzIRqhFpoQdatEmdbAkZPdx2CzHFXo=; b=Pg9+yJirYLlECVPfCZGKJ/CGtB54A5/pM5NSNrpYvqnlX8unq8EvvNufhKPwfniScr lqwEHl0t00ftRTMaB+iWHvw4X7DZmI3m4zGYtErDyFhCw8Uo+8KgMjP3alMIH+Xu1aYe wPro6BIbbFK35cJSri/XG8IbQaUbJ+nrnKq4Kf61HUb9dpmGoJM/FvOJm5/Eco87jEJV P5ADRUGL/HnMLC/zkg1B/wPwBDu1KxNaJRnQJSyWExlGoVDUVRzWaBrp8iW+/LE/leLQ 51SRnAx6z0IVjd8tivv93AIUnZ+sMBAzb/coni34b6DBJy7E6wsdlh2SFUUQKs/wyn5l Zf3Q==
X-Gm-Message-State: AOJu0YzfEsdwsc27LQFj0LImKdFMt7O4JqfX0IbqCacGZq0vcfidFORX Z8BvQw644OpONu8R7aj7+hBqWgaGY4rTkNjQvi6Qeie4OwNj8o90DdtoOVxH
X-Google-Smtp-Source: AGHT+IElrkBZJaVkliFZnaogo12hgiSKAxahbKrm3Lq6uzAfkefO+RnjvnOCtoa13hevNgo8RRq/ZpKHcCAsbsPnV14=
X-Received: by 2002:a05:6870:d611:b0:204:fcc:6c19 with SMTP id a17-20020a056870d61100b002040fcc6c19mr17623366oaq.109.1704301639271; Wed, 03 Jan 2024 09:07:19 -0800 (PST)
MIME-Version: 1.0
References: <20200414105445.DA392F4071E@rfc-editor.org> <CAGgd1Oe1PNRse8nnj=YURU6FX+hoA4O7Jid=8N+K8D_KnZosyA@mail.gmail.com> <EE1DF596-662F-406F-ABC5-33592F5258F6@gmail.com>
In-Reply-To: <EE1DF596-662F-406F-ABC5-33592F5258F6@gmail.com>
From: Aaron Gable <aaron@letsencrypt.org>
Date: Wed, 03 Jan 2024 09:07:08 -0800
Message-ID: <CAEmnErf-9eMfcncFi-ymM7fzrY+toSAt_FWOzWpV_UAjb61a-Q@mail.gmail.com>
To: Seo Suchan <tjtncks@gmail.com>
Cc: acme@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cc9ea5060e0da5cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/cbQIL94cVmmaihRMIkopLI73CvI>
Subject: Re: [Acme] [Editorial Errata Reported] RFC8555 (6104)
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: Wed, 03 Jan 2024 17:07:39 -0000

It appears to me (and `git diff -w`) that the only difference between these
blocks is whitespace: the original has the code block outdented to the
leftmost column of each line, while the new version has the code block
starting in the same vertical column as the "in the problem document" text.

This does appear to be a mistake (the other code blocks in the document are
indented to match their surrounding text). It's purely editorial.

Aaron

On Wed, Jan 3, 2024 at 6:15 AM Seo Suchan <tjtncks@gmail.com> wrote:

> It's about line changes, errata added line change between type: and it's
> body
>
>
> On 2024년 1월 3일 오후 9시 11분 18초 GMT+09:00, Deb Cooley <debcooley1@gmail.com>
> 작성함:
>
>> Yet another errata....  My old eyes don't see what the change is.  All
>> the brackets look lined up the same in both original and corrected.  If
>> someone can point out where the change is, we can move this along. Or we
>> reject it.
>>
>> Deb
>>
>> On Tue, Apr 14, 2020 at 9:19 AM RFC Errata System <
>> rfc-editor@rfc-editor.org> wrote:
>>
>>> The following errata report has been submitted for RFC8555,
>>> "Automatic Certificate Management Environment (ACME)".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> https://www.rfc-editor.org/errata/eid6104
>>>
>>> --------------------------------------
>>> Type: Editorial
>>> Reported by: Theodor Nolte <nolte@dfn-cert.de>
>>>
>>> Section: 6.7.1
>>>
>>> Original Text
>>> -------------
>>>    in the problem document.
>>>
>>> HTTP/1.1 403 Forbidden
>>> Content-Type: application/problem+json
>>> Link: <https://example.com/acme/directory>;rel="index"
>>>
>>> {
>>>     "type": "urn:ietf:params:acme:error:malformed",
>>>     "detail": "Some of the identifiers requested were rejected",
>>>     "subproblems": [
>>>         {
>>>             "type": "urn:ietf:params:acme:error:malformed",
>>>             "detail": "Invalid underscore in DNS name \"_example.org\"",
>>>             "identifier": {
>>>                 "type": "dns",
>>>                 "value": "_example.org"
>>>             }
>>>         },
>>>         {
>>>             "type": "urn:ietf:params:acme:error:rejectedIdentifier",
>>>             "detail": "This CA will not issue for \"example.net\"",
>>>             "identifier": {
>>>                 "type": "dns",
>>>                 "value": "example.net"
>>>             }
>>>         }
>>>     ]
>>> }
>>>
>>> Corrected Text
>>> --------------
>>>    in the problem document.
>>>
>>>    HTTP/1.1 403 Forbidden
>>>    Content-Type: application/problem+json
>>>    Link: <https://example.com/acme/directory>;rel="index"
>>>
>>>    {
>>>        "type": "urn:ietf:params:acme:error:malformed",
>>>        "detail": "Some of the identifiers requested were rejected",
>>>        "subproblems": [
>>>            {
>>>                "type": "urn:ietf:params:acme:error:malformed",
>>>                "detail": "Invalid underscore in DNS name \"_example.org
>>> \"",
>>>                "identifier": {
>>>                    "type": "dns",
>>>                    "value": "_example.org"
>>>                }
>>>            },
>>>            {
>>>                "type": "urn:ietf:params:acme:error:rejectedIdentifier",
>>>                "detail": "This CA will not issue for \"example.net\"",
>>>                "identifier": {
>>>                    "type": "dns",
>>>                    "value": "example.net"
>>>                }
>>>            }
>>>        ]
>>>    }
>>>
>>> Notes
>>> -----
>>> The code block of the HTTP reply is not aligned.
>>>
>>> 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.
>>>
>>> --------------------------------------
>>> 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 mailing list
>>> Acme@ietf.org
>>> https://www.ietf.org/mailman/listinfo/acme
>>>
>> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>