Re: [http-state] parser rules of draft-ietf-httpstate-cookie-22

Adam Barth <ietf@adambarth.com> Thu, 24 February 2011 05:16 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 7D0993A69A6 for <http-state@core3.amsl.com>; Wed, 23 Feb 2011 21:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.809
X-Spam-Level:
X-Spam-Status: No, score=-2.809 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 XF9U-pW2nSDu for <http-state@core3.amsl.com>; Wed, 23 Feb 2011 21:16:11 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id B7A443A69A2 for <http-state@ietf.org>; Wed, 23 Feb 2011 21:16:11 -0800 (PST)
Received: by iwl42 with SMTP id 42so118866iwl.31 for <http-state@ietf.org>; Wed, 23 Feb 2011 21:17:00 -0800 (PST)
Received: by 10.231.19.133 with SMTP id a5mr695710ibb.78.1298524620157; Wed, 23 Feb 2011 21:17:00 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id z4sm7924128ibg.13.2011.02.23.21.16.58 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 21:16:59 -0800 (PST)
Received: by iwl42 with SMTP id 42so118856iwl.31 for <http-state@ietf.org>; Wed, 23 Feb 2011 21:16:58 -0800 (PST)
Received: by 10.231.36.75 with SMTP id s11mr676263ibd.130.1298524616094; Wed, 23 Feb 2011 21:16:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.215.67 with HTTP; Wed, 23 Feb 2011 21:16:25 -0800 (PST)
In-Reply-To: <94DA5CF6-88AB-43BD-99AE-921BCA98C7A3@gbiv.com>
References: <20110204184735.26023.qmail@mm01.prod.mesa1.secureserver.net> <AANLkTi=qBVkGwMHqAidtwP5_A8pPrF-Y9MV4jgYS5_QM@mail.gmail.com> <7384878F-C44A-42A4-9694-1BB1C18AA5E6@gbiv.com> <AANLkTinFq7bE_e3SSgdjuFvZ8hGn1xy4Hc1VKwc=vp1D@mail.gmail.com> <49225418-A1AF-4299-8C4F-2E608D34265D@gbiv.com> <AANLkTimrJF3LFR4t4j=U2L33kFh+wf-R=sjjwexcmyPi@mail.gmail.com> <26240DE2-4DD3-4863-81B1-635D34BA4AE4@gbiv.com> <AANLkTikzB=VORtn7xiG2JY8ymTjk4epC9huZTC-s0nzq@mail.gmail.com> <4D5AEE94.6010303@gmx.de> <AANLkTimkmZ99qDcXB6=-PGtXq6WQ7+RSreRwsBAHryEj@mail.gmail.com> <DA7A626A-9613-4A49-8A46-8096F7F465B4@gbiv.com> <AANLkTi=aX26NgDx3J0zk6a6H-Fg-9hyuBhfwvVW5nBiH@mail.gmail.com> <AANLkTinnySHEXvaQSxoUAKNaPWThDWdJwnhvCdVfa5Vr@mail.gmail.com> <1E7DE6DF-864A-48AF-B9A3-698DEF4B3B2D@gbiv.com> <4D6590F4.6010505@stpeter.im> <94DA5CF6-88AB-43BD-99AE-921BCA98C7A3@gbiv.com>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 23 Feb 2011 21:16:25 -0800
Message-ID: <AANLkTikxOBCgiAwvg3z2DwyHtJXhTK1=6ipTo16csKr9@mail.gmail.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: iesg@iesg.org, http-state <http-state@ietf.org>
Subject: Re: [http-state] parser rules of draft-ietf-httpstate-cookie-22
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, 24 Feb 2011 05:16:12 -0000

On Wed, Feb 23, 2011 at 5:01 PM, Roy T. Fielding <fielding@gbiv.com>; wrote:
> On Feb 23, 2011, at 2:57 PM, Peter Saint-Andre wrote:
>> On 2/23/11 3:07 PM, Roy T. Fielding wrote:
>>
>> <snip/>
>>
>>> Therefore, I would like you to change the ABNF so that it
>>> reflects the reality of (Set-)Cookie usage on the Internet,
>>> for the same reason that you have insisted the algorithm
>>> for user agent parsing reflects reality.  Changing the ABNF
>>> to include base64 does not do that -- it is just another
>>> fantasy production that differs from all prior specs of
>>> the cookie algorithm.  Changing it to
>>>
>>> cookie-value      = %x21-2B / %x2D-3A / %x3C-7E / %x80-FF
>>>
>>> or just the minimum
>>>
>>> cookie-value      = %x21-2B / %x2D-3A / %x3C-7E
>>
>> Hi Roy,
>>
>> The latter seems fine, and in conversation with Adam he indicated to me
>> that he would not object to such a change.
>
> Okay by me.

One nit: I would exclude %x22 because there are interoperability
problems with cookie-values that contain %x22.

Adam