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

Sean Turner <sean@sn3rd.com> Tue, 01 October 2019 17:47 UTC

Return-Path: <sean@sn3rd.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 1D937120058 for <gendispatch@ietfa.amsl.com>; Tue, 1 Oct 2019 10:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 rKKSp2KPQisF for <gendispatch@ietfa.amsl.com>; Tue, 1 Oct 2019 10:47:30 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 494751200BA for <gendispatch@ietf.org>; Tue, 1 Oct 2019 10:47:30 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id c3so22669988qtv.10 for <gendispatch@ietf.org>; Tue, 01 Oct 2019 10:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1+aIiIEmsJn5GUtdvQ/HDB7bMIIUMUPEB612qcm6Y1c=; b=HIP4PzX7n1FJPZh0R+vwnpJFrqab8FvZaEhO9JTQpeglXkWWnlrTnXdTPhd05sD+v/ 2+9BFDhs2axf8zehUmBlYzC6O7Yy1uHibQ8B3cqkWpxift8YBw2E0GPuvG2q3Ht594Yq Z+czAYxZPfDi38Ez0ihE9OJFU6jOdQ1mIemL8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1+aIiIEmsJn5GUtdvQ/HDB7bMIIUMUPEB612qcm6Y1c=; b=F5tWFwZ8Jx4kXPGIg6r2DXdIUvJS6QATWemIr73P2mkwPVUU4PNFaie163jS9eDt0r Wgpu0wzpTKuAZ80GmzTxxh+In1rlVfg1ViN/mwSCkM9epxTis481NGy2nMu5ji0Spv/S 9W7Q+2vvC6vGBUISEbBVtSfUvMf9N996mJm0wmZqo97WOIOr4/p1Lm95YeOvPab1uH97 BubjZGHEp/L9kVmH2RdQJez6djrBD69Qk6fxKFG4ot/1bTjTQio8+829r2ZZ9uf3kKQg loAriwTZLo8GSQhDbj1oy9/ZC2PaQFiCVzTptetkkZaEq3eWIsTtS6DPw9n5cuREmgTt mHpQ==
X-Gm-Message-State: APjAAAWhO9kcBYNHEp4hCe7rnDyU1dETuwzcH78skv0tLSfI0rAzQYDe UY1sJAtZ2RJRR7if5TuOxgBzhw==
X-Google-Smtp-Source: APXvYqxsmXHY61dTp+pkbN7RtGw2/pg7EdAmdKmqWtoTz0rwYz2lBzv16gahfVUe2bu96XoHFo+89g==
X-Received: by 2002:ac8:27d9:: with SMTP id x25mr8317511qtx.321.1569952049345; Tue, 01 Oct 2019 10:47:29 -0700 (PDT)
Received: from [5.5.33.147] ([204.194.23.17]) by smtp.gmail.com with ESMTPSA id 187sm7693014qki.80.2019.10.01.10.47.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2019 10:47:28 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <1ED85E0F-0CB2-450F-8D55-AA6D2027D72E@sn3rd.com>
Date: Tue, 01 Oct 2019 18:47:26 +0100
Cc: gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D7F3F61-9789-41B5-B41D-65BD31353EB2@sn3rd.com>
References: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com> <1ED85E0F-0CB2-450F-8D55-AA6D2027D72E@sn3rd.com>
To: Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/BiQS_FvWNFw8TFDjMqpDlL8jcrg>
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, 01 Oct 2019 17:47:32 -0000

apologies for the double send.

> On Oct 1, 2019, at 16:30, Sean Turner <sean@sn3rd.com> wrote:
> 
> I am in favor of this proposal.  One question below:
> 
>> On Sep 26, 2019, at 23:44, The IESG <iesg-secretary@ietf.org> wrote:
>> 
>> f the group decides that a particular topic needs to be addressed by a new
>> WG, the normal IETF chartering process will be followed, including, for
>> instance, IETF-wide review of the proposed charter. Proposals for large work
>> efforts SHOULD lead to a BOF where the topic can be discussed in front of the
>> entire IETF community. Documents progressed as AD-sponsored would typically
>> include those that are extremely simple or make minor updates to existing
>> process documents.
> 
> Is the AD in this case always the IETF Chair?  I am somewhat concerned about increasing the workload of the IETF Chair when the I-D might doing something so minor (and possibly noncontroversial) that any AD could sponsor the I-D.
> 
> 
> spt