From: Jack Haverty <jack@3kitty.org>
To: "Livingood, Jason" <jason_livingood@comcast.com>,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards
Date: Wed, 15 Nov 2023 16:27:38 -0800 [thread overview]
Message-ID: <ef7b16ff-8348-4540-b467-5ec3c4f50f5e@3kitty.org> (raw)
In-Reply-To: <9B1B6C78-8200-4875-9F37-6688B3AE42B6@comcast.com>
[-- Attachment #1: Type: text/plain, Size: 2843 bytes --]
Interesting! I noticed that participants are limited to receive-only,
with only one able to speak at any time. From the guide:
"The general expectation is that participants will send audio or video
/only/ when recognized by a session chair as part of the queue."
That seems rather different from a virtual meeting in which hearty
discussions, arguments, interruptions, whispered side-discussions, and
such could approximate an in-person meeting. It seems more like an
audience watching a series of remote presentations than a forum for
discussions and debates, hallway encounters, and such.
If that's a "remote experience as good as possible", what are the
limiting factor(s) preventing a richer form of interactions? Is it
IETF policy, unwritten software, inadequate network performance, or ???
Are there any measurements taken? Do the remote participants feel that
they can participate as well as if they were onsite? Does the
experience vary depending on how remote you are from the meeting venue?
How does the network bandwidth and delay behave during meetings?
Jack Haverty
On 11/14/23 12:52, Livingood, Jason wrote:
>
> > And IIRC during covid, didn't the IETF do online only meetings?
>
> Yes, we did! The IETF pivoted in March 2020 to fully virtual with 701
> remote attendees. That continued for 2 years until March 2022 when we
> started having in-person again – and since that time they have been
> hybrid (and will continue to be so). The IETF also invested quite a
> lot in online meeting tools
> <https://www.ietf.org/how/meetings/technology/meetecho-guide-participant/>
> & supporting systems to try to make the remote experience as good as
> possible.
>
> IETF 118
>
> November 04-10, 2023, Prague, Czech Republic & Online
>
> 1067 onsite attendees
>
> 739 remote attendees
>
> IETF 117
>
> July 22-28, 2023, San Francisco, California & Online
>
> 890 onsite attendees
>
> 544 remote attendees
>
> IETF 116
>
> March 25-31, 2023, Yokohama, Japan & Online
>
> 993 onsite attendees
>
> 594 remote attendees
>
> IETF 115
>
> November 5-11, 2022, London, UK & Online
>
> 849 onsite attendees
>
> 667 remote attendees
>
> IETF 114
>
> July 23-29, 2022, Philadelphia, Pennsylvania & Online
>
> 618 onsite attendees
>
> 675 remote attendees
>
> IETF 113
>
> March 19-25, 2022, Vienna, Austria & Online
>
> 314 onsite attendees
>
> 976 remote attendees
>
> IETF 112
>
> November 08-12, 2021, Online
>
> 1177 remote attendees
>
> IETF 111
>
> July 26-30, 2021, Online
>
> 1206 remote attendees
>
> IETF 110
>
> March 8-12, 2021, Online
>
> 1177 remote attendees
>
> IETF 109
>
> November 16-20, 2020, Online
>
> 1061 remote attendees
>
> IETF 108
>
> July 27-31, 2020, Online
>
> 1102 remote attendees
>
> IETF 107
>
> March 23-27, 2020, Virtual
>
> 701 remote attendees
>
> //end//
>
[-- Attachment #2: Type: text/html, Size: 9686 bytes --]
next prev parent reply other threads:[~2023-11-16 0:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 16:32 Dave Taht
2023-11-11 18:24 ` rjmcmahon
2023-11-14 15:46 ` Livingood, Jason
2023-11-14 16:06 ` Dave Taht
2023-11-14 16:14 ` Frantisek Borsik
2023-11-14 16:15 ` Dave Taht
2023-11-14 16:26 ` [NNagain] [EXTERNAL] " Livingood, Jason
2023-11-14 16:33 ` [NNagain] " Sebastian Moeller
2023-11-14 16:14 ` Sebastian Moeller
2023-11-14 16:37 ` Livingood, Jason
2023-11-14 17:00 ` Sebastian Moeller
2023-11-14 17:25 ` Vint Cerf
2023-11-14 17:43 ` Dave Taht
2023-11-14 18:10 ` rjmcmahon
2023-11-14 18:02 ` Jack Haverty
2023-11-14 18:10 ` Sebastian Moeller
2023-11-14 19:27 ` Jack Haverty
2023-11-14 19:40 ` rjmcmahon
2023-11-14 21:01 ` Dave Taht
2023-11-14 21:45 ` rjmcmahon
2023-11-16 3:41 ` [NNagain] Metrics for Network Managers (was FCC NOI due dec 1 on broadband speed standards) Jack Haverty
2023-11-16 6:57 ` rjmcmahon
2023-11-14 19:53 ` [NNagain] FCC NOI due dec 1 on broadband speed standards Sebastian Moeller
2023-11-14 20:01 ` David Lang
2023-11-14 20:37 ` Dick Roy
[not found] ` <CA+aeVP8dT-ynmHxNCmZq1OWdw3VBMMJTH0zsL6dGASvfKVpDMQ@mail.gmail.com>
[not found] ` <CA+aeVP9XyNd1rL_7S7U4OdvOwtVR8Sae8QvtiQLX0HMyzE57Xw@mail.gmail.com>
2023-11-14 20:55 ` [NNagain] Virtual mtgs and conferences vs. in-person ones (was) " David Bray, PhD
2023-11-15 0:58 ` Jack Haverty
2023-11-14 20:52 ` [NNagain] " Livingood, Jason
2023-11-16 0:27 ` Jack Haverty [this message]
2023-11-16 2:31 ` Robert McMahon
2023-11-14 18:16 ` rjmcmahon
2023-11-14 18:30 ` rjmcmahon
2023-11-14 17:58 ` Jeremy Austin
2023-11-14 18:08 ` Sebastian Moeller
2023-11-14 18:34 ` [NNagain] [EXTERNAL] " Livingood, Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef7b16ff-8348-4540-b467-5ec3c4f50f5e@3kitty.org \
--to=jack@3kitty.org \
--cc=jason_livingood@comcast.com \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox