- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 14 Apr 2021 16:29:30 +0200
- To: ietf-http-wg@w3.org
Am 01.04.2021 um 19:31 schrieb Tommy Pauly: > ... OK, I re-read the spec, and found some editorial nits (see mails, issues, and PRs). The main class of editorial issues I found is the way bcp56bis refers to HTTP base (semantics) spec. One could see bcp56bis as a document *about* http-semantics, so essentially *all* of it refers to it in some way. That means that when it does want to refer to a *specific* part of HTTP, it should do so by actually telling the reader where *exactly* to look (that is, by Section number). I opened a few PRs for that, but I'M pretty sure there are some cases of unspecific references left. There's another procedural issue: this document has been waiting for the http-core specs for ~ 1.5 years alreads. These are now in the hands of the IESG. However, it also has a reference to rfc6265bis (cookies). I believe it would be better to refer to RFC 6265 (as the update isn't really relevant for BCP56bis), so that *this* document has a chance to get published soon after the http core specs. Best regards, Julian
Received on Wednesday, 14 April 2021 14:29:45 UTC