Re: [http-state] http-state charter
Mark Nottingham <mnot@mnot.net> Wed, 05 August 2009 01:26 UTC
Return-Path: <mnot@mnot.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 05E033A7115 for <http-state@core3.amsl.com>; Tue, 4 Aug 2009 18:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, NO_RDNS_DOTCOM_HELO=0.001]
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 5PQdnm6qNg-O for <http-state@core3.amsl.com>; Tue, 4 Aug 2009 18:26:54 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id EF7843A65A6 for <http-state@ietf.org>; Tue, 4 Aug 2009 18:26:53 -0700 (PDT)
Received: from wlanvpn-mc2e-247-156.corp.yahoo.com (unknown [209.131.62.145]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5C1D322E253; Tue, 4 Aug 2009 21:26:50 -0400 (EDT)
Message-Id: <FD75C039-3A9E-4477-ACC0-249A270615CC@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: Pascal Gaudette <acajou@gmail.com>
In-Reply-To: <ab2c53a20908041341x2cb954b7h856ccc43b3fb3313@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 04 Aug 2009 18:26:49 -0700
References: <4A70D2D2.9050900@corry.biz> <4A731FCC.5040102@gmail.com> <4A735DD4.9040007@corry.biz> <4A777D12.5000106@gmail.com> <ab2c53a20908041341x2cb954b7h856ccc43b3fb3313@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: http-state@ietf.org
Subject: Re: [http-state] http-state charter
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, 05 Aug 2009 01:26:55 -0000
FWIW - Almost every discussion I've had with people in the IETF regarding cookies could be characterised as "we need to document how cookies actually work." I would encourage people on this list to discuss how to make that happen, and not to try to second-guess the IETF process, what will and will not be acceptable to the IESG, etc; we'll get there soon enough. Cheers, On 04/08/2009, at 1:41 PM, Pascal Gaudette wrote: > Hi all, > > I'm very new to both this list and the IETF, but I wanted to ask a > question that might have been discussed in the past, possibly even > face to face during IETF meetings... > > The members of this list are currently discussing what type of > standards document the WG might end up writing. But has there been > any thought given to the development of a set of whitebox user-agent > tests that could be deployed on a domain and used to *document* > currently deployed user-agent behavior? (IE produce a table of > observed behavior vrs user-agent and test case.) > > I would see this as a very useful deliverable for the working group > to produce prior to any specification document, and I can see myself > adding test cases to such a test suite (provided it is written in a > language I am familliar with). I am currently in the process of > trying to implement cookie support in a simple user-agent as part of > Google's Summer of Code and such a suite would be very useful to > me... Many members of this list probably have extensive knowledge of > user-agent behavior, both where they converge and where they > diverge. Deploying such a test suite would allow the gathering of > all such knowledge in a single, public place. > > Unless such a thing already exists, in which case I shall be very > happy to be provided with a pointer... > > Just some thoughts, > -- > Pascal Gaudette <acajou@gmail.com> > _______________________________________________ > http-state mailing list > http-state@ietf.org > https://www.ietf.org/mailman/listinfo/http-state -- Mark Nottingham http://www.mnot.net/
- [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Ian Hickson
- Re: [http-state] http-state charter Prasad Shenoy
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Ian Hickson
- Re: [http-state] http-state charter =JeffH
- Re: [http-state] http-state charter Daniel Stenberg
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Dan Winship
- Re: [http-state] http-state charter Adam Barth
- Re: [http-state] http-state charter Daniel Stenberg
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Dan Winship
- Re: [http-state] http-state charter Ian Hickson
- Re: [http-state] http-state charter Adam Barth
- Re: [http-state] http-state charter Peter Saint-Andre
- Re: [http-state] http-state charter Adam Barth
- Re: [http-state] http-state charter Daniel Stenberg
- Re: [http-state] http-state charter Adam Barth
- Re: [http-state] http-state charter Daniel Stenberg
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Julian Reschke
- Re: [http-state] http-state charter Pascal Gaudette
- Re: [http-state] http-state charter Mark Nottingham
- Re: [http-state] http-state charter Bil Corry
- Re: [http-state] http-state charter Daniel Stenberg
- Re: [http-state] http-state charter Dan Winship
- Re: [http-state] http-state charter Mark Nottingham