From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bobcat.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 069C33B2A4 for ; Wed, 15 Nov 2023 21:31:33 -0500 (EST) Received: from [192.168.1.96] (c-69-181-111-171.hsd1.ca.comcast.net [69.181.111.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by bobcat.rjmcmahon.com (Postfix) with ESMTPSA id F27211B252; Wed, 15 Nov 2023 18:31:32 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 bobcat.rjmcmahon.com F27211B252 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjmcmahon.com; s=bobcat; t=1700101893; bh=747bIVgLT51Dg3HlksUsP3ANuf5XeKSINLXWWFwmdKU=; h=In-Reply-To:References:Subject:From:Date:To:CC:From; b=ZDwJ+SVN1HXIKME7vgynyD8BSkT/008An1A2yhUcpbm71AsYyuuQy8gvjDtKqXIcv E9HrM3y04R72aeprgMGa7UkAi5KEsfcTbJdSUmpAAUYsZLJFjfSTorunWSxVdMwDZX U8eRNG+XKaC6iy1CyfFkrNhxId2Eki5OOJjlanTQ= In-Reply-To: References: <96DDD887-4AC2-4F11-9B49-5ED6FC3F5FA2@gmx.de> <1F39BCDB-1AE0-45D4-B622-411478465119@gmx.de> <9B1B6C78-8200-4875-9F37-6688B3AE42B6@comcast.com> X-Referenced-Uid: 00011a35567702d5 Thread-Topic: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards User-Agent: Android X-Is-Generated-Message-Id: true MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----JHD258OLTF79HP4J5WAHETSRLLQRTA" Content-Transfer-Encoding: 7bit From: Robert McMahon Date: Wed, 15 Nov 2023 18:31:04 -0800 To: Andrew Odlyzko via Nnagain Message-ID: <6eda622f-0081-486a-81c9-fe0ff7e9a352@rjmcmahon.com> Subject: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards X-BeenThere: nnagain@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: =?utf-8?q?Network_Neutrality_is_back!_Let=C2=B4s_make_the_technical_aspects_heard_this_time!?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2023 02:31:34 -0000 ------JHD258OLTF79HP4J5WAHETSRLLQRTA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 The hackathon element requires in person with equipment=2E So there's that = too=2E =E2=81=A3Bob On Nov 15, 2023, 4:27 PM, at 4:27 PM, Jack Haverty vi= a Nnagain wrote: >Interesting!=C2=A0=C2= =A0 I noticed that participants are limited to receive-only, > >with only o= ne able to speak at any time=2E=C2=A0 From the guide: > >"The general expec= tation is that participants will send audio or video >/only/ when recogniz= ed by a session chair as part of the queue=2E" > >That seems rather differe= nt from a virtual meeting in which hearty >discussions, arguments, interru= ptions, whispered side-discussions, and >such could approximate an in-pers= on meeting=2E=C2=A0 It seems more like an >audience watching a series of r= emote presentations than a forum for >discussions and debates, hallway enc= ounters, and such=2E > >If that's a "remote experience as good as possible"= , what are the >limiting factor(s) preventing a richer form of interaction= s?=C2=A0=C2=A0=C2=A0 Is it >IETF policy, unwritten software, inadequate ne= twork performance, or ??? > >Are there any measurements taken?=C2=A0=C2=A0 = Do the remote participants feel >that >they can participate as well as if = they were onsite?=C2=A0=C2=A0 Does the >experience vary depending on how r= emote you are from the meeting >venue?=C2=A0 >How does the network bandwid= th 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=2E That continued for 2 years= until March 2022 when we > >> started having in-person again =E2=80=93 and= since that time they have been >> hybrid (and will continue to be so)=2E = The IETF also invested quite a >> lot in online meeting tools >> > > >= > & supporting systems to try to make the remote experience as good as >> = possible=2E >> >> IETF 118 >> >> November 04-10, 2023, Prague, Czech Republ= ic & Online >> >> 1067 onsite attendees >> >> 739 remote attendees >> >> IE= TF 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 rem= ote 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 att= endees >> >> 675 remote attendees >> >> IETF 113 >> >> March 19-25, 2022, V= ienna, Austria & Online >> >> 314 onsite attendees >> >> 976 remote attende= es >> >> IETF 112 >> >> November 08-12, 2021, Online >> >> 1177 remote atte= ndees >> >> IETF 111 >> >> July 26-30, 2021, Online >> >> 1206 remote atten= dees >> >> IETF 110 >> >> March 8-12, 2021, Online >> >> 1177 remote attend= ees >> >> IETF 109 >> >> November 16-20, 2020, Online >> >> 1061 remote att= endees >> >> IETF 108 >> >> July 27-31, 2020, Online >> >> 1102 remote atte= ndees >> >> IETF 107 >> >> March 23-27, 2020, Virtual >> >> 701 remote atte= ndees >> >> //end// >> > > >-----------------------------------------------= ------------------------- > >______________________________________________= _ >Nnagain mailing list >Nnagain@lists=2Ebufferbloat=2Enet >https://lists= =2Ebufferbloat=2Enet/listinfo/nnagain ------JHD258OLTF79HP4J5WAHETSRLLQRTA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
The hacka= thon element requires in person with equipment=2E So there's that too=2E
Bob