RE: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)

"Tobias Gondrom" <tobias.gondrom@gondrom.org> Tue, 18 April 2017 23:53 UTC

Return-Path: <tobias.gondrom@gondrom.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 DF66B1293EC for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.104
X-Spam-Level:
X-Spam-Status: No, score=-0.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_MIMEOLE=1.899, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
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 2QDVplLCzluO for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:53:45 -0700 (PDT)
Received: from gondrom.org (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DFDC12773A for <ietf@ietf.org>; Tue, 18 Apr 2017 16:53:45 -0700 (PDT)
Received: from seraph (x5ce4409f.dyn.telefonica.de [92.228.64.159]) by gondrom.org (Postfix) with ESMTPSA id A009E649EA; Wed, 19 Apr 2017 01:53:43 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gondrom.org; b=qodwgRBZTdwDQqFB+oPdW5RIAJq1VWHEeO6aTxxyttEy6gkRKqXxBFugEu8Eqkad3EXQFT37qUh1Nb9nBx27H6cNm5OdKsKCKevJzmAo3dOipsARfcjQwjmgS/WUkucRHXebeFGN5uFihW1w0Das7lUzgNig8kI7ZlCHEQtDqeg=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:Thread-Index:Content-Language:Importance;
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
To: 'Bob Hinden' <bob.hinden@gmail.com>, 'Toerless Eckert' <tte@cs.fau.de>
Cc: 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'IETF' <ietf@ietf.org>
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
In-Reply-To: <3CE3B17A-93B4-47E4-89B1-8C4347E874A9@gmail.com>
Subject: RE: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)
Date: Wed, 19 Apr 2017 01:53:38 +0200
Message-ID: <004a01d2b89f$01469740$03d3c5c0$@gondrom.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJFGqovNtf1uRc6szM4m5pwBAJ16gJh8oUHA5KikxgBt38BKAIbp3TrAnzs6jEBSR1mEQFhnYp9AMLftloC4U3kGALuGgGxAqc+CeICO78FPKAT4Lzw
Content-Language: en-us
Importance: Low
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YYQBTiAo1gkama6gYDdHB_3w9jI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 18 Apr 2017 23:53:47 -0000

<IAOC hat = "off">
Ps.: and I would like to add that at least in my personal understanding the content and format of the WG meetings is under the mandate of the WG chairs, the IESG and IETF chair. Same like the IETF meeting agenda is also not set by the IAOC. Of course the IAOC could (and I assume would be happy to) include questions from the IESG into the usual meeting survey, but I don't think it is the IAOC's place to discuss the content or how many Powerpoints are used within the WG meeting. IMHO that is for WG chairs and IESG to decide. And with these expectations, it is the IAOC task to arrange for an environment that is supporting to fulfill the expectations from the WG chairs, IETF and the IESG. 



-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Bob Hinden
Sent: Wednesday, April 19, 2017 1:09 AM
To: Toerless Eckert <tte@cs.fau.de>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>; Bob Hinden <bob.hinden@gmail.com>; IETF <ietf@ietf.org>
Subject: Re: Structure of IETF meeting weeks (was: Re: IAOC requesting input on (potential) meeting cities)

Toerless,

Responding with this thread as it’s not about meeting locations.

> On Apr 18, 2017, at 2:34 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> Hiya,
> 
> On 18/04/17 22:22, Toerless Eckert wrote:
>> For example, there is a lot of death by powerpoint in meetings that 
>> pushes off high bandwidth discussions ("oh, we're out of time"). 
>> AFAIK, most active work on drafts during IETF meeting week happens 
>> outside of the WG meetings. I think that
>> a) was not the original plan, and b) i have not seen IAOC sending 
>> around questionaires what/how to improve the quality of the meetings in this respect.

Regarding powerpoint, the problem isn't the use of slides, it the w.g., chairs not dealing with presenters who shows up with 20 slides for a 10 minutes slot, and the chairs not allocating enough time for a real discussions.

I think the meetings would be a lot more productive if a w.g. could have a meeting at the start of the week, work on the the issues during the week, send updates to the mailing list, have email and face to face discussions, and then have a second session at the end of the week to get consensus.  Clearly, impossible to schedule this with our current number of working groups, but I think it would make for a more productive week.

Bob