Re: [107attendees] Where the action is, at virtual meetings ...

Benjamin Kaduk <kaduk@mit.edu> Sat, 28 March 2020 03:46 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664423A0D92; Fri, 27 Mar 2020 20:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 rfmaN3Ce83MX; Fri, 27 Mar 2020 20:46:21 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 0C9BD3A0D8D; Fri, 27 Mar 2020 20:46:20 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 02S3kBSM016782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 Mar 2020 23:46:14 -0400
Date: Fri, 27 Mar 2020 20:46:11 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>
Cc: 107attendees@ietf.org, IETF list <ietf@ietf.org>
Subject: Re: [107attendees] Where the action is, at virtual meetings ...
Message-ID: <20200328034611.GZ50174@kduck.mit.edu>
References: <CAKKJt-eCsg4v2kawrDAYy3StYE=SEVDVQfqngZfO6PD0o1Tswg@mail.gmail.com> <CCA52B2C-A856-4814-83DF-58A012AB63BA@fugue.com> <CA+9_gVvSvdocYSsw-FEAFrAL8Fq--CQpRj2OFJfvUVx6PjBrTA@mail.gmail.com> <7316D61D-A962-4943-BF02-FC676D671219@icloud.com> <6c578ff5-2870-7b86-6590-7ab01f944376@htt-consult.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6c578ff5-2870-7b86-6590-7ab01f944376@htt-consult.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2fG26g5TBxpgWrXnnmeu67CSZMQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 28 Mar 2020 03:46:23 -0000

On Fri, Mar 27, 2020 at 01:44:37PM -0400, Robert Moskowitz wrote:
> 
> 
> On 3/27/20 1:24 PM, Carrick Bartle wrote:
> >> As a 2-year newbie to IETF I have found it hard to get into the 
> >> Jabber rooms for the meetings.
> >
> > As a <1-year newbie, I've also had difficulty with Jabber. When Adium 
> > wasn't sending my messages, I ended up creating an entirely new 
> > account and getting a different client, which worked once, but the 
> > second time, I couldn't get into a room for unknown reasons until it 
> > just magically worked about 10 minutes later.
> 
> I hope that after this week, there will be some good work in wringing 
> out the bumps and making test enviornments available.  Also if wg's 
> interim virtual meetings were to use Jabber, more people will gain the 
> needed skillls to guide new comers.

I will note that this meeting seems to have had enough load to induce
severe lag and maybe even full-on disconnections.  I am regularly in jabber
and hold a weekly meeting via jabber, but had to frantically engage an
alternate solution because my normal setup was not getting me all the
traffic in a timely fashion.  (I saw a couple other people comment about
lag, too, so at least that part is not just me.)

-Ben