- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Fri, 26 Oct 2018 04:51:52 +0000
- To: Mark Nottingham <mnot@mnot.net>, RFC Errata System <rfc-editor@rfc-editor.org>
- CC: "erik+ietf@nygren.org" <erik+ietf@nygren.org>, "ben@nostrum.com" <ben@nostrum.com>, "aamelnikov@fastmail.fm" <aamelnikov@fastmail.fm>, "adam@nostrum.com" <adam@nostrum.com>, "patrick.ducksong@gmail.com" <patrick.ducksong@gmail.com>, "lucaspardue.24.7@gmail.com" <lucaspardue.24.7@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Just to save Mark some typing on his phone, what he meant was probably: This is an issue in the html rendering, NOT IN the rfc text itself. The HTML version at https://tools.ietf.org/html/rfc8336 is based on heuristics, and heuristics sometimes fail. Regards, Martin. On 2018/10/26 05:37, Mark Nottingham wrote: > This is an issue in the html rendering, it the rfc text itself. > > Sent from my iPhone > >> On 26 Oct 2018, at 2:07 am, RFC Errata System <rfc-editor@rfc-editor.org> wrote: >> >> The following errata report has been submitted for RFC8336, >> "The ORIGIN HTTP/2 Frame".
Received on Friday, 26 October 2018 04:52:18 UTC