[arch-d] Two outcomes from the Plenary and iabopen

mark@mcfaddencentral.com Fri, 12 March 2021 14:22 UTC

Return-Path: <mark@mcfaddencentral.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F843A0BFA for <architecture-discuss@ietfa.amsl.com>; Fri, 12 Mar 2021 06:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hva-S4EJHISJ for <architecture-discuss@ietfa.amsl.com>; Fri, 12 Mar 2021 06:22:31 -0800 (PST)
Received: from smtprelay.hostedemail.com (smtprelay0122.hostedemail.com [216.40.44.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 763EA3A0BF1 for <architecture-discuss@ietf.org>; Fri, 12 Mar 2021 06:22:31 -0800 (PST)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay04.hostedemail.com (Postfix) with ESMTP id 83B161810D759 for <architecture-discuss@ietf.org>; Fri, 12 Mar 2021 14:22:29 +0000 (UTC)
X-Session-Marker: 6D61726B406D6366616464656E63656E7472616C2E636F6D
X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, mark@mcfaddencentral.com, , RULES_HIT:41:152:355:379:582:962:967:973:988:989:1152:1189:1221:1260:1313:1314:1345:1381:1436:1437:1516:1517:1518:1534:1541:1575:1588:1589:1592:1594:1711:1730:1777:1792:2527:2557:2559:2562:2741:3138:3139:3140:3141:3142:3353:3769:3865:3866:3867:3868:3870:3871:3872:3874:4250:5007:6261:7903:7974:8603:8957:9010:10004:10400:10848:11218:11232:11658:11914:12043:12297:13139:13161:13229:13439:14093:14721:21063:21080:21433:21450:21451:21627:21740:21881:21939:30054, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:0, DNSBL:none, Custom_rules:0:0:0, LFtime:1, LUA_SUMMARY:none
X-HE-Tag: wave80_300538c27713
X-Filterd-Recvd-Size: 4365
Received: from mail.mcfaddencentral.com (imap-ext [216.40.42.5]) (Authenticated sender: webmail@mark@mcfaddencentral.com__47.34.59.16) by omf13.hostedemail.com (Postfix) with ESMTPA for <architecture-discuss@ietf.org>; Fri, 12 Mar 2021 14:22:29 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 12 Mar 2021 08:22:28 -0600
From: mark@mcfaddencentral.com
To: architecture-discuss@ietf.org
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <5be7de41840d30fde71e062dad266ba9@mcfaddencentral.com>
X-Sender: mark@mcfaddencentral.com
X-Originating-IP: [47.34.59.16]
Content-Type: multipart/alternative; boundary="=_5783379eac141641326666e4344e58f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/TN9RVNCou4zqoOpWMS3H4ZM3uGU>
Subject: [arch-d] Two outcomes from the Plenary and iabopen
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2021 14:22:33 -0000

I agree with Lixia's summary of the two recommendations that came out of 
the plenary and IABOPEN discussions.

After I suggested a workshop on consolidation, Jari presented a wealth 
of prior art on the topic. And, during the Plenary, Stephen made the 
remark, "What was wrong with the previous workshop?" Both are helpful.

In thinking about both it seems that any workshop needs to be tightly 
focused on the relationship between protocol design and consolidation. 
An open forum on the economic, political or social implications of 
consolidation would certainly be interesting, but probably not lead to 
actionable outcomes. For me, there are other venues that might be more 
appropriate to talk about societal implications of consolidation.

But I can think of no better place to talk about the relationship 
between consolidation and protocol design than the IETF. So, my feedback 
to the IAB is that, yes, a workshop on consolidation would still be 
useful. The scoping of such a workshop is crucial and should be focused 
on protocol design and Internet architecture. Perhaps, in setting up 
such a workshop, the IAB could clearly indicate what was both in, and 
out, of scope.

So, echoing Lixia: 1] yes, to a different admin/announce IAB list; and 
2] yes, to a properly scoped IAB workshop on consolidation.

mark
-- 
Mark McFadden