[http-state] http-state charter

Bil Corry <bil@corry.biz> Wed, 29 July 2009 22:53 UTC

Return-Path: <bil@corry.biz>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 5A6FD3A68A1 for <http-state@core3.amsl.com>; Wed, 29 Jul 2009 15:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.69
X-Spam-Status: No, score=-4.69 tagged_above=-999 required=5 tests=[AWL=-2.955, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id zfpM6RAACNAF for <http-state@core3.amsl.com>; Wed, 29 Jul 2009 15:53:15 -0700 (PDT)
Received: from mail.mindio.com (app1.bc.anu.net []) by core3.amsl.com (Postfix) with ESMTP id 7C50F3A67A8 for <http-state@ietf.org>; Wed, 29 Jul 2009 15:53:15 -0700 (PDT)
Received: from [] (unknown []) by mail.mindio.com (Postfix) with ESMTP id D2907FC493 for <http-state@ietf.org>; Wed, 29 Jul 2009 17:53:15 -0500 (CDT)
Message-ID: <4A70D2D2.9050900@corry.biz>
Date: Wed, 29 Jul 2009 17:53:06 -0500
From: Bil Corry <bil@corry.biz>
User-Agent: Thunderbird (Windows/20090605)
MIME-Version: 1.0
To: "http-state@ietf.org" <http-state@ietf.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [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, 29 Jul 2009 22:53:16 -0000

Much delayed, but I'm now working on creating our charter.  I've included a first draft below; it borrows heavily from the httpbis charter.  Feedback welcomed.  For a sense of what other WG charters look like, they are here:


- Bil


Charter: HTTP State Management Mechanism (http-state) WG

Last Modified: 2008-07-29

Mailing Lists:
General Discussion: http-state@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/http-state
Archive: http://www.ietf.org/mail-archive/web/http-state/current/maillist.html

Description of Working Group:

The HTTP State Management Mechanism (Cookies) was original created
by Netscape Communications in their Netscape cookie specification,
from which a formal specification followed (RFC 2109, RFC 2965).
Due to years of implementation and extension, several ambiguities
have become evident, impairing interoperability and the ability to
easily implement and use HTTP State Management Mechanism.

The working group will refine RFC2965 to:
* Incorporate errata and updates
* Clarify conformance requirements
* Remove known ambiguities where they affect interoperability
* Clarify existing methods of extensibility
* Remove or deprecate those features that are not widely implemented
and also unduly affect interoperability
* Where necessary, add implementation advice
* Document the security properties of HTTP State Management
Mechanism and its associated echanisms for common applications

In doing so, it should consider:
* Implementer experience
* Demonstrated use of HTTP State Management Mechanism
* Impact on existing implementations and deployments

The Working Group's specification deliverables are:
* A document that is suitable to supersede RFC 2965
* A document cataloguing the security properties of HTTP
State Management Mechanism

Goals and Milestones:

No Current Internet-Drafts
No Request For Comments