RE: WG meeting structure

"Black, David" <David.Black@dell.com> Wed, 15 May 2019 17:34 UTC

Return-Path: <David.Black@dell.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B04A12011E for <wgchairs@ietfa.amsl.com>; Wed, 15 May 2019 10:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dell.com header.b=wrYdnsiB; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=dP6tQF4+
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 Z_Pael9gMFvh for <wgchairs@ietfa.amsl.com>; Wed, 15 May 2019 10:34:37 -0700 (PDT)
Received: from mx0a-00154904.pphosted.com (mx0a-00154904.pphosted.com [148.163.133.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E80112008C for <wgchairs@ietf.org>; Wed, 15 May 2019 10:34:37 -0700 (PDT)
Received: from pps.filterd (m0170393.ppops.net [127.0.0.1]) by mx0a-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4FHUZkW027982; Wed, 15 May 2019 13:34:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=smtpout1; bh=6AMlfob2AIU012PsSpP6EXuY46pXRt8kzHhGClU3pwE=; b=wrYdnsiBS/jvcjf+H7TrdsF1tWj8pfQpW1OGz3Ghg9lic/jWQuvUZi9E55oBr4tEXmGl FxSX2Ef8SY5oMoJEADlFDaKqD7Ex51OFN5a6UOSPgXJtbtjZchoVLxfgfYSbpOgdu6Qo qeEQuWGs/D10zFpaY3oIbpudUqGRLbUO2zytWRfHkJd5D221myjQx35uC5GLXjxx1cOE cWO1xrfsZVhrwaVWd0OdXtsdkriQUgRNVUGhNxTc6kpK6U4tqM7RHtilF6S55BWTzqmQ AhlcKQBXCdYmyzvsCJZSozAO06vksOHPRML9yY51Y+oSOfrCo1orhxMcIVTcE3jjBJ8N Vg==
Received: from mx0a-00154901.pphosted.com (mx0a-00154901.pphosted.com [67.231.149.39]) by mx0a-00154904.pphosted.com with ESMTP id 2sg1fjm78j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 15 May 2019 13:34:36 -0400
Received: from pps.filterd (m0090351.ppops.net [127.0.0.1]) by mx0b-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4FHSVVV122909; Wed, 15 May 2019 13:34:36 -0400
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by mx0b-00154901.pphosted.com with ESMTP id 2sgkskuy64-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 15 May 2019 13:34:36 -0400
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x4FHYXVP031189 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 May 2019 13:34:34 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com x4FHYXVP031189
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1557941674; bh=qo4DxtP3EeVuhTdS2+tLqmsVms4=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=dP6tQF4+vCushhvrzGgN957kj/p0BLVsEZvxUovCeuDmXGc3Iw0peuA1Zp2NBLLeE r2YqLXQ7pm+4SK3zzivJl6a1RyjrChl5ajdp04w+dMNX8MzAhRy7KbbbMasd+gBYJH Qxnvm4GRSHtcbFUBd9Z0QvydocjsGaBD3p5R3y7M=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com x4FHYXVP031189
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd05.lss.emc.com (RSA Interceptor); Wed, 15 May 2019 13:34:20 -0400
Received: from MXHUB320.corp.emc.com (MXHUB320.corp.emc.com [10.146.3.98]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x4FHYLGw013377 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Wed, 15 May 2019 13:34:21 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB320.corp.emc.com ([10.146.3.98]) with mapi id 14.03.0439.000; Wed, 15 May 2019 13:34:21 -0400
From: "Black, David" <David.Black@dell.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: "'wgchairs@ietf.org'" <wgchairs@ietf.org>
Subject: RE: WG meeting structure
Thread-Topic: WG meeting structure
Thread-Index: AQHVCqrR53PwkgHuLUKKh3PVqKT8I6ZroNgAgAADA4CAALrgAIAAHJ8A///IlKCAAG4rgP//v4pg
Date: Wed, 15 May 2019 17:34:20 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493630568EA5@MX307CL04.corp.emc.com>
References: <61D81D11-1BA0-4123-80C9-C7A97297ED5C@episteme.net> <BF668B4C-6D67-4D7D-A31F-C24523F04EB2@gmail.com> <c3469366-323a-4c15-a504-51e059660ac1@www.fastmail.com> <2D09D61DDFA73D4C884805CC7865E6114E18C7CF@GAALPA1MSGUSRBF.ITServices.sbc.com> <13571.1557928942@localhost> <CE03DB3D7B45C245BCA0D24327794936305686F2@MX307CL04.corp.emc.com> <1983.1557940699@localhost>
In-Reply-To: <1983.1557940699@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.238.21.130]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-15_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905150106
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905150106
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/9cGw4PlEgnQiak-fkmcVsdgLpqc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 17:34:40 -0000

>     > On the original topic, the U-shaped structure is interesting, but a WG
>     > chairs table may still be needed on one side of the screen so that the
>     > WG chairs have a complete view of the action without their backs turned
>     > to anyone.   I also want to reinforce that use of that structure needs
>     > to be at the discretion of WG chairs.  Thinking about the WGs that I
>     > have chaired and currently chair, there have been WG meetings for which
>     > the U-shaped structure would work well and WG meetings for which it
>     > would have been disastrous.
> 
> Care you provide some details?
> 
> I have a hypothesis that the WGs in which it would not work are dysfunctional
> for a multitude of reasons.

Sure:

Area-wide catch-all WG spanning a bunch of topics, e.g., TSVWG - the U-shape will tend to result in many of those seated at the U being disengaged on topics in which they are not involved.   Mic lines result in self-selection of interested participants for each topic, which works well as the WG moves from topic to topic.

Very active WG for which the "working set" of seriously involved participants exceeds the seated capacity of the U-shape.

Beyond that, I have a general concern that the U-shape accompanied by expectations that seats at the U are for active participants may implicitly tend to discourage newcomers and tourists ... who may have crucial insights that everyone else in the WG has missed ...

Thanks, --David

> -----Original Message-----
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> Sent: Wednesday, May 15, 2019 1:18 PM
> To: Black, David
> Cc: 'wgchairs@ietf.org'
> Subject: Re: WG meeting structure
> 
> 
> Black, David <David.Black@dell.com> wrote:
>     > An approach that I like is that if discussion at the microphones is
>     > going nowhere slowly, figure out who the key participants are and
>     > charter a design team with a near-term deadline to come back with a
>     > preferred outcome or a set of thought-out alternatives that are
>     > conducive to hums in a room with 100+ people ... getting to an
>     > agreement to disagree is much easier in a small design team than in a
>     > room with 100+ people.
> 
> Yes, this is a good plan.
> 
> This is why I would like every WG to have 1HR session with as few conflicts
> as possible, early in the week, and a second session later on in the week,
> after sufficient unstructured time to have hashed out a solution.
> 
> Okay, so not every problem can be solved with five people, two couches and
> seven beers, but I'll bet that a good problem statement can be articulated in
> such a period of time, such that if you really need the formalism of a
> chartered design-team, then you at least have the text by the end of the
> week.
> 
>     > On the original topic, the U-shaped structure is interesting, but a WG
>     > chairs table may still be needed on one side of the screen so that the
>     > WG chairs have a complete view of the action without their backs turned
>     > to anyone.   I also want to reinforce that use of that structure needs
>     > to be at the discretion of WG chairs.  Thinking about the WGs that I
>     > have chaired and currently chair, there have been WG meetings for
> which
>     > the U-shaped structure would work well and WG meetings for which it
>     > would have been disastrous.
> 
> Care you provide some details?
> 
> I have a hypothesis that the WGs in which it would not work are
> dysfunctional
> for a multitude of reasons.
> 
> All the WG sessions are on youtube... I spend many days after each meeting
> watching the meetings I missed.  Can you handle 1.5 speed? 1.75? 2x? :-)
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
>