IETF Logo Mail Archive

Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

Alissa Cooper <alissa@cooperw.in> Fri, 26 April 2019 20:02 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 457761205E6; Fri, 26 Apr 2019 13:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=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=AlxNtaEt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=s2NCQG4n
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 tz8tyB0YqaBN; Fri, 26 Apr 2019 13:02:36 -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 5EB261205D0; Fri, 26 Apr 2019 13:02:36 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6576D21E97; Fri, 26 Apr 2019 16:02:35 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 26 Apr 2019 16:02:35 -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=fm2; bh=5 PBPKG5g+hEhw4EBhpczpQyGqM1uVopr0/apl7J3QMc=; b=AlxNtaEtwozRLO0c/ +ZE8cAxXK+GdEpKvEMIhiL5g7hAES/Omt3pbCv0wVbF9DmhPy9rzFNlLK6PDDwMb 39eB7KIvzNdUQVvALvcc/Ki6yOtKQ4qkV/G8oUlTovFE2DJ54RAtkxDzF9H8soqP 0xSC9/XtLi7x7QkpHnfN5HNfLsWaCx6O+VAaqKhizqYpRttxRu1mc+RCDUOnnn8c 5pR9sP5OOSQxDFx5+5jWrp3Zc80yepnHOdnz+cx/e3EPYoIuyvYPvDhFe8kPq5Ez Rj+6K5GYO3JpaBMe4VcSU83QyQqwcW/sKLkBNGh5m1jWWt1DyOCSK0dakLP4VM9o DZrcw==
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=fm2; bh=5PBPKG5g+hEhw4EBhpczpQyGqM1uVopr0/apl7J3Q Mc=; b=s2NCQG4n/JP6lUsdc8VWhP2oQuHDsJ5+jAbKlgZSUmVCLb4gA01S1Ul4q POvOhcjUKlQSX11A1qCEORVH612SwUIFyO2Y++uojnceGIAxDGZ2XIz7HXls76gQ 504/W2a0VtINx38IN8UcE5CgUuI8GgRQhnKcoT99tiJza+MN/kiX3V3IF3MjDz7e gpZNacZRpHp8TIvrOWIQXNVLhFIQwphofBi6cFkvndsB4XsbigzMwXsRT52TpX6q uxQEzZxlwotlWRlvCheJPOK7Lq2vcvwN8Pq1xjgbHl7X+h1eF/dKFyCcAJvnRcj0 3dcPiL6uq7yNTIBn+zsEyuEXYnomg==
X-ME-Sender: <xms:22PDXAlWxXXQ3BoRlqESHtgjwAR_J-E8C9Yj3Uq_dzmic0DDGpGcdQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrheeigddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhsshgrsegt ohhophgvrhifrdhinheqnecukfhppedujeefrdefkedruddujedrkeejnecurfgrrhgrmh epmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsthgv rhfuihiivgeptd
X-ME-Proxy: <xmx:22PDXIYMZuuG9ATz_fevjT8RwHY3yem3MXUTEEGJeRxThbOTqiDQDA> <xmx:22PDXFtdNUYbYGfvWVqM4e78_e7hP2E-w50Gv5OLxddrUwHFvRkIlw> <xmx:22PDXBrfT-0DJ-ePLsGwTaLQmkAW0VCzODL25_n_TcF6RtMJTKeFpQ> <xmx:22PDXJLvBslzQ7NhYMst6J2WJzHkBN188tMcx6aDphu9_c_a8pA0FQ>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id BE841E4173; Fri, 26 Apr 2019 16:02:34 -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: <6.2.5.6.2.20190418115734.0dffb680@elandnews.com>
Date: Fri, 26 Apr 2019 16:02:33 -0400
Cc: IESG <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A8EB85F-9A5A-4E33-AC82-78B49A3D8BE1@cooperw.in>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <6.2.5.6.2.20190418115734.0dffb680@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/7bEH_sEWX7Iury0MgZmip8fIKzw>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2019 20:02:46 -0000

Hi SM,

> On Apr 19, 2019, at 10:06 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Hi Alissa,
> At 07:46 AM 17-04-2019, Alissa Cooper wrote:
>> I discussed this with the IESG and our recommendation is for you to submit a BOF proposal if you'd like to pursue this further. We think these kinds of changes to the IETF's governance structure need the more in-depth problem statement discussion and broader review that a chartering process and working group would provide.
> 
> Thank you for discussing the request with the IESG.
> 
> There is currently a working group discussing the governance structure of the IETF.  I doubt that the draft would be in scope for that working group given that its charter specifically sets "the standards process" as outside its scope.  

If you are referring to IASA2, I think that WG is explicitly not about the governance structure of the IETF, but rather its administration.

> Is the IESG recommending an in-depth problem statement about the Internet Standards Process?

We did not make that recommendation. I believe what we are looking for is a clear articulation of the underlying problem(s) that the draft and the resutling community discussions are seeking to address.

Alissa

> 
> Regards,
> S. Moonesamy

v2.23.0 | Report a Bug | By Email