Re: WGLC: p6 editorial nits

Mark Nottingham <mnot@mnot.net> Tue, 23 April 2013 06:16 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE68521F9601 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Apr 2013 23:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.503
X-Spam-Level:
X-Spam-Status: No, score=-10.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1jgVqi54kA8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Apr 2013 23:16:34 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id F0D9621F8ACE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 22 Apr 2013 23:16:33 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UUWW4-0000S6-1O for ietf-http-wg-dist@listhub.w3.org; Tue, 23 Apr 2013 06:15:48 +0000
Resent-Date: Tue, 23 Apr 2013 06:15:48 +0000
Resent-Message-Id: <E1UUWW4-0000S6-1O@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UUWW0-0000RE-2J for ietf-http-wg@listhub.w3.org; Tue, 23 Apr 2013 06:15:44 +0000
Received: from mxout-08.mxes.net ([216.86.168.183]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UUWVz-0005up-BO for ietf-http-wg@w3.org; Tue, 23 Apr 2013 06:15:44 +0000
Received: from [192.168.1.80] (unknown [118.209.190.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 53A1750A87; Tue, 23 Apr 2013 02:15:20 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5150B0F2.5020307@andrew.cmu.edu>
Date: Tue, 23 Apr 2013 16:15:18 +1000
Cc: ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF7F546F-AD86-4561-8F78-AC64C104EF89@mnot.net>
References: <5150B0F2.5020307@andrew.cmu.edu>
To: Ken Murchison <murch@andrew.cmu.edu>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass client-ip=216.86.168.183; envelope-from=mnot@mnot.net; helo=mxout-08.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.3
X-W3C-Hub-Spam-Report: AWL=-3.342, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UUWVz-0005up-BO 20cfe8f60213af3085bb6665a62186e4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: WGLC: p6 editorial nits
Archived-At: <http://www.w3.org/mid/DF7F546F-AD86-4561-8F78-AC64C104EF89@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17484
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 26/03/2013, at 7:17 AM, Ken Murchison <murch@andrew.cmu.edu> wrote:

> Hi All,
> 
> Sec 7.2, last sentence: "... otherwise stated otherwise." -> "... unless stated otherwise."

I think Julian has already taken care of this; thanks.

> I'm also wondering if draft-snell-http-prefer can have any effect on the cacheability of responses to PUT/POST, namely a response that includes Preference-Applied:return=representation.  Since the purpose of return=representation is to eliminate the need for a subsequent GET, it would seem to me that the response could be used to update a cache.  The current language in p2 and p6 doesn't appear to leave any wiggle room for an "extension" such as Prefer.  Of course, I'm the farthest thing from a HTTP cache expert and might have missed such text and/or don't understand the implications of allowing such a thing.

A new header can enhance the caching behaviour, just as a new cache-control directive can. However, it needs to be in a backwards compatible way; i.e., it can't place any requirements upon implementations that don't understand it.

We probably need a few words about this in p2's "considerations for new headers"; I have a few other suggestions there that I'll include it with.

Cheers,

--
Mark Nottingham   http://www.mnot.net/