Re: [Gendispatch] WG Review: General Area Dispatch (gendispatch)

Jari Arkko <jari.arkko@piuha.net> Sat, 12 October 2019 01:12 UTC

Return-Path: <jari.arkko@piuha.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 1F0C1120059; Fri, 11 Oct 2019 18:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 40_AYKr3uFg0; Fri, 11 Oct 2019 18:12:18 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 243111200B6; Fri, 11 Oct 2019 18:12:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6A0CD6601D7; Sat, 12 Oct 2019 04:12:15 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjZLZBuuzxkQ; Sat, 12 Oct 2019 04:12:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 7C83E66013D; Sat, 12 Oct 2019 04:12:12 +0300 (EEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <bafee1cd-d238-73b3-fd35-993dd44041a2@gmail.com>
Date: Sat, 12 Oct 2019 04:12:11 +0300
Cc: gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>, IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6B44037-8804-4B8A-9058-53E614AB144E@piuha.net>
References: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com> <8A15D8AF-6B1A-42A0-85CE-DF861E73C1C2@nostrum.com> <CALaySJL0-=Jn0Wk8GR+xrGcZ6Vyv4QO+p=LgkKt5srdVu+Zh_g@mail.gmail.com> <6CC7893B-7A6C-4A6A-9AB4-9C62A4E1777A@nostrum.com> <6F6819D9-E681-4247-8C19-F87709ADB1CA@mnot.net> <2DE4AAEA-13A0-4D49-AE3E-8ACCD81BF49E@nostrum.com> <2E4933D9-ECD0-436A-9ADA-5EF6C6470C01@nostrum.com> <bafee1cd-d238-73b3-fd35-993dd44041a2@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/dZyW_gnvdhoh7r5xQCRUxMC600k>
Subject: Re: [Gendispatch] WG Review: General Area Dispatch (gendispatch)
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: Sat, 12 Oct 2019 01:12:21 -0000

Brian, Alissa,

> I think that we have never really had a problem handling minor process fixes. That's why we have so many process-related RFCs, in fact. For those, GENDISPATCH will clearly help us do the triage a bit more systematically, and that is a Good Thing. 

For what it is worth, I’m in favour of setting up this new group. I agree with Brian’s assessment above; when it comes to non-technical work, we’ve certainly been able to do many small changes.  Actually, unlike Brian I think we’ve also been able to do some bigger things as well (IASA 2.0 comes to mind as a recent example) but maybe some of those are more under the topic of administration rather than process work.

Anyway, I think what this new working group will bring is a bit more structure and additional people and more eyes on topics that have traditionally too reliant on GEN AD sponsorship and IESG discussions. That’s great, and an improvement (even if we previously were able to produce process RFCs as well).

This new working group does not remove all problems from this space, of course, and one of the continuing challenges is to get the people who do normal IETF work to know and care about process issues. Bringing things up on plenaries etc will be useful, as well as on ietf@ietf (but clearly, the set of people on that != the set of people doing IETF work).

Also, +1 to what Mirja wrote.

Jari