[HASMAT] draft IETF-78 agenda to be posted Thu 24-Jun

=JeffH <Jeff.Hodges@KingsMountain.com> Wed, 23 June 2010 20:45 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2065E28C167 for <hasmat@core3.amsl.com>; Wed, 23 Jun 2010 13:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_50=0.001, 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 x724KlqcIB90 for <hasmat@core3.amsl.com>; Wed, 23 Jun 2010 13:45:50 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id F2C6328C166 for <hasmat@ietf.org>; Wed, 23 Jun 2010 13:45:49 -0700 (PDT)
Received: (qmail 5098 invoked by uid 0); 23 Jun 2010 20:45:57 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 23 Jun 2010 20:45:57 -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=OSr7J/q15hpWNIHcNU3lN7Ej+PdjOy0iSrYHsOdmBxKCrNXF4adE9puyO5NZ8tP+I20M9op8MTLLis/CdbVju/m8ZipsF5JcdzrZYNid7kF7nSx6G/YcZwFnNQ+fUVuH;
Received: from c-24-4-121-195.hsd1.ca.comcast.net ([24.4.121.195] 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 1ORWpZ-000871-Ec for hasmat@ietf.org; Wed, 23 Jun 2010 14:45:57 -0600
Message-ID: <4C227283.2010807@KingsMountain.com>
Date: Wed, 23 Jun 2010 13:45:55 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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.121.195 authed with jeff.hodges+kingsmountain.com}
Subject: [HASMAT] draft IETF-78 agenda to be posted Thu 24-Jun
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 20:45:51 -0000

So the draft IETF-78 agenda to be posted Thu 24-Jun (tomorrow; a day later than 
scheduled).

Below's the explanation from Russ Housley (IETF chair).

I requested of our ADs that we try to schedule at least hasmat, httpstate, 
hybi, httpbis, appsarea across two or three days. I don't at this time know how 
this worked out. Given the full meeting schedule, it may or may not get set up 
this way. Anyway, we'll see the draft schedule tomorrow and can supply feedback 
on it and see what we can work out. I am aware of at least some folks who 
aren't able to attend the entire week and who're holding off on making 
arrangements in order to see the agenda. Please remember the first agenda 
iteration is a draft.

thanks for your patience,
looking forward to seeing many of you in Maastricht,

=JeffH
------

Subject: Very Full IETF 78 Agenda
From: Russ Housley <housley@vigilsec.com>
Date: Wed, 23 Jun 2010 09:42:57 -0400 (06:42 PDT)
To: IETF WG Chairs <wgchairs@ietf.org>

The IESG is working with the Secretariat to come up with the first
public draft of the agenda.  We received requests for 14 more slots than
exist on the extended (through Friday at 1515) schedule.  We have an
agenda that gives each request one meeting slot.  However, 13 groups
requested two slots, and at this point, none are receiving a second slot.

The agenda will be posted on Thursday for your review and comment.  We
are behind schedule, but further coordination between the IESG and the
Secretariat is needed.  Please recognize that a lot of work has already
gone into the agenda, and there is little room for adjustment.  It is
quite a balancing act for this meeting.

Thanks for your patience and cooperation,
   Russ