[http-state] Draft httpstate agenda for IETF-78 Maastricht

=JeffH <Jeff.Hodges@KingsMountain.com> Wed, 14 July 2010 04:12 UTC

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 591073A681A for <http-state@core3.amsl.com>; Tue, 13 Jul 2010 21:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level:
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=0.891, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 Tmg+oQ4Anam8 for <http-state@core3.amsl.com>; Tue, 13 Jul 2010 21:12:41 -0700 (PDT)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id 327653A67AE for <http-state@ietf.org>; Tue, 13 Jul 2010 21:12:41 -0700 (PDT)
Received: (qmail 11308 invoked by uid 0); 14 Jul 2010 04:12:50 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 14 Jul 2010 04:12:50 -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=vChyrplgz2t4k28hvTK4P8QGLz8uZxvM4nPAQntntf4Fnd5eEcaLv4FR0nW/vb/X7OqGvSNbMuMzVF4VjNdDSJfMyW4hn7vAykjN7gwHogpXmJ7GmmQXDjGeqkqYp87r;
Received: from c-24-4-122-173.hsd1.ca.comcast.net ([24.4.122.173] helo=[192.168.11.10]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1OYtL0-0002Ej-6B for http-state@ietf.org; Tue, 13 Jul 2010 22:12:50 -0600
Message-ID: <4C3D393E.1040403@KingsMountain.com>
Date: Tue, 13 Jul 2010 21:12:46 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
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 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Subject: [http-state] Draft httpstate agenda for IETF-78 Maastricht
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, 14 Jul 2010 04:12:42 -0000

Draft agenda is attached below.

items 2 and 3 are a bit of a shot in the dark because we ought to be able to 
make some progress on them before the meeting.

for item 4, I see these I-Ds as possible httpstate-phase-2 discussion items..

   draft-pettersen-cookie-v2-05

   draft-pettersen-cookie-origin-01

   draft-pettersen-subtld-structure-06

   draft-salgueiro-secure-state-management-03

any others?

Any overall comments on the proposed agenda?

thanks,

=JeffH

========================================
IETF httpstate WG
DRAFT Agenda for IETF-78  Maastricht, NL
----------------------------------------
Monday 1740-1940 Afternoon Session III
========================================

Charter:
http://www.ietf.org/dyn/wg/charter/httpstate-charter

Current I-D:
http://tools.ietf.org/html/draft-abarth-cookie-09

Bug/ticket list:
<out of date>


Agenda (draft)
--------------

1. Agenda bash & Blue sheets                            (  5 min )

2. Review changes from -08 (LCWD)  to -09               ( 20 min )

3. Discuss changes yet to be finished (if any)          ( 20 min )



4. Discuss possible future work post-httpstate-cookie   ( 75 min )
    e.g. Yngve's I-Ds


----------------------------
Jeff Hodges, httpstate Chair