Re: [IAB] "community" for the RFC series

Colin Perkins <csp@csperkins.org> Sun, 06 October 2019 21:07 UTC

Return-Path: <csp@csperkins.org>
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 D819B12011D; Sun, 6 Oct 2019 14:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 wCqp0T_BOg0U; Sun, 6 Oct 2019 14:07:01 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 186CB1200CE; Sun, 6 Oct 2019 14:07:01 -0700 (PDT)
Received: from [81.187.2.149] (port=37287 helo=[192.168.0.66]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1iHDjx-00087h-88; Sun, 06 Oct 2019 22:06:57 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [IAB] "community" for the RFC series
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <6.2.5.6.2.20191005105448.1189ca38@elandnews.com>
Date: Sun, 06 Oct 2019 22:06:09 +0100
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, rfc-interest@rfc-editor.org, IETF <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>, iab@iab.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C19C2185-A2C4-46C4-9E76-B320B304E1FC@csperkins.org>
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> <6.2.5.6.2.20191005105448.1189ca38@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xjhHFD42pxubKxGEQyxqpCcQWeU>
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: Sun, 06 Oct 2019 21:07:03 -0000

> On 5 Oct 2019, at 20:14, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 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.

The IRTF is not a subset of the IETF, although the participants have significant overlap. The RFC Editor and IAB have been careful to involve the IRTF in this discussion.

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

I’ve certainly not seen any suggestion to 'seat the IRTF under the IETF umbrella' from the IAB.

Colin



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



-- 
Colin Perkins
https://csperkins.org/