[mmox] meeting minutes from today's ietf mmox simulcasting meeting
"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Thu, 19 February 2009 04:45 UTC
Return-Path: <infinity@lindenlab.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DF2C3A685B for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 20:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level:
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 lDkeIhnxQ3tL for <mmox@core3.amsl.com>; Wed, 18 Feb 2009 20:45:36 -0800 (PST)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 4D27B3A6824 for <mmox@ietf.org>; Wed, 18 Feb 2009 20:45:36 -0800 (PST)
Received: from infinity.vpn.lindenlab.com (infinity.vpn.lindenlab.com [10.0.254.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id 94F4F3DBC064 for <mmox@ietf.org>; Wed, 18 Feb 2009 20:45:48 -0800 (PST)
Message-Id: <6A5E83A8-A7A1-4D38-8FAC-C04E360E4777@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: mmox@ietf.org
In-Reply-To: <5B7AC832-F851-4103-AB45-9FF2A536CCD5@multicasttech.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 18 Feb 2009 20:45:45 -0800
References: <499CC99D.8040302@cox.net> <5B7AC832-F851-4103-AB45-9FF2A536CCD5@multicasttech.com>
X-Mailer: Apple Mail (2.930.3)
Subject: [mmox] meeting minutes from today's ietf mmox simulcasting meeting
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 04:45:37 -0000
the meeting today was just to review requirements and get input from peeps with experience hosting large concurrent real-world / virtual- world events. Sai / Lawton already posted the chat logs at http://wiki.secondlife.com/wiki/MMOX/Chat_Logs/19-2-2009 . i'm on the hook for boiling it down to its essential points. so.. might as well present it here as well: * there are two major issues... streaming the video out of the physical meeting space and providing for input from geographically distributed participants * streaming out... * the IETF generally doesn't do video anymore, we're told it's cause they don't want to have a camera and camera operator per room * we have at least one video camera, a firewire cable, a macbook pro running quicktime broadcaster, and a commercial partner who can replicate those streams * do we need additional audio equipment (tie mic for presenters, microphone for attendees to ask questions / make comments?) * those who want to view the stream (either within the virtual world, or without) would use an RTSP url in their favorite streaming video client to access the stream * this should work with QuickTime Player, mplayer, miro / democracy, et al * second life parcel / estate owners and open sim instance operators may set the "parcel media stream" to this RTSP url * this will allow anyone who enters the parcel to get a reference to the RTSP url and establish a stream from our commercial stream partner to the user's client host * it's important to note that for second life and open sim instances, this will consume one RTSP stream per client, not one stream per virtual world * qwaq says they can consume a single stream and rebroadcast it within their virtual world. (which is pretty darn'd awesome) * there was considerable variability in the estimates of how many streams would be required * bjornlyn loon and bevan whitfield were present, giving advice for how to judge the requirements * the low estimate was 2 streams required * the high estimate was 300 streams (eliminating the outliers of 5k and 20k) * we want to get this number pinned down by COB this Friday (20 Feb 2009) * qwaq has a strong preference / requirement for using H.264 instead of H.263 * but that's not a terrible issue, the SL clients on Mac and Windows are known to support H.264. * we would love to hear from users / developers of other viewers if H.264 support is present. * with so many moving parts, it would be nice to have a test run or two (or three) * fortunately, whump linden will be using a similar configuration to broadcast Ursala K. LeGuin's reading from the upcoming Potlatch literary event * getting questions / comments back into the face to face meeting * there is a concern that all participants volunteering information (questions, comments, etc.) have been made aware of the IETF IPR Disclosure rules * you can find information about this at http://www.ietf.org/NOTEWELL.html * this issue is the primary "business requirement" * there were several proposals for how to ensure remote participants were presented with the NOTEWELL URL and told to read it before commenting * one solution was to require people to visit a "click through" web page requiring you to acknowledge you were told to read the contents of the NOTEWELL page * another solution (for virtual worlds) was to spam users with notecards and placards telling them to read the contents of the NOTEWELL page * this won't work for people who aren't in one of the virtual worlds, assuming people come in via XMPP * assuming we resolve the technical challenges of connecting to jabber.ietf.org with mac clients * yet another solution was for the person relaying questions from the virtual world to ask everyone, "have you read and understand the IETF IPR disclosure policy as outlined on the NOTEWELL page?" * we assume there will be one person physically present at the meeting who will relay questions from geographically distributed participants to the presenters * related, but not completely the same, is the idea of having chat- bridges for people viewing the the meeting in a virtual world to talk to each other, and the people in various XMPP / IRC chatrooms * it would be great if _this_ was the mechanism that relayed questions / comments from geographically distributed participants * if we used one that only worked on second life, would this be fair to the qwaq participants or the OSGrid participants? * other issues * bjornlyn loon has a solution for accessibility, w00t! * IETF meetings are considered public, so we are assuming the video, audio, audio transcription and chat log will be archived and freely available. * so don't say anything you don't want your (grand)kids hearing you say 15 years from now * moving forward * we need to figure out how many streams we're going to purchase by close of business on friday 20 february, 2009 * we need to get guidance from the IETF with respect to what constitutes "notice" for IETF IPR disclosure policy * it would be great to test this configuration * is the use of mmox@jabber.ietf.org required? several mac users have noted difficulty in using it. -cheers -meadhbh
- [mmox] Historic meeting Lawson English
- Re: [mmox] Historic meeting Marshall Eubanks
- Re: [mmox] Historic meeting Meadhbh Hamrick (Infinity)
- Re: [mmox] Historic meeting Lawson English
- [mmox] meeting minutes from today's ietf mmox sim… Meadhbh Hamrick (Infinity)
- Re: [mmox] meeting minutes from today's ietf mmox… Dave Coyle
- Re: [mmox] meeting minutes from today's ietf mmox… Morgaine
- Re: [mmox] meeting minutes from today's ietf mmox… Marshall Eubanks
- Re: [mmox] meeting minutes from today's ietf mmox… Meadhbh Hamrick (Infinity)
- Re: [mmox] meeting minutes from today's ietf mmox… Morgaine
- [mmox] Jabber clients for mmox (Re: meeting minut… Rob Lanphier
- Re: [mmox] Jabber clients for mmox (Re: meeting m… Marshall Eubanks
- Re: [mmox] Jabber clients for mmox (Re: meeting m… Rob Lanphier
- Re: [mmox] Jabber clients for mmox (Re: meeting m… Marshall Eubanks
- Re: [mmox] Jabber clients for mmox (Re: meeting m… Meadhbh Hamrick (Infinity)
- Re: [mmox] Jabber clients for mmox (Re: meeting m… Marshall Eubanks