[rtcweb] Update on remote participation for the interim
Ted Hardie <ted.ietf@gmail.com> Mon, 12 May 2014 16:46 UTC
Return-Path: <ted.ietf@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7251A072A for <rtcweb@ietfa.amsl.com>; Mon, 12 May 2014 09:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vP6IT7R98hbO for <rtcweb@ietfa.amsl.com>; Mon, 12 May 2014 09:46:01 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 17ED01A072E for <rtcweb@ietf.org>; Mon, 12 May 2014 09:46:01 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id h3so4062314igd.1 for <rtcweb@ietf.org>; Mon, 12 May 2014 09:45:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3VeGL51cgk9z7rgp+iwU4a4Qyli1pS7gKwREcxp/CQw=; b=s1e869ykr+47fcJ74dVvEllgPvtUPlJPXlWVyB36Z9SjlQG5HrfHnlXVkLgQ3UGpTc TPYXvYXpbKvaQU6MFFVQdEW9Uoy1J2E/SvtrXthZn2EW12MyT4rDRZeHD9bvssprBCfA m6NLOnyt+TxBox3wGWSZu8UwY23pXieHLSrk6FKEA3FYQ6eSAa5JL4C1UyeMh91bvetR H9dlqVgOAfm/cd2cxY54QmcKatH3mdYXKBF3aYUw+YVRKv6R/3kDGaQeqQ0f0qbIJ0q2 pwJusITCmdSeZu71cqzBTzy3FYDmfW5bj1e7UUvEBZ5okhtlO9OixLRg13tFtcJoesHS yg/Q==
MIME-Version: 1.0
X-Received: by 10.50.22.37 with SMTP id a5mr46502346igf.30.1399913154975; Mon, 12 May 2014 09:45:54 -0700 (PDT)
Received: by 10.42.200.204 with HTTP; Mon, 12 May 2014 09:45:54 -0700 (PDT)
Date: Mon, 12 May 2014 09:45:54 -0700
Message-ID: <CA+9kkMDC2tsV6_Ut6W751hHK-WRAqZ6qVMdMAgqdO57QaF4hmg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b10c99151bcc704f936aed9"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/YJ_WgQdbe0XwLkeaGOlCrUa-wsQ
Subject: [rtcweb] Update on remote participation for the interim
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2014 16:46:05 -0000
The folks on site have confirmed that there are microphones and a video conferencing system in the room. One oddity is that the video conferencing is an older unit that is not currently directly capable of running Hangouts, but for which there is a bridge. My current theory is: Bridge the system in the room to hangouts. Have a laptop in the room join the hangout. Record the hangout. Invite those who wish to attend remotely via email once the hangout has been created. (I do not believe you will need to have Google credentials to attend). End this hangout at each day's shift from IETF to W3C , starting a new hangout for the W3C part of the day when the group reconvenes. This is similar to what we did in Stockholm, though not exactly the same. Does anyone have any heartburn with this approach? Ted