Re: Fundamental changes in IETF discussions? (was: Re: Messages from the ietf list for the week ending Sun Dec 27 06:00:02 2020)

Eliot Lear <lear@cisco.com> Mon, 28 December 2020 12:54 UTC

Return-Path: <lear@cisco.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 229123A09C9; Mon, 28 Dec 2020 04:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Cto0ExSaqk2B; Mon, 28 Dec 2020 04:54:46 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65F883A09C6; Mon, 28 Dec 2020 04:54:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2229; q=dns/txt; s=iport; t=1609160085; x=1610369685; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=jeboTPlAwCqmoj9a6rsrfHH8y8MtQvDxnmAv2EsspdU=; b=HT4DrtLd1fxy4BgC4n6jo//aqvd1TOyEAE/ohH04tqjXhwLHcr+B84ip P6R5B6DCR221aA+xEtvgz4TjS4MWtH4pAOoC9J5qlM+Yg3wpNTyzoCgWO JGTCzgY6yKkf5db7NxHWrWAodz1aESH9JEWrpy5AS857cQn+BF/jR/NrY U=;
X-Files: signature.asc : 488
X-IPAS-Result: A0DcAADZ1Olf/xbLJq1iHAEBAQEBAQcBARIBAQQEAQFAgT4EAQELAYF1ggIBIBIujUOIKpw3BAcBAQEKAwEBLwQBAYRKAoF0JjcGDgIDAQEBAwIDAQEBAQUBAQECAQYEcYVthXQBBAF5BQsLOwtXBhMUBYMNAYJmIK1SdIE0hViEbxCBOAGBUotWQYIAgREnHIJWPoEEhwaCLASBVRCBcoMFD5Y/hRecKIMAgyeBN5Z6Ax+TBo9KsVCDbgIEBgUCFoFsJCqBLTMaCBsVOyoBgj4+EhkNjjkfjhNAAzA3AgYKAQEDCY0tAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,455,1599523200"; d="asc'?scan'208";a="29812653"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Dec 2020 12:54:41 +0000
Received: from [10.61.233.244] ([10.61.233.244]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 0BSCsefb031958 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 28 Dec 2020 12:54:41 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <437C1407-5C5B-493E-967A-5FB7666E3392@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_545FCF08-7805-4132-9269-32E5D56AECCE"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Fundamental changes in IETF discussions? (was: Re: Messages from the ietf list for the week ending Sun Dec 27 06:00:02 2020)
Date: Mon, 28 Dec 2020 13:54:39 +0100
In-Reply-To: <CC21057C9D957E9D9DFA0241@PSB>
Cc: John Levine <johnl@taugh.com>, The IETF List <ietf@ietf.org>, iesg@ietf.org
To: John C Klensin <john-ietf@jck.com>
References: <20201227105938.90242.qmail@submit.iecc.com> <CC21057C9D957E9D9DFA0241@PSB>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.233.244, [10.61.233.244]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M1f8O_jih6m_OBzfWXaydmfQebg>
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: Mon, 28 Dec 2020 12:54:47 -0000

Hi,

> On 27 Dec 2020, at 18:42, John C Klensin <john-ietf@jck.com> wrote:

> However, I wonder if we are not losing something by what appears
> to me to be a growing trend to separate discussion topics off
> into topic-specific lists and to do so fairly early in the life
> cycle of topics and clusters of discussions.

+1.

Either we are a community or we are not.  IMHO we have reason to act as a community, because one result of not being one is a lack of situational awareness on the part of participants with regard to relevant work that takes place in areas they may not normally follow.  This in turn leads to disparate incompatible approaches, rather than architectural building blocks that the IESG alone cannot possibly scale to address.  IoT has been particularly harmed by this fragmentation, but it is surely not alone.

Of course, being part of a community entails responsibilities as well as privileges.  Part of that responsibility is a code of conduct to which members agree and adhere.  Rapid fire responses, and ad hominem attacks have played a role in diminishing the plenary function of this list, as some lamented earlier this year.

My view: some new thinking is needed about this.

Eliot