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

Adam Barth <ietf@adambarth.com> Thu, 24 February 2011 05:16 UTC

MIME-Version: 1.0
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
Precedence: list

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

Re: [http-state] Is this an omission in the parse… Remy Lebeau
[http-state] Is this an omission in the parser ru… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Julian Reschke
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Roy T. Fielding
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Peter Saint-Andre
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Peter Saint-Andre
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Roy T. Fielding
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Roy T. Fielding
Re: [http-state] Is this an omission in the parse… Julian Reschke
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Julian Reschke
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Roy T. Fielding
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Adam Barth
Re: [http-state] Is this an omission in the parse… Remy Lebeau
Re: [http-state] Is this an omission in the parse… Dan Winship
Re: [http-state] Is this an omission in the parse… Remy Lebeau
[http-state] parser rules of draft-ietf-httpstate… Roy T. Fielding
Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre
Re: [http-state] parser rules of draft-ietf-https… Roy T. Fielding
Re: [http-state] parser rules of draft-ietf-https… Adam Barth
Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre
Re: [http-state] parser rules of draft-ietf-https… Roy T. Fielding
Re: [http-state] parser rules of draft-ietf-https… Remy Lebeau
Re: [http-state] parser rules of draft-ietf-https… Adam Barth
Re: [http-state] parser rules of draft-ietf-https… Roy T. Fielding
Re: [http-state] parser rules of draft-ietf-https… Adam Barth
Re: [http-state] parser rules of draft-ietf-https… Dan Winship
Re: [http-state] parser rules of draft-ietf-https… Adam Barth
Re: [http-state] parser rules of draft-ietf-https… Peter Saint-Andre