Re: [arch-d] on the nature of architecture discussion (was: Re: [Chirp] Fwd: IETF 107 Vancouver In-Person Meeting Cancelled)

Toerless Eckert <tte@cs.fau.de> Thu, 02 April 2020 19:34 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 2986C3A102C for <architecture-discuss@ietfa.amsl.com>; Thu, 2 Apr 2020 12:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 tZYjPhXKReeq for <architecture-discuss@ietfa.amsl.com>; Thu, 2 Apr 2020 12:34:36 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479C93A1028 for <architecture-discuss@ietf.org>; Thu, 2 Apr 2020 12:34:35 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 5DCC4548015; Thu, 2 Apr 2020 21:34:30 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 56FAF440040; Thu, 2 Apr 2020 21:34:30 +0200 (CEST)
Date: Thu, 02 Apr 2020 21:34:30 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Melinda Shore <melinda.shore@nomountain.net>
Cc: architecture-discuss@ietf.org
Message-ID: <20200402193430.GQ28965@faui48f.informatik.uni-erlangen.de>
References: <158386742797.16091.1025684270011519738@ietfa.amsl.com> <efbf8fd0-4673-3a93-2add-6bbc6ff0dca9@cs.tcd.ie> <a5046b41-b44e-d292-e0da-da6ec6d599ad@cs.tcd.ie> <20200402152717.GK28965@faui48f.informatik.uni-erlangen.de> <7de683b6-172b-7e7b-e043-d241804eaa42@nomountain.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7de683b6-172b-7e7b-e043-d241804eaa42@nomountain.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/m_UdvTWI5zVy_Ie1mKGexcqSzsk>
Subject: Re: [arch-d] on the nature of architecture discussion (was: Re: [Chirp] Fwd: IETF 107 Vancouver In-Person Meeting Cancelled)
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: Thu, 02 Apr 2020 19:34:38 -0000

On Thu, Apr 02, 2020 at 11:14:46AM -0800, Melinda Shore wrote:
> On 4/2/20 7:27 AM, Toerless Eckert wrote:
> > We have this mode of operations in hundreds of conferences
> > including IRTF, we have it in IETF WGs for standards, we do
> > not have this for architectural discussions for the Internet. 
> 
> FWIW, many years ago we had these discussions in the technical
> plenaries.  They were, as a rule, unproductive, which may be why
> they have fallen by the wayside.

I vaguely remember there was something, but i don't remember the format. 

> I'm curious to know what you think would change if there were
> structured general architectural discussions.

Was it only presentations or also associated drafts ? Was the
material asked to be make available sufficiently long ago to
allow quality updates be prior review ? Was there an organized
attempt to get upfront or afterwards reviews ? Was there an associated
email discussion forum ? Was there the opportunity to follow up
across multiple such plenaries to refine the content ? Was
there somebody responsible trying to help with a dispatch style
mechanism to help get material further reviewed by other IETF/IRTF
groups that might hav emore interest ? Was there any attempt to
force authors to fold feedback into updated documents so that
final versions summarized not only author opinion but also community
feedback ?  Just off the top of my head. There certainly a lot more
aspects.

I think we know a lot of the process steps that can help to make
discussions/presentations about these difficult topics more successful,
i don't think we experiment enough with them. Especially not on
what i think is the architecture track. We only have well working
tracks for research and standardization. Not architecture. 

But architecture specifically could learn and experiment with a lot
of the mechanisms in the range from research conferences over to
IETF WGs.

Cheers
    Toerless

> Melinda
> 
> -- 
> Melinda Shore
> melinda.shore@nomountain.net
> 
> Software longa, hardware brevis
> 




> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss


-- 
---
tte@cs.fau.de