[admin-discuss] Re: Second consultation on Remote Rooms for IETF Meetings
Mirja Kuehlewind <ietf@kuehlewind.net> Mon, 31 August 2026 18:18 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: admin-discuss@mail2.ietf.org
Delivered-To: admin-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 81DC713276C9C for <admin-discuss@mail2.ietf.org>; Mon, 31 Aug 2026 11:18:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788200298; bh=pYBy6IKSUojsg5aU6XY4vmH1g5S9RoVVTMLcFA7q99Q=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=NeERx0tIjmKm3gJiYJsq8ufYLcqdtHOuZeVYRlHh3z2RsV/hCM2mQjPj3GeNZfrlJ 2jKc3ND2s25sMmlUHFpT4hbeuKCEO+ySOkwx/EUpp+y+jQL2aBqaOu9VDvUFhSRjKg CTFhl7dFp7JzrCecUtuLhHGE55fQiwgkm3pZHFHs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level:
X-Spam-Status: No, score=-1.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=kuehlewind.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysQ5ZU1_GOAd for <admin-discuss@mail2.ietf.org>; Mon, 31 Aug 2026 11:18:17 -0700 (PDT)
Received: from outbound.ci.icloud.com (ci-2006k-snip6-6.eps.apple.com [IPv6:2a01:b747:3005:201::6d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7CF7913276C78 for <admin-discuss@ietf.org>; Mon, 31 Aug 2026 11:18:17 -0700 (PDT)
Received: from outbound.ci.icloud.com (unknown [127.0.0.2]) by p00-icloudmta-asmtp-us-central-1k-20-percent-1 (Postfix) with ESMTPS id 38BC818000FC; Mon, 31 Aug 2026 18:18:09 +0000 (UTC)
X-ICL-RepId: 01a0590b-0386-74ee-aa09-94ed2986709d
X-ICL-Out-Info: HUtFAUMHWwJACUgATUQeDx5WFlZNRAJCTQhICkMDWxxEAVYBXAFLVxQEEVYZUStZBVwQXwhAAlwUFxZWGRcNVk1SDVYFWw5FGVccHQNSHxICWkUGTV8OXh8EF0YZVQRHHl1WUAQZAlEcVg1XQ1QEX1BJDEFQbFoARxdIHV0ZWW9QXRwOBkIOWhxcD1oDU0VcFU1YXgRTVg5FCzkBXAVTCl0MQANaGl8BRwlVcVsOWR9DfUsKWAFSd0B8OXAtXB5XGFUdRARZDxweXAwNTUMSQhUEG0YeQwRfL10XXgxeBQ==
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuehlewind.net; s=sig1; t=1788200291; x=1790792291; bh=1ornRL+PGGoU1gWmjoCY7l26ebOemlHuHCVPh3fIHao=; h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To:x-icloud-hme; b=RKlDhQtm1IptIc6b6RYzMwwKY4wAYtWWF8wAfDMzzZzLl3DQwWDg+7uHuglQBXfUmOWLV/zQqRkfCjj4zSA2kSFi+tT8b4VwUlS6bYD5o56mI1tMpnmf1qFWSWr77AJszHGZtRX93J/bwkcs3TmsCrCExRHNejQPZS149ciMHkd8CjG2ZuKkgH9t0LHEWmx9ZP+YQnUwsl/3bUoisbL6/lUWmoemXI7oDNORnUXaGWCMspUqA9eE46bT37Y+fDERNWjYYv6djXP7wxTZI//Nm05H3S7+lAWaq6LfbSWBb61lw4+1LO3pfyfkHe6JSTy1PKDlMx4UhpIqOODxOovjig==
mail-alias-created-date: 1725731591227
Received: from smtpclient.apple (unknown [17.57.156.36]) by p00-icloudmta-asmtp-us-central-1k-20-percent-1 (Postfix) with ESMTPSA id F07541800616; Mon, 31 Aug 2026 18:18:07 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-1109EC56-A627-4BDD-82B7-49D16B98293A"
Content-Transfer-Encoding: 7bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Mime-Version: 1.0 (1.0)
Date: Mon, 31 Aug 2026 20:15:27 +0200
Message-Id: <52A21288-5807-4370-B692-3D39569E0EAC@kuehlewind.net>
References: <4789ACBE-5F85-4786-B4F4-2815D982A43E@csperkins.org>
In-Reply-To: <4789ACBE-5F85-4786-B4F4-2815D982A43E@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: iPhone Mail (23G83)
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwODMxMDE1OCBTYWx0ZWRfX6Ok0do4dhaZP q4hTgb07T+tngisgALdztGe5FlxbvW87aQ1/HqMDJAUcFP+YJKZosjHjFyVZMYtHJbqJXaEb5SX mXiRPJcuaXbYmDcB00y9MLdOIrgpwmRoXPOxRIICyQzb8P2OEywtlRVXApFjrlj5IWswCB5jqpc 0BvTWboog9w/GHA07R1HM5L14RRE76ud+DgY+c1Mw4JjymXGpUXDyPl4J2jqs/8IwhjwuZcrMOl 9ZzBP5YiH7fVZvObh0zZPPSxNyT0XqMrCiobXeSP56GPoe2WlS3oupamvKNESs42NMhVuODumcH unfocZIjxWmMTgoef/Q1yX/9b151hHgvUjG+w0uIIwfWsDkbn5FfdRkWjdBrb0=
X-Proofpoint-ORIG-GUID: lkJ4OCP1hR4wKIBjhNV9B8U9JySF7W6-
X-Proofpoint-GUID: lkJ4OCP1hR4wKIBjhNV9B8U9JySF7W6-
X-Authority-Info-Out: v=2.4 cv=SvydKfO0 c=1 sm=1 tr=0 ts=6a95c561 cx=c_apl:c_pps:t_out a=2G65uMN5HjSv0sBfM2Yj2w==:117 a=2G65uMN5HjSv0sBfM2Yj2w==:17 a=Sv0fKeRqtYgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=vQ6dKL7GAAAA:8 a=CyoNnzhyKsYbQBf1r-gA:9 a=CYAqtJmOr_62xGyU:21 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=mJ0ar-z9p3RXkz0ikL7Z:22
X-JNJ: AAAAAAAB08sT5+S0D2uL/gVgVlGIZwV9lsa0YsQXh8mooLe1PD90mMwtQBKGsKjZxyKssaOPXebRs54xN/azQXiaT97jkoBbcl9l5rfum5kl/J1zP7RBFrZkMsA2BDrL5jC6nXJQyAtAFj2nLoKV4TXASrDgQ/aX4uaynza9AE45eTTPPyIkY7Fgx+FaSQrqyH0lWysE52s+ZTMxyNRcnKNHnZx4pYe3D1Kc5bYKookdd1s9NzRJnFI46gWBgjr0PDhPZ+vm+iTDXbnFkKJ+GG8AxbvN/CUTJMZrguce/1uEBSBiAnBW/titickPtM4i7nqXHiN2DPyyHo18/niLIwz6AJWl6H3wgOJOxNkKdDyfcGJicBGTpjvinwwXu8X+JhEckVZdIzNOcL4HoYHE37s+u4J02VbsqGeT5UX5U9nRygp4PdZHBtIM428aMf+Vk8Lo2d9OqEAIK8Y0WFay4VrG3sA2ni986ZwG6Y4gPYpArxaHeG4YdTtKZDJo96V4Cs4//rmJDo3BrXVYxterE6lj7YdPLRo9knddABucE8rxGzPnEkS8r3wID7G1RNzmTlPEovFyNFGOArIZQPOTDkDtOgdf6/yGJTplz/rT8ex/y7FASZjyvruomBdHf5pLyu4KeqAYQjTl/lSML99gFpQj03EKhFKQnN5LSlvU6RsPv9EkVn1DJbQ0X3erVix8ETWx1DkD0gfV2ESQrwJEgYjZ+msEfFpaisVn7Eg2WXUeLJHxfBg2oNdlvaPsngEGneJRVLSBolrMaI6HS7gVWPxxk1/W8t0OEAHOZ/Ws2kbZbl8qpjcO48KH7u5bgY4SalfuAUF7vYLuovq+QWH2MrXKvfPNBgTFa9ehBh0w7xkVHpnBWbc9QLk6XI3EmjVDBZJWSv6fMsTw16wdzI0MUgX4Kfxs8sa6CdTGW6mjoxCfF+FXrEHJRVIrZ4Gb6rWq868bGy56mJsMfGsHjbUaYS1xawHONA5 j2S3PxWJnoczoubcCNoTS8g26U+HLtRlB2XxJBbvQ9BW0ntwfD+8Evht8+TyELPyxLqeOELBmIoVY5zFNrLBbZJLOOmKPJqteavzzsaS0f8xVcGvX+hcPFjN+B43OMSV90O/aGh5loN1g7JpAgNneh73YLaQCDDqWVhcG2nZ5xH3eSGQJKKNYCdI3WahHVJg9Ino2beLX4SqBopTt7egsZDlERgFavXswh2TnxOegsb3vvH0a791gMFS3gd+bbmRgYQs32D0OlvR7rBjaKTN8F88SBotWHLA04JCK19QU40jSzeQXxEHNEQkkVvj7YCa9l+Cm96SWVzGqdk1YZPo4SDvqeyUPdgH0m42AyC/rkhHe8JZFPbmCEM1B8LNZ4l1IUSWOUVWffGFNt+3b+sP/fDYprcchiu2Pa6dAmC3c38VWQUrQB6ysPC76VaLv1It/18j65nl9F6aWwz5GkEZSvxm2/ak0b2kOCPUiMrxyO0F/Hw==
Message-ID-Hash: WFOGDTWVDGD35Z4SY5BBNHT2ZVX5DKKV
X-Message-ID-Hash: WFOGDTWVDGD35Z4SY5BBNHT2ZVX5DKKV
X-MailFrom: ietf@kuehlewind.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Brian Campbell <bcampbell=40pingidentity.com@dmarc.ietf.org>, David Schinazi <dschinazi.ietf@gmail.com>, admin-discuss@ietf.org, Executive Director IETF <exec-director@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [admin-discuss] Re: Second consultation on Remote Rooms for IETF Meetings
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/KRlqbbi2114_XAFcKQrkHVvCSCk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:admin-discuss-owner@ietf.org>
List-Post: <mailto:admin-discuss@ietf.org>
List-Subscribe: <mailto:admin-discuss-join@ietf.org>
List-Unsubscribe: <mailto:admin-discuss-leave@ietf.org>
Am 28.08.2026 um 21:10 schrieb Colin Perkins <csp@csperkins.org>:
--And this is what we need to balance: as a way of improving the experience for those who wouldn’t otherwise be able to attend, the remote hubs are beneficial. As a way of allowing a clique to meet separately, they’re a problem.
I think we should support remote hubs, and I think the Tokyo hub was an excellent proof-of-concept, but we should try to articulate some norms for when it’s appropriate to setup a remote hub.
Cheers,
Colin(full disclosure: I was at the Tokyo remote hub)
On 28 Aug 2026, at 16:58, Brian Campbell wrote:
From the perspective of an onsite participant in Shenzhen, the experience of the remote rooms/hub was not particularly positive. Possibly exacerbated by other connectivity issues, it felt disjointed and not especially productive or collaborative. The air of exclusivity around the Tokyo hub was off-putting as well, which might have affected my perception of the experience.
Hi Jay,I was one of the Google employees who helped facilitate the Tokyo satellite meeting. I found it to be a very successful experiment.Please find responses to your questions below:# Question 1: In principle, do you think that Remote Rooms/Remote Hubs similar to those described above should be available for IETF meetings and/or Interim meetings?In principle, and more importantly in practice, I think that the Remote Room feature is incredibly useful and productive. 89% of the attendees of the remote hub would not have attended Shenzhen in person if Tokyo had not been an option. So for all these people - and for anyone who values their contributions - the Remote Room feature increased the productivity of IETF 125.
# Question 1a: If so then should there be any restrictions on how they are used, or who can use them?
In a perfect world, it would be great to mandate that these remote hubs be open to all for free, announced publicly months in advance, and provide cookies. But, then again, we don't live in a perfect world. If we did, we wouldn't need these in the first place because everyone would be able to attend the main location. In the real world, the remote hub organizers do have practical limits on how many people they can host, due to limitations in meeting room size, budget, etc. As soon as those come into play, you have to introduce restrictions. For this experiment, the limit was reached by communicating by word of mouth. I'm sure there are other reasonable ways to reach those limits. But we can't simply mandate that no restrictions exist, that's not realistic.# Question 2: How, if at all, do you see the use of Remote Rooms/Remote Hubs for IETF meetings, similar to those described above, impacting the IETF?In our increasingly geopolitically polarized world, not everyone will be able to feel safe attending every meeting location. And not everyone will be able to afford travelling to all meetings. Those aren't new problems, but the situation is growing more acute. So the IETF is impacted whether we like it or not. And some of these remote attendants might decide to meet up in a city, so they can recreate the hallway track. That's going to happen no matter what we (the IETF) decide. Given that, I think the remote rooms will make the IETF more productive compared to the alternative of having a bunch of people all dialed in from their own laptop.
# Question 3: Should anything change in the way Remote Hubs/Remote Rooms work?If I could have a poney, I would ask for the ability to have a second video feed in the remote room so we can point one at the chair table and one at the room/mic. But honestly, it's working great even without that. Meetecho did a great job. Regarding the other aspects, those will depend on the organization hosting/funding the remote hub. Every venue will have its own idiosyncrasies, but we're innovators - we can handle change.
# Question 4: Should the IETF LLC support either of the alternatives discussed above and under what conditions? & Question 4a: If so, then is that in addition to or in place of the Remote Rooms/Remote Hubs described above?The alternative of one large screen plus everyone logged into their laptop isn't something the IETF needs to allow or disallow - participants might decide to do that on their own without asking for permission. But it would definitely be less productive, and would make the experience less pleasant for people both in the hub and the main location. I would not recommend that. LLC exists to support the operation of the IETF, and remote rooms/hubs make the IETF more productive. If we're very concerned about the added costs to the LLC of the remote rooms feature, I'm sure we can figure out creative solutions such as finding sponsors for the remote hubs.I don't think the IETF should host multiple official remote venues with no limit on attendance - the cost would be prohibitive, and the steady state would be to have everyone attend their closest official location. The space-limited remote hubs prevent that from happening, even if it inevitably leads to some people being left out.All in all, thank you for the remote room feature. I really wish we didn't need it, but we do.Cheers,David
--This is a request for community feedback following the Remote Rooms experiment which took place during IETF 125 in Shenzhen, China in March 2026.
The specification for Remote Rooms was developed with input gathered through community consultation and following an open call for interest, a single Remote Hub was supported that operated in Tokyo, Japan with three simultaneous Remote Rooms hosting approximately 30 participants.
While engagement and satisfaction among participants who used the Remote Rooms was high, the experiment highlighted technical challenges and significant resource requirements for both organizers and IETF staff that require consideration for possible future editions. It also raised concerns about effects on the IETF meeting experience.
Please read the full consultation document here:
https://www.ietf.org/media/documents/Second_Consultation_on_Remote_Rooms_for_IETF_Meetings.pdf" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/media/documents/Second_Consultation_on_Remote_Rooms_for_IETF_Meetings.pdf
Please respond by 27 September 2026 either privately to the IETF LLC Board and the Executive Director at llc-feedback@ietf.org or to the public administrative discussion list admin-discuss@ietf.org.
--
Jay Daley
exec-director@ietf.org
http://www.ietf.org" rel="noreferrer nofollow" target="_blank">www.ietf.org
_______________________________________________
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-leave@ietf.org
admin-discuss mailing list -- admin-discuss@ietf.org
To unsubscribe send an email to admin-discuss-leave@ietf.org
CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.> --
admin-discuss mailing list -- admin-discuss@ietf.org
To unsubscribe send an email to admin-discuss-leave@ietf.org
admin-discuss mailing list -- admin-discuss@ietf.org
To unsubscribe send an email to admin-discuss-leave@ietf.org
- [admin-discuss] Re: Second consultation on Remote… Martine S. Lenders
- [admin-discuss] Re: Second consultation on Remote… Jay Daley
- [admin-discuss] Re: Second consultation on Remote… Martine Sophie Lenders
- [admin-discuss] Re: Second consultation on Remote… David Schinazi
- [admin-discuss] Re: Second consultation on Remote… Brian Campbell
- [admin-discuss] Re: Second consultation on Remote… Colin Perkins
- [admin-discuss] Re: Second consultation on Remote… Mirja Kuehlewind
- [admin-discuss] Re: Second consultation on Remote… Eric Vyncke (evyncke)
- [admin-discuss] Re: Second consultation on Remote… Michael Richardson
- [admin-discuss] Re: Second consultation on Remote… Jay Daley
- [admin-discuss] Re: Second consultation on Remote… Michael Richardson