IETF Logo Mail Archive

[httpwg/http-extensions] Julian's CH feedback (#359)

HTTP issue updates <http-issues@ietf.org> Tue, 20 June 2017 00:16 UTC

Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level:
X-Spam-Status: No, score=-9.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Date: Mon, 19 Jun 2017 17:16:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497917819; bh=mkXC7dzd4CrpwoPSbbyWseJ1kL66whKUiBpS+svJIwo=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=qCTt/EkuKOvDzxdg97/d3GUpJasc4t9kMtLTR++z0NkcbnDP/PxFQx4zY1tLTrgd4 +HjjJmOSmgc/pryGm+SAlYu187dAGBAWQr067cLuYbLsHrx502iAizMBztCyqPZLZ6 QQbyYodEy8/Wxqj7ShV5bhT0gi5fKRSTxKoHY/lU=
To: httpwg/http-extensions <http-extensions@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [httpwg/http-extensions] Julian's CH feedback (#359)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5948697bbc585_54413f866bf5dc384243"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-issues/Js1Jgk5FWiSX8xWu6DZ8D59RO3E>
Message-ID: <mailman.2209.1497917823.31347.http-issues@ietf.org>
From: HTTP issue updates <http-issues@ietf.org>
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates <http-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-issues>, <mailto:http-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-issues/>
List-Post: <mailto:http-issues@ietf.org>
List-Help: <mailto:http-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-issues>, <mailto:http-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2017 00:17:03 -0000

http://www.w3.org/mid/624e3e87-43bc-0dc2-d38c-2d69cbb9e93b@gmx.de

Most of this is editorial, so you can dispose of it as you see fit (although some of it is likely to come back up in IETF LC if not addressed. The exceptions are **bold**; I think we need to give some sort of response to those.

* [ ] Througout: avoid lowercase BCP14 keywords (may->can, should->ought to, ...), or actually invoke the new boilerplate defined in draft-leiba-rfc2119-update.
* [ ] s/headers/header fields/
* [ ] **It's not optimal to mention a draft that for now is work in progress so close to a "MUST", even with "optionally" sprinkled in. My recommendation continues to move all material that refers to the Key header field to an appendix.**
* [ ] s/defines/defines the/
* [ ] We should define "origin" somewhere (and also explain "subresource").
* [ ] Througout: uppercase "header field" in section titles.
* [ ] Isn't that evident because sending the hints is purely OPTIONAL anyway?
* [ ] **Why aren't we using HTTP list syntax here? Also, what does it mean when the field appears more than once?**
* [ ] I would rename this to "CSSVAL" (or something like that) for readability.
* [ ] I would rename this to "HTML5" (or something like that) for readability. 
* [ ] I would rename this to "KEY" (or something like that) for readability. 
* [ ] Finally: no Acknowledgements?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/359

v2.23.0 | Report a Bug | By Email