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

"Paul E. Jones" <paulej@packetizer.com> Mon, 15 March 2010 23:57 UTC

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 6073C3A6862 for <http-state@core3.amsl.com>; Mon, 15 Mar 2010 16:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level:
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 P1AKfzgv8qwB for <http-state@core3.amsl.com>; Mon, 15 Mar 2010 16:57:48 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id 10F033A66B4 for <http-state@ietf.org>; Mon, 15 Mar 2010 16:57:47 -0700 (PDT)
Received: from berlin.arid.us (rrcs-98-101-146-183.midsouth.biz.rr.com [98.101.146.183]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id o2FNvg7p014967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 15 Mar 2010 19:57:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1268697467; bh=QtCpgXDV9wHh/mf+WOfsBDFlhdaYwJ/HwC/G3Jf7jFM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=CjxjtUwbUpyFX85PHBPZQ52TAw+CJIzAAU+BKOlWGRgitbzdXE7WzM+gtG85zsL+7 mkBHKPGblZ21sX+HaBJ2aSP5NyUON9AHXz+w0lB+dyvzaGwWp3Pb8v+vhok4fXpUQx uoKlsp9xldpnC8e4idk8qiZKfbWZ9J17iogfsITo=
Received: from sydney (sydney.arid.us [192.168.1.20]) (authenticated bits=0) by berlin.arid.us (8.14.2/8.14.2) with ESMTP id o2FNvevo016492 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 15 Mar 2010 19:57:41 -0400
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Daniel Stenberg'" <daniel@haxx.se>
References: <5c4444771003071050r3475798co95cc192d1f2e8190@mail.gmail.com> <op.u9dpzpdoqrq7tp@acorna> <5c4444771003101823u25842652o33b49b2be81f4cfc@mail.gmail.com> <alpine.DEB.2.00.1003112201360.25452@tvnag.unkk.fr> <op.u9feulgkqrq7tp@acorna> <009401cac476$eb8c83c0$c2a58b40$@com> <5c4444771003151240h61a87c3fp9a1649d1163111ce@mail.gmail.com> <009a01cac489$47f0fda0$d7d2f8e0$@com> <alpine.DEB.2.00.1003152251531.27391@tvnag.unkk.fr> <00a601cac496$2be978a0$83bc69e0$@com> <alpine.DEB.2.00.1003160023200.1644@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1003160023200.1644@tvnag.unkk.fr>
Date: Mon, 15 Mar 2010 19:57:39 -0400
Message-ID: <00ac01cac49b$4b669730$e233c590$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-us
Thread-index: AcrEl3vSGXsafuaOTnC+Uaf60iJtmAAAz1fQ
Cc: 'http-state' <http-state@ietf.org>
Subject: Re: [http-state] draft-ietf-httpstate-cookie-05 posted
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2010 23:57:49 -0000

Daniel,

> > there are only a small handful of browsers that need to handle those
> > cookies.
> 
> I'm claiming that statement is wrong.
> 
> Cookies are handled client-side by HTTP clients that handle cookies.
> There are
> far more such client implementations in wide use than "just" the major
> browsers, like for example the library I myself work with: libcurl. But
> there
> are a large number of other implementations of tools and libraries
> handling
> cookies that are used out there.
> 
> Most probably not at all as many as the server-side apps creating the
> cookies,
> but certainly not limited to "a small handful of browsers".

Ah, yes... I understand your point now, and you're right.

However, the fact you're engaged in this draft speaks to the point I tried
to make: those building UAs are likely going to read this spec.  I would
venture to guess there will be thousands of application developers
generating cookies that never read this spec.

Paul