Re: [vmeet] Meetecho sessions start/stop time

Dave Crocker <dhc@dcrocker.net> Sun, 10 April 2016 18:43 UTC

Return-Path: <dhc@dcrocker.net>
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 32D4B12D622 for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 11:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 n190qp1ePW5Y for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 11:43:16 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B8C612D61F for <vmeet@ietf.org>; Sun, 10 Apr 2016 11:43:16 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u3AIhFE0002748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 10 Apr 2016 11:43:15 -0700
To: Meetecho IETF support <ietf@meetecho.com>
References: <570A8E5C.8040301@meetecho.com> <20F7413E33810665077E7003@JcK-HP8200.jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <570A9EBE.7090908@dcrocker.net>
Date: Sun, 10 Apr 2016 11:43:10 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20F7413E33810665077E7003@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 10 Apr 2016 11:43:15 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/yEppSnnTjUVCGayh2jHFkxsC4eM>
Cc: vmeet@ietf.org
Subject: Re: [vmeet] Meetecho sessions start/stop time
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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 18:43:17 -0000

On 4/10/2016 11:04 AM, John C Klensin wrote:
> There were a couple of times when I was
> typing something into Jabber (via Meetecho) when the session
> ended.  That resulted in the screen, and Jabber session,
> abruptly clearing, so I couldn't finish the message for the
> Jabber log, copy the partially-finished one so I could later
> send something similar in email, or otherwise salvage what had
> been typed already.


IETF Meeting Jabber sessions, outside of Meetecho, are long-lived.  So 
the problem being described is quite basic.

Unfortunately the only reasonable solution is to permit continued use of 
jabber, but possibly better to permit a "session not active" form of 
session participation (both before and after the session) with use of 
jabber.

This could have a number of benefits, for preparation, coordination and 
-- in the current example -- finishing one's thoughts.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net