IETF Logo Mail Archive

Re: AD Sponsorship of draft-moonesamy-recall-rev

Eliot Lear <lear@cisco.com> Wed, 24 April 2019 22:22 UTC

Return-Path: <lear@cisco.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 95F9312011F for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 15:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Ih5C42vZvAVo for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 15:22:57 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D519112008F for <ietf@ietf.org>; Wed, 24 Apr 2019 15:22:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7794; q=dns/txt; s=iport; t=1556144576; x=1557354176; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=ZsQiy6rlz+fRi5XO+tkEpWe4XPceUDpquxv8AqUDyRY=; b=IfVV1NvL8haAJyMDDcm6ZWAyQUi18nNiPqV1UuCJGR3MtYdKgch9WyGa 8SHs1EI0M0edPr58Xh8XU01Y1aWf5BxeqpVknYJpm1HBO813sg10phIZc sCQVOrnZrNjABBJ4G9PLzjl0YeYT4aUyFFekjcDRwgTeiIpZEWKRu8xqc U=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BdAABp4MBc/5BdJa1mGgEBAQEBAgEBAQEHAgEBAQGBZYEPWCqBOQEyKIQPkyCBaCWSUYd1AgkDAQGEbQKGLyM4EwEDAQEEAQECAQJtKIVKAQEBAwEjVgULCxgqAgJXBhODIgGBG14Pqi+BL4VHhFsQgTKBTIl+F4F/gREnDBOCTD6HTjGCJgSSWZN9CYIKgn6LGYQTFAeCNZJfnUqCdQIEBgUCFYFmIYFWMxoIGxVlAYJBPoJ1AQmNMCMDMJByAQE
X-IronPort-AV: E=Sophos;i="5.60,391,1549929600"; d="asc'?scan'208,217";a="551168272"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Apr 2019 22:22:55 +0000
Received: from che-vpn-cluster-2-27.cisco.com (che-vpn-cluster-2-27.cisco.com [10.86.242.27]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x3OMMsJQ016011 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 Apr 2019 22:22:55 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <EBA37D53-E2D4-4056-97AC-B9C1A57388D0@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4011C3A4-391C-4A87-9C4D-3DF1BE2D14E5"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Date: Wed, 24 Apr 2019 18:22:53 -0400
In-Reply-To: <20190424201939.GM3137@localhost>
Cc: "Salz, Rich" <rsalz@akamai.com>, "ietf@ietf.org" <ietf@ietf.org>
To: Nico Williams <nico@cryptonector.com>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <C7274EAB-7DDC-491F-9DD2-0CFFADB13CA9@cooperw.in> <72f00d0b-7ec6-ba6a-b17b-97879d457ae3@comcast.net> <CAKKJt-fOMMdM-mkbJaYpsH6XPCpatUkwZY-d_A+MaNa3nhaNDg@mail.gmail.com> <CABcZeBNdaWU4wwOK_MnWC5hOr7Lu3osmC_6_KKxB5fHuHVHyTw@mail.gmail.com> <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net> <6.2.5.6.2.20190424095017.13cdadc8@elandnews.com> <51068F13-E90F-42A2-8AE2-627D5E18B145@akamai.com> <20190424201939.GM3137@localhost>
X-Mailer: Apple Mail (2.3445.104.8)
X-Outbound-SMTP-Client: 10.86.242.27, che-vpn-cluster-2-27.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pHNAAHtshIE8N_sNL-1BiuuJGfI>
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: Wed, 24 Apr 2019 22:22:59 -0000

Hi Nico,

> On 24 Apr 2019, at 16:19, Nico Williams <nico@cryptonector.com> wrote:
> 
> I'd also like to second EKR's proposal that the IAB and IESG should get
> a first crack at policing themselves.  That wouldn't exclude a proper
> recall mechanism that can be initiated outside the IAB/IESG, but maybe
> we wouldn't need to make that mechanism too easy to start.  Lastly, a
> mechanism for quickly dealing with frivolous petitions can make it
> tolerable to make starting a recall process too easy.


I’m all for steady incremental change.  Having a mechanism to address a situation in the IESG, with notice, would be a good thing.  Even having the mechanism available might have eliminated several instances where it might otherwise have been used.  I feel a little differently about the IAB.  If someone skips out on the IAB, it’s not earth shattering.

Eliot

v2.23.0 | Report a Bug | By Email