Re: WG Review: General Area Dispatch (gendispatch)
Keith Moore <moore@network-heretics.com> Tue, 08 October 2019 20:16 UTC
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E9E120041 for <ietf@ietfa.amsl.com>; Tue, 8 Oct 2019 13:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 hU8sUPo3YZIM for <ietf@ietfa.amsl.com>; Tue, 8 Oct 2019 13:15:58 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 935311200A3 for <ietf@ietf.org>; Tue, 8 Oct 2019 13:15:49 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C3D5F21F48; Tue, 8 Oct 2019 16:15:48 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 08 Oct 2019 16:15:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ogjMFl KeACEPbTqzKpYnMxkFyu1FQo26Yrk7tWeq/6U=; b=dPOvgMzFCMCWvrjaMuqg/x SqR4JFtnrwChbHGLOio/1Eo8/t0sPnQRX9RA9WqyqQBM+aCle1CKXUVvElRnJYuT cUeyrvPG4zANC63K15mngTAinKWZPCU07D9zJ7CjJ+JG04wSkRKLu3VTT7bbceIM LkiM2EDxuuAo//FdgHF/gWiI0UclDosqdIy3F3seBX8AMq0aqbSZ8U+bc/tZCtgB e6pKU73R11peQa6/9PFvVlwm14i87YvkAYBUOcdQvnmrnaSYRpVkoxYFRjf3NXdY erHcdYL9vAWyr+w2PNC1r71iRCLumk+NnXU/kGXW7/3cb+EMDSLCS8JMiQHpQ9eA ==
X-ME-Sender: <xms:c-6cXQDLEFyXTMiRRtu9jVVpDxZn2h7rN1j5GX-e88hXO3xr8I9Sxw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheelgddugeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgv thhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:c-6cXcpAWdAoGuJB08iaFya8fHMpg3O2OgVJQSZgm8buhQOG67qMqQ> <xmx:c-6cXYmbwN7cNlgkSJuAS201e7lHJNsCmvNDupGasUUXoa_4y0DaBQ> <xmx:c-6cXa5aUBuBpfKtfQKBFWtw0UMRiWFC3zCl1BTbyn3jKTXJJRDgpA> <xmx:dO6cXZSjXEHjOTYlgqoP0xf8MNKxab2JrpBJ3mkhMOsmf7bnh_wqDQ>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 817C1D60066; Tue, 8 Oct 2019 16:15:47 -0400 (EDT)
Subject: Re: WG Review: General Area Dispatch (gendispatch)
To: ietf@ietf.org
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>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <2e73785c-2405-bd5b-93ba-bac85af16e20@network-heretics.com>
Date: Tue, 08 Oct 2019 16:15:46 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CALaySJL0-=Jn0Wk8GR+xrGcZ6Vyv4QO+p=LgkKt5srdVu+Zh_g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------CFC2892C62DFA9733BA16611"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GunIHHut1_qsOKm8MKuObLmL6Qo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 20:16:00 -0000
On 10/8/19 3:18 PM, Barry Leiba wrote: >> At the risk of strawman-ing: If the problem is mainly that GEN issues >> tend to eat the IESG list, then a separate mailing list could be >> enough. Maybe the idea is mainly to have chairs responsible for >> discussion wrangling? If so, then a more conventional “GenArea” working >> group might do the trick. > I don't think it's that they "eat the IESG list" so much as that they > "eat the IETF list". And not in the sense that they monopolize the > list, but that that particular list isn't sufficiently focused to give > process issues proper consideration and determine what the right way > to handle them is. The flip side of this argument is that the IETF list might represent a broader spectrum of concerns, than a group that's specifically devoted to looking at process changes. If the gendispatch WG doesn't enjoy a broad spectrum of representation from the IETF community as a whole, it could easily go off the rails. And it also seems likely that such a group would be biased towards those who think that process changes are a Good Thing, and perhaps against those who think current processes are mostly ok. I certainly don't think that process changes should be hashed out in detail on the IETF list, but it might still be better for initial discussion of new ideas than a separate WG. I'm also one of those asking "what are the problems to be solved?" Because the proposed charter for this WG seemed to indicate some sense of urgency, so presumably there are some problems that the group's proponents have in mind. Keith
- Re: WG Review: General Area Dispatch (gendispatch) Alissa Cooper
- Re: WG Review: General Area Dispatch (gendispatch) Keith Moore
- Re: WG Review: General Area Dispatch (gendispatch) Eric Rescorla
- Re: WG Review: General Area Dispatch (gendispatch) Sean Turner
- Re: WG Review: General Area Dispatch (gendispatch) Alissa Cooper
- Re: WG Review: General Area Dispatch (gendispatch) Alissa Cooper
- RE: WG Review: General Area Dispatch (gendispatch) Roni Even (A)
- Re: WG Review: General Area Dispatch (gendispatch) John Levine
- Re: WG Review: General Area Dispatch (gendispatch) Alissa Cooper
- Re: WG Review: General Area Dispatch (gendispatch) Alissa Cooper
- RE: WG Review: General Area Dispatch (gendispatch) Roni Even (A)
- Re: WG Review: General Area Dispatch (gendispatch) Keith Moore
- Re: WG Review: General Area Dispatch (gendispatch) Ben Campbell
- Re: WG Review: General Area Dispatch (gendispatch) Barry Leiba
- Re: WG Review: General Area Dispatch (gendispatch) Ben Campbell
- Re: WG Review: General Area Dispatch (gendispatch) Keith Moore
- Re: WG Review: General Area Dispatch (gendispatch) Mark Nottingham
- Re: WG Review: General Area Dispatch (gendispatch) Ben Campbell
- Re: WG Review: General Area Dispatch (gendispatch) John C Klensin
- Re: WG Review: General Area Dispatch (gendispatch) Ben Campbell
- Re: WG Review: General Area Dispatch (gendispatch) Ben Campbell
- Re: WG Review: General Area Dispatch (gendispatch) Mirja Kuehlewind
- Re: [Gendispatch] WG Review: General Area Dispatc… Brian E Carpenter
- Re: [Gendispatch] WG Review: General Area Dispatc… Alissa Cooper
- Re: [Gendispatch] WG Review: General Area Dispatc… Alissa Cooper
- Re: WG Review: General Area Dispatch (gendispatch) John C Klensin
- Re: WG Review: General Area Dispatch (gendispatch) Keith Moore
- Re: [Gendispatch] WG Review: General Area Dispatc… Ben Campbell
- Re: [Gendispatch] WG Review: General Area Dispatc… Ben Campbell
- Re: [Gendispatch] WG Review: General Area Dispatc… Jari Arkko
- Re: WG Review: General Area Dispatch (gendispatch) Patrick McManus
- Re: [Gendispatch] WG Review: General Area Dispatc… Michael Richardson
- Re: [Gendispatch] WG Review: General Area Dispatc… Alissa Cooper
- Re: [Gendispatch] WG Review: General Area Dispatc… Spencer Dawkins at IETF
- Re: WG Review: General Area Dispatch (gendispatch) S Moonesamy
- Re: WG Review: General Area Dispatch (gendispatch) Benjamin Kaduk
- Re: WG Review: General Area Dispatch (gendispatch) S Moonesamy