Re: The Next Generation

Nico Williams <nico@cryptonector.com> Wed, 11 September 2019 19:47 UTC

Return-Path: <nico@cryptonector.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 16B761201E4 for <ietf@ietfa.amsl.com>; Wed, 11 Sep 2019 12:47:53 -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=cryptonector.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 gqqxdU5BSJd7 for <ietf@ietfa.amsl.com>; Wed, 11 Sep 2019 12:47:50 -0700 (PDT)
Received: from brown.elm.relay.mailchannels.net (brown.elm.relay.mailchannels.net [23.83.212.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52DF1120018 for <ietf@ietf.org>; Wed, 11 Sep 2019 12:47:34 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 825911A0F6B; Wed, 11 Sep 2019 19:47:33 +0000 (UTC)
Received: from pdx1-sub0-mail-a60.g.dreamhost.com (100-96-169-124.trex.outbound.svc.cluster.local [100.96.169.124]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 04A301A25CC; Wed, 11 Sep 2019 19:47:33 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a60.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.5); Wed, 11 Sep 2019 19:47:33 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Grain-Thoughtful: 6dd632bf1ad60295_1568231253271_1326070335
X-MC-Loop-Signature: 1568231253271:162253142
X-MC-Ingress-Time: 1568231253271
Received: from pdx1-sub0-mail-a60.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a60.g.dreamhost.com (Postfix) with ESMTP id C948D80107; Wed, 11 Sep 2019 12:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=PHrO0XMYH72ZNg zA0fEOGQWEyOA=; b=pl0fNql+grbaZ0jQs/Epe3d84/6FXziV8DJakRGio7Q3XA xwaveYwWS25U+1uY/P0cKWUOBns2LPAvVp/wbzaZob4+A1aQ9cXRvfloavYWQ1B/ urUmghjkvGoPJGSnYHWpqaBqYS3nGl/93J0XiHILCE8PTk29zrHmyFLrlj29A=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a60.g.dreamhost.com (Postfix) with ESMTPSA id 8983F80105; Wed, 11 Sep 2019 12:47:26 -0700 (PDT)
Date: Wed, 11 Sep 2019 14:47:24 -0500
X-DH-BACKEND: pdx1-sub0-mail-a60
From: Nico Williams <nico@cryptonector.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Rob Sayre <sayrer@gmail.com>, ietf@ietf.org
Subject: Re: The Next Generation
Message-ID: <20190911194723.GC18811@localhost>
References: <CAChr6Sz3j0iLGsB2bGvfitPzCkiTCJYHfmUF5S-8zPYMt1r+3A@mail.gmail.com> <6.2.5.6.2.20190911094010.0c933fa8@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20190911094010.0c933fa8@elandnews.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrtdefgdduudeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucfkphepvdegrddvkedruddtkedrudekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhenucevlhhushhtvghrufhiiigvpedt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j08PNH5qGZqNT72_TIuan-_uLKA>
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, 11 Sep 2019 19:47:53 -0000

On Wed, Sep 11, 2019 at 11:22:39AM -0700, S Moonesamy wrote:
> Hi Rob,
> At 05:35 PM 03-09-2019, Rob Sayre wrote:
> > I noticed there were some parts of the last IETF meeting (105) that were
> > sparsely attended. And, the attendees of those meetings tended to be
> > [removed]. There's nothing wrong with that: no one chooses their
> > [removed].
> > 
> > Although there is value in experience, maybe the IETF should work to
> > hand off some duties to more diverse younger people.
> > 
> > As a start, I propose identifying some current groups that could be
> > better-handled by
> 
> My reading of the relevant rules is that the message which I am sending is
> off-topic for this mailing list.  For what it is worth, one of the points in
> your message (re. newcomers) was discussed [1] on this mailing list about a
> decade ago.

Did the SAAs call out Sayre's post as off-topic??  I didn't notice.  But
you know, there's so much noise on this list lately...  If they said
nothing even privately, then frankly that would be another stain on
their recent performance.  We can't quite know if they objected
privately, of course, so it's hard to say.

> There has been various proposals over the years about newcomers.  Those
> proposals do not set a metric for success.  Some time ago, I chose a number
> as part of an effort to get new people interested in working for free.  I
> reached half that number at the end of that endeavor.  Based on that, I
> would describe the venture as a failure.
> 
> The person selecting people for the various roles is the Area Director.  It
> is his/her responsibility to assess whether the Area is attracting new
> people and whether there aren't any obstacles which prevent or discourage
> those new people from staying around.

Not quite so.  We're a VOLUNTEER organization.  That means we're
self-selected.  ADs don't get to select participants.  ADs may get to
select or help select chairs for WGs, but that's about it.

Now, some volunteers are asked by their employers to work on IETF
matters, some by their customers, and others do it for other reasons.

In principle the IETF could ask employers to be more, er, discriminating
as to who they assign to work at the IETF.  I wonder what the EEOC in
the U.S. would think of that, were the IETF to do such a thing.  I can
imagine lawsuits.  So before the IETF does any such thing, I'd recommend
talking to lawyers.  In any case, that leaves all other self-selected
volunteers free to self-select.

IETF leadership is another story.  Though again, one wonders what the
EEOC would think of the NomCom discriminating on bases for which
discrimination in employment is forbidden -- the NomCom isn't an
employer, so perhaps "nothing" is what the EEOC would think, but maybe
Congress would think something else entirely.  Again, speak to a lawyer
before you think of engaging in such discrimination at the NomCom!

Even so, the NomCom selects from among the group of self-selected
volunteers.

We can have a self-selected volunteer organization with zero control
over its volunteers diversity scores, or we can have a non-volunteer
organization that might be able to have an effect on the diversity of
its actual participants through bylaws and governance that would have
to..  not run afoul of American laws (the IETF, ISOC, and related
entities being American legal entities).

Who here can imagine the IETF no longer being a volunteer organization?

I can, with effort anyways.  I can imagine the IETF being like the
Unicode Consortium, the IEEE, OASIS, ISO/ANSI, ITU-T -- pay-big-bucks-
to-play.  It's somewhat surprising that the IETF has not yet become a
pay-to-play organization, or that it exists at all instead of the ITU-T
taking over its functions.  The IETF becoming pay-to-play would be the
simplest way to put an end to all the recent bickering on this list, so
there's that.

Nico
--