Re: [Mtgvenue] Update of RFC8719 not needed
John C Klensin <john-ietf@jck.com> Fri, 29 December 2023 16:44 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBFAC14F71C; Fri, 29 Dec 2023 08:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HpgMYPiDYIbN; Fri, 29 Dec 2023 08:44:45 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98AFAC14CF18; Fri, 29 Dec 2023 08:44:39 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1rJFyP-0004qn-MV; Fri, 29 Dec 2023 11:44:37 -0500
Date: Fri, 29 Dec 2023 11:44:32 -0500
From: John C Klensin <john-ietf@jck.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, John Levine <johnl@taugh.com>, mtgvenue@ietf.org
cc: benson_muite@emailplus.org
Message-ID: <C00426A3234571904A04FE07@PSB>
In-Reply-To: <1072653199.139533.1703855297096@appsuite-gw1.open-xchange.com>
References: <937cb1c0-b718-7d78-c27f-7ecdffc81380@emailplus.org> <20231228172411.910427F55FB9@ary.qy> <1072653199.139533.1703855297096@appsuite-gw1.open-xchange.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/pWujAtuOC6_dD1FBb4S85VNq8RM>
Subject: Re: [Mtgvenue] Update of RFC8719 not needed
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for email discussion of the IETF meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Dec 2023 16:44:49 -0000
--On Friday, December 29, 2023 14:08 +0100 Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote: >> Il 28/12/2023 18:24 CET John Levine <johnl@taugh.com> ha >> scritto: >> >> I don't see the point, other to reinforce the reality that the >> sensible places to meet are in the northern hemisphere. We >> already know that people in South America can remotely attend >> meetings in North America at hours when they would normally >> be awake, people in Africa and the Middle East can remotely >> attend Europe and people in Oceania can remotely attend >> Japan, Taiwan, or Korea. > > I don't have a strong opinion yet, but... It doesn't make much > sense to say that we need to meet in person to be effective, > but also that not meeting in certain parts of the world is not > a problem for participants who live there because they can > attend remotely. Pick one. One can turn that around a bit in a way that is more consistent but, perhaps, even more complicated and difficult.... First, even though I have been able to attend very few in-person meetings in the last few years (I think none since the onset of COVID, but only a small fraction of them before that), I still recognize the value and increased effectiveness of those meetings. And, while I think our mechanisms and tools for remote participation are much better than they were a decade ago, they still are not nearly good enough to be a complete substitute for face to face meetings and discussions. What makes that even more complicated is that we seem to have shifted away from a reliance on email for discussing and working out issues -- traditionally a technology that is fully asynchronous, insensitive to location and time zones, and that even enables those who are not completely comfortable in English to translate and refine text at their leisure -- to more real time interactions that, at least from my perspective, often combines the worst characteristics of in-person meetings with the worst one of email. In the process, we have turned many of our email interactions into fast-reaction messages of no more than a few sentences and "if anyone has objections, speak up" ratification of discussions and decisions made elsewhere and in real-time. The combination of all of that suggests some very complex tradeoffs that, at least IMO, we are not getting right. Rather than addressing them as part of a system and trying to find the right balance, we often seem to focus on one corner of the system, ignore everything else, and act surprised when it does not solve the whole problem. >> Since IETF meetings are working sessions, if someone is not >> already reading and writing I-Ds and following the mailing >> lists, a physical meeting is a waste of time. I entirely >> agree that it would be good to have more IETFers from places >> beyond where we come from now, but first we get people >> active, then we might consider adjusting the meeting >> schedules to match the places where active workers are. > This is going to be a philosophical (political?) debate > between those who think that representation should match > current reality and those who think that it should match a > desired reality which can only come true if under-represented > groups get disproportionately higher representation right now. > I suspect that there will never be consensus on this point - > not in this organization. I agree about the lack of consensus but, again, see other dimensions of the problem. While details of their characteristics differ with, e.g., geography, the two most underrepresented groups we have are (i) people whose experience with the Internet is solely through phones or maybe small tablets and perhaps with IoT devices that they don't really see as part of the Internet, but who have little or no experience with full-featured devices with keyboards, etc., and the ability to run applications other than web browser and (ii) people with no real interest in the technology other than it does what they want it to do. Those groups overlap somewhat but not completely. On the one hand, the IETF suffers badly from the absence of those perspectives. On the other, getting people from either or both groups to contribute usefully involves issues that our "newcomer" and "outreach" efforts don't even begin to address in useful ways. best, john
- [Mtgvenue] Update of RFC8719 Benson Muite
- Re: [Mtgvenue] Update of RFC8719 urgently needed Benson Muite
- Re: [Mtgvenue] Update of RFC8719 not needed John Levine
- Re: [Mtgvenue] Update of RFC8719 still not needed John R Levine
- Re: [Mtgvenue] Update of RFC8719 Brian E Carpenter
- Re: [Mtgvenue] Update of RFC8719 required to conf… Benson Muite
- Re: [Mtgvenue] Update of RFC8719 not needed Vittorio Bertola
- Re: [Mtgvenue] Do you believe in magic, Update of… John R Levine
- Re: [Mtgvenue] Update of RFC8719 not needed John C Klensin
- Re: [Mtgvenue] Update of RFC8719 Benson Muite
- Re: [Mtgvenue] Update of RFC8719 Michael Richardson
- Re: [Mtgvenue] Update of RFC8719 Christian Huitema
- Re: [Mtgvenue] Update of RFC8719 Benson Muite
- Re: [Mtgvenue] Update of RFC8719 Benson Muite
- Re: [Mtgvenue] Update of RFC8719 Benson Muite