IETF Logo Mail Archive

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

Sean Turner <sean@sn3rd.com> Tue, 01 October 2019 15:31 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 D06F5120886 for <gendispatch@ietfa.amsl.com>; Tue, 1 Oct 2019 08:31:05 -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 gJibqCK9Hd2Z for <gendispatch@ietfa.amsl.com>; Tue, 1 Oct 2019 08:31:03 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 AED6E120860 for <gendispatch@ietf.org>; Tue, 1 Oct 2019 08:30:59 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id r5so22166911qtd.0 for <gendispatch@ietf.org>; Tue, 01 Oct 2019 08:30:59 -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=nL1dEsOTOuoD4dH50yA6u5AxjyHJtGM8wZ1aDBC5Wtc=; b=KOCca439NTvZKEZqtmDUJolz5TNkgySKLRekcaYS0lo4uO7+uk4JjvLXFwLsF6e1uN PIA6lmWRpLI47lV0YSGGUILZBvmL6GdTJK8ePM7KHuP7z9qSVu1Za8GUOznY6B1UXahM /FF/MRbsZsR7YF2K0i0Vd+CtIiT3Ls6+GXO1U=
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=nL1dEsOTOuoD4dH50yA6u5AxjyHJtGM8wZ1aDBC5Wtc=; b=WfXqUH/O4xWEzEkZmLMvcqY8QqcWtC7LIv4C4fB5mIWe+p66vssHdcHllW1eOr1+TV PnPlru48srYM4kvzenroIFeAlEqOgQY/rDdAyNWZwgR+eobjaQF94MeYWBpX+se4qMOH 31kHjnUo9vdkP43HOjML6v4LUk3IM9ylJrqDR2Zi1NOGwyTACDiYHpnMffZeKljD9uD/ 93a+CvPSnKlrw9f5VwYTHOyi3BEwiAPtD/Bf32VF33sKM7zRNnB7k0MvFl4zaoSue8p4 dnvm3WloPkSJGO+GMM80jCVnjSJtdu+CvDaZWDjrOEvehwGa9SLjhgNGEJd8Mf+08GLi DY1A==
X-Gm-Message-State: APjAAAW5pPg53wH5iryKe8411cYlxWahggEAFWuu0z9t773ysUqjGGAf BhRvJ08cUFoXNNY3Q+FZSzhUZw==
X-Google-Smtp-Source: APXvYqyE6tzXDR2jqxtQRGRKejPJXt0bDUX3XNzhCwylcZYSLJNL9vcNT6jaWayRASYAvpTbeyl8JQ==
X-Received: by 2002:ac8:65c5:: with SMTP id t5mr23095446qto.217.1569943858729; Tue, 01 Oct 2019 08:30:58 -0700 (PDT)
Received: from ?IPv6:2a06:98c0:1000:8800:2c45:f2bd:808b:f893? ([2a06:98c0:1000:8800:2c45:f2bd:808b:f893]) by smtp.gmail.com with ESMTPSA id x15sm7505291qkh.44.2019.10.01.08.30.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2019 08:30:57 -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: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2019 16:30:55 +0100
Cc: gendispatch@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1ED85E0F-0CB2-450F-8D55-AA6D2027D72E@sn3rd.com>
References: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com>
To: Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Eh5NZRusqcybG9cw3ncIQVdR-pE>
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 15:31:06 -0000

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

v2.23.0 | Report a Bug | By Email