Re: [rfc-i] "community" for the RFC series

John C Klensin <john-ietf@jck.com> Sat, 05 October 2019 08:03 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D956120169 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 5 Oct 2019 01:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 V3BOM9OkBssM for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 5 Oct 2019 01:03:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDA6512081C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sat, 5 Oct 2019 01:03:27 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 44C16B812BE; Sat, 5 Oct 2019 01:03:22 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 3A6D3B812B8 for <rfc-interest@rfc-editor.org>; Sat, 5 Oct 2019 01:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95lETBT3uNiM for <rfc-interest@rfc-editor.org>; Sat, 5 Oct 2019 01:02:30 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by rfc-editor.org (Postfix) with ESMTPS id D30AEB812B4 for <rfc-interest@rfc-editor.org>; Sat, 5 Oct 2019 01:02:29 -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>
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-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
Subject: Re: [rfc-i] "community" for the RFC series
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org, iab@iab.org, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>


--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

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest