Re: Meetecho overtime?

Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.com> Thu, 23 July 2015 09:29 UTC

Return-Path: <laurent.ciavaglia@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6651A8756 for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2015 02:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 efyFbVu-HiwQ for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2015 02:29:18 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 360A21A037E for <ietf@ietf.org>; Thu, 23 Jul 2015 02:29:18 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 167ABDCE43C0F; Thu, 23 Jul 2015 09:29:14 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t6N9T87W001457 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jul 2015 11:29:15 +0200
Received: from [172.27.205.245] (135.239.27.38) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 23 Jul 2015 11:29:12 +0200
Message-ID: <55B0B3E7.7060008@alcatel-lucent.com>
Date: Thu, 23 Jul 2015 11:29:11 +0200
From: Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.com>
Organization: Alcatel-Lucent Bell Labs France
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Lorenzo Miniero <lorenzo@meetecho.com>
Subject: Re: Meetecho overtime?
References: <55AFD9F7.3040001@alcatel-lucent.com> <20150722201452.66cd42f9@lminiero>
In-Reply-To: <20150722201452.66cd42f9@lminiero>
Content-Type: multipart/alternative; boundary="------------010904070109070003060602"
X-Originating-IP: [135.239.27.38]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nTrUDg4QD_Iod08qjQ486wksdBg>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 09:29:21 -0000

Dear Lorenzo,

Thanks for the feedback (and indeed the stream remains active for some 
minutes).
I hope these situations (overtime) will stay exceptional cases.

Best regards, Laurent.


On 22/07/2015 20:14, Lorenzo Miniero wrote:
> On Wed, 22 Jul 2015 19:59:19 +0200
> Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.com> wrote:
>
>> Dear IETF community, Meetecho team,
>>
>> Please apology if the problem is solved, but I have been confronted
>> two times today with WG sessions finishing beyond the schedule with
>> important decision points at the end.
>>
>> I am participating remotely. The issue is that the Meetecho stream
>> closes few minutes after the scheduled session end time.
>>
>> As a proposal (if no other solution is already in place), I would
>> suggest that the WG chairs / Meetecho operator could "extend" the
>> Meetecho session by 5-minutes time slots on a per need basis to cover
>> for the overtime.
>>
>> Thanks.
>>
> Hi Laurent,
>
> what we close is just the access, that is new participants can't join
> after the end time triggers. We don't interrupt ongoing sessions for
> participants that are still in, though, and we don't hangup the media
> streams unless the overtime reaches 10 minutes. In that case, we do
> have to interrupt the session, as preparations for the following
> meeting need to be made and cannot unfortunately be delayed.
>
> Lorenzo
>

-- 

Bien cordialement, Best regards,

*Laurent Ciavaglia*

Secure Cloud Networking

Bell Labs | Alcatel Lucent

phone: +33 160 402 636

email: laurent.ciavaglia@alcatel-lucent.com 
<mailto:laurent.ciavaglia@alcatel-lucent.com>

linkedin: laurentciavaglia <http://fr.linkedin.com/in/laurentciavaglia/>

address: Route de Villejust | 91620 Nozay | France