IETF Logo Mail Archive

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

Alissa Cooper <alissa@cooperw.in> Fri, 04 October 2019 17:22 UTC

Return-Path: <alissa@cooperw.in>
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 F0D1D120143; Fri, 4 Oct 2019 10:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=bQLvzBQF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jL0HLZ9s
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 et7QTrS8bxhQ; Fri, 4 Oct 2019 10:22:32 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D5DD1208D9; Fri, 4 Oct 2019 10:22:32 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6D2D321E50; Fri, 4 Oct 2019 13:22:31 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 04 Oct 2019 13:22:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=x SGWTZLlBizNmpa92l7jbiHQt5FlJhEN3RW1qxv728E=; b=bQLvzBQFIh0dKNSrD fPZiYVIaOumMYAqkzxL3Niu1GK5RsEKQR/rh/HVCHqwThj7B1exnSkkTW4NLoD6D 2vMTcZ8kYcpzxt4M8LflF9IZG8C1BaTdklkbl20Z0NmVpzXKB9iRE2DHxZG5Qj/E NDUWdnhd47fa8GQCTRpF6zM2UXBRbW2mmPOplpW9nl50HIk7PdTesN81HPXJrNcN JrhzYmQuymihvT8r7KWFyzmGVJdOOdNE+qXcjqkM9EzqUVBbjVVVTXLZD6wkJ54F AVDAZymfNIIpvE6xBLvtC3JeRZ6MBBRREYBrGB0aNauNyhoXjfRE31W/T87mIzx7 pO1aw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm3; bh=xSGWTZLlBizNmpa92l7jbiHQt5FlJhEN3RW1qxv72 8E=; b=jL0HLZ9s2PAdkY8BHPQvg9HAwwsisWMLnA+cO+Dye87f/VFbva2mNGF3o eZDM3APRio/mVHRRG6BP0NS63LT5we/q789O8fliUZS3SQjBam2/Lv8LV/eRclYs IxauZ8xTp1sH9RkL9Gd8j3A4S/2PD+k0GIPYgZEw4nKlbAkajTYSkdEOAw4pIvgB n83x2jPRvHKsE0mn/3tCWSQ72dziCHXvORykKDEu98vChml3jf4ky0gzUm3udA8P 5hN21XkurOLBtKr6CNTOoZY3vRhtA18ySgixA3xihwH9GqnpgqT1aPZZTU7rmMeF i5tz6zP1WaQq8aE5kVIRyHtIXeuIw==
X-ME-Sender: <xms:13-XXfcNrpxI6IDYZY1tkLlgaPH6a-TV2qm3RSg59-vrv94gtEyUBA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrhedugddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucfkphepud dtkedrhedurddutddurdelkeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgr segtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:13-XXaKR6DUnt6Dya3RRwxCeYnFgBLGRKc3Q6ZkcgbVdzsrlYxVM4Q> <xmx:13-XXcy9tSWjRlvti2QYBmiZsOCyhnz7E4UU6Z4hr3yQksK-v0IYlA> <xmx:13-XXQvOmEjEu9szI0LoBw_MUcuaPxq34Sld8EV5XEvEGkjD0G5MFg> <xmx:13-XXd_kNN-SFBLEuq_Ni9ehFWytXLB3vU49Ej0bOJHOEiBCk8sBQA>
Received: from alcoop-m-c46z.fios-router.home (pool-108-51-101-98.washdc.fios.verizon.net [108.51.101.98]) by mail.messagingengine.com (Postfix) with ESMTPA id EE0DAD6005D; Fri, 4 Oct 2019 13:22:30 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <0D7F3F61-9789-41B5-B41D-65BD31353EB2@sn3rd.com>
Date: Fri, 04 Oct 2019 13:22:30 -0400
Cc: gendispatch@ietf.org, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <796BC62F-1CA7-4FDC-AC0A-E6C24C4A7595@cooperw.in>
References: <156953786511.31837.12069537821662045851.idtracker@ietfa.amsl.com> <1ED85E0F-0CB2-450F-8D55-AA6D2027D72E@sn3rd.com> <0D7F3F61-9789-41B5-B41D-65BD31353EB2@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/8cbmmgQOiYL8aeMpOUgnOMz2-b4>
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: Fri, 04 Oct 2019 17:22:34 -0000

Hi Sean,

> On Oct 1, 2019, at 1:47 PM, Sean Turner <sean@sn3rd.com> wrote:
> 
> 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.

It need not be. To take a recent example, RFC 8318 was a process doc that was AD-sponsored by an ART AD.

Thanks,
Alissa

>> 
>> 
>> spt
>

v2.23.0 | Report a Bug | By Email