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

Adam Barth <ietf@adambarth.com> Thu, 11 March 2010 18:04 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 90D7E3A6D18 for <http-state@core3.amsl.com>; Thu, 11 Mar 2010 10:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 0CwLAOyc4HrI for <http-state@core3.amsl.com>; Thu, 11 Mar 2010 10:04:17 -0800 (PST)
Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.221.175]) by core3.amsl.com (Postfix) with ESMTP id B705A3A6D1A for <http-state@ietf.org>; Thu, 11 Mar 2010 09:41:51 -0800 (PST)
Received: by qyk5 with SMTP id 5so304256qyk.13 for <http-state@ietf.org>; Thu, 11 Mar 2010 09:41:54 -0800 (PST)
Received: by 10.229.222.139 with SMTP id ig11mr163690qcb.13.1268329284649; Thu, 11 Mar 2010 09:41:24 -0800 (PST)
Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by mx.google.com with ESMTPS id 20sm169190iwn.1.2010.03.11.09.41.23 (version=SSLv3 cipher=RC4-MD5); Thu, 11 Mar 2010 09:41:23 -0800 (PST)
Received: by iwn27 with SMTP id 27so332374iwn.5 for <http-state@ietf.org>; Thu, 11 Mar 2010 09:41:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.145.204 with SMTP id e12mr447493ibv.36.1268329283088; Thu, 11 Mar 2010 09:41:23 -0800 (PST)
In-Reply-To: <op.u9exs1lkvqd7e2@killashandra.oslo.osa>
References: <5c4444771003071050r3475798co95cc192d1f2e8190@mail.gmail.com> <op.u9dpzpdoqrq7tp@acorna> <5c4444771003101823u25842652o33b49b2be81f4cfc@mail.gmail.com> <op.u9exs1lkvqd7e2@killashandra.oslo.osa>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 11 Mar 2010 09:41:03 -0800
Message-ID: <5c4444771003110941g18bc3a47t72cae43ca430eaf4@mail.gmail.com>
To: 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: Thu, 11 Mar 2010 18:04:18 -0000

On Thu, Mar 11, 2010 at 9:06 AM, Yngve Nysaeter Pettersen
<yngve@opera.com> wrote:
> On Thu, 11 Mar 2010 03:23:03 +0100, Adam Barth <ietf@adambarth.com> wrote:
>>> * Section 2. "General nonsense"? Maybe a more "appropriate" title should
>>> be used?
>>
>> I'm open to suggestions.  The term "general nonsense" comes from the
>> mathematics literature, where it refers to somewhat boilerplate
>> information that needs to be included for correctness.
>
> In some documents I've seen these are included in the introduction section,
> such as in RFC 2616
>
> I have tended to reference syntax conventions at the beginning of the syntax
> section

Yeah, my concern is I'd like folks to read the introduction by I don't
care if people read that section because it doesn't say anything folks
don't already know...

>>> * 5.3 step 10: Maybe specify that client must ignore cookies with
>>> expiration date at the current time? (similar with use of "expiration
>>> date
>>> in the past" elsewhere)
>>
>> I'm not too worried about that.  It's virtually impossible to hit the
>> current time on the dot.
>
> It is possible for "max-age=0"

That's a good point.  I'll read through all the time processing and
make sure these cases work correctly.

Adam