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

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

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: chirp@ietfa.amsl.com
Delivered-To: chirp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B031D3A1546 for <chirp@ietfa.amsl.com>; Thu, 2 Apr 2020 08:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id R45KpxEAD-Kc for <chirp@ietfa.amsl.com>; Thu, 2 Apr 2020 08:27:24 -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 ACF553A159E for <chirp@iab.org>; Thu, 2 Apr 2020 08:27:22 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de []) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 3E568548049; Thu, 2 Apr 2020 17:27:17 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 39727440040; Thu, 2 Apr 2020 17:27:17 +0200 (CEST)
Date: Thu, 2 Apr 2020 17:27:17 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "chirp@iab.org" <chirp@iab.org>, architecture-discuss@ietf.org
Message-ID: <20200402152717.GK28965@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a5046b41-b44e-d292-e0da-da6ec6d599ad@cs.tcd.ie>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/chirp/v4VJ-yh6ejm_FvUS1G2sQN0AvTo>
Subject: [Chirp] on the nature of architecture discussion (was: Re: Fwd: IETF 107 Vancouver In-Person Meeting Cancelled)
X-BeenThere: chirp@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "CHallenges for Internet Resilience \(proto-\)Program" <chirp.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/chirp>, <mailto:chirp-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/chirp/>
List-Post: <mailto:chirp@iab.org>
List-Help: <mailto:chirp-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/chirp>, <mailto:chirp-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2020 15:27:27 -0000

[Cc'ing to architecture-discuss, because this reply goes
beyond the scope of chirp.]

Stephen, *:

I don't think that a mailing list alone is a sufficient way to
encourage interested parties to invest significant amount of
cycles to contribute original work towards a subject even if
as a one off: document and/or presentation. If you want
people to invest cycles towards something you're interested in,
you need to give contributors a well defined opportunity to
engage in-person through a meeting (or virtual meeting
in the time of corona) and allowing the work invested to be
referenceable by future work of others (such as meeting
proceedings for presentations).

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. 

Why not ?

Stephen, I know we may have a fundamental difference in opinion about
this if i correctly interpret your harsh criticism about my teams
organized inofficial side-meeting in march, but i for once don't
think that a discussion about internet architecture will magically
improve through the absence of such meetings.

Why is there no internet architecture discuss meeting slot in
every IETF meeting (virtual in times of corona) ? I can not
even start to comprehend why i am seemingly the only one asking
this question.

To me, providing such fairly open scoped meeting looks like
the most fundamental meeting the IAB should organize to engage
the community in an open fashion. Consider it the "dispatch"
equivalent of other areas.

Topics of special interest to IAB (such as chirp) could be
indicated as prioritized topics to encourage contribution to 
them, and if they show critical mass the could be dispatched
into separate forums.

I can see no outcome worse than what we seemingly have now on
this architecture-discuss mailing list: agony and inactivity
interrupted by often snide lecturing meta discussions about those who
attempt to contribute something, however well or badly that is done.


On Thu, Apr 02, 2020 at 12:32:27PM +0100, Stephen Farrell wrote:
> Hiya,
> I only got one request to hold such a meeting so I guess
> we don't want one.
> That, and the lack of activity on this list is a bit of
> a pity I think so ideas welcome as to how to energise a
> discussion... If you have such an idea, then please just
> start a new thread on the list.
> Cheers,
> S.
> On 10/03/2020 20:50, Stephen Farrell wrote:
> > 
> > Hi all,
> > 
> > Many of you will have seen this but we'll not be meeting
> > f2f in Vancouver this time. Hopefully things will have
> > improved by the timeframe of IETF108 and we'll be able
> > to enjoy a meeting then.
> > 
> > In the meantime, would people like to organise a call
> > in a few weeks to replace our planned get together in
> > Vancouver? If so, please mail me, the IAB or the list:-)
> > 
> > If we do want a call, the IESG have asked for a
> > bit of time to do some scheduling that they need to do
> > before WGs (and groups like us:-) start to schedule
> > such calls. So let's first see if we want a call and
> > then we can do scheduling.
> > 
> > Cheers,
> > S.
> > 
> > 
> > -------- Forwarded Message --------
> > Subject: IETF 107 Vancouver In-Person Meeting Cancelled
> > Date: Tue, 10 Mar 2020 12:10:27 -0700
> > From: The IESG <iesg@ietf.org>
> > Reply-To: iesg@ietf.org
> > To: IETF Announcement List <ietf-announce@ietf.org>
> > CC: irtf-announce@irtf.org, ietf@ietf.org, 107all@ietf.org
> > 
> > The IESG and the IRTF Chair have decided to cancel the in-person IETF
> > 107 Vancouver meeting. This decision is based on input we gathered from
> > Working Group (WG) and Research Group (RG) chairs about our ability to
> > hold productive WG and RG sessions at IETF 107. Our assessment of this
> > feedback is that a majority of sessions would not be viable if we were
> > to hold the in-person IETF meeting. On this basis, we believe we cannot
> > hold an effective in-person meeting.
> > As a result of this cancellation, the in-person Hackathon, Code Sprint,
> > all other in-person events planned for the weekend of March 21-22, the
> > chairs training scheduled for March 20, and all other in-person sessions
> > during the week are cancelled.
> > 
> > The IESG is working on an alternative all-virtual agenda for the week of
> > March 21-27 with a limited schedule adapted to accommodate the time
> > zones of as many participants as possible. We are also planning to
> > support an increased volume of virtual interim meetings during the weeks
> > that follow. We will send another update to the community soon with more
> > information about these plans. The Hackathon organizers are also
> > considering plans for virtual Hackathon support.
> > 
> > We have re-opened Internet-Draft submissions, which had been closed on
> > March 9 in anticipation of the in-person meeting. Internet-Drafts may be
> > submitted at <https://datatracker.ietf.org/submit/>.
> > 
> > A separate announcement from the IETF Executive Director will follow
> > with details about registration cancellations and refunds.
> > These are unusual times given the circumstances created by the spread of
> > COVID-19.  We hope that everyone remains safe and healthy.
> > 
> > Regards,
> > The IESG and the IRTF Chair
> > 
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> > 
> > 
> > 

pub   RSA 4096/7B172BEA 2017-12-22 Stephen Farrell (2017) <stephen.farrell@cs.tcd.ie>
> sub   RSA 4096/36CB8BB6 2017-12-22

> -- 
> Chirp mailing list
> Chirp@iab.org
> https://www.iab.org/mailman/listinfo/chirp