Re: [vmeet] Stockholm

"Scott Lawrence" <scott.lawrence@nortel.com> Mon, 27 July 2009 14:29 UTC

Return-Path: <scott.lawrence@nortel.com>
X-Original-To: vmeet@core3.amsl.com
Delivered-To: vmeet@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0DD33A6A27 for <vmeet@core3.amsl.com>; Mon, 27 Jul 2009 07:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.129
X-Spam-Level:
X-Spam-Status: No, score=-5.129 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 TTA1AI0F6G7o for <vmeet@core3.amsl.com>; Mon, 27 Jul 2009 07:29:06 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id DDB963A6B1F for <vmeet@ietf.org>; Mon, 27 Jul 2009 07:29:05 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n6RESa304594; Mon, 27 Jul 2009 14:28:36 GMT
Received: from [127.0.0.1] ([47.17.25.99]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Jul 2009 10:28:20 -0400
From: Scott Lawrence <scott.lawrence@nortel.com>
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20090727060258.6E99D9A4726@odin.smetech.net>
References: <20090727055308.GB9935@verdi> <20090727060258.6E99D9A4726@odin.smetech.net>
Content-Type: text/plain
Organization: Nortel Networks
Date: Mon, 27 Jul 2009 10:28:18 -0400
Message-Id: <1248704898.5653.91.camel@scott>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jul 2009 14:28:20.0357 (UTC) FILETIME=[7D651350:01CA0EC6]
Cc: vmeet@ietf.org
Subject: Re: [vmeet] Stockholm
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vmeet>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 14:29:06 -0000

On Mon, 2009-07-27 at 02:02 -0400, Russ Housley wrote:

> Only Dispatch and V6Ops have remote presenters that are going to use 
> WebEx.  We hope to make more use of this capability in the future, 
> but the needed technical information to connect to the meeting room 
> system was not available to us before we got on site.  So, we are 
> only going to focus on the two sessions that need to support remote presenters.

I was one of those remote presenters (the DISPATCH session).  I decided
to cancel my presentation rather than attempt it remotely.

This was only in part due to the difficulties in being remote, but they
were a factor: in particular, the total lack of information on how
remote participation would work, what I would need at my end, and the
fact that WebEx won't work from my normal Linux work environment.  I was
not able to find any information at all (despite repeated requests) on
how I could test anything in advance.

There were other contributing factors - I'm not blaming my decision to
cancel on the poor support for remote presentation, but it was very
poor.