[admin-discuss] Re: Second consultation on Remote Rooms for IETF Meetings

David Schinazi <dschinazi.ietf@gmail.com> Thu, 27 August 2026 23:44 UTC

Return-Path: <dschinazi.ietf@gmail.com>
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 C65A4130AA392 for <admin-discuss@mail2.ietf.org>; Thu, 27 Aug 2026 16:44:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787874265; bh=mPeCxk2aC/IOZsTvkabzNMzEtgyLIFg/mV0Vgp0W5so=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=iHS/e54KHrb2x+JdEDaA7nXGAFvJ5hVNZgz6prgJrBStuB/46VHFDRj61NQ9bN4Fv YrhmNrShVvbExGpFZTkfQ3ZS3bpCHY5ZTfPSp+Svc7HmqiS+oLufEseHpD4NbgC+s2 yvYaCAEDuxLibr5olw5nhyiTi6w4qlwKm7otc7lc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 za_ezsqn_0-l for <admin-discuss@mail2.ietf.org>; Thu, 27 Aug 2026 16:44:24 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id DFD7A130AA38B for <admin-discuss@ietf.org>; Thu, 27 Aug 2026 16:44:24 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id 5614622812f47-4b2ff8ca537so213028b6e.3 for <admin-discuss@ietf.org>; Thu, 27 Aug 2026 16:44:24 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1787874264; cv=none; d=google.com; s=arc-20260327; b=SaZVZmWv+AdxB5nBDKBeHXeAvQmOTkq4Dn22cvJjvdC2N0BwNEYvxwnQUqh/sWnTCG N6siVyi2eQqshCRiHrZzWrsUsSLjCxE2hYEmyuYiKK6hS7RGeZBUbAOZiwqHRgxh+3NJ imXo+IrTATg4yUIpUq3kr79m97MPSkgZVjREmV/w2ZlqzS91kxpJUB5I5J3VnFRGUf4U U3uyMfIFkM5Av2DtTA21ThEjX6ZzxtJ+gTaktFcbZchAbNP7kktQzkb0xjjktniFGbdI Ov9AyVmrcJm47Z+fmNkF52rd08Fw8qpvXr8ajMI6cYdU5zZeUi8igcQDJaxw33h0FoHD v/CA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=mPeCxk2aC/IOZsTvkabzNMzEtgyLIFg/mV0Vgp0W5so=; fh=IXvTCrrVCgglzU7Bsgz4u6msiaveM/F0VBMwoY2NquA=; b=LczCdEeN6mhCJhCGNoKyqO5bMDbUfFe+7j370gtzGQON20H9denwGB0orM/BYrg84C 818pVPUoINR6X3Ef9iSUEQByLfz+BTfZ61kie6uvkZSPp39eR6WzIQi/d3trwiDCm2JV GKzKfmB+KoPUh4llU+U9J0kox57R5Y7Jf/kETosL5KsEKv3oPxrrTXA/mFY31f427+q5 ft+aSexlQTzkOMaMhvW0sY7dEjnZgoEV2EX95GsRLHv/c+9rhj7V6T998vwJ4C+jVwdi 8qk7dne17f4RR5t3bPi7ZNtviyk78rLL7gy+8x7JBnzCCNE2Z+6FepTt2/lgCWoAaXd3 FYAg==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1787874264; x=1788479064; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=mPeCxk2aC/IOZsTvkabzNMzEtgyLIFg/mV0Vgp0W5so=; b=ah9IfkgVQw1iZ7u9TvIgoC0E9tdW4JYAgOI8vmhHaTLlRNbrcgtvcSpewEi4hd8naX MdISgnY1DMAPLNtzzETTggLr2151KZJrTe1LojPhZeRX5uUFJmgEQ1g/6ZsBpeVPluEO 1vsvu4eqJdRKwamJmPav0u75Fqx5esgFXrvGhqD5aLIJ7xMQXivwmWhVivzgxqfZ1EXE RSNUYuXCI1FakrxKuLX81W7Io69CVL58SI6jOHCJXZZc+6mBnYDhgi2kQ5bjHUl/tspI 6rr+TXaVtUud8JQuEoyY2YzcHsE4LfOk9F5KSOEWN/qn9g447jmV1HHDjm7xAam4zd3r oL0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787874264; x=1788479064; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=mPeCxk2aC/IOZsTvkabzNMzEtgyLIFg/mV0Vgp0W5so=; b=n+eTN9COdIXRxtcwB5h/v/KY0D480VBGAIDUp2+XN2e9iHC7grZ8w5lTKDyZICc8it 9H/zDyN73FyuCf5lqFVa/zsizbJIKkLWWQ6l9SuyCjcrBnZ0W/FnFzy+l1PO0wrkBX+g 2WUxBoQ+5bfYfRjungJj9oUTMe2KC2Cr4MDO60F/tXbXDbSdtumJsn9N3IEBqJX94zUs SGURqG+yDqAhXtgHs65cHPeJo/DG2SepdPOOny/z4LEdfCT/BLjkqnAqz9wz1OCTYG1I TMRWNbVKpfHOcZtuOnjIZnTFoSrxelIQeNBJ93aihPPcwOLOzGMhRP8eSjRQC+ZPpUwm vZxw==
X-Gm-Message-State: AFuF++nM9RjRy31BLvSq9vfLCMWmZ5yUesRLD4y1s9WBynIK97JxWUp/ SaSUufa5OosVMe2TdNptcRsBjVCS+1ZTGaWaPLqYhd7laHlP/UOGGlE6SwD/Dgkdki7OvGkoVD1 CZ9AO53b33n/pzfQfN5wuynoP02Bw6NNQSBcAn3w=
X-Gm-Gg: AR+sD10LQzDVzcg4bhjz83fT6YxzFxtmHVOqq2hNr769JHIss72SJScNHrmbwR3+qgW 2K0A/9IidQU5e5uf1qSI47DoJaJbuWgeATQWjUWuJYUO+bRaougNe/8z7g9Ndc7G3pTMT1bF8oT TTQrBHN/3tFQE1WfOHx4y3GdBhUAwniZH4g6a6LeevGvdd3JaeZpE/p5UpHJWBzuJEVK0UHQD98 m+RogP4xnQk6hgF0daKhD+6TsGqC2Ml2+dZCDjuRhvqN/aQlEyoHIhgiBMy2XuwXx5x5BTLBZMP 3svvzQMR0d92lKbdHU+EEPb9uWA2lNQ0fW7XSRSIJ+CvIzs=
X-Received: by 2002:a05:6808:538e:b0:4b2:e9d9:f13f with SMTP id 5614622812f47-4b3982ee646mr3543873b6e.17.1787874263996; Thu, 27 Aug 2026 16:44:23 -0700 (PDT)
MIME-Version: 1.0
References: <7CB35E99-5418-4296-AD1A-079946178AB6@ietf.org>
In-Reply-To: <7CB35E99-5418-4296-AD1A-079946178AB6@ietf.org>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 27 Aug 2026 16:44:11 -0700
X-Gm-Features: AcwNN1VUNaFyZdYiqqnwAVgjDlfXVAFSxihTSYX7vDVsEsH6ausyHUT_8o6Jj1U
Message-ID: <CAPDSy+5-SuaYbKprp=cGFfxYr8Si0ERuWqK7FKgbMhq-xBrWsQ@mail.gmail.com>
To: admin-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000689d54065a0fea2c"
Message-ID-Hash: MHRC2JG57ZXZPVOE76MB23JTFYYCTT25
X-Message-ID-Hash: MHRC2JG57ZXZPVOE76MB23JTFYYCTT25
X-MailFrom: dschinazi.ietf@gmail.com
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: IETF Executive Director <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/TPwXbFADHNixuZE0uEBmnvg8LIU>
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>

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

On Wed, Aug 26, 2026 at 6:08 PM IETF Executive Director <
exec-director@ietf.org> wrote:

> 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
>
> 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
> www.ietf.org
>
>
>
> _______________________________________________
> IETF-Announce mailing list -- ietf-announce@ietf.org
> To unsubscribe send an email to ietf-announce-leave@ietf.org
>