[http-state] BOF at IETF meeting

Bil Corry <bil@corry.biz> Tue, 13 January 2009 18:07 UTC

Return-Path: <http-state-bounces@ietf.org>
X-Original-To: http-state-archive@ietf.org
Delivered-To: ietfarch-http-state-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 183BD28C12E; Tue, 13 Jan 2009 10:07:33 -0800 (PST)
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 488AE3A6A67 for <http-state@core3.amsl.com>; Tue, 13 Jan 2009 10:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.286
X-Spam-Status: No, score=-4.286 tagged_above=-999 required=5 tests=[AWL=-3.151, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_42=0.6]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 72kOflq3-p9u for <http-state@core3.amsl.com>; Tue, 13 Jan 2009 10:07:30 -0800 (PST)
Received: from mail.mindio.com (app1.bc.anu.net []) by core3.amsl.com (Postfix) with ESMTP id 5F0913A67E9 for <http-state@ietf.org>; Tue, 13 Jan 2009 10:07:30 -0800 (PST)
Received: from [] (c-98-206-56-182.hsd1.in.comcast.net []) by mail.mindio.com (Postfix) with ESMTP id D87A819C145 for <http-state@ietf.org>; Tue, 13 Jan 2009 12:07:06 -0600 (CST)
Message-ID: <496CD848.4020706@corry.biz>
Date: Tue, 13 Jan 2009 12:07:04 -0600
From: Bil Corry <bil@corry.biz>
User-Agent: Thunderbird (Windows/20081209)
MIME-Version: 1.0
To: "http-state@ietf.org" <http-state@ietf.org>
X-Enigmail-Version: 0.95.7
Subject: [http-state] BOF at IETF meeting
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Discuss HTTP State Management Mechanism <http-state@ietf.org>
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: http-state-bounces@ietf.org
Errors-To: http-state-bounces@ietf.org

In order for us to get a BOF at the next IETF meeting, I need to provide to Lisa Dusseault the following by January 23:

(1) The number of people who are interested in participating in the BOF at the March IETF meeting (San Francisco).  So far, there are two of us.  Anyone else?  A BOF is not strictly required to form a Working Group, but it's the accepted practice to do so.  A Working Group is required to create a RFC.

(2) A list of work items for our group.  I'm clarifying with Lisa if she wants the work items for our eventual Working Group, or if she wants the work items that we'll be tackling during the BOF.

(3) An experienced IETF chair or BOF organizer involved, probably as BOF chair or co-chair running the actual meeting.  Is anyone here an experienced IETF'er or know of someone who would be willing to lend their experience to our forming WG (and is willing to attend the next IETF meeting)?

Related to #2, we also need to create a charter for the Working Group in order to form a Working Group.  I think creating a list of work items will be much easier if we already have the Charter created, or at least have consensus on most of it.  Here's an example of a charter for the Hypertext Transfer Protocol Bis Working Group:


I started typing up our options here for the type of RFC we want to create, but I see Dan has summed it up nicely, so I'll continue off of his post.

- Bil

http-state mailing list