Re: [http-state] draft-ietf-httpstate-cookie-05 posted

Adam Barth <ietf@adambarth.com> Mon, 15 March 2010 16:07 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5EF33A683C for <http-state@core3.amsl.com>; Mon, 15 Mar 2010 09:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OIr+Gy3IvM+6 for <http-state@core3.amsl.com>; Mon, 15 Mar 2010 09:07:07 -0700 (PDT)
Received: from mail-px0-f187.google.com (mail-px0-f187.google.com [209.85.216.187]) by core3.amsl.com (Postfix) with ESMTP id 273F53A6A68 for <http-state@ietf.org>; Mon, 15 Mar 2010 09:07:04 -0700 (PDT)
Received: by pxi17 with SMTP id 17so2072564pxi.5 for <http-state@ietf.org>; Mon, 15 Mar 2010 09:07:10 -0700 (PDT)
Received: by 10.115.66.8 with SMTP id t8mr5485917wak.157.1268669230058; Mon, 15 Mar 2010 09:07:10 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id 21sm5914933pzk.12.2010.03.15.09.07.08 (version=SSLv3 cipher=RC4-MD5); Mon, 15 Mar 2010 09:07:09 -0700 (PDT)
Received: by pwj6 with SMTP id 6so2010704pwj.31 for <http-state@ietf.org>; Mon, 15 Mar 2010 09:07:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.3.3 with SMTP id f3mr6004964rvi.215.1268669228139; Mon, 15 Mar 2010 09:07:08 -0700 (PDT)
In-Reply-To: <op.u9lshdbjqrq7tp@acorna.oslo.opera.com>
References: <5c4444771003071050r3475798co95cc192d1f2e8190@mail.gmail.com> <op.u9k0zvitqrq7tp@acorna.oslo.opera.com> <5c4444771003142306k3c8b66k53bafb15141efde5@mail.gmail.com> <op.u9lshdbjqrq7tp@acorna.oslo.opera.com>
From: Adam Barth <ietf@adambarth.com>
Date: Mon, 15 Mar 2010 09:06:48 -0700
Message-ID: <5c4444771003150906qba561e7ta0fc67831ae183cb@mail.gmail.com>
To: "Yngve N. Pettersen (Developer Opera Software ASA)" <yngve@opera.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state <http-state@ietf.org>
Subject: Re: [http-state] draft-ietf-httpstate-cookie-05 posted
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2010 16:07:09 -0000

On Mon, Mar 15, 2010 at 2:54 AM, Yngve N. Pettersen (Developer Opera
Software ASA) <yngve@opera.com> wrote:
> On Mon, 15 Mar 2010 07:06:40 +0100, Adam Barth <ietf@adambarth.com> wrote:
>> On Sun, Mar 14, 2010 at 5:00 PM, Yngve N. Pettersen (Developer Opera
>> Software ASA) <yngve@opera.com> wrote:
>>>
>>> On Sun, 07 Mar 2010 19:50:57 +0100, Adam Barth <ietf@adambarth.com>
>>> wrote:
>>>
>>>> My understanding is that Monday is the deadline for uploading I-Ds
>>>> before IETF77.  I've uploaded the latest version of the draft:
>>>>
>>>> http://www.ietf.org/id/draft-ietf-httpstate-cookie-05.txt
>>>>
>>>> If you're going to IETF77, this is the version of the draft that we'll
>>>> be discussing.  Looking forward to seeing many of you there.
>>>
>>> Yet another possible issue, not sure if it has been mentioned in the
>>> group
>>> before (I have discussed it with others off-list):
>>>
>>> * cookie-name should not be allowed to start with "$". I would prefer a
>>> MUST
>>> NOT, but a SHOULD NOT might be sufficient.
>>
>> Do you mean that servers SHOULD NOT send cookie names that start with
>> $ or are you recommending some conformance requirement for user
>> agents?
>
> Mostly as a server requirement.
>
> Unless the requirement on servers is MUST NOT, it is not possible to add a
> requirement for clients. Although, if there is also text saying that clients
> MAY refuse cookies with names starting with $, that would certainly
> emphasize the point (and would be useful for clients supporting RFC 2965 or
> the proposed $Origin attribute).

We've decided as a general principle that servers ought to be allowed
to use the full protocol specified in Section 5.  That implies we'd
add this requirement as a "SHOULD NOT" for servers.

> RFC 2109 also says about name
>
>      NAMEs that begin with $ are reserved for
>      other uses and must not be used by applications.
>
> Admittedly it is only only using small letters, but maybe it is time to
> strengthen that language?

RFC 2109 says a lot of nonsense.  I'd rather focus on the facts on the
ground when making decisions.

Adam