Re: [Gendispatch] I-D Action: draft-nottingham-discussion-recharter-00.txt
Pete Resnick <resnick@episteme.net> Thu, 20 August 2020 16:19 UTC
Return-Path: <resnick@episteme.net>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF2A3A0933 for <gendispatch@ietfa.amsl.com>; Thu, 20 Aug 2020 09:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A25o1dU5-8AO for <gendispatch@ietfa.amsl.com>; Thu, 20 Aug 2020 09:19:02 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98B7E3A0964 for <gendispatch@ietf.org>; Thu, 20 Aug 2020 09:19:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 05688B95E325; Thu, 20 Aug 2020 11:18:56 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cD38gG_AIqb4; Thu, 20 Aug 2020 11:18:46 -0500 (CDT)
Received: from [172.16.1.10] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 918F5B95E308; Thu, 20 Aug 2020 11:18:46 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: Christian Huitema <huitema@huitema.net>, gendispatch@ietf.org
Date: Thu, 20 Aug 2020 11:18:27 -0500
X-Mailer: MailMate (1.13.1r5706)
Message-ID: <B27F01EA-0BC4-46AB-A118-78ACC2B33C82@episteme.net>
In-Reply-To: <7B731DC9-5CB6-4D5B-A382-1E3179D39A9F@mnot.net>
References: <159762600034.21012.3531565855695172680@ietfa.amsl.com> <cbcda2fa-5ef2-93a7-6ae6-a78603ad97b8@gmail.com> <48D4FA55-C03F-47D8-B91C-4D14A99829B7@mnot.net> <CAChr6Sx34auWJ3T2T6GueVGqJ6ZzSMOMsWiAVD2Gy9m42RaJyQ@mail.gmail.com> <0BD00993-D007-48E3-ABAE-157CCF0CE2C3@akamai.com> <20200818164957.GA86346@straasha.imrryr.org> <090f2c01-6494-7be3-4b99-280576733f35@huitema.net> <7B731DC9-5CB6-4D5B-A382-1E3179D39A9F@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/0AambvGfuAzxcgPySWZJPHsfRuU>
Subject: Re: [Gendispatch] I-D Action: draft-nottingham-discussion-recharter-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2020 16:19:04 -0000
It sounds to me like Christian is saying, "The lack of rules of order for the IETF list is a problem", and it sounds like that is a statement with which Mark would probably agree. I'm also guessing that the two of you would also agree that the "SAA SoP" is not a workable set of rules of order. So it sounds like the counter-proposal to Mark's would have to say what kinds of rules of order might work. That might be good to explore. I'm definitely hearing a contingent saying that they don't want Mark's proposal moving forward, but if I think about DISPATCHing it, I'd like to hear if work on some form of change to the structure of or operational rules of the IETF list would be acceptable to that contingent. Is there something here people think would be useful, and if so, in what forum should it be worked on? Cheers, pr -- Pete Resnick https://www.episteme.net/ All connections to the world are tenuous at best On 19 Aug 2020, at 0:35, Mark Nottingham wrote: > Hi Christian, > > I'm not going to respond to every message on this thread, as I want to > hear what others think. > > I think we agree that the question at hand is reconciling the nature > of the discussion with the need for it. My draft is one proposal; > there maybe others, and I'm happy to discuss changing mine. I wrote > this one down because it's pretty clear (at least to me) that imposing > rules of order on this list isn't possible, because many people are > unwilling to change how they use or think about it. If I'm wrong about > that, that's great. > > Regarding 'Mark's proposal also does away with any notion of an online > general assembly' -- My expectation is that even if the IESG and > other leadership would be told that they don't have to listen to > ietf@, they still would -- provided that the list didn't become mired > in endless acrimonious cycles, as it has of late. De-emphasing the > list also restores some balance between those that use it to amplify > their voices and those who are turned away from such activity. > > Perhaps that goes too far, and there does need to be an expectation > that leadership will be on the list. If that's the case, it's > important to recognise that this becomes a selector for leadership -- > if you can't 'take it' on the ietf@ list, you're not fit for > leadership. That will in turn reduce the diversity of work and > participants in the IETF over time. > > Cheers, > > >> On 19 Aug 2020, at 3:32 am, Christian Huitema <huitema@huitema.net> >> wrote: >> >> I am not entirely convinced by Mark's draft either. My personal >> assessment is that we have many problems: >> >> * The IETF list acts as the offline general assembly, but without any >> rules of order. We would not run a meeting of 1000 people without any >> such rules, and for example we use mike queues and time limits during >> the plenary. The lack of order leads to poor behavior and reduced >> utility. >> >> * The IETF list also acts as the IETF lobby, a place that newcomers >> might join in order to sense the pulse of the organization. But we >> are conducting a permanent and sometimes very loud general assembly >> in the lobby, and that scares visitors away. >> >> * To expand on the previous point, the tolerance for loud discussions >> naturally selects for loud spoken and loudness tolerant individuals, >> typically oldtimers. It turns away other types of participants, >> contributing to lack of renewal and lack of diversity in the >> organization. >> >> * As Mark points out, the list membership is a fraction of the IETF >> participants, which makes it a rather unrepresentative general >> assembly. But that may well be a consequence of the other issues. >> >> Mark's proposal addresses the "rules of order" issue by directing >> discussions to the gendispatch WG, and then possibly to specialized >> WG. The advantage is that WG chairs can and do impose discussion >> rules. We have examples that it works, e.g., moving the RFC-ED >> discussion from the IETF list to a specialized group. But Mark's >> proposal also does away with any notion of an online general assembly >> -- the IETF list is left to its own devices, some kind of playground >> for people who like loud debates, and the IESG is told that it just >> does not have to listen. That seems sub-optimal, because feedback is >> indeed useful. >> >> If I am right -- :-) -- the main missing component is some kind of >> "rules of order" for the IETF list, similar to the mike lines and >> time limits that we have in working groups or in the physical >> plenary. This requires some authority to enforce the rules, an >> authority that should be separate from the IAB/IESG leadership if we >> want an avenue of feedback for that leadership. >> >> We may also consider not washing our dirty laundry in the front >> lobby, i.e., separating the "social discussion" and "plenary" >> functions. >> > > -- > Mark Nottingham https://www.mnot.net/
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mirja Kuehlewind
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Salz, Rich
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Bron Gondwana
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Salz, Rich
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Kyle Rose
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Colin Perkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Viktor Dukhovni
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Nico Williams
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mirja Kuehlewind
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Dan Harkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Christian Huitema
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Salz, Rich
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mary Barnes
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Colin Perkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Dan Harkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Keith Moore
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Keith Moore
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Keith Moore
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Dan Harkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Dan Harkins
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Kyle Rose
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Pete Resnick
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Salz, Rich
- [Gendispatch] Proposed list reorganization (was: … Keith Moore
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-nottingham-di… Keith Moore