Re: Proposal: Cookie Priorities

Amos Jeffries <squid3@treenet.co.nz> Mon, 07 March 2016 02:34 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E741B33E4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 6 Mar 2016 18:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x44gDVGEx6zJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 6 Mar 2016 18:34:47 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC3B21B33E1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 6 Mar 2016 18:34:47 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ackv6-0007ER-0R for ietf-http-wg-dist@listhub.w3.org; Mon, 07 Mar 2016 02:29:16 +0000
Resent-Date: Mon, 07 Mar 2016 02:29:16 +0000
Resent-Message-Id: <E1ackv6-0007ER-0R@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <squid3@treenet.co.nz>) id 1ackv1-0007Dg-8q for ietf-http-wg@listhub.w3.org; Mon, 07 Mar 2016 02:29:11 +0000
Received: from [121.99.228.82] (helo=treenet.co.nz) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <squid3@treenet.co.nz>) id 1ackuz-0004UA-Lv for ietf-http-wg@w3.org; Mon, 07 Mar 2016 02:29:10 +0000
Received: from [192.168.20.251] (unknown [121.98.45.158]) by treenet.co.nz (Postfix) with ESMTP id 2A3C4E6F60 for <ietf-http-wg@w3.org>; Mon, 7 Mar 2016 15:28:37 +1300 (NZDT)
To: ietf-http-wg@w3.org
References: <CAKXHy=dvxE5f25_xx3mKTc+XRDU_Hp=uFDy-iL-_c0s+xHGydw@mail.gmail.com> <4F1B2115-C2BB-42AD-A5AB-EC02E9598ACB@mnot.net> <CACweHNCFzsrc1HacyFdj6Oigm1pxJaeqFjXWaZC9jz-oYboymQ@mail.gmail.com>
From: Amos Jeffries <squid3@treenet.co.nz>
Message-ID: <56DCE753.6020409@treenet.co.nz>
Date: Mon, 07 Mar 2016 15:28:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CACweHNCFzsrc1HacyFdj6Oigm1pxJaeqFjXWaZC9jz-oYboymQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=121.99.228.82; envelope-from=squid3@treenet.co.nz; helo=treenet.co.nz
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: AWL=-1.092, BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ackuz-0004UA-Lv 535543adb619154e8d0a90d8c7efb6ba
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Proposal: Cookie Priorities
Archived-At: <http://www.w3.org/mid/56DCE753.6020409@treenet.co.nz>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31205
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 4/03/2016 1:52 p.m., Matthew Kerwin wrote:
> On 04/03/2016 10:09 AM, "Mark Nottingham" wrote:
>>
>> Thanks, Mike.
>>
>> As I understand it, this is already implemented in one browser, which is
> good in that we're looking for implementation.
>>
>> What do folks -- both other browser implementers and site folks -- think
> about this?
>>
> 
> It's a practical issue with a simple (demonstrated) improvement. And hints
> like this usually fall under "handy at best, harmless at worst" so I see no
> harm in and of itself.
> 
> That said, maybe I've been listening to PHK for too long, but I wonder if
> all these cookie patches aren't just putting band-aids over a fundamentally
> flawed system. How many (and how big) cookies do you need to receive before
> this priority comes to the fore?
> 

Oh, its absolutely a battered, abused, and broken mechanism. I am
doubtful that many would even attempt to argue the contrary.

My take has been from the beginning that we should start pruning away
pieces of Cookie to prevent bad usages a much as possible.

This particular baindaid proposal looks like it might double as a nice
way to allow any recipient or relay to proactively prune away the
low-priority Cookies in traffic when bandwidth gets overloaded. Can it
be the beginning of an efficient Cookie deletion mechanism?

Amos