IETF Logo Mail Archive

Re: [vmeet] Meetecho sessions start/stop time

Dan York <york@isoc.org> Mon, 11 April 2016 09:44 UTC

Return-Path: <york@isoc.org>
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 51C0B12E5BD for <vmeet@ietfa.amsl.com>; Mon, 11 Apr 2016 02:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.com
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 SkbIFhSbnRHn for <vmeet@ietfa.amsl.com>; Mon, 11 Apr 2016 02:44:33 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0680.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:680]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B613B12E5AE for <vmeet@ietf.org>; Mon, 11 Apr 2016 02:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com; s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=akRmyaTSB4BY7Jl16ha3cGGJlYHaiIkgBvehkdMVHyo=; b=FXcYWEoUFJIrMT0rOMU5daM/8YL+HFJ2poukBd8WFf9TF8Ny/3GsZX3FBrlePNhG8ACRb5ysQUQWJEqMZNvzCMxryeso3qV11rAW2p8zWjLYxipbZKRL24dLO0UZOVzwSShhw85AcGYxvyXHPvIIraLwviaaYQeE1dy2qN1qMUc=
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com (10.163.232.19) by CY1PR0601MB1657.namprd06.prod.outlook.com (10.163.232.19) with Microsoft SMTP Server (TLS) id 15.1.453.26; Mon, 11 Apr 2016 09:44:12 +0000
Received: from CY1PR0601MB1657.namprd06.prod.outlook.com ([10.163.232.19]) by CY1PR0601MB1657.namprd06.prod.outlook.com ([10.163.232.19]) with mapi id 15.01.0453.029; Mon, 11 Apr 2016 09:44:12 +0000
From: Dan York <york@isoc.org>
To: John C Klensin <john-ietf@jck.com>
Thread-Topic: [vmeet] Meetecho sessions start/stop time
Thread-Index: AQHRk08Yfxt78slTK0mjz8CUSt1WzJ+DgFkAgAEGbgA=
Date: Mon, 11 Apr 2016 09:44:11 +0000
Message-ID: <CD301AF4-ECAA-4FAB-8D38-A3CC343F7853@isoc.org>
References: <570A8E5C.8040301@meetecho.com> <20F7413E33810665077E7003@JcK-HP8200.jck.com>
In-Reply-To: <20F7413E33810665077E7003@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: jck.com; dkim=none (message not signed) header.d=none;jck.com; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [74.69.229.215]
x-ms-office365-filtering-correlation-id: 7bbee406-c1bf-4e97-f4e0-08d361edd66e
x-microsoft-exchange-diagnostics: 1; CY1PR0601MB1657; 5:Oh+rGmqvqzULjx0ouYGae9iXqNLZV5PhqQdHTerAgWPTu9RdUKhLyippkXFURpT3/9M1D+Ik2pciZuSE/q43TVFrw/ll8hCwyvnDR8IKalW9NR3X1TSpV6OF0AD56vI/aQkISOtbnTj4xOcmKhlBeg==; 24:4NU9X9rsy4nC/OAfJDeATZ2coKUWNNaap7bBxBEsvQGwae2fsIOQiNmHLRJPUuvZKZ4bV1Jq0APjdsxJ9egvLS/naQuMlI8yLbA6aHZP6kM=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1657;
x-microsoft-antispam-prvs: <CY1PR0601MB165711EF5C941C50D14F8877B7940@CY1PR0601MB1657.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:CY1PR0601MB1657; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1657;
x-forefront-prvs: 09090B6B69
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(24454002)(377454003)(19617315012)(2906002)(189998001)(110136002)(106116001)(122556002)(87936001)(83716003)(5004730100002)(54356999)(50986999)(82746002)(76176999)(11100500001)(19580395003)(19580405001)(99286002)(92566002)(3280700002)(81166005)(3660700001)(5002640100001)(77096005)(15395725005)(16236675004)(2900100001)(2950100001)(5008740100001)(33656002)(86362001)(36756003)(1096002)(1220700001)(66066001)(10400500002)(102836003)(6116002)(15975445007)(3846002)(4326007)(586003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1657; H:CY1PR0601MB1657.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CD301AF4ECAA4FAB8D38A3CC343F7853isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2016 09:44:11.9611 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1657
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/AuV4A4S_kJitub7tLGTmCyWPkAw>
Cc: "vmeet@ietf.org" <vmeet@ietf.org>
Subject: Re: [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: Mon, 11 Apr 2016 09:44:35 -0000

John,

While I think the "one minute to disconnection" warning the Meetecho team just suggested is a great addition...

On Apr 10, 2016, at 2:04 PM, John C Klensin <john-ietf@jck.com<mailto:john-ietf@jck.com>> wrote:

I'd simply run a session with a separate Jabber
client, but that introduces some extra synchronization problems.

... I've alway run a separate Jabber client connected into each working group chat when remote.

I've done this for a couple of reasons:

1. In the past, I had occasions when the Meetecho client would freeze or otherwise require me to disconnect and restart the session;

2. I've had issues where my browser crashed because of some other site... but in doing so it took down the Meetecho session; and

3. I've had a number of cases where I wanted to go back and get something out of a chat and I knew from experience that when Meetecho ended you had to get the chat from the chat logs... which was another place to go.

Typically, I've often been monitoring several sessions simultaneously through Jabber chat rooms, and so I'm already running a separate Jabber client.  My usual process has been to have one Meetecho session up with the main group I'm interested in, and then separate Jabber chat windows for the other sessions.  So it's no big deal for me to also have a Jabber chat room for the working group that I'm also in via Meetecho.

It does mean I'm in that room twice via two different clients, but that is what has worked for me.

Dan

--
Dan York
Senior Content Strategist, Internet Society
york@isoc.org<mailto:york@isoc.org>   +1-802-735-1624
Jabber: york@jabber.isoc.org<mailto:york@jabber.isoc.org>
Skype: danyork   http://twitter.com/danyork

http://www.internetsociety.org/

v2.8.7 | Report a Bug | By Email