[imss] STORM BOF date/time determination

Black_David@emc.com Wed, 11 February 2009 01:52 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: imss@core3.amsl.com
Delivered-To: imss@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 494B63A6883; Tue, 10 Feb 2009 17:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id bIhET1dv7u1I; Tue, 10 Feb 2009 17:52:34 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com []) by core3.amsl.com (Postfix) with ESMTP id 5F8723A67FB; Tue, 10 Feb 2009 17:52:34 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com []) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id n1B1qaLo020193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 20:52:36 -0500 (EST)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com (numailhub.lss.emc.com []) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Tue, 10 Feb 2009 20:52:24 -0500
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com []) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n1B1qOBw019581; Tue, 10 Feb 2009 20:52:24 -0500
Received: from CORPUSMX80A.corp.emc.com ([]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Feb 2009 20:52:23 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Feb 2009 20:52:22 -0500
Message-ID: <9FA859626025B64FBC2AF149D97C944A01A04A02@CORPUSMX80A.corp.emc.com>
Thread-Topic: STORM BOF date/time determination
Thread-Index: AcmL62GuOmAo/IQYSoGRXfP3oljoQw==
To: <ips@ietf.org>
X-OriginalArrivalTime: 11 Feb 2009 01:52:23.0617 (UTC) FILETIME=[62194B10:01C98BEB]
X-EMM-EM: Active
Cc: imss@ietf.org, Black_David@emc.com, rddp@ietf.org
Subject: [imss] STORM BOF date/time determination
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imss>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 01:52:35 -0000

Someone asked - when will we know whether it's Thu or Fri
(Mar 26 or 27) and what time the STORM BOF is?

The secretariat should have (or shortly will have) gathered
all the inputs for session scheduling for San Francisco.

According to this page:
There should be a preliminary agenda for the SF meeting week
out this Friday.  That preliminary agenda inevitably leads to
multiple rounds of "<X> conflicts with <Y>, can we swap it with
<Z>" discussions, even though conflicts are an input to the
initial agenda.  Some conflicts are inevitably overlooked,
forgotten, or not noticed until the initial agenda is published
- think of this as a demonstration that IETF session scheduling
is at least an NP-Hard problem ;-).

The final agenda, with the STORM date, time and room should be
published on Mar 2.  That's 3+ weeks in advance, so reasonable
domestic airfares to SF should still be available.

David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754