Re: [Editorial Errata Reported] RFC7838 (6480)

Julian Reschke <julian.reschke@greenbytes.de> Sat, 13 March 2021 10:24 UTC

Resent-Date: Sat, 13 Mar 2021 10:22:10 +0000
Resent-Message-Id: <E1lL1PO-0006lP-7f@lyra.w3.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>, mnot@mnot.net, mcmanus@ducksong.com, superuser@gmail.com, barryleiba@computer.org, tpauly@apple.com
Cc: lucaspardue.24.7@gmail.com, ietf-http-wg@w3.org
References: <20210312233241.8A61DF40743@rfc-editor.org>
From: Julian Reschke <julian.reschke@greenbytes.de>
Message-ID: <f30c6c4d-ca99-06e6-a03e-9e534d89eced@greenbytes.de>
Date: Sat, 13 Mar 2021 11:21:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <20210312233241.8A61DF40743@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Received-SPF: pass client-ip=5.10.171.186; envelope-from=julian.reschke@greenbytes.de; helo=mail.greenbytes.de
Subject: Re: [Editorial Errata Reported] RFC7838 (6480)
Archived-At: <https://www.w3.org/mid/f30c6c4d-ca99-06e6-a03e-9e534d89eced@greenbytes.de>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Am 13.03.2021 um 00:32 schrieb RFC Errata System:
> The following errata report has been submitted for RFC7838,
> "HTTP Alternative Services".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6480
> 
> --------------------------------------
> Type: Editorial
> Reported by: Lucas Pardue <lucaspardue.24.7@gmail.com>
> 
> Section: 2
> 
> Original Text
> -------------
> Formally, an alternative service is identified by the combination of:
> 
>     o  An Application Layer Protocol Negotiation (ALPN) protocol name, as
>        per [RFC7301]
> 
> Corrected Text
> --------------
> Formally, an alternative service is identified by the combination of:
> 
>     o  An Application-Layer Protocol Negotiation (ALPN) protocol name, as
>        per [RFC7301]
> 
> Notes
> -----
> RFC 7301 seems to formally use the hyphenated version. Most relevant to RFC 7838 is the ALPN ID registry, which RFC 7301 states:
> 
>     This document establishes a registry for protocol identifiers
>     entitled "Application-Layer Protocol Negotiation (ALPN) Protocol IDs"
> 
> 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.
> 
> --------------------------------------
> RFC7838 (draft-ietf-httpbis-alt-svc-14)
> --------------------------------------
> Title               : HTTP Alternative Services
> Publication Date    : April 2016
> Author(s)           : M. Nottingham, P. McManus, J. Reschke
> Category            : PROPOSED STANDARD
> Source              : HTTP
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG

A missing hyphen is, well, an error, but on a severity scale from 0 to 
10 it's clearly very close to 0.

I think "held for document update" is the right status here.

Best regards, Julian

-- 
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782

[Editorial Errata Reported] RFC7838 (6480) RFC Errata System
Re: [Editorial Errata Reported] RFC7838 (6480) Julian Reschke