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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 29 March 2020 16:39 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 107attendees@ietfa.amsl.com
Delivered-To: 107attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57783A0E1E; Sun, 29 Mar 2020 09:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 9qAgpsN3qRIP; Sun, 29 Mar 2020 09:39:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5391C3A0E1D; Sun, 29 Mar 2020 09:39:23 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9516D3897C; Sun, 29 Mar 2020 12:37:54 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2E11CFC9; Sun, 29 Mar 2020 12:39:22 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 107attendees@ietf.org, IETF list <ietf@ietf.org>
In-Reply-To: <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> <20200328034611.GZ50174@kduck.mit.edu>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 29 Mar 2020 12:39:22 -0400
Message-ID: <11945.1585499962@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/107attendees/I2zzxMnfasGc5fXfw9eksff68sU>
Subject: Re: [107attendees] Where the action is, at virtual meetings ...
X-BeenThere: 107attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 107 attendees for official communication <107attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/107attendees>, <mailto:107attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/107attendees/>
List-Post: <mailto:107attendees@ietf.org>
List-Help: <mailto:107attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/107attendees>, <mailto:107attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Mar 2020 16:39:25 -0000

Benjamin Kaduk <kaduk@mit.edu> wrote:
    >> 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.)

I once saw a 2 minute lag in seeing my comments echo back.
All the traffic showed up for me, eventually.

I think it was during plenary.
I don't know if there was a new TCP session or not, it didn't persist long
enough for me to investigate, but I certainly did notice and was perplexed.

I didn't remember it until reading your comment.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-