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

John C Klensin <john-ietf@jck.com> Thu, 18 April 2019 03:38 UTC

Return-Path: <john-ietf@jck.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 00764120294 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2019 20:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 hJb84n8q0KXY for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2019 20:38:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A61C12029E for <ietf@ietf.org>; Wed, 17 Apr 2019 20:38:09 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hGxsE-000I46-Lj; Wed, 17 Apr 2019 23:38:06 -0400
Date: Wed, 17 Apr 2019 23:38:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Benjamin Kaduk <kaduk@mit.edu>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Message-ID: <5FBF0B8BB0D83073FD89FAB7@PSB>
In-Reply-To: <20190418030456.GB70338@kduck.mit.edu>
References: <6.2.5.6.2.20190405085139.0d5c39b0@elandnews.com> <54510B49-175B-4CE6-9319-1F9A4803940E@cooperw.in> <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <BB40F115-46E8-4EF3-ABDE-15ABB33B4ACA@akamai.com> <C11980900F520E0EFCC83CEB@PSB> <98e75e64-f381-7788-aea2-31218eeaebfc@gmail.com> <20190418030456.GB70338@kduck.mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EmsrNZUZYigaoT0cPSvkmMY-sck>
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: Thu, 18 Apr 2019 03:38:11 -0000


--On Wednesday, April 17, 2019 22:04 -0500 Benjamin Kaduk
<kaduk@mit.edu> wrote:

> On Thu, Apr 18, 2019 at 08:38:44AM +1200, Brian E Carpenter
> wrote:
>> It would certainly be ironic if a proposal to alleviate some
>> of the disadvantages of remote participation couldn't be be
>> discussed by remote participants in multiple time zones.
>> 
>> With all due respect, etc. etc., I've always understood that
>> discussion by email was intended to alleviate exactly that
>> problem, and this list *is* the IETF plenary. So exactly who
>> has been disenfranchised from this discussion who would be
>> enfranchised by a physical or virtual BOF?
> 
> Taking this question at face value: technically, "no one",
> since membership in the list is open modulo posting actions or
> SAA actions (I think there may be one or two of the latter
> still active, hence scare quotes). But in practice, I hear
> from the grapevine that many people are unwilling to subscribe
> to or participate in discussions solely on this list, because
> the volume of traffic is large and the perceived signal/noise
> ratio insufficient to merit the time commitment.
> 
> Having a dedicated discussion forum other than this one is
> both in keeping with the list charter and would provide a
> lower barrier to participation from those who have stayed away
> from the general discussion list but do care about remote
> participation.  It is fair to debate the cardinality of that
> set, if you have a different perception than me, of course.

Ben,

Correct me if I'm wrong, but I think you have just made an
argument for either a dedicated mailing list or, as Spencer
suggested, using something like the ietf-nomcom (more like
co-opting, because this really isn't about the nomcom) list and
no argument at all for a BOF.   

    john