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

Ben Campbell <ben@nostrum.com> Tue, 08 October 2019 22:20 UTC

Return-Path: <ben@nostrum.com>
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 D0830120813; Tue, 8 Oct 2019 15:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level:
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.4, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 x2Rf6g-aM5gM; Tue, 8 Oct 2019 15:19:59 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 773311201E5; Tue, 8 Oct 2019 15:19:59 -0700 (PDT)
Received: from bens-macbook.lan (cpe-66-25-20-105.tx.res.rr.com [66.25.20.105]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x98MJtBJ012661 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 8 Oct 2019 17:19:56 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1570573197; bh=L9nBN9MeKBJKE+6W0A1gJIA2sY3qzqG77UpBSBPzIbg=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=M0fRUJeteZS6reuo+fMVKEiar2kcOUF0YvYbiDlZExJjZ57UrqibL+nvBNghRonpQ FFWWUTAWN77DNed/I63T01mbyzUJVrFg5rlCcSiANb1fujYwRWPW7TWA9tzl3hqNJE zzq+nQL5UsjGW8j9reIPaMckozwJTthQQ64CUKOc=
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-20-105.tx.res.rr.com [66.25.20.105] claimed to be bens-macbook.lan
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <6F6819D9-E681-4247-8C19-F87709ADB1CA@mnot.net>
Date: Tue, 08 Oct 2019 17:19:50 -0500
Cc: Barry Leiba <barryleiba@computer.org>, gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DE4AAEA-13A0-4D49-AE3E-8ACCD81BF49E@nostrum.com>
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>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/cdxMUODA_mgAO2hZPA2MjjJiQYM>
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: Tue, 08 Oct 2019 22:20:06 -0000

> On Oct 8, 2019, at 5:06 PM, Mark Nottingham <mnot@mnot.net> wrote:
> 
> Anecdata - 
> 
> I made a proposal at the plenary mic in Montreal for a separate last-call@ list. I'd made that proposal at least twice before to iesg@ in the past, but it never got traction, until it was suggested I bring it up at the mic. Once it got some support in the room, the IESG went away and came up with a fully-baked proposal for an experiment in the community.
> 
> Under GENDISPATCH, I would have taken the proposal there (I didn't take it to ietf@ because it was too focused on other issues, and I didn't see it as likely to gain traction there). It would have been discussed and presumably we would have developed a proposal in the open, guided by the chair(s).

I don’t disagree with any of your points. But keep in mind that, according the proposed charter, GENDISPATCH would develop a problem statement, context, and assess the level of interest, then pass the work on somewhere else for the developing a solution part. For some things that can help focus thinking. For others it can become yet another process speed bump. For relatively self-contained proposals like the one you suggest, I suspect it may be more of the latter.

> 
> I think that's a better outcome; certainly, as someone who wants to suggest a change to the process, GENDISPATCH is more straightforward and requires less "inside" knowledge.

That’s a pretty good point—it’s possible that GENDISPATCH could become a well-known entry point, with less guessing about who one needs to talk to to promote an idea. DISPATCH has occasionally had complaints from people from areas that don’t use the dispatch process because it doesn’t match the processes they are familiar with. But that’s probably easier for something with more cross-area appeal.

> 
> I do think there are going to be some cases where process changes are only going to get rough consensus, and the chair(s) of GENDISPATCH need to be able to make that consensus stick -- but that's just as it is in every other working group. I suspect that developing the proposals and making those calls in a public process rather than (what some perceive to be) as proclamations from on high is a better way to promote what resembles harmony in our community.

No disagreement there.

Thanks!

Ben.