From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Jack Haverty" <jack@3kitty.org>
Subject: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards
Date: Tue, 14 Nov 2023 20:52:28 +0000 [thread overview]
Message-ID: <9B1B6C78-8200-4875-9F37-6688B3AE42B6@comcast.com> (raw)
In-Reply-To: <1F39BCDB-1AE0-45D4-B622-411478465119@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
> 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: 7396 bytes --]
next prev parent reply other threads:[~2023-11-14 20:52 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 ` Livingood, Jason [this message]
2023-11-16 0:27 ` [NNagain] " Jack Haverty
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=9B1B6C78-8200-4875-9F37-6688B3AE42B6@comcast.com \
--to=jason_livingood@comcast.com \
--cc=jack@3kitty.org \
--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