Re: [apps-discuss] FYI: LCI -02

Mark Nottingham <mnot@mnot.net> Mon, 04 June 2012 10:34 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB8721F865F for <apps-discuss@ietfa.amsl.com>; Mon, 4 Jun 2012 03:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.83
X-Spam-Level:
X-Spam-Status: No, score=-103.83 tagged_above=-999 required=5 tests=[AWL=-1.231, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 d08Dlk0oWhpM for <apps-discuss@ietfa.amsl.com>; Mon, 4 Jun 2012 03:34:00 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA1E21F8799 for <discuss@apps.ietf.org>; Mon, 4 Jun 2012 03:34:00 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.203.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6893D22E1EB; Mon, 4 Jun 2012 06:33:51 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4FCC6D13.9020106@gmx.de>
Date: Mon, 04 Jun 2012 20:33:47 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D56AA605-F799-407A-AB0C-F97D080A1DEA@mnot.net>
References: <7B9B7D15-9510-4C90-9B77-EEC55262758C@mnot.net> <4FCC6D13.9020106@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1278)
Cc: Apps Discuss <discuss@apps.ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, Mike Kelly <mike@stateless.co>
Subject: Re: [apps-discuss] FYI: LCI -02
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 10:34:01 -0000

On 04/06/2012, at 6:08 PM, Julian Reschke wrote:

> On 2012-06-01 03:08, Mark Nottingham wrote:
>> We've published an -02 draft of LCI:
>>   <http://tools.ietf.org/html/draft-nottingham-linked-cache-inv-02>
>> 
>> and intend to request publication as an Individual Submission Informational RFC soon (the link relations have just been submitted for review). Feedback still welcome (http list is best, I think).
> 
> Here's another question: the proposal defines both a cache directive and link relations. Have you considered putting all the link-related information into a cache directive as well? (Not saying it should be the case but wondering whether that would keep things together that belong together).


Yes. However, some use cases are to strip the link on the way out, and it's easier to strip all Link headers than to parse and selectively change Cache-Control headers. I know that theoretically other Link headers could be emitted, but with current software, this is the easier path.

Additionally, I didn't want to rely on the quality of Cache-Control parsers already out there.

Also, we didn't want to re-invent the Link header and all of its associated machinery (e.g., relative vs. absolute, scoping, etc.).

Finally, it's conceivable that some folks might want to use the relations for other purposes.

After all, they may be separate headers, but they'll be in the same message. 

Cheers,

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