- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Mon, 15 Mar 2021 03:56:18 -0700 (PDT)
- To: lucaspardue.24.7@gmail.com, mnot@mnot.net, mcmanus@ducksong.com, julian.reschke@greenbytes.de
- Cc: francesca.palombini@ericsson.com, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been held for document update
for RFC7838, "HTTP Alternative Services".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6480
--------------------------------------
Status: Held for Document Update
Type: Editorial
Reported by: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date Reported: 2021-03-12
Held by: Francesca Palombini (IESG)
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"
--------------------------------------
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
Received on Monday, 15 March 2021 10:56:36 UTC