Re: [Dclc] Increasing RG meeting effectiveness

"Fred Baker (fred)" <fred@cisco.com> Tue, 19 August 2014 15:37 UTC

Return-Path: <fred@cisco.com>
X-Original-To: dclc@ietfa.amsl.com
Delivered-To: dclc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9771A03F9 for <dclc@ietfa.amsl.com>; Tue, 19 Aug 2014 08:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.569
X-Spam-Level:
X-Spam-Status: No, score=-114.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 6S1uzOU1VFsP for <dclc@ietfa.amsl.com>; Tue, 19 Aug 2014 08:37:20 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3FC01A03E6 for <dclc@irtf.org>; Tue, 19 Aug 2014 08:37:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8665; q=dns/txt; s=iport; t=1408462640; x=1409672240; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3JAB+okTzAMiaefuiUbuIyFmJj6v+o4FbM11I220BUs=; b=ixZfc+0WGd1Qy8+kc8Rhitm1XKNQP+jagVHgABeNdXPTyYvv0MvnkOkP D4J5Fujai14dLDQURjK50Lmxobzanlz3XXUW2HAz9vbGawpp5jx4MfLpp oXnbJvN52dxVqEEW6q9znPPPilYDJFWy3ZrRg19YsjkbUsE2mk8p101SS U=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkHAMhu81OtJV2Y/2dsb2JhbABZgw2BKgTQa4NTAYEKFneEBAEBAwEdXAULAgEIRjIlAgQOBQ4GiCYIwUEXiX+Eaw4CAgFPB4MvgR0FkSWCAIFKgxWEPpUDg11sgUiBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.01,895,1400025600"; d="asc'?scan'208";a="348681500"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 19 Aug 2014 15:37:19 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s7JFbJi5007386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Aug 2014 15:37:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.15]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Tue, 19 Aug 2014 10:37:19 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: dclc <dclc@irtf.org>
Thread-Topic: Increasing RG meeting effectiveness
Thread-Index: AQHPtfpvcDdJ7MEJm0e0cbqb250HHZvYbsaA
Date: Tue, 19 Aug 2014 15:37:18 +0000
Message-ID: <30B5DC39-75B2-446C-89A2-4E783FC8E078@cisco.com>
References: <16537E36-88DC-4C6C-A556-1F8EA8C66430@netapp.com>
In-Reply-To: <16537E36-88DC-4C6C-A556-1F8EA8C66430@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.114]
Content-Type: multipart/signed; boundary="Apple-Mail=_27CB00CD-A89C-43CE-B4AE-B7B9E9F1D2FF"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dclc/BRSBW8C2BYvmWpZ_5lxRPGAdi1U
Cc: 邓灵莉/Lingli Deng <denglingli@chinamobile.com>
Subject: Re: [Dclc] Increasing RG meeting effectiveness
X-BeenThere: dclc@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of Data Center Latency Control <dclc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dclc>, <mailto:dclc-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dclc/>
List-Post: <mailto:dclc@irtf.org>
List-Help: <mailto:dclc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dclc>, <mailto:dclc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Aug 2014 15:37:23 -0000

I had a strange mail outage; I sent this a couple of days ago, and I see it neither in my own records nor on dclc@. Apologies if it’s a repeat.

Lars (IRTF Chair) sent the following a couple of weeks ago. We’re a poster child, and Lingli and I think the point is well taken.

We have had two meetings. One, at IETF-89, wasn’t widely announced. It happened in a small room with perhaps 20 chairs and as many people. Lingli showed a couple of slides, as did I, and we had a good general discussion. Our first “real” meeting was at IETF-90, in a room for 300 with construction noise and 39 scattered participants. A number of factors contributed, but the meeting was well described as a sequence of presentations with a little discussion after each.

Lars is suggesting meetings in places suited to the number of participants, in a discussion format. Sounds good to us. If that makes someone feel excluded, we obviously don’t want that, but we think this might be more inclusive anyway.

My suggestion for the moment is that people post what they like to the list, and if we have enough to have one, we can have a webex-or-whatever meeting. Otherwise, perhaps in October, we’ll ask what topics people would like to discuss f2f, and organize a meeting around a few topics.

On Aug 11, 2014, at 11:55 PM, Eggert, Lars <lars@netapp.com> wrote:

> Hi,
> 
> sorry for the length of this email.
> 
> I've been thinking about how we can increase the effectiveness of IRTF RG meetings during IETF weeks. My personal experience over the last few years is that RG meetings in very large IETF meeting rooms generally do not work well for many RGs.
> 
> These huge IETF rooms encourage a one-way pass-down of information from the speaker to the (silent) audience, and only a few participants (usually the same ones) making their way to the microphones to ask a few questions. It's usually impossible to have any sort of deeper or longer discussion under these circumstances.
> 
> I'm not saying that these classroom-style setups are wrong for all RGs - they may work well for some that operate more like academic workshops (e.g., NMRG), but they strike me as the wrong forum for RGs that need to operate differently in order to make progress.
> 
> As an example, I was struck by how much more effective the DCLC side meeting in London was, compared to the on-the-agenda meeting the proposed RG had in Toronto. In London, the meeting was in a boardroom-style arrangement with about 20 seats; in Toronto, it was in a huge IETF meeting room with a 300-seat classroom setup. 
> 
> Part of the reason was that in the small room in London, no microphones were used, and there were almost no presentations. It was a free-flowing discussion that was minuted and later continued by email. The Toronto meeting, in contrast, emulated an IETF WG meeting as many RGs are prone to do when meeting in IETF rooms: invited presentations, very little discussion, very little email followup, everyone dutifully using the microphones and jabber scribing, although there seemed to be only a single remote participant who actually participated (and that is one more than many RGs usually have.)
> 
> (To be clear: I picked DCLC above as an example; I've experienced the same with other groups.)
> 
> So, I'd like to try a somewhat radical experiment in the IRTF, and try and meet differently. In short: No more huge IETF rooms, no more microphone lines, a lot fewer presentations.
> 
> The longer version is this:
> 
> 
> (1) Rooms 
> 
> I'm trying to see if the secretariat can set up one meeting room for the IRTF that has a boardroom-style table at the front of the room, and a few classroom-style seating rows in the back. The idea is that active participants chose to sit at the boardroom table, while folks that are mostly there to listen sit in the rows. As chairs, you either select who you think your active participants are by some process you choose, or you trust your participants to self-regulate. Yes, this will require some planning by the chairs.
> 
> The boardroom-style table has a few omnidirectional microphones, so people around the table can speak freely without needing to form a line. (Chairs may still need to manage a virtual queue when the discussion gets heated.) There is the usual floor mike near the classroom-style seating rows, so everyone has a chance to chime in.
> 
> (Variant: If the boardroom+classroom setup cannot be done, a boardroom-only setup may be sufficient. In that case, the chairs will need to crowd control their meeting in some form.)
> 
> It's likely that not everyone showing up for an RG session will fit into the room, if the seating arrangement is changed in this way. To me, this is fine. IRTF RGs do not do standards, and while I like the groups to be as open as possible, that doesn't mean that we need to cater to 200 tourists in an RG session that do not usefully contribute to what the RG is trying to achieve. I'm happy to be the point man here to argue this to the community, so chairs don't have to.
> 
> 
> (2) Remote attendance
> 
> Nobody at the boardroom table will remember to say their name before they speak. That's OK, as long as they say it once. Regular participants who happen to be remote will usually recognize others by voice. Everyone else will have a bit of a hard time.
> 
> That's OK by me - I don't think we need to bend over backwards to make in-room interactions too difficult for the sake of remote participants, few of whom actually do actively participate in the meeting. I wish there was a way to make in-room and remote participation similarly effective, but I don't know of one. If I have to pick, I want to optimize for those folks who actually show up in the room.
> 
> (Yes, this is controversial, and I would not suggest this for an IETF WG.)
> 
> 
> (3) Meeting style
> 
> In general, there are too many presentations at RG meetings, and too little discussion. Your duty as chairs is not to simply do a call for presentations and then fill up the available meeting time with random presentation requests as they come in. You are chairs because you care about the topic of your RG and want to see certain outcomes happening. Use the meeting time you have towards that goal. Be ruthless.
> 
> This can mean no presentations at all. It can mean having a single, carefully prepared presentation on a hard question, followed by a long discussion. It can mean a series of related smaller presentations on a given topic, followed by discussion. Do whatever furthers the goals you want to achieve.
> 
> I've been in too many RG meetings that filled 80% of their agenda time with presentations, all of which ran long, leaving maybe 5% of the effective time for any sort of group discussion. If your group needs this kind of meeting at the moment , please consider if a Webex wouldn't be a more effective way of making progress. There is no need to wait for a face-to-face opportunity for these meetings, and wasting facetime on such meetings doesn't seem like a great idea.
> 
> (There are RGs that operate more like academic workshops, i.e., the NMRG at the moment. Much of the above doesn't really apply to them.)
> 
> 
> I'm very interested in your feedback here. I have chatted with the secretariat in London about whether the boardroom+classroom setup is possible to try out in Honolulu (and I'm CC'in Stephanie so she remembers we chatted about this, since it was Friday :-)
> 
> Once this is hashed out a bit more, I'd love for some RGs to try this approach out and see if it works better for them.
> 
> Lars
>