Re: "community" for the RFC series

S Moonesamy <sm+ietf@elandsys.com> Sat, 05 October 2019 19:15 UTC

Return-Path: <sm@elandsys.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 DA5061200D8 for <ietf@ietfa.amsl.com>; Sat, 5 Oct 2019 12:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 4HKG4jZJijv1 for <ietf@ietfa.amsl.com>; Sat, 5 Oct 2019 12:15:26 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 1D28F1200A4 for <ietf@ietf.org>; Sat, 5 Oct 2019 12:15:26 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.12.111]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x95JEoPj002609 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Oct 2019 12:15:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1570302906; x=1570389306; i=@elandsys.com; bh=3oK48afAiG9vtWDmpxDxnPuurpsR569vO9neWF851zc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vyDkgT2UQUiypc16JnXXSQ6Hz8Ud5BE4aTnD0UbT57ssjqd65XZ5AfdgQQy4H7sQK Kn/BQwTmCDMGSeM3eku7q2U3V5+qYow37/2q+kWsEPk7o6Cc23rhD0e48S/PkUw1Ze dyb3/YVkzaFF00HlmyL7VYrVw01kxOmsk/VkoUTo=
Message-Id: <6.2.5.6.2.20191005105448.1189ca38@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 05 Oct 2019 12:14:21 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, rfc-interest@rfc-editor.org, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: "community" for the RFC series
Cc: iab@iab.org, Christian Huitema <huitema@huitema.net>, John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <47f240cc-dc70-20e3-ffe2-61daf700501d@cs.tcd.ie>
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> <4D2F30897EC9E2205E427D46@PSB> <47f240cc-dc70-20e3-ffe2-61daf700501d@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RDPXV8tLWc6f-Pgv3CjHacapM2c>
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 19:15:27 -0000

Hi Stephen,
At 04:20 AM 05-10-2019, Stephen Farrell wrote:
>ISTM that damages the argument that there's more than the
>IETF involved - if we can't characterise (characterise, not
>"count") the "who else" in some sensible manner then we do
>kinda end up where Christian seemed to be starting from.

That's a good point.

I went through some documents, e.g. RFC 6635 and the discussions 
which happened many years ago.  There is the following in the RFC: 
"to better serve the communities that produce and depend on the RFC 
Series".  I gather that the usage of the word "communities"  is 
intentional, i.e. it means that there is more than one community.

Is the IRTF a subset of the IETF?  If that was the case, they can 
folded into one community.  One side-effect of such a decision is 
that it constrains (future) decisions of the IRTF about its 
identity.  We could hand-wave that question and deal with it when it 
becomes a problem.  As I look back, I would say that this is why the 
IETF ended up with its inconsistent stories.

I assume that the IAB is aware that there are other organizations 
which rely on documents published through the Series.  In my opinion, 
some of those organization might not agree to be seated under the 
IETF umbrella.

There was a comment [1] from Mr Johansson.  There are a few persons 
on the ietf@ mailing list who are ex-IAB members.  I have no doubt 
that they would understand what the comment means.

Regards,
S. Moonesamy

1. https://mailarchive.ietf.org/arch/msg/ietf/3lVQg1IX1HGjgT-ogevbLPHqyyc