[vmeet] Meetecho sessions start/stop time
Meetecho IETF support <ietf@meetecho.com> Sun, 10 April 2016 17:33 UTC
Return-Path: <ietf@meetecho.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id ACDFA12D61E
for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 10:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
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 2wQ3N9VqclxZ for <vmeet@ietfa.amsl.com>;
Sun, 10 Apr 2016 10:33:23 -0700 (PDT)
Received: from smtpcmd01218.aruba.it (smtpcmd10101.aruba.it [62.149.156.101])
by ietfa.amsl.com (Postfix) with ESMTP id C71FF12D095
for <vmeet@ietf.org>; Sun, 10 Apr 2016 10:33:22 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.161.70])
by smtpcmd10.ad.aruba.it with bizsmtp
id ghZM1s00u1XS04f01hZM3Q; Sun, 10 Apr 2016 19:33:22 +0200
To: vmeet@ietf.org
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <570A8E5C.8040301@meetecho.com>
Date: Sun, 10 Apr 2016 19:33:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/-Jts64D53ulC3CGsRJM0NqBMqig>
Subject: [vmeet] Meetecho sessions start/stop time
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>,
<mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 10 Apr 2016 17:33:25 -0000
Folks, just to clarify that Meetecho sessions do start 5 minutes before the WG meeting scheduled start time, and never stops before the meeting has actually finished. Only when the previous meeting runs *very* long, we have to shift the start time of the following Meetecho session. This is needed in order to avoid overlaps in the recordings. This was the case of the 6LO session on Thursday, which started at 17.30 sharp because the MTGVENUE session ended at 17.30. Cheers, the Meetecho team
- [vmeet] Meetecho sessions start/stop time Meetecho IETF support
- Re: [vmeet] Meetecho sessions start/stop time John C Klensin
- Re: [vmeet] Meetecho sessions start/stop time Dave Crocker
- Re: [vmeet] Meetecho sessions start/stop time Paul Kyzivat
- Re: [vmeet] Meetecho sessions start/stop time Meetecho IETF support
- Re: [vmeet] Meetecho sessions start/stop time Dan York
- Re: [vmeet] Meetecho sessions start/stop time Dave Crocker