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

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
>>