Re: "community" for the RFC series

John C Klensin <john-ietf@jck.com> Sat, 05 October 2019 08:02 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 0B5BE120110; Sat, 5 Oct 2019 01:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 A5gn3vjohcwm; Sat, 5 Oct 2019 01:02:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 0EA3412004E; Sat, 5 Oct 2019 01:02:36 -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 1iGf1I-000M8o-TR; Sat, 05 Oct 2019 04:02:28 -0400
Date: Sat, 05 Oct 2019 04:02:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: Christian Huitema <huitema@huitema.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, rfc-interest@rfc-editor.org, iab@iab.org, IETF <ietf@ietf.org>
Subject: Re: "community" for the RFC series
Message-ID: <4D2F30897EC9E2205E427D46@PSB>
In-Reply-To: <3ea3fbe0-d307-03b4-ed78-757ee6c2e0c1@gmail.com>
References: <394203C8F4EF044AA616736F@PSB> <4097464f-d038-2439-5ca5-70bac46b25ea@huitema.net> <69DAA6BBBE243BAD98926154@PSB> <750a842a-b527-82b9-e8b8-1d23fdc5cc72@cs.tcd.ie> <31b3720b-c8f1-3964-ae30-ce391007b3aa@gmail.com> <120cf3cb-31a6-7cc9-d6e3-7daee0f9d11d@cs.tcd.ie> <21c43d80-0e0b-4ee8-2cf6-232eb9b66f01@gmail.com> <66ad948c-e95f-e61c-20cd-c4376c393053@cs.tcd.ie> <c5765055-40e6-9e77-c090-e7a40f39c3a6@huitema.net> <3ea3fbe0-d307-03b4-ed78-757ee6c2e0c1@gmail.com>
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/jNYfLqq6o8dxXx0N6b-3hGjfEh4>
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: Sat, 05 Oct 2019 08:02:38 -0000


--On Saturday, October 5, 2019 11:07 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On the underlying point - the fuzziness of the community
> boundary - I really don't believe in magic, or that the
> community we should worry about is 7.7 billion people. But we
> would be deluding ourselves to think that we can count the
> members of the community; we can't even count the members of
> the IETF. So we really have to accept, IMHO, that there is an
> open-ended public service responsibility here, not just a
> responsibility to a well-defined closed community. And if an
> obscure network operator in Northern Elbonia has a comment to
> make on an RFC from 1969 tagged in the index as "(Status:
> UNKNOWN)", that is automatically part of the community
> discourse, even though we don't know which stream that RFC
> belongs to.

I think this is key although I look at it a bit differently.
Nothing I've said implied that we should be seeking consensus
of, much less speaking for, several billion people (nor trying
to enumerate them).   I don't think we should even be trying to
determine consensus among ISOC members or ISOC chapters even
though we presumably could get them enumerated if we asked
nicely.   At the same time, we know they are out there.  We can
identify many of the communities and at least crudely describe
their needs.  We should not presume we can identify all possible
communities or get the description of any one of them and their
needs exactly right.   We don't even make that presumption about
the community of active IETF participants and that is one reason
we talk only about "rough consensus" and not "strong consensus"
or "broad consensus".  To those communities who are part of the
global Internet community and whom we can identify, we owe a
real, good-faith, effort to try to make educated guesses at
their needs and to take what Brian calls an open-ended public
service responsibility and what I described earlier as acting as
trustees for that broader community.  We also have some
obligation to keep looking for and identifying those smaller
communities and clusters, rather than, in the extreme case,
either no one we cannot precisely identify or no one who is not
an active IETF participant, actually counts.

best,
   john