Re: [vmeet] Stockholm

Doug Otis <> Tue, 28 July 2009 23:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7DAD83A6D69 for <>; Tue, 28 Jul 2009 16:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.129
X-Spam-Status: No, score=-1.129 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_MLH_Stock1=0.87]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mqs+Vqs-5U2f for <>; Tue, 28 Jul 2009 16:51:07 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 408123A6D3B for <>; Tue, 28 Jul 2009 16:51:07 -0700 (PDT)
Received: by ewy26 with SMTP id 26so448746ewy.37 for <>; Tue, 28 Jul 2009 16:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Hm9uqBGPxRfF3/grkOTfWfs5TAUH/xrWKXmf+uTi6CQ=; b=qiJm/g96TeVphQXDdm5jWHw/wjKAfwynF2rWA7JBTl9lsYXWbrbTb+r34dFTcKKvD1 5Bq+pFT5Y6iiAfVU7eywPsfoakJ0bYMZBk7hBW7/k5mjib+GgaAtBVbZx07l/ZcNhx8J CBjrtYpJrT+/FO3Bv4UrlCZSxKLyxmmKWLtS4=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=BReMwuXy+6tGn/SR8j+EemOp7sBuTuIUrReLTwMuOSxBgLmdUIiHI2+WHTYbEn8Jce jBg05oNFl8eVVkcNwF5GMjyvSnCih7nCrbDrRJR1LKpwf3ZEH/txOolnqRwF7d3grTsg 6A+V/fmn/mHB5W1G/079x1RV5vLoEoXJTX9g0=
Received: by with SMTP id w4mr10721227ebp.46.1248825065776; Tue, 28 Jul 2009 16:51:05 -0700 (PDT)
Received: from ( []) by with ESMTPS id 7sm205685eyg.35.2009. (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 28 Jul 2009 16:51:04 -0700 (PDT)
Message-ID: <>
Date: Wed, 29 Jul 2009 01:51:01 +0200
From: Doug Otis <>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Russ Housley <>
References: <20090727055308.GB9935@verdi> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [vmeet] Stockholm
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF remote participation meeting services discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 28 Jul 2009 23:51:08 -0000

On 7/27/09 8:02 AM, 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.

Remote presentations in the Large Stage also included a presenter
who had someone patch a laptop into the PA system to enable a
speaker with a heavy accent.  This setup suffered from poor audio
quality compared to what WebEx had been providing.

There were several other problems beyond those with remote sound
problems during Monday.  Congress Hall C had a pin 9 of a video cable
grounded which shorted video adapters for two presenter's PC laptops
(where I understand they were required to completely power-off to recover).

The Small Stage also had a problem where a Video to CAT5 converter
failed to identify itself as a display, that then confused several older
versions of Mac laptop's Autodetect.

Delays created by presenters attempting to connect their laptops to the
digital display device, or a lack of standardization for remote
presentations could be remedied by using pre-configured net-boxes in 
each meeting room.

Such use would create two pre-conditions for presenters:

1) Slides would need to be published on a web accessible file server.

2) Utilization of a common control mechanism such as WebEx, VNC, or a
wireless media keyboard. (The keyboard could provide an emergency
fall-back mode.)

The Mute key on the keyboard could also enable remote presenters that
might use VoIP or some alternative to avoid reliance upon third-party
services, such as WebEx which omits VoIP with their Event for 
non-Windows clients.  The Net-Box could also source a web-stream of live 
slide presentations as an alternative to WebEx that would not require 
prior arrangements.

Pre-configured net-boxes could allow better integration with remote
presenters as well as enable remote question microphones not made
available in the Large Stage WebEx presentations.  To support a remote
question microphone, some queuing mechanism is needed, such as the
feature found in the WebEx Event client.

By using net-boxes as a tie-point for remote audio feeds, perhaps this
could standardize what is needed to bring up remote audio feeds.

While the IETF operates within a small budget, the IETF would also be
providing leadership in how to better utilize networks to improve remote
participation.  Use of net-boxes would not represent much in the way of
additional equipment to store and ship.  They would not require much in
the way of an expenditure, perhaps $300 x 12 (50% surplus) even when
considered disposable.  Importantly, these devices could help ensure
fewer delays and availability of live slide and audio, along with access 
to remote microphones for remote presenters and questioners.