
From paulej@packetizer.com  Thu Jan  6 07:56:12 2011
Return-Path: <paulej@packetizer.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 3A08C3A6E2B for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 07:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_66=0.6]
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 3K5Uhxptb58l for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 07:56:11 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id 910B33A6E1A for <http-state@ietf.org>; Thu,  6 Jan 2011 07:56:10 -0800 (PST)
Received: from sydney (rrcs-98-101-155-83.midsouth.biz.rr.com [98.101.155.83]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id p06Fw9Vn015514 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jan 2011 10:58:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1294329495; bh=96DwfddGe0Uthvnyki5qC3kNcHbRctqR8WRFoXh3Cws=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=TyMMkN4uQnvOevZ89xVh2rCWJ4DXIegaIKhvNdZd8Z8u4lRxzcsiy2eDG6oNewvx1 6n97EpdAp3lFkPUAQ8qH5QIkT0F7poswVOY6eRrK/XkyHjwNmS39SGvKYqKfXWmi01 4Y1JGgglhxdKr8dH88G4Sxy8RkWraejytrO/YYyI=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Adam Barth'" <ietf@adambarth.com>
References: <20101219190001.812.87795.idtracker@localhost>
In-Reply-To: <20101219190001.812.87795.idtracker@localhost>
Date: Thu, 6 Jan 2011 10:57:59 -0500
Message-ID: <072301cbadba$829adaa0$87d08fe0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKbH5XLhNoFTCnbrQLedk+kxu/zxJIlLF/g
Content-Language: en-us
Cc: http-state@ietf.org
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-20.txt
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, 06 Jan 2011 15:56:12 -0000

Adam,

In the RFC 2109, the "domain" attribute is optional.  Specifically, it says:

   Domain=domain
      Optional.  The Domain attribute specifies the domain for which the
      cookie is valid.  An explicitly specified domain must always start
      with a dot.

 It also defined a default:
   Domain Defaults to the request-host.  (Note that there is no dot at
          the beginning of request-host.)

I found this in the -20 draft:

4.1.2.3:
   If the server omits the Domain attribute, the user
   agent will return the cookie only to the origin server.

      WARNING: Some existing user agents treat an absent Domain
      attribute as if the Domain attribute were present and contained
      the current host name.  For example, if example.com returns a Set-
      Cookie header without a Domain attribute, these user agents will
      erroneously send the cookie to www.example.com as well.

If I received a cookie without a domain from test.example.com, I would
assume the cookie's domain is "test.example.com".  The wording above
confuses me a little, as I would bind the cookie to the host I accessed.
The first sentence in the WARNING seems like what I should do, but the
example presented is not the origin server or the "current host name".  I
agree that it would be an error for a browser to assume a larger domain
scope than just the single host being accessed.  But, I would think that
absence of or an empty string for "Domain" would be bound only to the server
being accessed.  I believe that is the intent, as stated in other sections,
but the warning text seems to suggest otherwise when I read it.

In Section 5.2.3, this text appears:
   If the attribute-value is empty, the behavior is undefined.  However,
   user agent SHOULD ignore the cookie-av entirely.

Why would the behavior be undefined?  Why would these not be treated
identically?
Set-Cookie: mycookie=myvalue; path=/
Set-Cookie: mycookie=myvalue; path=/; domain=

Why isn't an empty string a valid value?  I ask, because we assign an empty
value internally.  In 5.3, paragraph 4, we have:
   4.   If the cookie-attribute-list contains an attribute with an
        attribute-name of "Domain":

           Let the domain-attribute be the attribute-value of the last
           attribute in the cookie-attribute-list with an attribute-name
           of "Domain".

        Otherwise:

           Let the domain-attribute be the empty string.

So, this does suggest "domain=" would be the same as absence of the domain
parameter, no?  Paragraph 6 then explains that in such cases, the domain is
assigned to "the canonicalized request-host", which is consistent.

So, any reason why the Domain a/v syntax isn't this?
domain-value      = <subdomain> | ""

Paul

> -----Original Message-----
> From: http-state-bounces@ietf.org [mailto:http-state-bounces@ietf.org]
> On Behalf Of Internet-Drafts@ietf.org
> Sent: Sunday, December 19, 2010 2:00 PM
> To: i-d-announce@ietf.org
> Cc: http-state@ietf.org
> Subject: [http-state] I-D Action:draft-ietf-httpstate-cookie-20.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the HTTP State Management Mechanism Working
> Group of the IETF.
> 
> 
> 	Title           : HTTP State Management Mechanism
> 	Author(s)       : A. Barth
> 	Filename        : draft-ietf-httpstate-cookie-20.txt
> 	Pages           : 44
> 	Date            : 2010-12-19
> 
> This document defines the HTTP Cookie and Set-Cookie header fields.
> These header fields can be used by HTTP servers to store state (called
> cookies) at HTTP user agents, letting the servers maintain a stateful
> session over the mostly stateless HTTP protocol.  Although cookies have
> many historical infelicities that degrade their security and privacy,
> the Cookie and Set-Cookie header fields are widely used on the
> Internet.Editorial Note (To be removed by RFC Editor)
> 
> If you have suggestions for improving this document, please send email
> to <mailto:http-state@ietf.org>.  Suggestions with test cases are
> especially appreciated.  Further Working Group information is available
> from <https://tools.ietf.org/wg/httpstate/>.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-20.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


From ietf@adambarth.com  Thu Jan  6 12:48:51 2011
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 D8F3F3A6DF5 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 12:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.68
X-Spam-Level: 
X-Spam-Status: No, score=-3.68 tagged_above=-999 required=5 tests=[AWL=-1.303,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_66=0.6, 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 qtI5d7KWunNY for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 12:48:51 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 7A5423A6CFF for <http-state@ietf.org>; Thu,  6 Jan 2011 12:48:50 -0800 (PST)
Received: by fxm9 with SMTP id 9so16511488fxm.31 for <http-state@ietf.org>; Thu, 06 Jan 2011 12:50:56 -0800 (PST)
Received: by 10.223.83.201 with SMTP id g9mr959710fal.140.1294347056764; Thu, 06 Jan 2011 12:50:56 -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 z1sm5976734fau.45.2011.01.06.12.50.55 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 12:50:56 -0800 (PST)
Received: by iwn40 with SMTP id 40so17680013iwn.31 for <http-state@ietf.org>; Thu, 06 Jan 2011 12:50:54 -0800 (PST)
Received: by 10.231.156.1 with SMTP id u1mr8536135ibw.52.1294347054440; Thu, 06 Jan 2011 12:50:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.11.140 with HTTP; Thu, 6 Jan 2011 12:50:24 -0800 (PST)
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 6 Jan 2011 12:50:24 -0800
Message-ID: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: [http-state] The Domain attribute (was Re: I-D Action:draft-ietf-httpstate-cookie-20.txt)
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, 06 Jan 2011 20:48:52 -0000

On Thu, Jan 6, 2011 at 7:57 AM, Paul E. Jones <paulej@packetizer.com> wrote=
:
> Adam,
>
> In the RFC 2109, the "domain" attribute is optional. =A0Specifically, it =
says:
>
> =A0 Domain=3Ddomain
> =A0 =A0 =A0Optional. =A0The Domain attribute specifies the domain for whi=
ch the
> =A0 =A0 =A0cookie is valid. =A0An explicitly specified domain must always=
 start
> =A0 =A0 =A0with a dot.
>
> =A0It also defined a default:
> =A0 Domain Defaults to the request-host. =A0(Note that there is no dot at
> =A0 =A0 =A0 =A0 =A0the beginning of request-host.)

Right.

> I found this in the -20 draft:
>
> 4.1.2.3:
> =A0 If the server omits the Domain attribute, the user
> =A0 agent will return the cookie only to the origin server.
>
> =A0 =A0 =A0WARNING: Some existing user agents treat an absent Domain
> =A0 =A0 =A0attribute as if the Domain attribute were present and containe=
d
> =A0 =A0 =A0the current host name. =A0For example, if example.com returns =
a Set-
> =A0 =A0 =A0Cookie header without a Domain attribute, these user agents wi=
ll
> =A0 =A0 =A0erroneously send the cookie to www.example.com as well.
>
> If I received a cookie without a domain from test.example.com, I would
> assume the cookie's domain is "test.example.com". =A0The wording above
> confuses me a little, as I would bind the cookie to the host I accessed.
> The first sentence in the WARNING seems like what I should do, but the
> example presented is not the origin server or the "current host name". =
=A0I
> agree that it would be an error for a browser to assume a larger domain
> scope than just the single host being accessed. =A0But, I would think tha=
t
> absence of or an empty string for "Domain" would be bound only to the ser=
ver
> being accessed. =A0I believe that is the intent, as stated in other secti=
ons,
> but the warning text seems to suggest otherwise when I read it.

Right, the issue is that some browsers forget to set the host-only
flag on the cookie if you omit the Domain attribute.  That causes the
cookie to be returned to the origin server as well as all subdomains
of the origin server's host name.

> In Section 5.2.3, this text appears:
> =A0 If the attribute-value is empty, the behavior is undefined. =A0Howeve=
r,
> =A0 user agent SHOULD ignore the cookie-av entirely.
>
> Why would the behavior be undefined? =A0Why would these not be treated
> identically?
> Set-Cookie: mycookie=3Dmyvalue; path=3D/
> Set-Cookie: mycookie=3Dmyvalue; path=3D/; domain=3D

It's undefined because different implementations do different things
and I didn't have the energy or the inclination to beat them up on
this point.  They should do what the document suggests, but it's not
the end of the world fi they don't.

> Why isn't an empty string a valid value? =A0I ask, because we assign an e=
mpty
> value internally. =A0In 5.3, paragraph 4, we have:
>
> =A0 4. =A0 If the cookie-attribute-list contains an attribute with an
> =A0 =A0 =A0 =A0attribute-name of "Domain":
>
> =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the attribute-value of th=
e last
> =A0 =A0 =A0 =A0 =A0 attribute in the cookie-attribute-list with an attrib=
ute-name
> =A0 =A0 =A0 =A0 =A0 of "Domain".
>
> =A0 =A0 =A0 =A0Otherwise:
>
> =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the empty string.
>
> So, this does suggest "domain=3D" would be the same as absence of the dom=
ain
> parameter, no?

Well, the complexity actually arises when the server provides multiple
Domain attributes, some of which are the empty string.  Which one
actually controls the result varies.

The rules are written such that if you follow them, you get reasonable
behavior that matches practice.  There's also some wiggle room to in
this extreme corner case (multiple attributes, one of which is the
empty string).  We could nail that issue down, but it didn't seem
worth the hassle.

>=A0Paragraph 6 then explains that in such cases, the domain is
> assigned to "the canonicalized request-host", which is consistent.
>
> So, any reason why the Domain a/v syntax isn't this?
> domain-value =A0 =A0 =A0=3D <subdomain> | ""

Just because it's nonsense semantically and an interoperability
sandtrap.  If you'd like to use the empty string, just omit the Domain
attribute instead.  Your life and everyone else's life will be happier
for it.

Adam


>> -----Original Message-----
>> From: http-state-bounces@ietf.org [mailto:http-state-bounces@ietf.org]
>> On Behalf Of Internet-Drafts@ietf.org
>> Sent: Sunday, December 19, 2010 2:00 PM
>> To: i-d-announce@ietf.org
>> Cc: http-state@ietf.org
>> Subject: [http-state] I-D Action:draft-ietf-httpstate-cookie-20.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the HTTP State Management Mechanism Working
>> Group of the IETF.
>>
>>
>> =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : HTTP State Management Mechanism
>> =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : A. Barth
>> =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-httpstate-cookie-20.txt
>> =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 44
>> =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-12-19
>>
>> This document defines the HTTP Cookie and Set-Cookie header fields.
>> These header fields can be used by HTTP servers to store state (called
>> cookies) at HTTP user agents, letting the servers maintain a stateful
>> session over the mostly stateless HTTP protocol. =A0Although cookies hav=
e
>> many historical infelicities that degrade their security and privacy,
>> the Cookie and Set-Cookie header fields are widely used on the
>> Internet.Editorial Note (To be removed by RFC Editor)
>>
>> If you have suggestions for improving this document, please send email
>> to <mailto:http-state@ietf.org>. =A0Suggestions with test cases are
>> especially appreciated. =A0Further Working Group information is availabl=
e
>> from <https://tools.ietf.org/wg/httpstate/>.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-20.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>
>

From paulej@packetizer.com  Thu Jan  6 14:20:31 2011
Return-Path: <paulej@packetizer.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 879BF3A6F29 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 14:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.939
X-Spam-Level: 
X-Spam-Status: No, score=-1.939 tagged_above=-999 required=5 tests=[AWL=-0.540, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, J_CHICKENPOX_73=0.6]
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 ACQkYBM0ComB for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 14:20:28 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id 7C4FF3A6B9E for <http-state@ietf.org>; Thu,  6 Jan 2011 14:20:28 -0800 (PST)
Received: from sydney (rrcs-98-101-155-83.midsouth.biz.rr.com [98.101.155.83]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id p06MMRQs028135 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jan 2011 17:22:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1294352553; bh=/ftQs42vo0coePYKX4l/rmog8ZKZct6Z06+zJYUh/MQ=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=adv+d4kUDtIT1S18pSz2YZS8WN3DmONYspeUZWS3/GbY06tA+cYQxEsBqV1p6eViO nO6rCybGtErdHtrXOAhzad0L1PAoi6kg58sV91AivzO615cJBqzM+adDBUQu++eBXT 4eN7bR1TvsHTI9UNbwISCz2j1oUCKR88rIHNbiR4=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Adam Barth'" <ietf@adambarth.com>
References: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com>
In-Reply-To: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com>
Date: Thu, 6 Jan 2011 17:22:19 -0500
Message-ID: <07d501cbadf0$31e13470$95a39d50$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOsylhA7Jc/U76u6c6ZWuz0pv934ZACQIyw
Content-Language: en-us
Cc: http-state@ietf.org
Subject: Re: [http-state] The Domain attribute (was Re: I-D Action:draft-ietf-httpstate-cookie-20.txt)
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, 06 Jan 2011 22:20:31 -0000

Adam,

Thanks for the clarification.  Now I understand that many of the =
decisions
made were based on real-world implementations and a desire to make =
things no
worse than they already are. ;-)

Perhaps the one point of disagreement is whether this syntax is valid:
domain-value      =3D <subdomain> | ""

I agree that one could omit the Domain attribute and probably should, =
but
the above syntax is consistent with text that talks about an "empty =
string".
We have to give that treatment, since an empty string actually means
something.

The empty string is also used in this example:
Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT

For this reason, this might be another area where we need to consider a
syntax change:
cookie-pair       =3D cookie-name "=3D" cookie-value
cookie-name       =3D token
cookie-value      =3D token | ""
                         ^^^^^

These are the only examples I can think of where I've seen attributes =
that
do not have assigned values (i.e., have an empty strings) on the wire, =
each
done so deliberately and with a particular meaning.

In any case, I don't have a strong preference and if the group wants to
change the syntax.  That's OK.  It just seems allowing an empty string =
for
"Domain" is more consistent with the text than not.

Paul

> -----Original Message-----
> From: Adam Barth [mailto:ietf@adambarth.com]
> Sent: Thursday, January 06, 2011 3:50 PM
> To: Paul E. Jones
> Cc: http-state@ietf.org
> Subject: The Domain attribute (was Re: [http-state] I-D Action:draft-
> ietf-httpstate-cookie-20.txt)
>=20
> On Thu, Jan 6, 2011 at 7:57 AM, Paul E. Jones <paulej@packetizer.com>
> wrote:
> > Adam,
> >
> > In the RFC 2109, the "domain" attribute is optional. =
=A0Specifically, it
> says:
> >
> > =A0 Domain=3Ddomain
> > =A0 =A0 =A0Optional. =A0The Domain attribute specifies the domain =
for which
> > the
> > =A0 =A0 =A0cookie is valid. =A0An explicitly specified domain must =
always
> > start
> > =A0 =A0 =A0with a dot.
> >
> > =A0It also defined a default:
> > =A0 Domain Defaults to the request-host. =A0(Note that there is no =
dot at
> > =A0 =A0 =A0 =A0 =A0the beginning of request-host.)
>=20
> Right.
>=20
> > I found this in the -20 draft:
> >
> > 4.1.2.3:
> > =A0 If the server omits the Domain attribute, the user
> > =A0 agent will return the cookie only to the origin server.
> >
> > =A0 =A0 =A0WARNING: Some existing user agents treat an absent Domain
> > =A0 =A0 =A0attribute as if the Domain attribute were present and =
contained
> > =A0 =A0 =A0the current host name. =A0For example, if example.com =
returns a
> > Set-
> > =A0 =A0 =A0Cookie header without a Domain attribute, these user =
agents will
> > =A0 =A0 =A0erroneously send the cookie to www.example.com as well.
> >
> > If I received a cookie without a domain from test.example.com, I =
would
> > assume the cookie's domain is "test.example.com". =A0The wording =
above
> > confuses me a little, as I would bind the cookie to the host I
> accessed.
> > The first sentence in the WARNING seems like what I should do, but =
the
> > example presented is not the origin server or the "current host
> name".
> > I agree that it would be an error for a browser to assume a larger
> > domain scope than just the single host being accessed. =A0But, I =
would
> > think that absence of or an empty string for "Domain" would be bound
> > only to the server being accessed. =A0I believe that is the intent, =
as
> > stated in other sections, but the warning text seems to suggest
> otherwise when I read it.
>=20
> Right, the issue is that some browsers forget to set the host-only =
flag
> on the cookie if you omit the Domain attribute.  That causes the =
cookie
> to be returned to the origin server as well as all subdomains of the
> origin server's host name.
>=20
> > In Section 5.2.3, this text appears:
> > =A0 If the attribute-value is empty, the behavior is undefined.
> > However,
> > =A0 user agent SHOULD ignore the cookie-av entirely.
> >
> > Why would the behavior be undefined? =A0Why would these not be =
treated
> > identically?
> > Set-Cookie: mycookie=3Dmyvalue; path=3D/
> > Set-Cookie: mycookie=3Dmyvalue; path=3D/; domain=3D
>=20
> It's undefined because different implementations do different things =
and
> I didn't have the energy or the inclination to beat them up on this
> point.  They should do what the document suggests, but it's not the =
end
> of the world fi they don't.
>=20
> > Why isn't an empty string a valid value? =A0I ask, because we assign =
an
> > empty value internally. =A0In 5.3, paragraph 4, we have:
> >
> > =A0 4. =A0 If the cookie-attribute-list contains an attribute with =
an
> > =A0 =A0 =A0 =A0attribute-name of "Domain":
> >
> > =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the attribute-value =
of the last
> > =A0 =A0 =A0 =A0 =A0 attribute in the cookie-attribute-list with an
> > attribute-name
> > =A0 =A0 =A0 =A0 =A0 of "Domain".
> >
> > =A0 =A0 =A0 =A0Otherwise:
> >
> > =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the empty string.
> >
> > So, this does suggest "domain=3D" would be the same as absence of =
the
> > domain parameter, no?
>=20
> Well, the complexity actually arises when the server provides multiple
> Domain attributes, some of which are the empty string.  Which one
> actually controls the result varies.
>=20
> The rules are written such that if you follow them, you get reasonable
> behavior that matches practice.  There's also some wiggle room to in
> this extreme corner case (multiple attributes, one of which is the =
empty
> string).  We could nail that issue down, but it didn't seem worth the
> hassle.
>=20
> >=A0Paragraph 6 then explains that in such cases, the domain is  =
assigned
> >to "the canonicalized request-host", which is consistent.
> >
> > So, any reason why the Domain a/v syntax isn't this?
> > domain-value =A0 =A0 =A0=3D <subdomain> | ""
>=20
> Just because it's nonsense semantically and an interoperability
> sandtrap.  If you'd like to use the empty string, just omit the Domain
> attribute instead.  Your life and everyone else's life will be happier
> for it.
>=20
> Adam
>=20
>=20
> >> -----Original Message-----
> >> From: http-state-bounces@ietf.org
> >> [mailto:http-state-bounces@ietf.org]
> >> On Behalf Of Internet-Drafts@ietf.org
> >> Sent: Sunday, December 19, 2010 2:00 PM
> >> To: i-d-announce@ietf.org
> >> Cc: http-state@ietf.org
> >> Subject: [http-state] I-D Action:draft-ietf-httpstate-cookie-20.txt
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >> This draft is a work item of the HTTP State Management Mechanism
> >> Working Group of the IETF.
> >>
> >>
> >> =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : HTTP State Management =
Mechanism
> >> =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : A. Barth
> >> =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: =
draft-ietf-httpstate-cookie-20.txt
> >> =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 44
> >> =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-12-19
> >>
> >> This document defines the HTTP Cookie and Set-Cookie header fields.
> >> These header fields can be used by HTTP servers to store state
> >> (called
> >> cookies) at HTTP user agents, letting the servers maintain a =
stateful
> >> session over the mostly stateless HTTP protocol. =A0Although =
cookies
> >> have many historical infelicities that degrade their security and
> >> privacy, the Cookie and Set-Cookie header fields are widely used on
> >> the Internet.Editorial Note (To be removed by RFC Editor)
> >>
> >> If you have suggestions for improving this document, please send
> >> email to <mailto:http-state@ietf.org>. =A0Suggestions with test =
cases
> >> are especially appreciated. =A0Further Working Group information is
> >> available from <https://tools.ietf.org/wg/httpstate/>.
> >>
> >> A URL for this Internet-Draft is:
> >> =
http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-20.tx
> >> t
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> Below is the data which will enable a MIME compliant mail reader
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >
> >


From ietf@adambarth.com  Thu Jan  6 15:16:48 2011
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 322DE3A6DF6 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 15:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.371
X-Spam-Level: 
X-Spam-Status: No, score=-3.371 tagged_above=-999 required=5 tests=[AWL=-1.594, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_66=0.6, J_CHICKENPOX_73=0.6, 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 hnqk34JiuMb7 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 15:16:47 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id C42743A6D06 for <http-state@ietf.org>; Thu,  6 Jan 2011 15:16:46 -0800 (PST)
Received: by qyj19 with SMTP id 19so18301166qyj.10 for <http-state@ietf.org>; Thu, 06 Jan 2011 15:18:53 -0800 (PST)
Received: by 10.229.224.212 with SMTP id ip20mr21346579qcb.237.1294355933077;  Thu, 06 Jan 2011 15:18:53 -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 q12sm14707532qcu.18.2011.01.06.15.18.51 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 15:18:52 -0800 (PST)
Received: by iwn40 with SMTP id 40so17791598iwn.31 for <http-state@ietf.org>; Thu, 06 Jan 2011 15:18:50 -0800 (PST)
Received: by 10.231.12.132 with SMTP id x4mr482622ibx.177.1294355930555; Thu, 06 Jan 2011 15:18:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.11.140 with HTTP; Thu, 6 Jan 2011 15:18:20 -0800 (PST)
In-Reply-To: <07d501cbadf0$31e13470$95a39d50$@packetizer.com>
References: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com> <07d501cbadf0$31e13470$95a39d50$@packetizer.com>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 6 Jan 2011 15:18:20 -0800
Message-ID: <AANLkTi=M7ZW2FGtV6okTOswiS3sQPM8O07xhF6ifMwVK@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: Re: [http-state] The Domain attribute (was Re: I-D Action:draft-ietf-httpstate-cookie-20.txt)
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, 06 Jan 2011 23:16:48 -0000

On Thu, Jan 6, 2011 at 2:22 PM, Paul E. Jones <paulej@packetizer.com> wrote=
:
> Thanks for the clarification. =A0Now I understand that many of the decisi=
ons
> made were based on real-world implementations and a desire to make things=
 no
> worse than they already are. ;-)
>
> Perhaps the one point of disagreement is whether this syntax is valid:
> domain-value =A0 =A0 =A0=3D <subdomain> | ""
>
> I agree that one could omit the Domain attribute and probably should, but
> the above syntax is consistent with text that talks about an "empty strin=
g".
> We have to give that treatment, since an empty string actually means
> something.

We don't have to do anything.  In particular, not every piece of
syntax that semantically meaningful need be valid.

> The empty string is also used in this example:
> Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT

Why is that?  The "lang" attribute has not been defined, so the valid
values for the lang attribute certainly haven't been defined.

> For this reason, this might be another area where we need to consider a
> syntax change:
> cookie-pair =A0 =A0 =A0 =3D cookie-name "=3D" cookie-value
> cookie-name =A0 =A0 =A0 =3D token
> cookie-value =A0 =A0 =A0=3D token | ""
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^

I would not recommend that servers send empty attribute values.
That's just asking for interoperability problems.

> These are the only examples I can think of where I've seen attributes tha=
t
> do not have assigned values (i.e., have an empty strings) on the wire, ea=
ch
> done so deliberately and with a particular meaning.
>
> In any case, I don't have a strong preference and if the group wants to
> change the syntax. =A0That's OK. =A0It just seems allowing an empty strin=
g for
> "Domain" is more consistent with the text than not.

More consistent with what text?  The text in the User Agent
Requirements section is for user agents and not for servers.  You're
talking about what's useful for syntax for servers to generate.  It's
not useful for servers to generate empty Domain attributes.  Instead
of generating an empty Domain attribute, they ought to simply omit the
Domain attribute.

Adam


>> -----Original Message-----
>> From: Adam Barth [mailto:ietf@adambarth.com]
>> Sent: Thursday, January 06, 2011 3:50 PM
>> To: Paul E. Jones
>> Cc: http-state@ietf.org
>> Subject: The Domain attribute (was Re: [http-state] I-D Action:draft-
>> ietf-httpstate-cookie-20.txt)
>>
>> On Thu, Jan 6, 2011 at 7:57 AM, Paul E. Jones <paulej@packetizer.com>
>> wrote:
>> > Adam,
>> >
>> > In the RFC 2109, the "domain" attribute is optional. =A0Specifically, =
it
>> says:
>> >
>> > =A0 Domain=3Ddomain
>> > =A0 =A0 =A0Optional. =A0The Domain attribute specifies the domain for =
which
>> > the
>> > =A0 =A0 =A0cookie is valid. =A0An explicitly specified domain must alw=
ays
>> > start
>> > =A0 =A0 =A0with a dot.
>> >
>> > =A0It also defined a default:
>> > =A0 Domain Defaults to the request-host. =A0(Note that there is no dot=
 at
>> > =A0 =A0 =A0 =A0 =A0the beginning of request-host.)
>>
>> Right.
>>
>> > I found this in the -20 draft:
>> >
>> > 4.1.2.3:
>> > =A0 If the server omits the Domain attribute, the user
>> > =A0 agent will return the cookie only to the origin server.
>> >
>> > =A0 =A0 =A0WARNING: Some existing user agents treat an absent Domain
>> > =A0 =A0 =A0attribute as if the Domain attribute were present and conta=
ined
>> > =A0 =A0 =A0the current host name. =A0For example, if example.com retur=
ns a
>> > Set-
>> > =A0 =A0 =A0Cookie header without a Domain attribute, these user agents=
 will
>> > =A0 =A0 =A0erroneously send the cookie to www.example.com as well.
>> >
>> > If I received a cookie without a domain from test.example.com, I would
>> > assume the cookie's domain is "test.example.com". =A0The wording above
>> > confuses me a little, as I would bind the cookie to the host I
>> accessed.
>> > The first sentence in the WARNING seems like what I should do, but the
>> > example presented is not the origin server or the "current host
>> name".
>> > I agree that it would be an error for a browser to assume a larger
>> > domain scope than just the single host being accessed. =A0But, I would
>> > think that absence of or an empty string for "Domain" would be bound
>> > only to the server being accessed. =A0I believe that is the intent, as
>> > stated in other sections, but the warning text seems to suggest
>> otherwise when I read it.
>>
>> Right, the issue is that some browsers forget to set the host-only flag
>> on the cookie if you omit the Domain attribute. =A0That causes the cooki=
e
>> to be returned to the origin server as well as all subdomains of the
>> origin server's host name.
>>
>> > In Section 5.2.3, this text appears:
>> > =A0 If the attribute-value is empty, the behavior is undefined.
>> > However,
>> > =A0 user agent SHOULD ignore the cookie-av entirely.
>> >
>> > Why would the behavior be undefined? =A0Why would these not be treated
>> > identically?
>> > Set-Cookie: mycookie=3Dmyvalue; path=3D/
>> > Set-Cookie: mycookie=3Dmyvalue; path=3D/; domain=3D
>>
>> It's undefined because different implementations do different things and
>> I didn't have the energy or the inclination to beat them up on this
>> point. =A0They should do what the document suggests, but it's not the en=
d
>> of the world fi they don't.
>>
>> > Why isn't an empty string a valid value? =A0I ask, because we assign a=
n
>> > empty value internally. =A0In 5.3, paragraph 4, we have:
>> >
>> > =A0 4. =A0 If the cookie-attribute-list contains an attribute with an
>> > =A0 =A0 =A0 =A0attribute-name of "Domain":
>> >
>> > =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the attribute-value of=
 the last
>> > =A0 =A0 =A0 =A0 =A0 attribute in the cookie-attribute-list with an
>> > attribute-name
>> > =A0 =A0 =A0 =A0 =A0 of "Domain".
>> >
>> > =A0 =A0 =A0 =A0Otherwise:
>> >
>> > =A0 =A0 =A0 =A0 =A0 Let the domain-attribute be the empty string.
>> >
>> > So, this does suggest "domain=3D" would be the same as absence of the
>> > domain parameter, no?
>>
>> Well, the complexity actually arises when the server provides multiple
>> Domain attributes, some of which are the empty string. =A0Which one
>> actually controls the result varies.
>>
>> The rules are written such that if you follow them, you get reasonable
>> behavior that matches practice. =A0There's also some wiggle room to in
>> this extreme corner case (multiple attributes, one of which is the empty
>> string). =A0We could nail that issue down, but it didn't seem worth the
>> hassle.
>>
>> >=A0Paragraph 6 then explains that in such cases, the domain is =A0assig=
ned
>> >to "the canonicalized request-host", which is consistent.
>> >
>> > So, any reason why the Domain a/v syntax isn't this?
>> > domain-value =A0 =A0 =A0=3D <subdomain> | ""
>>
>> Just because it's nonsense semantically and an interoperability
>> sandtrap. =A0If you'd like to use the empty string, just omit the Domain
>> attribute instead. =A0Your life and everyone else's life will be happier
>> for it.
>>
>> Adam
>>
>>
>> >> -----Original Message-----
>> >> From: http-state-bounces@ietf.org
>> >> [mailto:http-state-bounces@ietf.org]
>> >> On Behalf Of Internet-Drafts@ietf.org
>> >> Sent: Sunday, December 19, 2010 2:00 PM
>> >> To: i-d-announce@ietf.org
>> >> Cc: http-state@ietf.org
>> >> Subject: [http-state] I-D Action:draft-ietf-httpstate-cookie-20.txt
>> >>
>> >> A New Internet-Draft is available from the on-line Internet-Drafts
>> >> directories.
>> >> This draft is a work item of the HTTP State Management Mechanism
>> >> Working Group of the IETF.
>> >>
>> >>
>> >> =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : HTTP State Management Mechani=
sm
>> >> =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : A. Barth
>> >> =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-httpstate-cookie-20.=
txt
>> >> =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 44
>> >> =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-12-19
>> >>
>> >> This document defines the HTTP Cookie and Set-Cookie header fields.
>> >> These header fields can be used by HTTP servers to store state
>> >> (called
>> >> cookies) at HTTP user agents, letting the servers maintain a stateful
>> >> session over the mostly stateless HTTP protocol. =A0Although cookies
>> >> have many historical infelicities that degrade their security and
>> >> privacy, the Cookie and Set-Cookie header fields are widely used on
>> >> the Internet.Editorial Note (To be removed by RFC Editor)
>> >>
>> >> If you have suggestions for improving this document, please send
>> >> email to <mailto:http-state@ietf.org>. =A0Suggestions with test cases
>> >> are especially appreciated. =A0Further Working Group information is
>> >> available from <https://tools.ietf.org/wg/httpstate/>.
>> >>
>> >> A URL for this Internet-Draft is:
>> >> http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-20.tx
>> >> t
>> >>
>> >> Internet-Drafts are also available by anonymous FTP at:
>> >> ftp://ftp.ietf.org/internet-drafts/
>> >>
>> >> Below is the data which will enable a MIME compliant mail reader
>> >> implementation to automatically retrieve the ASCII version of the
>> >> Internet-Draft.
>> >
>> >
>
>

From paulej@packetizer.com  Thu Jan  6 18:11:18 2011
Return-Path: <paulej@packetizer.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 C2DA53A6DF7 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 18:11:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_73=0.6]
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 mzYqvec9P1Ae for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 18:11:17 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id A5A753A6DD2 for <http-state@ietf.org>; Thu,  6 Jan 2011 18:11:17 -0800 (PST)
Received: from sydney (rrcs-98-101-155-83.midsouth.biz.rr.com [98.101.155.83]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id p072DGmH001169 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jan 2011 21:13:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1294366402; bh=Tfw2FGLqp3KW47CO69AuZiiXsOUOWZc80LnHa1ZL1ZE=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=GoEp2EBSDzRdQOlVePRDVHeZ1ysbSgrWJKQ5ACbMx2vGZTbZqkjCDhQyE3DcBZcZk iIzoNuaDIrraVJN7oKz1Wh2OyNRM8KyXnKSBMjX2udv2pofkIklFSkGd/SG6BFsejL 6WrPAft/r3PzUu0+RjEKoCk+0VxmJDH8FIbKFLuI=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Adam Barth'" <ietf@adambarth.com>
References: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com> <07d501cbadf0$31e13470$95a39d50$@packetizer.com> <AANLkTi=M7ZW2FGtV6okTOswiS3sQPM8O07xhF6ifMwVK@mail.gmail.com>
In-Reply-To: <AANLkTi=M7ZW2FGtV6okTOswiS3sQPM8O07xhF6ifMwVK@mail.gmail.com>
Date: Thu, 6 Jan 2011 21:13:07 -0500
Message-ID: <081f01cbae10$706f6750$514e35f0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQOsylhA7Jc/U76u6c6ZWuz0pv934QKw1aHPAkTKXpKP2sHOEA==
Content-Language: en-us
Cc: http-state@ietf.org
Subject: Re: [http-state] The Domain attribute (was Re: I-D Action:draft-ietf-httpstate-cookie-20.txt)
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: Fri, 07 Jan 2011 02:11:18 -0000

Adam,

> > The empty string is also used in this example:
> > Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT
>=20
> Why is that?  The "lang" attribute has not been defined, so the valid
> values for the lang attribute certainly haven't been defined.
>=20
> > For this reason, this might be another area where we need to =
consider
> > a syntax change:
> > cookie-pair =A0 =A0 =A0 =3D cookie-name "=3D" cookie-value =
cookie-name =A0 =A0 =A0 =3D
> > token cookie-value =A0 =A0 =A0=3D token | ""
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^
>=20
> I would not recommend that servers send empty attribute values.
> That's just asking for interoperability problems.

But, "lang" is sent in the above example as an empty string.  Thus, this
should be the definition of "cookie-value":
cookie-value      =3D token | ""

As the text is current written, I think this is illegal:
Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT

> > In any case, I don't have a strong preference and if the group wants
> > to change the syntax. =A0That's OK. =A0It just seems allowing an =
empty
> > string for "Domain" is more consistent with the text than not.
>=20
> More consistent with what text?  The text in the User Agent =
Requirements
> section is for user agents and not for servers.  You're talking about
> what's useful for syntax for servers to generate.  It's not useful for
> servers to generate empty Domain attributes.  Instead of generating an
> empty Domain attribute, they ought to simply omit the Domain =
attribute.

OK, that's a good argument. :-)

Paul


From ietf@adambarth.com  Thu Jan  6 18:16:41 2011
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 1C4F23A6DD2 for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 18:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.659
X-Spam-Level: 
X-Spam-Status: No, score=-3.659 tagged_above=-999 required=5 tests=[AWL=-1.282, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_73=0.6, 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 761M967WWX+Q for <http-state@core3.amsl.com>; Thu,  6 Jan 2011 18:16:40 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id A7F133A6D19 for <http-state@ietf.org>; Thu,  6 Jan 2011 18:16:39 -0800 (PST)
Received: by gwj17 with SMTP id 17so9110816gwj.31 for <http-state@ietf.org>; Thu, 06 Jan 2011 18:18:46 -0800 (PST)
Received: by 10.150.181.18 with SMTP id d18mr1862998ybf.46.1294366726084; Thu, 06 Jan 2011 18:18:46 -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 i39sm809798yhd.11.2011.01.06.18.18.44 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 18:18:44 -0800 (PST)
Received: by iwn40 with SMTP id 40so17896568iwn.31 for <http-state@ietf.org>; Thu, 06 Jan 2011 18:18:43 -0800 (PST)
Received: by 10.231.19.138 with SMTP id a10mr8794178ibb.127.1294366723406; Thu, 06 Jan 2011 18:18:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.11.140 with HTTP; Thu, 6 Jan 2011 18:18:13 -0800 (PST)
In-Reply-To: <081f01cbae10$706f6750$514e35f0$@packetizer.com>
References: <AANLkTinK+2sfe4UZLKF5G0MLrQ6es2BfTHwtT769sgSM@mail.gmail.com> <07d501cbadf0$31e13470$95a39d50$@packetizer.com> <AANLkTi=M7ZW2FGtV6okTOswiS3sQPM8O07xhF6ifMwVK@mail.gmail.com> <081f01cbae10$706f6750$514e35f0$@packetizer.com>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 6 Jan 2011 18:18:13 -0800
Message-ID: <AANLkTikniWbJ1Whw-CWkRXimKqGq8GptS6zNQ56D=kWD@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: Re: [http-state] The Domain attribute (was Re: I-D Action:draft-ietf-httpstate-cookie-20.txt)
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: Fri, 07 Jan 2011 02:16:41 -0000

On Thu, Jan 6, 2011 at 6:13 PM, Paul E. Jones <paulej@packetizer.com> wrote=
:
>> > The empty string is also used in this example:
>> > Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT
>>
>> Why is that? =A0The "lang" attribute has not been defined, so the valid
>> values for the lang attribute certainly haven't been defined.
>>
>> > For this reason, this might be another area where we need to consider
>> > a syntax change:
>> > cookie-pair =A0 =A0 =A0 =3D cookie-name "=3D" cookie-value cookie-name=
 =A0 =A0 =A0 =3D
>> > token cookie-value =A0 =A0 =A0=3D token | ""
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^
>>
>> I would not recommend that servers send empty attribute values.
>> That's just asking for interoperability problems.
>
> But, "lang" is sent in the above example as an empty string. =A0Thus, thi=
s
> should be the definition of "cookie-value":
> cookie-value =A0 =A0 =A0=3D token | ""
>
> As the text is current written, I think this is illegal:
> Set-Cookie: lang=3D; Expires=3DSun, 06 Nov 1994 08:49:37 GMT

Oh, sorry, got confused.  Empty strings should be allowed for
cooke-values but not for attribute-values.

Adam


>> > In any case, I don't have a strong preference and if the group wants
>> > to change the syntax. =A0That's OK. =A0It just seems allowing an empty
>> > string for "Domain" is more consistent with the text than not.
>>
>> More consistent with what text? =A0The text in the User Agent Requiremen=
ts
>> section is for user agents and not for servers. =A0You're talking about
>> what's useful for syntax for servers to generate. =A0It's not useful for
>> servers to generate empty Domain attributes. =A0Instead of generating an
>> empty Domain attribute, they ought to simply omit the Domain attribute.
>
> OK, that's a good argument. :-)
>
> Paul
>
>

From Internet-Drafts@ietf.org  Wed Jan 19 15:15:03 2011
Return-Path: <Internet-Drafts@ietf.org>
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 115D23A71DF; Wed, 19 Jan 2011 15:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 nV0dBrihtY5y; Wed, 19 Jan 2011 15:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11D393A7021; Wed, 19 Jan 2011 15:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110119231502.3778.58453.idtracker@localhost>
Date: Wed, 19 Jan 2011 15:15:02 -0800
Cc: http-state@ietf.org
Subject: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt
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: Wed, 19 Jan 2011 23:15:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the HTTP State Management Mechanism Working Group of the IETF.


	Title           : HTTP State Management Mechanism
	Author(s)       : A. Barth
	Filename        : draft-ietf-httpstate-cookie-21.txt
	Pages           : 43
	Date            : 2011-01-19

This document defines the HTTP Cookie and Set-Cookie header fields.
These header fields can be used by HTTP servers to store state
(called cookies) at HTTP user agents, letting the servers maintain a
stateful session over the mostly stateless HTTP protocol.  Although
cookies have many historical infelicities that degrade their security
and privacy, the Cookie and Set-Cookie header fields are widely used
on the Internet.Editorial Note (To be removed by RFC Editor)

If you have suggestions for improving this document, please send
email to <mailto:http-state@ietf.org>.  Suggestions with test cases
are especially appreciated.  Further Working Group information is
available from <https://tools.ietf.org/wg/httpstate/>.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-21.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-httpstate-cookie-21.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-19151038.I-D@ietf.org>


--NextPart--

From stpeter@stpeter.im  Wed Jan 19 15:36:46 2011
Return-Path: <stpeter@stpeter.im>
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 7BEB628C123 for <http-state@core3.amsl.com>; Wed, 19 Jan 2011 15:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 XciRMUwZsZfX for <http-state@core3.amsl.com>; Wed, 19 Jan 2011 15:35:44 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 1747F3A71F0 for <http-state@ietf.org>; Wed, 19 Jan 2011 15:35:44 -0800 (PST)
Received: from squire.local (dsl-251-175.dynamic-dsl.frii.net [216.17.251.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4B79E400EE for <http-state@ietf.org>; Wed, 19 Jan 2011 16:54:03 -0700 (MST)
Message-ID: <4D3775EF.1090602@stpeter.im>
Date: Wed, 19 Jan 2011 16:38:23 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: http-state@ietf.org
References: <20110119231502.3778.58453.idtracker@localhost>
In-Reply-To: <20110119231502.3778.58453.idtracker@localhost>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030202020202010804020402"
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt
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: Wed, 19 Jan 2011 23:36:47 -0000

This is a cryptographically signed message in MIME format.

--------------ms030202020202010804020402
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In case you were wondering, Adam has submitted this version to address
feedback from IESG members. The diff is here:

http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-httpstate-cookie-21

Thanks, Adam!

On 1/19/11 4:15 PM, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> This draft is a work item of the HTTP State Management Mechanism Workin=
g Group of the IETF.
>=20
>=20
> 	Title           : HTTP State Management Mechanism
> 	Author(s)       : A. Barth
> 	Filename        : draft-ietf-httpstate-cookie-21.txt
> 	Pages           : 43
> 	Date            : 2011-01-19
>=20
> This document defines the HTTP Cookie and Set-Cookie header fields.
> These header fields can be used by HTTP servers to store state
> (called cookies) at HTTP user agents, letting the servers maintain a
> stateful session over the mostly stateless HTTP protocol.  Although
> cookies have many historical infelicities that degrade their security
> and privacy, the Cookie and Set-Cookie header fields are widely used
> on the Internet.Editorial Note (To be removed by RFC Editor)
>=20
> If you have suggestions for improving this document, please send
> email to <mailto:http-state@ietf.org>.  Suggestions with test cases
> are especially appreciated.  Further Working Group information is
> available from <https://tools.ietf.org/wg/httpstate/>.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-httpstate-cookie-21.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20


--------------ms030202020202010804020402
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEx
OTIzMzgyM1owIwYJKoZIhvcNAQkEMRYEFBzVHqxLgIfqWAIgUG7jz49XgPDzMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQCIY7/ouhlI7UNjf1tv0PDK4wyH/WiFPEiBkMBiQRDSpGbvjGhgO/0cfqAl
hkkt7qRqFjyYvNgpUi/UI3WmP+3xkLJCqw2sqZlSLUENzE2rKy7oUabV9D7UY21RXHYyFHKL
g/2Fw/YZhql9cP6uow1OnXeuN0ewbgYZn5Q0cegznKLgsWo5REFyLEplsCs9SHUK09DEWB1y
DsIUkgi9V4gjzCTopDVKWzl2fJb7vRI8c3qUX1/EyMs5NZ4nUGjZp/oNFnkGFJsYN9bNohsz
YIykdbnkUKDthvBxwe/0axUx8YlD3KrfJMQQUCwyXYMpnQOjZcRsvSdfFBmfIkF75CyNAAAA
AAAA
--------------ms030202020202010804020402--

From julian.reschke@gmx.de  Thu Jan 20 00:37:57 2011
Return-Path: <julian.reschke@gmx.de>
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 23B293A70EE for <http-state@core3.amsl.com>; Thu, 20 Jan 2011 00:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.935
X-Spam-Level: 
X-Spam-Status: No, score=-103.935 tagged_above=-999 required=5 tests=[AWL=-1.336, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 l3TOqCmDTBEP for <http-state@core3.amsl.com>; Thu, 20 Jan 2011 00:37:56 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id DA9523A70E6 for <http-state@ietf.org>; Thu, 20 Jan 2011 00:37:55 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2011 08:40:34 -0000
Received: from p508FD1B8.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.209.184] by mail.gmx.net (mp060) with SMTP; 20 Jan 2011 09:40:34 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1972WFwSdp7+XjtIB76SNY6yO/+NkU6kml0n67+ud SgaVo/hfEPbDlt
Message-ID: <4D37F4EE.80700@gmx.de>
Date: Thu, 20 Jan 2011 09:40:14 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: "http-state@ietf.org" <http-state@ietf.org>
References: <20110119231502.3778.58453.idtracker@localhost>
In-Reply-To: <20110119231502.3778.58453.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt
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, 20 Jan 2011 08:37:57 -0000

On 20.01.2011 00:15, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the HTTP State Management Mechanism Working Group of the IETF.
>
>
> 	Title           : HTTP State Management Mechanism
> 	Author(s)       : A. Barth
> 	Filename        : draft-ietf-httpstate-cookie-21.txt
> 	Pages           : 43
> 	Date            : 2011-01-19
> ...

Nit: there's an unused reference to RFC 5246, probably caused by a 
change in draft 20 
(<http://tools.ietf.org/rfcdiff?url2=draft-ietf-httpstate-cookie-20.txt> 
and 
<http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-httpstate-cookie-21.txt>).

There's also ABNF text that needs to be reformatted due to the width 
constraints...

Best regards, Julian

From ietf@adambarth.com  Thu Jan 20 00:39:59 2011
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 5281F3A71F8 for <http-state@core3.amsl.com>; Thu, 20 Jan 2011 00:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.785
X-Spam-Level: 
X-Spam-Status: No, score=-3.785 tagged_above=-999 required=5 tests=[AWL=-0.808, 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 BmP-alnVLxsF for <http-state@core3.amsl.com>; Thu, 20 Jan 2011 00:39:58 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 69EE43A71ED for <http-state@ietf.org>; Thu, 20 Jan 2011 00:39:58 -0800 (PST)
Received: by ywk9 with SMTP id 9so110748ywk.31 for <http-state@ietf.org>; Thu, 20 Jan 2011 00:42:40 -0800 (PST)
Received: by 10.151.48.12 with SMTP id a12mr2164635ybk.159.1295512960468; Thu, 20 Jan 2011 00:42:40 -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 p2sm5049786ybh.15.2011.01.20.00.42.38 (version=SSLv3 cipher=RC4-MD5); Thu, 20 Jan 2011 00:42:38 -0800 (PST)
Received: by iwn40 with SMTP id 40so380321iwn.31 for <http-state@ietf.org>; Thu, 20 Jan 2011 00:42:37 -0800 (PST)
Received: by 10.231.192.7 with SMTP id do7mr2117564ibb.102.1295512957570; Thu, 20 Jan 2011 00:42:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.38.5 with HTTP; Thu, 20 Jan 2011 00:42:07 -0800 (PST)
In-Reply-To: <4D37F4EE.80700@gmx.de>
References: <20110119231502.3778.58453.idtracker@localhost> <4D37F4EE.80700@gmx.de>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 20 Jan 2011 00:42:07 -0800
Message-ID: <AANLkTi=KJWYVdLKbdtXgZb68bsQHEWw0tuqMdLRKTKMw@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "http-state@ietf.org" <http-state@ietf.org>
Subject: Re: [http-state] I-D Action:draft-ietf-httpstate-cookie-21.txt
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, 20 Jan 2011 08:39:59 -0000

Thanks.

Adam


On Thu, Jan 20, 2011 at 12:40 AM, Julian Reschke <julian.reschke@gmx.de> wr=
ote:
> On 20.01.2011 00:15, Internet-Drafts@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the HTTP State Management Mechanism Working
>> Group of the IETF.
>>
>>
>> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : HTTP State Management Mechani=
sm
>> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : A. Barth
>> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-httpstate-cookie-21.=
txt
>> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 43
>> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-01-19
>> ...
>
> Nit: there's an unused reference to RFC 5246, probably caused by a change=
 in
> draft 20
> (<http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-httpstate-cookie-20.txt=
> and
> <http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-h=
ttpstate-cookie-21.txt>).
>
> There's also ABNF text that needs to be reformatted due to the width
> constraints...
>
> Best regards, Julian
>

From stpeter@stpeter.im  Wed Jan 26 18:40:48 2011
Return-Path: <stpeter@stpeter.im>
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 6BFDE3A6906 for <http-state@core3.amsl.com>; Wed, 26 Jan 2011 18:40:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pi8nAm88rv62 for <http-state@core3.amsl.com>; Wed, 26 Jan 2011 18:40:47 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 316323A6898 for <http-state@ietf.org>; Wed, 26 Jan 2011 18:40:47 -0800 (PST)
Received: from squire.local (dsl-251-175.dynamic-dsl.frii.net [216.17.251.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 095EF400F6; Wed, 26 Jan 2011 20:00:05 -0700 (MST)
Message-ID: <4D40DBD3.6070603@stpeter.im>
Date: Wed, 26 Jan 2011 19:43:31 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Discuss HTTP State Management Mechanism <http-state@ietf.org>,  Robert Sparks <rjsparks@nostrum.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060903000909060505040400"
Subject: [http-state] cookie server conformance
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, 27 Jan 2011 02:40:48 -0000

This is a cryptographically signed message in MIME format.

--------------ms060903000909060505040400
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

During IESG review, Robert Sparks posted the following DISCUSS regarding
draft-ietf-httpstate-cookie:

   In 4.1.1 (Syntax) - Why is the specification part of this proposed
   standard allowing implementations to  violate the grammar defined by
   this standard? The SHOULD NOT in the first paragraph of this section
   must be a MUST NOT. If the intent is to make sure clients are
   liberal in what they accept because existing servers may generate
   non-conformant grammar, just say that (and if possible, point to
   what they might need to expect). If the intent is to allow servers
   that are compliant to generate messages not covered by this grammar,
   then the grammar is incorrect. If that's the case, the grammar
   should be extended to  allow the alternate behavior and the
   document's prose can say that servers SHOULD NOT use those parts of
   the grammar.

We've had some discussion between Robert, Adam, Jeff, and me to clarify
Robert's concerns. In essence, Robert is concerned that it's merely
implicit that a compliant server MUST NOT generate cookies that don't
conform to the well-behaved profile defined in Section 4. He derives
this conclusion from two pieces of evidence...

First, Section 1 of verson -21 states:

   To maximize interoperability with user agents, servers SHOULD limit
   themselves to the well-behaved profile defined in Section 4 when
   generating cookies.

Second, Section 4 states:

   Servers SHOULD NOT send Set-Cookie headers that fail to conform to
   the following grammar:

Therefore, we can conclude that if a server sends a Set-Cookie header
that violates the grammar, then it is non-conforming. However, we don't
come right out and say that.

To address Robert's concern and to make the constraints more explicit
(it's often problematic to let such things remain implicit), in the
off-list thread with Robert I formulated some proposed text, which I'd
like to share with the working group...

First, I proposed that we could modify Section 1 as follows:

   Compliant servers MUST limit themselves to the well-behaved profile
   defined in Section 4 when generating cookies.

Second, I proposed that we could then simplify Section 4 as follows:

   This section describes the syntax and semantics of a well-behaved
   profile of the Cookie and Set-Cookie headers.

I think that's a bit cleaner because it's not subject to as much
interpretation. However, the change from SHOULD to MUST is not
insignificant, so I think it's something that the working group needs to
discuss.

Your feedback is welcome.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms060903000909060505040400
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEy
NzAyNDMzMVowIwYJKoZIhvcNAQkEMRYEFAEcl3ktMdBEP7QL7fco7NB1wl01MF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQA/osSyNuG58lUn8wvVGPziXBYFFmlBRhKBZ6VwYq49H880zoO1np2QzNjd
en59AY/C4ZUOyvG0+zjTqbbOKxgNsFytAo7NDEL+gPOJIcrGMYnB3gKjCet1NaFY+gcYarVa
YCHRqwZp3A+ZLAXDmjBrTjoZalitP0sz//1I3RKDJyV0OAT2PrN/aOF4wXpdkTFU6C25ugX5
32JbR+vmCwZ9C4iHnFIK9I3JRz6oyaEArkQxbTCdO/0ChmtyNgEEPEwECkZwR2TXfcmSjPlG
CcM/VmeSF+zEhAf9vhptVQ1Lm+9qdtzjn64M+BgSWIl+O8XZFBQJtmYvcXs5W/yEQPNXAAAA
AAAA
--------------ms060903000909060505040400--

From daniel@haxx.se  Thu Jan 27 07:14:03 2011
Return-Path: <daniel@haxx.se>
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 CEDFC3A68B0 for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 07:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.026
X-Spam-Level: 
X-Spam-Status: No, score=-3.026 tagged_above=-999 required=5 tests=[AWL=-0.777, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 3MhlJTmuxr1f for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 07:14:02 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 6CF833A6882 for <http-state@ietf.org>; Thu, 27 Jan 2011 07:14:02 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0RFH4VF030533; Thu, 27 Jan 2011 16:17:04 +0100
Date: Thu, 27 Jan 2011 16:17:04 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4D40DBD3.6070603@stpeter.im>
Message-ID: <alpine.DEB.2.00.1101271611010.24604@tvnag.unkk.fr>
References: <4D40DBD3.6070603@stpeter.im>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: Robert Sparks <rjsparks@nostrum.com>, Discuss HTTP State Management Mechanism <http-state@ietf.org>
Subject: Re: [http-state] cookie server conformance
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, 27 Jan 2011 15:14:03 -0000

On Wed, 26 Jan 2011, Peter Saint-Andre wrote:

>   To maximize interoperability with user agents, servers SHOULD limit
>   themselves to the well-behaved profile defined in Section 4 when
>   generating cookies.

> First, I proposed that we could modify Section 1 as follows:
>
>   Compliant servers MUST limit themselves to the well-behaved profile
>   defined in Section 4 when generating cookies.

+1

I think this is only sensible. This spec documents a way to interoperate with 
cookies and of course we can't interoperate properyl if the spec isn't 
followed so the phrasing makes perfect sense.

If there are servers not adhering to this spec, they're not compliant and we 
should push them to become so. I don't think we gain anything by having that 
softened to a SHOULD.

It's a really good find and fix!

>   This section describes the syntax and semantics of a well-behaved
>   profile of the Cookie and Set-Cookie headers.

Nothing controversial there methinks, looks fine.

-- 

  / daniel.haxx.se

From Jeff.Hodges@KingsMountain.com  Thu Jan 27 14:46:16 2011
Return-Path: <Jeff.Hodges@KingsMountain.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 D18E13A69EC for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 14:46:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.279
X-Spam-Level: 
X-Spam-Status: No, score=-102.279 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4XaFeRZHH1ID for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 14:46:15 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by core3.amsl.com (Postfix) with SMTP id A35C83A69E4 for <http-state@ietf.org>; Thu, 27 Jan 2011 14:46:15 -0800 (PST)
Received: (qmail 11370 invoked by uid 0); 27 Jan 2011 22:49:20 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy1.bluehost.com.bluehost.com with SMTP; 27 Jan 2011 22:49:19 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=EF+WS9HvJdCJlElykylWDNxOwJcphnUTZmsHCi/KVFarqPNIo2THS4sy2i0Kkqmqqg/SMVzqoWj/Pur7xv+yjDuOQzPRkBO2sfRnPAjJlx98TtI4fDUmLVCi7b1wRkQr;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.134]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PiaeV-0000pr-Ag; Thu, 27 Jan 2011 15:49:19 -0700
Message-ID: <4D41F670.2080006@KingsMountain.com>
Date: Thu, 27 Jan 2011 14:49:20 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [http-state] cookie server conformance
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, 27 Jan 2011 22:46:17 -0000

<individual>

 > First, I proposed that we could modify Section 1 as follows:
 >
 >    Compliant servers MUST limit themselves to the well-behaved profile
 >    defined in Section 4 when generating cookies.
 >
 > Second, I proposed that we could then simplify Section 4 as follows:
 >
 >    This section describes the syntax and semantics of a well-behaved
 >    profile of the Cookie and Set-Cookie headers.
 >

+1

</individual>


=JeffH


From Jeff.Hodges@KingsMountain.com  Thu Jan 27 15:03:43 2011
Return-Path: <Jeff.Hodges@KingsMountain.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 D263F3A69F1 for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 15:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.13
X-Spam-Level: 
X-Spam-Status: No, score=-102.13 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 j62e2EEkFWxq for <http-state@core3.amsl.com>; Thu, 27 Jan 2011 15:03:41 -0800 (PST)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id 749A23A69EE for <http-state@ietf.org>; Thu, 27 Jan 2011 15:03:41 -0800 (PST)
Received: (qmail 27076 invoked by uid 0); 27 Jan 2011 23:06:43 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy3.bluehost.com with SMTP; 27 Jan 2011 23:06:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=ySJNEfmiLCCDQ1JzEhOrWzDpPtEzuwcRX3ZfB/EPYBXWLsNU8bUT7ce3gvsBLlGG8ngw8OrbzpkFpeGoNdbNcQg64lrZOjsx/6nT0ff9g9x3RFRNwzb9pMW05kQBaktU;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.134]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PiavL-0004gX-JY for http-state@ietf.org; Thu, 27 Jan 2011 16:06:43 -0700
Message-ID: <4D41FA83.5040302@KingsMountain.com>
Date: Thu, 27 Jan 2011 15:06:43 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: [http-state] consensus call: cookie server conformance
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, 27 Jan 2011 23:03:43 -0000

<chair>

Please see PeterSA's recent message..

   http://www.ietf.org/mail-archive/web/http-state/current/msg01151.html


Absent explicitly expressed opposing views here on the http-state@ mailing 
list, I'm going to interpret the WG's consensus to be in favor of the 
modification as proposed by PeterSA...

 > First, I proposed that we could modify Section 1 as follows:
 >
 >    Compliant servers MUST limit themselves to the well-behaved profile
 >    defined in Section 4 when generating cookies.
 >
 > Second, I proposed that we could then simplify Section 4 as follows:
 >
 >    This section describes the syntax and semantics of a well-behaved
 >    profile of the Cookie and Set-Cookie headers.


Y'all have 1 week, till 2400h PST 3-Feb-2011 (next Thu night) for expressing 
viewpoints on this.

thanks,

=JeffH


</chair>


From Jeff.Hodges@KingsMountain.com  Fri Jan 28 12:55:03 2011
Return-Path: <Jeff.Hodges@KingsMountain.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 2FA6B3A6862 for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 12:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 aXZjp9VaqyqR for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 12:55:02 -0800 (PST)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 0E28E3A680E for <http-state@ietf.org>; Fri, 28 Jan 2011 12:55:02 -0800 (PST)
Received: (qmail 23688 invoked by uid 0); 28 Jan 2011 20:58:09 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 28 Jan 2011 20:58:09 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=SV+qhiuT4WeJm0Iy4bzdy8byvSxFSdc1V/r5l9L4NhRHurX+ZCavdHfGGawQklyV4cwexDMwD+rCqpjF+nWr6LnhwwH8CpFIFPTkIatVArBVa4czuQy0TdtCV9/8Ndep;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.134]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PivOS-0004xR-Ef for http-state@ietf.org; Fri, 28 Jan 2011 13:58:08 -0700
Message-ID: <4D432DE2.8010107@KingsMountain.com>
Date: Fri, 28 Jan 2011 12:58:10 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: [http-state] phase 2 work? (was: cake spec: server-side initiation only?)
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: Fri, 28 Jan 2011 20:55:03 -0000

Adam said..
 >
 > I've been holding off discussing these topics until we're done with
 > the basic cookie spec.  That seems to be mostly wrapping up.  This
 > working group isn't charted to work on improvements to the cookie
 > protocol, but I suspect Jeff would indulge us if we wanted to discuss
 > it for a bit.

sure, at this point it seems draft-ietf-httpstate-cookie is essentially done 
(fingers crossed), so it seems appropriate to discuss where we might want to 
take HTTP State Management (and where we might want to at all).

So please feel free to discuss what you think may be on the proverbial table 
for "phase 2" work if we were to recharter the working group.

thanks,

=JeffH



From Jeff.Hodges@KingsMountain.com  Fri Jan 28 13:01:17 2011
Return-Path: <Jeff.Hodges@KingsMountain.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 3408A3A6874 for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.155
X-Spam-Level: 
X-Spam-Status: No, score=-102.155 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 MIlQdW0NICgu for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:01:16 -0800 (PST)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id 25BB23A68FA for <http-state@ietf.org>; Fri, 28 Jan 2011 13:01:16 -0800 (PST)
Received: (qmail 7134 invoked by uid 0); 28 Jan 2011 21:04:23 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 28 Jan 2011 21:04:23 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=5QGGcs/aDE/fL7Cmu7SRqAVSpD9IQMATkqenW/z8fQPN55JRwZCKpqjYZRDx8aggfpp/ftNPHdNFsZbu188dhxz8N1467xzbo1YPirus97A+VCoBicRyAXp8VYAoeR8W;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.134]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PivUU-00044B-VG for http-state@ietf.org; Fri, 28 Jan 2011 14:04:23 -0700
Message-ID: <4D432F58.3080406@KingsMountain.com>
Date: Fri, 28 Jan 2011 13:04:24 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: [http-state] HTTP WG meeting @IETF-80 Prague CZ ?
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: Fri, 28 Jan 2011 21:01:17 -0000

Do folks feel there is a need to hold a f2f HTTP WG meeting @IETF-80 Prague CZ 
(March 27-April 1) ?

We have a couple weeks to decide.

draft-ietf-httpstate-cookie is almost complete. If folks have burning ideas for 
new/enhanced HTTP State Management approaches to present/discuss face-to-face, 
and are prepared to do so, that'd be a reason to have a session. Otherwise, we 
can skip IETF-80, and figure out whether we actually have follow-on work, what 
it might be, discuss rechartering, and see about meeting @IETF-81 Quebec (say).

thanks,

=JeffH



From ietf@adambarth.com  Fri Jan 28 13:47:11 2011
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 4424C3A697A for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.725
X-Spam-Level: 
X-Spam-Status: No, score=-3.725 tagged_above=-999 required=5 tests=[AWL=-0.748, 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 pAk4RX3tCi9J for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:47:10 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4AAE23A6968 for <http-state@ietf.org>; Fri, 28 Jan 2011 13:47:10 -0800 (PST)
Received: by vws7 with SMTP id 7so1301259vws.31 for <http-state@ietf.org>; Fri, 28 Jan 2011 13:50:17 -0800 (PST)
Received: by 10.220.178.140 with SMTP id bm12mr826051vcb.18.1296251415531; Fri, 28 Jan 2011 13:50:15 -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 c4sm6252107vcc.6.2011.01.28.13.50.13 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Jan 2011 13:50:14 -0800 (PST)
Received: by iwn40 with SMTP id 40so3847128iwn.31 for <http-state@ietf.org>; Fri, 28 Jan 2011 13:50:12 -0800 (PST)
Received: by 10.231.30.73 with SMTP id t9mr3358843ibc.64.1296251412900; Fri, 28 Jan 2011 13:50:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.35.13 with HTTP; Fri, 28 Jan 2011 13:49:42 -0800 (PST)
In-Reply-To: <4D432DE2.8010107@KingsMountain.com>
References: <4D432DE2.8010107@KingsMountain.com>
From: Adam Barth <ietf@adambarth.com>
Date: Fri, 28 Jan 2011 13:49:42 -0800
Message-ID: <AANLkTi=f3Jw=hffHjjL2vMx2zVWiCQDOjM3PE_DCCQgC@mail.gmail.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] phase 2 work? (was: cake spec: server-side initiation only?)
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: Fri, 28 Jan 2011 21:47:11 -0000

On Fri, Jan 28, 2011 at 12:58 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:
> Adam said..
>> I've been holding off discussing these topics until we're done with
>> the basic cookie spec. =A0That seems to be mostly wrapping up. =A0This
>> working group isn't charted to work on improvements to the cookie
>> protocol, but I suspect Jeff would indulge us if we wanted to discuss
>> it for a bit.
>
> sure, at this point it seems draft-ietf-httpstate-cookie is essentially d=
one
> (fingers crossed), so it seems appropriate to discuss where we might want=
 to
> take HTTP State Management (and where we might want to at all).
>
> So please feel free to discuss what you think may be on the proverbial ta=
ble
> for "phase 2" work if we were to recharter the working group.

I'm still interested in "phase 2" work.  We've been kicking around
with a bunch of different designs.  The main problems I'd like to
solve are the following:

1) Privacy.  Cookies have terrible privacy.  If we could design a
state management mechanism with better privacy properties, the world
would be a happier place.

2) Integrity.  If you run an HTTPS site, you can protect the
confidentiality of your session from eavesdroppers, but you can't
prevent active network attackers from overwriting your cookies and
disrupting the integrity of your sessions.

3) Federation.  To share a session between two servers with cookies,
you need to use a shared secret, which means both parties can
impersonate the user to the other.  Ideally, you'd be able to federate
your session (e.g., between login.example.com, mail.example.com, and
photos.example.com) without giving away your credentials.

At this point, we have some reasonable designs that address (2) and
(3), but we don't have much of a handle on how to address (1).  I'm
happy to share those ideas with the working group.  I'd also like to
invite folks to suggest problems that they'd like to see "phase 2"
work address.

Adam

From dan.winship@gmail.com  Fri Jan 28 13:57:57 2011
Return-Path: <dan.winship@gmail.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 A55B73A697B for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:57:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.064
X-Spam-Level: 
X-Spam-Status: No, score=-3.064 tagged_above=-999 required=5 tests=[AWL=-1.387, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 FPfip4JaOM73 for <http-state@core3.amsl.com>; Fri, 28 Jan 2011 13:57:57 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id F37A53A6975 for <http-state@ietf.org>; Fri, 28 Jan 2011 13:57:56 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id ACC4934A13; Fri, 28 Jan 2011 17:01:02 -0500 (EST)
Message-ID: <4D433C9A.7010203@gmail.com>
Date: Fri, 28 Jan 2011 17:00:58 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: =JeffH <Jeff.Hodges@KingsMountain.com>
References: <4D41FA83.5040302@KingsMountain.com>
In-Reply-To: <4D41FA83.5040302@KingsMountain.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Fri, 28 Jan 2011 21:57:57 -0000

On 01/27/2011 06:06 PM, =JeffH wrote:
>> First, I proposed that we could modify Section 1 as follows:
>>
>>    Compliant servers MUST limit themselves to the well-behaved profile
>>    defined in Section 4 when generating cookies.
>>
>> Second, I proposed that we could then simplify Section 4 as follows:
>>
>>    This section describes the syntax and semantics of a well-behaved
>>    profile of the Cookie and Set-Cookie headers.

-1, because Section 4 says "cookie-value=token", which is annoying
(since it prohibits both base64 and URI encoding, both of which are
commonly used) and unnecessary for interoperability (both existing and
future clients will DTRT with non-token values) and widely violated by
real-world servers that would otherwise be considered well-behaved.

I suppose I could probably be happy with

    cookie-value  = token | base64-string
    base64-string = <a base64 string, defined in [RFC4648], Section 4>

and then change the later Base 16 reference back to Base 64. This still
declares lots of perfectly-interoperable servers "non-compliant", but it
at least provides them with a sane way out.

-- Dan


From annevk@opera.com  Sat Jan 29 02:21:52 2011
Return-Path: <annevk@opera.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 394883A697A for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 02:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 C5CKCksETJgM for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 02:21:51 -0800 (PST)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id D2D7E3A693A for <http-state@ietf.org>; Sat, 29 Jan 2011 02:21:50 -0800 (PST)
Received: from anne-van-kesterens-macbook-pro.local (5355737B.cm-6-6b.dynamic.ziggo.nl [83.85.115.123]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0TAOtPS019488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 29 Jan 2011 10:24:56 GMT
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: =JeffH <Jeff.Hodges@kingsmountain.com>, "Dan Winship" <dan.winship@gmail.com>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com>
Date: Sat, 29 Jan 2011 11:24:57 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.vp2e7uyj64w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <4D433C9A.7010203@gmail.com>
User-Agent: Opera Mail/11.01 (MacIntel)
X-Scanned-By: MIMEDefang 2.64 on 213.236.208.81
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 10:21:52 -0000

On Fri, 28 Jan 2011 23:00:58 +0100, Dan Winship <dan.winship@gmail.com>  
wrote:
> -1, because Section 4 says "cookie-value=token", which is annoying
> (since it prohibits both base64 and URI encoding, both of which are
> commonly used) and unnecessary for interoperability (both existing and
> future clients will DTRT with non-token values) and widely violated by
> real-world servers that would otherwise be considered well-behaved.
>
> I suppose I could probably be happy with
>
>     cookie-value  = token | base64-string
>     base64-string = <a base64 string, defined in [RFC4648], Section 4>
>
> and then change the later Base 16 reference back to Base 64. This still
> declares lots of perfectly-interoperable servers "non-compliant", but it
> at least provides them with a sane way out.

Why would we not want to their usage conforming too?


-- 
Anne van Kesteren
http://annevankesteren.nl/

From dan.winship@gmail.com  Sat Jan 29 08:12:01 2011
Return-Path: <dan.winship@gmail.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 B70833A6833 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 08:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.717
X-Spam-Level: 
X-Spam-Status: No, score=-2.717 tagged_above=-999 required=5 tests=[AWL=-1.040, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 47PvZbzAE428 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 08:12:00 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id C01E83A6814 for <http-state@ietf.org>; Sat, 29 Jan 2011 08:12:00 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id 952E734A3D; Sat, 29 Jan 2011 11:15:09 -0500 (EST)
Message-ID: <4D443D0C.2050009@gmail.com>
Date: Sat, 29 Jan 2011 11:15:08 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: Anne van Kesteren <annevk@opera.com>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com> <op.vp2e7uyj64w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <op.vp2e7uyj64w2qv@anne-van-kesterens-macbook-pro.local>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 16:12:01 -0000

On 01/29/2011 05:24 AM, Anne van Kesteren wrote:
> On Fri, 28 Jan 2011 23:00:58 +0100, Dan Winship <dan.winship@gmail.com>
> wrote:
>> -1, because Section 4 says "cookie-value=token", which is annoying
>> (since it prohibits both base64 and URI encoding, both of which are
>> commonly used) and unnecessary for interoperability (both existing and
>> future clients will DTRT with non-token values) and widely violated by
>> real-world servers that would otherwise be considered well-behaved.
>>
>> I suppose I could probably be happy with
>>
>>     cookie-value  = token | base64-string
>>     base64-string = <a base64 string, defined in [RFC4648], Section 4>
>>
>> and then change the later Base 16 reference back to Base 64. This still
>> declares lots of perfectly-interoperable servers "non-compliant", but it
>> at least provides them with a sane way out.
> 
> Why would we not want to their usage conforming too?

Well, really, very few servers are going to be fully conforming right
away, since the majority don't use rfc1123-date for Expires, etc.
(There's no way we can have a sane server grammar and NOT declare at
least 50% of existing servers non-compliant.) The question is how hard
it is for them to become compliant (if they care) and how hard it is for
new servers to start out compliant. (And how ugly we want to let the
"sane" grammar get.)

But then again, why should servers care about becoming compliant?
Compliant clients MUST be able to deal with servers that violate every
single line of the Section 4 grammar, and non-compliant clients are not
guaranteed to deal with Max-Age, so for a server, compliance with the
section 4 grammar is neither necessary nor sufficient to guarantee
interoperability. So what exactly is "compliant server" supposed to
mean, besides "You get a gold star"?

I think "well-behaved" was a good description of Section 4, and we
should just leave it at that, and not even say that servers SHOULD obey it.

(So that's a change to my previous vote. I still think we should open up
the definition of cookie-value a bit, to closer reflect reality, and to
get rid of the silly Base 16 suggestion. But I'm -1 to "MUST" even after
that.)

-- Dan

From daniel@haxx.se  Sat Jan 29 08:48:57 2011
Return-Path: <daniel@haxx.se>
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 A35063A6842 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 08:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[AWL=-0.749, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 14up66M98RBs for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 08:48:56 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 2E1A43A6840 for <http-state@ietf.org>; Sat, 29 Jan 2011 08:48:55 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0TGq4x7031255; Sat, 29 Jan 2011 17:52:04 +0100
Date: Sat, 29 Jan 2011 17:52:04 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Dan Winship <dan.winship@gmail.com>
In-Reply-To: <4D433C9A.7010203@gmail.com>
Message-ID: <alpine.DEB.2.00.1101291735580.10943@tvnag.unkk.fr>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: =JeffH <Jeff.Hodges@KingsMountain.com>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 16:48:57 -0000

On Fri, 28 Jan 2011, Dan Winship wrote:

>>>    This section describes the syntax and semantics of a well-behaved
>>>    profile of the Cookie and Set-Cookie headers.
>
> -1, because Section 4 says "cookie-value=token", which is annoying
> (since it prohibits both base64 and URI encoding, both of which are
> commonly used)

I hadn't really considered these details about 'token' there and I agree that 
it seems a bit too strict.

Why did we limit it like that?

-- 

  / daniel.haxx.se

From ietf@adambarth.com  Sat Jan 29 11:34:49 2011
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 6E1453A6856 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 11:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.721
X-Spam-Level: 
X-Spam-Status: No, score=-3.721 tagged_above=-999 required=5 tests=[AWL=-0.744, 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 JuEmWIDEDA-R for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 11:34:48 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 6CEBF3A6826 for <http-state@ietf.org>; Sat, 29 Jan 2011 11:34:48 -0800 (PST)
Received: by yie19 with SMTP id 19so1702865yie.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 11:37:57 -0800 (PST)
Received: by 10.150.102.40 with SMTP id z40mr5907245ybb.430.1296329877582; Sat, 29 Jan 2011 11:37:57 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id r41sm12457121yba.16.2011.01.29.11.37.54 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 11:37:54 -0800 (PST)
Received: by iyi42 with SMTP id 42so3975111iyi.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 11:37:53 -0800 (PST)
Received: by 10.231.14.136 with SMTP id g8mr4455517iba.114.1296329873583; Sat, 29 Jan 2011 11:37:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.35.13 with HTTP; Sat, 29 Jan 2011 11:37:23 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1101291735580.10943@tvnag.unkk.fr>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com> <alpine.DEB.2.00.1101291735580.10943@tvnag.unkk.fr>
From: Adam Barth <ietf@adambarth.com>
Date: Sat, 29 Jan 2011 11:37:23 -0800
Message-ID: <AANLkTin1kyVmqAObQAMobf8d97jQjqtP7Ldsh_=s0OTL@mail.gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 19:34:49 -0000

On Sat, Jan 29, 2011 at 8:52 AM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Fri, 28 Jan 2011, Dan Winship wrote:
>>>> =A0 This section describes the syntax and semantics of a well-behaved
>>>> =A0 profile of the Cookie and Set-Cookie headers.
>>
>> -1, because Section 4 says "cookie-value=3Dtoken", which is annoying
>> (since it prohibits both base64 and URI encoding, both of which are
>> commonly used)
>
> I hadn't really considered these details about 'token' there and I agree
> that it seems a bit too strict.
>
> Why did we limit it like that?

That rule comes from RFC 2109 (with the bogus parts of the RFC 2109
cookie-value syntax removed).  It's certainly stricter than we need.
Something like allowing base64 sounds reasonable to me.

Adam

From derhoermi@gmx.net  Sat Jan 29 12:16:04 2011
Return-Path: <derhoermi@gmx.net>
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 5FD3E3A686A for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 12:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.234
X-Spam-Level: 
X-Spam-Status: No, score=-3.234 tagged_above=-999 required=5 tests=[AWL=-0.635, BAYES_00=-2.599]
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 oxIvWmakIEZL for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 12:16:03 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id DD7523A681C for <http-state@ietf.org>; Sat, 29 Jan 2011 12:16:02 -0800 (PST)
Received: (qmail invoked by alias); 29 Jan 2011 20:19:10 -0000
Received: from dslb-094-223-191-191.pools.arcor-ip.net (EHLO hive) [94.223.191.191] by mail.gmx.net (mp016) with SMTP; 29 Jan 2011 21:19:10 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+HNx1CtUmHS4J9PNxFB+H/RnWp8atRo8PQVkKF5x V/unsx11pdfZja
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: =JeffH <Jeff.Hodges@KingsMountain.com>
Date: Sat, 29 Jan 2011 21:19:03 +0100
Message-ID: <2eq8k6p06r3b3fdlrsnplt8sa9bvjfmsbm@hive.bjoern.hoehrmann.de>
References: <4D41FA83.5040302@KingsMountain.com>
In-Reply-To: <4D41FA83.5040302@KingsMountain.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 20:16:04 -0000

* =JeffH wrote:
>Absent explicitly expressed opposing views here on the http-state@ mailing 
>list, I'm going to interpret the WG's consensus to be in favor of the 
>modification as proposed by PeterSA...

I think the Working Group should recharter, or, alternatively, do what
the charter says. Apart from producing a proper test suite and a proper
description of deviations from the main specification, that would mean
replacing, say, the date parsing algorithm that's been made up on the
spot, and not doing what is proposed here, namely describing the proto-
col in a manner that is inconsistent with the vast majority of servers.

At the very least I would expect the main specification to say that the
protocol it describes is how some people wish it would work, instead of
incorrectly claiming it is an actual description of how it's "actually
used on the Internet". I don't mind requirements that are unlikely to
ever propagate into practise, but I do mind being dishonest about them.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From daniel@haxx.se  Sat Jan 29 13:48:29 2011
Return-Path: <daniel@haxx.se>
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 5B2293A6880 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 13:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.972
X-Spam-Level: 
X-Spam-Status: No, score=-2.972 tagged_above=-999 required=5 tests=[AWL=-0.723, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 n1yW4z--IJF4 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 13:48:27 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id EF2B63A6866 for <http-state@ietf.org>; Sat, 29 Jan 2011 13:48:26 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0TLpaj5022512; Sat, 29 Jan 2011 22:51:36 +0100
Date: Sat, 29 Jan 2011 22:51:36 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Bjoern Hoehrmann <derhoermi@gmx.net>
In-Reply-To: <2eq8k6p06r3b3fdlrsnplt8sa9bvjfmsbm@hive.bjoern.hoehrmann.de>
Message-ID: <alpine.DEB.2.00.1101292246120.1561@tvnag.unkk.fr>
References: <4D41FA83.5040302@KingsMountain.com> <2eq8k6p06r3b3fdlrsnplt8sa9bvjfmsbm@hive.bjoern.hoehrmann.de>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: =JeffH <Jeff.Hodges@KingsMountain.com>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 21:48:29 -0000

On Sat, 29 Jan 2011, Bjoern Hoehrmann wrote:

> replacing, say, the date parsing algorithm that's been made up on the spot, 
> and not doing what is proposed here, namely describing the proto- col in a 
> manner that is inconsistent with the vast majority of servers.

I read the date parser algorithm as describing a parser with a set of 
capabilities that a date parser for cookies should have. It doesn't say that 
the parser has to work exactly like that.

I consider "my" date parser compliant, but it parses the string in a different 
way than described in the spec.

-- 

  / daniel.haxx.se

From ietf@adambarth.com  Sat Jan 29 13:51:46 2011
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 7DBAB3A6866 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 13:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level: 
X-Spam-Status: No, score=-3.716 tagged_above=-999 required=5 tests=[AWL=-0.739, 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 Dha7FuW2Iqqf for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 13:51:45 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 5F5E23A683F for <http-state@ietf.org>; Sat, 29 Jan 2011 13:51:45 -0800 (PST)
Received: by gwb20 with SMTP id 20so1762195gwb.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 13:54:55 -0800 (PST)
Received: by 10.150.204.7 with SMTP id b7mr1003890ybg.150.1296338094894; Sat, 29 Jan 2011 13:54:54 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id r24sm974718yba.6.2011.01.29.13.54.53 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 13:54:54 -0800 (PST)
Received: by iyi42 with SMTP id 42so4039281iyi.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 13:54:52 -0800 (PST)
Received: by 10.231.14.136 with SMTP id g8mr4565525iba.114.1296338092573; Sat, 29 Jan 2011 13:54:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.35.13 with HTTP; Sat, 29 Jan 2011 13:54:22 -0800 (PST)
From: Adam Barth <ietf@adambarth.com>
Date: Sat, 29 Jan 2011 13:54:22 -0800
Message-ID: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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: Sat, 29 Jan 2011 21:51:46 -0000

On Sat, Jan 29, 2011 at 1:51 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Sat, 29 Jan 2011, Bjoern Hoehrmann wrote:
>> replacing, say, the date parsing algorithm that's been made up on the
>> spot, and not doing what is proposed here, namely describing the proto- col
>> in a manner that is inconsistent with the vast majority of servers.
>
> I read the date parser algorithm as describing a parser with a set of
> capabilities that a date parser for cookies should have. It doesn't say that
> the parser has to work exactly like that.
>
> I consider "my" date parser compliant, but it parses the string in a
> different way than described in the spec.

When you say "in a different way", do you mean via a different
algorithm or that your implementation outputs different dates for some
input strings?

Adam

From daniel@haxx.se  Sat Jan 29 14:04:51 2011
Return-Path: <daniel@haxx.se>
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 BE9473A687F for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level: 
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_51=0.6]
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 jmqrfexx7E3J for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:04:50 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 338193A680E for <http-state@ietf.org>; Sat, 29 Jan 2011 14:04:50 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0TM81Y3032470; Sat, 29 Jan 2011 23:08:01 +0100
Date: Sat, 29 Jan 2011 23:08:01 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Adam Barth <ietf@adambarth.com>
In-Reply-To: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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: Sat, 29 Jan 2011 22:04:51 -0000

On Sat, 29 Jan 2011, Adam Barth wrote:

>> I consider "my" date parser compliant, but it parses the string in a 
>> different way than described in the spec.
>
> When you say "in a different way", do you mean via a different algorithm or 
> that your implementation outputs different dates for some input strings?

I mean that it uses a different algorithm but ends up with the same output for 
most strings and certainly for all strings using sensible formats.

For really crazy inputs the output may differ a bit, like for example my 
parser is less forgiving on rubbish in the middle of the string as in "Thu, 
999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17 boink:z 21:01:22".

-- 

  / daniel.haxx.se

From daniel@haxx.se  Sat Jan 29 14:10:12 2011
Return-Path: <daniel@haxx.se>
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 874923A6890 for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.916
X-Spam-Level: 
X-Spam-Status: No, score=-3.916 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_SE=0.35]
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 pepeZS42GmAN for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:10:11 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 3B30B3A6886 for <http-state@ietf.org>; Sat, 29 Jan 2011 14:10:11 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0TMDMCq002064; Sat, 29 Jan 2011 23:13:22 +0100
Date: Sat, 29 Jan 2011 23:13:22 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Adam Barth <ietf@adambarth.com>
In-Reply-To: <AANLkTin1kyVmqAObQAMobf8d97jQjqtP7Ldsh_=s0OTL@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1101292242340.1561@tvnag.unkk.fr>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com> <alpine.DEB.2.00.1101291735580.10943@tvnag.unkk.fr> <AANLkTin1kyVmqAObQAMobf8d97jQjqtP7Ldsh_=s0OTL@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 22:10:12 -0000

On Sat, 29 Jan 2011, Adam Barth wrote:

>> I hadn't really considered these details about 'token' there and I agree
>> that it seems a bit too strict.
>
> That rule comes from RFC 2109 (with the bogus parts of the RFC 2109 
> cookie-value syntax removed).  It's certainly stricter than we need. 
> Something like allowing base64 sounds reasonable to me.

As a little comparison, my parser (that seems to work with a vast majority of 
all sites) simply allows anything except ; and = in a cookie name, and 
everything except ; and \r and \n in cookie contents.

Of course that doesn't really say that servers will use all those letters, 
only that a receiving end really has little reason to make it more strict than 
this.

-- 

  / daniel.haxx.se

From ietf@adambarth.com  Sat Jan 29 14:42:13 2011
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 C2E953A68BC for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.712
X-Spam-Level: 
X-Spam-Status: No, score=-4.712 tagged_above=-999 required=5 tests=[AWL=0.265,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, 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 p4KLwW+UKDoM for <http-state@core3.amsl.com>; Sat, 29 Jan 2011 14:42:13 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id D65903A68BB for <http-state@ietf.org>; Sat, 29 Jan 2011 14:42:12 -0800 (PST)
Received: by gxk27 with SMTP id 27so1770871gxk.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 14:45:22 -0800 (PST)
Received: by 10.236.105.226 with SMTP id k62mr708540yhg.53.1296341122592; Sat, 29 Jan 2011 14:45:22 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id 26sm3527559yhl.23.2011.01.29.14.45.20 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 14:45:21 -0800 (PST)
Received: by iyi42 with SMTP id 42so4061522iyi.31 for <http-state@ietf.org>; Sat, 29 Jan 2011 14:45:19 -0800 (PST)
Received: by 10.231.11.139 with SMTP id t11mr4570027ibt.189.1296341119728; Sat, 29 Jan 2011 14:45:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.35.13 with HTTP; Sat, 29 Jan 2011 14:44:47 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1101292242340.1561@tvnag.unkk.fr>
References: <4D41FA83.5040302@KingsMountain.com> <4D433C9A.7010203@gmail.com> <alpine.DEB.2.00.1101291735580.10943@tvnag.unkk.fr> <AANLkTin1kyVmqAObQAMobf8d97jQjqtP7Ldsh_=s0OTL@mail.gmail.com> <alpine.DEB.2.00.1101292242340.1561@tvnag.unkk.fr>
From: Adam Barth <ietf@adambarth.com>
Date: Sat, 29 Jan 2011 14:44:47 -0800
Message-ID: <AANLkTikxq2HFstovE9ENjXgv0CxXHsuDX2Tr95wKfNEJ@mail.gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] consensus call: cookie server conformance
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: Sat, 29 Jan 2011 22:42:13 -0000

On Sat, Jan 29, 2011 at 2:13 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Sat, 29 Jan 2011, Adam Barth wrote:
>>> I hadn't really considered these details about 'token' there and I agre=
e
>>> that it seems a bit too strict.
>>
>> That rule comes from RFC 2109 (with the bogus parts of the RFC 2109
>> cookie-value syntax removed). =A0It's certainly stricter than we need.
>> Something like allowing base64 sounds reasonable to me.
>
> As a little comparison, my parser (that seems to work with a vast majorit=
y
> of all sites) simply allows anything except ; and =3D in a cookie name, a=
nd
> everything except ; and \r and \n in cookie contents.
>
> Of course that doesn't really say that servers will use all those letters=
,
> only that a receiving end really has little reason to make it more strict
> than this.

I'd have to check the details, but I suspect that agrees with the user
agent requirements for the current draft, although there might be some
subtitles w.r.t. whitespace handling.

That said, I wouldn't recommend that servers make use of that full
flexibility.  For example, sending unpaired UTF-16 surrogates,
malformed UTF-8 sequences, or null characters is probably not a good
idea.

The question boils down what's sensible for servers to send.  IMHO,
token + base64 is reasonable, but I don't feel that strongly about it.

Adam

From annevk@opera.com  Mon Jan 31 02:35:43 2011
Return-Path: <annevk@opera.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 2E0623A68F6 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:35:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_MED=-4]
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 7pmLBUQyElCN for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:35:42 -0800 (PST)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id C5D683A68F5 for <http-state@ietf.org>; Mon, 31 Jan 2011 02:35:41 -0800 (PST)
Received: from anne-van-kesterens-macbook-pro.local (5355737B.cm-6-6b.dynamic.ziggo.nl [83.85.115.123]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0VAceGx028451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 10:38:41 GMT
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "Adam Barth" <ietf@adambarth.com>, "Daniel Stenberg" <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr>
Date: Mon, 31 Jan 2011 11:38:40 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr>
User-Agent: Opera Mail/11.01 (MacIntel)
X-Scanned-By: MIMEDefang 2.64 on 213.236.208.81
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 10:35:43 -0000

On Sat, 29 Jan 2011 23:08:01 +0100, Daniel Stenberg <daniel@haxx.se> wrote:
> On Sat, 29 Jan 2011, Adam Barth wrote:
>>> I consider "my" date parser compliant, but it parses the string in a  
>>> different way than described in the spec.
>>
>> When you say "in a different way", do you mean via a different  
>> algorithm or that your implementation outputs different dates for some  
>> input strings?
>
> I mean that it uses a different algorithm but ends up with the same  
> output for most strings and certainly for all strings using sensible  
> formats.
>
> For really crazy inputs the output may differ a bit, like for example my  
> parser is less forgiving on rubbish in the middle of the string as in  
> "Thu, 999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17 boink:z  
> 21:01:22".

That would mean it is not compliant.


-- 
Anne van Kesteren
http://annevankesteren.nl/

From daniel@haxx.se  Mon Jan 31 02:39:03 2011
Return-Path: <daniel@haxx.se>
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 7DE073A690A for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.626
X-Spam-Level: 
X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=-0.977, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_51=0.6]
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 m41MDomb6c2F for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:39:02 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 23A953A68FE for <http-state@ietf.org>; Mon, 31 Jan 2011 02:39:01 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0VAgEQD001549; Mon, 31 Jan 2011 11:42:14 +0100
Date: Mon, 31 Jan 2011 11:42:14 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Anne van Kesteren <annevk@opera.com>
In-Reply-To: <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local>
Message-ID: <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF HTTP State WG <http-state@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 10:39:03 -0000

On Mon, 31 Jan 2011, Anne van Kesteren wrote:

>> For really crazy inputs the output may differ a bit, like for example my 
>> parser is less forgiving on rubbish in the middle of the string as in "Thu, 
>> 999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17 boink:z 21:01:22".
>
> That would mean it is not compliant.

Sorry, can you please point out what section that says so?

-- 

  / daniel.haxx.se

From annevk@opera.com  Mon Jan 31 02:59:01 2011
Return-Path: <annevk@opera.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 50CED3A68FF for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:59:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_MED=-4]
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 kjJh4FmgdSc2 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 02:59:00 -0800 (PST)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id 5E0C33A68ED for <http-state@ietf.org>; Mon, 31 Jan 2011 02:58:58 -0800 (PST)
Received: from anne-van-kesterens-macbook-pro.local (5355737B.cm-6-6b.dynamic.ziggo.nl [83.85.115.123]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0VB1xaN001944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 11:02:00 GMT
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "Daniel Stenberg" <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr>
Date: Mon, 31 Jan 2011 12:01:59 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr>
User-Agent: Opera Mail/11.01 (MacIntel)
X-Scanned-By: MIMEDefang 2.64 on 213.236.208.81
Cc: IETF HTTP State WG <http-state@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 10:59:01 -0000

On Mon, 31 Jan 2011 11:42:14 +0100, Daniel Stenberg <daniel@haxx.se> wrote:
> On Mon, 31 Jan 2011, Anne van Kesteren wrote:
>>> For really crazy inputs the output may differ a bit, like for example  
>>> my parser is less forgiving on rubbish in the middle of the string as  
>>> in "Thu, 999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17  
>>> boink:z 21:01:22".
>>
>> That would mean it is not compliant.
>
> Sorry, can you please point out what section that says so?

5.1.1 (in combination with 2.1) says so.


-- 
Anne van Kesteren
http://annevankesteren.nl/

From daniel@haxx.se  Mon Jan 31 03:56:47 2011
Return-Path: <daniel@haxx.se>
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 109E53A6915 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 03:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=-0.948, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_51=0.6]
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 xb7HQoVRcOpX for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 03:56:46 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id AD3FE3A68DF for <http-state@ietf.org>; Mon, 31 Jan 2011 03:56:45 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0VBxv79017436; Mon, 31 Jan 2011 12:59:57 +0100
Date: Mon, 31 Jan 2011 12:59:57 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Anne van Kesteren <annevk@opera.com>
In-Reply-To: <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local>
Message-ID: <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF HTTP State WG <http-state@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 11:56:47 -0000

On Mon, 31 Jan 2011, Anne van Kesteren wrote:

>>>> "Thu, 999999999999-Aug-2007 20:49:07 GMT" or "Sat, 15-Apr-17 boink:z 
>>>> 21:01:22".
>>> 
>>> That would mean it is not compliant.
>> 
>> Sorry, can you please point out what section that says so?
>
> 5.1.1 (in combination with 2.1) says so.

That's not my interpretation at all. I can't find any mention of the algorithm 
having to skip "rubbish" in the date field and continue parsing on after it.

Or what did you mean with not compliant? For the above two examples, what 
would you claim the spec says the algorithm should do?

-- 

  / daniel.haxx.se

From annevk@opera.com  Mon Jan 31 05:15:37 2011
Return-Path: <annevk@opera.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 97F843A6C13 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 DXo+Fc3YeKTw for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:15:36 -0800 (PST)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by core3.amsl.com (Postfix) with ESMTP id 5CE653A696D for <http-state@ietf.org>; Mon, 31 Jan 2011 05:15:36 -0800 (PST)
Received: from anne-van-kesterens-macbook-pro.local (5355737B.cm-6-6b.dynamic.ziggo.nl [83.85.115.123]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0VDIfDs002899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 13:18:42 GMT
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "Daniel Stenberg" <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
Date: Mon, 31 Jan 2011 14:18:41 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.vp6cledg64w2qv@anne-van-kesterens-macbook-pro.local>
In-Reply-To: <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
User-Agent: Opera Mail/11.01 (MacIntel)
X-Scanned-By: MIMEDefang 2.64 on 213.236.208.81
Cc: IETF HTTP State WG <http-state@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 13:15:37 -0000

On Mon, 31 Jan 2011 12:59:57 +0100, Daniel Stenberg <daniel@haxx.se> wrote:
> That's not my interpretation at all. I can't find any mention of the  
> algorithm having to skip "rubbish" in the date field and continue  
> parsing on after it.
>
> Or what did you mean with not compliant? For the above two examples,  
> what would you claim the spec says the algorithm should do?

As far as I can tell in case of rubbish parsing fails and the algorithm  
therefore fails. It is a little unclear though. If it is supposed to be  
undefined it would be better if that were explicitly stated I think.


-- 
Anne van Kesteren
http://annevankesteren.nl/

From dan.winship@gmail.com  Mon Jan 31 05:56:21 2011
Return-Path: <dan.winship@gmail.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 4939B3A6973 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=-0.832, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 yZJJGsNVmxM1 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 05:56:20 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id 8F29A3A67E1 for <http-state@ietf.org>; Mon, 31 Jan 2011 05:56:20 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id 5B80E34A3D; Mon, 31 Jan 2011 08:59:34 -0500 (EST)
Message-ID: <4D46C045.4070101@gmail.com>
Date: Mon, 31 Jan 2011 08:59:33 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com>	<alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr>	<op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local>	<alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr>	<op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 13:56:21 -0000

On 01/31/2011 06:59 AM, Daniel Stenberg wrote:
>> 5.1.1 (in combination with 2.1) says so.
> 
> That's not my interpretation at all. I can't find any mention of the
> algorithm having to skip "rubbish" in the date field and continue
> parsing on after it.

"The user agent MUST use an algorithm equivalent to the following
algorithm to parse a cookie-date." If you reject some dates that the
5.1.1 algorithm would accept, then your algorithm is not equivalent.

(Likewise if you accept some strings that the 5.1.1 algorithm rejects,
or interpret any accepted string as referring to a different date than
the 5.1.1 algorithm does.)

-- Dan

From daniel@haxx.se  Mon Jan 31 06:00:01 2011
Return-Path: <daniel@haxx.se>
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 B77F03A6BFF for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.869
X-Spam-Level: 
X-Spam-Status: No, score=-2.869 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 FYZQsAcO1mre for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:00:00 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id F21AE3A6973 for <http-state@ietf.org>; Mon, 31 Jan 2011 05:59:59 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0VE3DE9009165; Mon, 31 Jan 2011 15:03:13 +0100
Date: Mon, 31 Jan 2011 15:03:13 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Dan Winship <dan.winship@gmail.com>
In-Reply-To: <4D46C045.4070101@gmail.com>
Message-ID: <alpine.DEB.2.00.1101311500240.28922@tvnag.unkk.fr>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr> <4D46C045.4070101@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 14:00:01 -0000

On Mon, 31 Jan 2011, Dan Winship wrote:

> "The user agent MUST use an algorithm equivalent to the following algorithm 
> to parse a cookie-date." If you reject some dates that the 5.1.1 algorithm 
> would accept, then your algorithm is not equivalent.

Right, and I realize I have myself to blame for expressing myself sloppy in my 
first statement, but I was actually comparing my parser's strictness to a few 
browsers' parsers that I know are more liberal in what they parse than what 
the current spec say.

You can all stop pointing fingers now. I'll deal with my parser's compliance, 
and you can deal with yours.

-- 

  / daniel.haxx.se

From dan.winship@gmail.com  Mon Jan 31 06:02:38 2011
Return-Path: <dan.winship@gmail.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 D5CCA3A6973 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[AWL=-0.694, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 tTraGTIlplM6 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:02:38 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id 3848B3A67B2 for <http-state@ietf.org>; Mon, 31 Jan 2011 06:02:38 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id 6E2E234A3D; Mon, 31 Jan 2011 09:05:52 -0500 (EST)
Message-ID: <4D46C1B6.8030100@gmail.com>
Date: Mon, 31 Jan 2011 09:05:42 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr> <4D46C045.4070101@gmail.com> <alpine.DEB.2.00.1101311500240.28922@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1101311500240.28922@tvnag.unkk.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 14:02:39 -0000

On 01/31/2011 09:03 AM, Daniel Stenberg wrote:
> You can all stop pointing fingers now. I'll deal with my parser's
> compliance, and you can deal with yours.

I was just pointing out what the spec says. At the moment, I have no
plans to "fix" my date parser to conform (though I'm not ruling it out
either).

-- Dan

From daniel@haxx.se  Mon Jan 31 06:06:34 2011
Return-Path: <daniel@haxx.se>
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 3FDB13A6BED for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.851
X-Spam-Level: 
X-Spam-Status: No, score=-2.851 tagged_above=-999 required=5 tests=[AWL=-0.602, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 Q6Uc-HUyjVwm for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:06:33 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 13C4A3A6B32 for <http-state@ietf.org>; Mon, 31 Jan 2011 06:06:32 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0VE9lhv013835; Mon, 31 Jan 2011 15:09:47 +0100
Date: Mon, 31 Jan 2011 15:09:47 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Dan Winship <dan.winship@gmail.com>
In-Reply-To: <4D46C1B6.8030100@gmail.com>
Message-ID: <alpine.DEB.2.00.1101311508360.28922@tvnag.unkk.fr>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr> <4D46C045.4070101@gmail.com> <alpine.DEB.2.00.1101311500240.28922@tvnag.unkk.fr> <4D46C1B6.8030100@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 14:06:34 -0000

On Mon, 31 Jan 2011, Dan Winship wrote:

> At the moment, I have no plans to "fix" my date parser to conform (though 
> I'm not ruling it out either).

Does this mean your parser is better (than the spec) in some aspects that you 
think are necesary?

-- 

  / daniel.haxx.se

From dan.winship@gmail.com  Mon Jan 31 06:57:11 2011
Return-Path: <dan.winship@gmail.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 B0C233A6C21 for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.271
X-Spam-Level: 
X-Spam-Status: No, score=-2.271 tagged_above=-999 required=5 tests=[AWL=-0.594, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311]
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 LswGbXq+kEfO for <http-state@core3.amsl.com>; Mon, 31 Jan 2011 06:57:11 -0800 (PST)
Received: from mysterion.org (li168-117.members.linode.com [173.230.128.117]) by core3.amsl.com (Postfix) with ESMTP id 183E43A6C12 for <http-state@ietf.org>; Mon, 31 Jan 2011 06:57:11 -0800 (PST)
Received: from desktop.home.mysterion.org (c-76-97-71-164.hsd1.ga.comcast.net [76.97.71.164]) by mysterion.org (Postfix) with ESMTPSA id 1329C34A3D; Mon, 31 Jan 2011 10:00:24 -0500 (EST)
Message-ID: <4D46CE86.7090406@gmail.com>
Date: Mon, 31 Jan 2011 10:00:22 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
References: <AANLkTikTG0cu-q+OxLFvc9WeLgZMrfooZ9Ndoc=AmGDq@mail.gmail.com> <alpine.DEB.2.00.1101292300070.1561@tvnag.unkk.fr> <op.vp546pcd64w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311141230.26269@tvnag.unkk.fr> <op.vp559k1664w2qv@anne-van-kesterens-macbook-pro.local> <alpine.DEB.2.00.1101311254360.26269@tvnag.unkk.fr> <4D46C045.4070101@gmail.com> <alpine.DEB.2.00.1101311500240.28922@tvnag.unkk.fr> <4D46C1B6.8030100@gmail.com> <alpine.DEB.2.00.1101311508360.28922@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1101311508360.28922@tvnag.unkk.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF HTTP State WG <http-state@ietf.org>
Subject: Re: [http-state] Date parsing (was Re: consensus call: cookie server conformance)
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, 31 Jan 2011 14:57:11 -0000

On 01/31/2011 09:09 AM, Daniel Stenberg wrote:
> On Mon, 31 Jan 2011, Dan Winship wrote:
> 
>> At the moment, I have no plans to "fix" my date parser to conform
>> (though I'm not ruling it out either).
> 
> Does this mean your parser is better (than the spec) in some aspects
> that you think are necesary?

No, it's definitely "worse". (It makes no attempt to parse dates whose
fields aren't in one of the standard orders, for instance.) I just don't
think that the "improvement" involved in changing exactly which subset
of the long tail of insanely-wrong Expires attributes I accept is worth
the time it would take to write the code, particularly given that (a)
other implementations are not consistent anyway, and (b) the price of
failure is just "the cookie is expired at the end of the session", not
"the cookie is rejected entirely".

-- Dan
