RE: IETF103 Plenary discussion on WG meeting conduct

"BRUNGARD, DEBORAH A" <db3546@att.com> Fri, 08 February 2019 17:06 UTC

Return-Path: <db3546@att.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 5AD06128766 for <wgchairs@ietfa.amsl.com>; Fri, 8 Feb 2019 09:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.611
X-Spam-Level:
X-Spam-Status: No, score=-0.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 IRadADpN179q for <wgchairs@ietfa.amsl.com>; Fri, 8 Feb 2019 09:06:33 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 486971200ED for <wgchairs@ietf.org>; Fri, 8 Feb 2019 09:06:33 -0800 (PST)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x18H4h7h002348; Fri, 8 Feb 2019 12:06:30 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049287.ppops.net-00191d01. with ESMTP id 2qhduqg1h4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 08 Feb 2019 12:06:29 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x18H6QoN011400; Fri, 8 Feb 2019 12:06:27 -0500
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [135.66.87.50]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x18H6NCZ011332; Fri, 8 Feb 2019 12:06:23 -0500
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [127.0.0.1]) by zlp27128.vci.att.com (Service) with ESMTP id 25EF6400043A; Fri, 8 Feb 2019 17:06:23 +0000 (GMT)
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (unknown [130.9.129.149]) by zlp27128.vci.att.com (Service) with ESMTPS id 0EAD64039454; Fri, 8 Feb 2019 17:06:23 +0000 (GMT)
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.226]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0435.000; Fri, 8 Feb 2019 12:06:22 -0500
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
CC: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: IETF103 Plenary discussion on WG meeting conduct
Thread-Topic: IETF103 Plenary discussion on WG meeting conduct
Thread-Index: AdSTEBncsIFj0MT7TvejEpDMUQdaJwsF6NcAACkv7yA=
Date: Fri, 08 Feb 2019 17:06:22 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C89D10626A@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <F64C10EAA68C8044B33656FA214632C8884ADCE3@MISOUT7MSGUSRDE.ITServices.sbc.com> <trinity-51896772-e513-4bd1-ab89-2ce50e768315-1549555050066@3c-app-gmx-bs18>
In-Reply-To: <trinity-51896772-e513-4bd1-ab89-2ce50e768315-1549555050066@3c-app-gmx-bs18>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.16.234.244]
Content-Type: multipart/alternative; boundary="_000_F64C10EAA68C8044B33656FA214632C89D10626AMISOUT7MSGUSRDE_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-02-08_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 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-1902080117
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/TmGtbYyTDC-bYXyg3MWHPVWCPVI>
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: Fri, 08 Feb 2019 17:06:36 -0000

Hi Hannes,

Much thanks for the pointer ā€“ it does summarize quite well our frustrationšŸ˜Š

When you have time (be sure to have a drink in hand) to browse the rest of the thread, my take is we ended up with two items:

  *   Meeting group conduct ā€“ especially new chairs would like training/guidance on how to recognize the potential for a discussion to go bad and how to handle difficult discussions. A talk by Radia was noted (cookies are critical):
https://www.ietf.org/proceedings/53/slides/plenary-3/index.html


  *   Archiving expired work

Among the IESG, we are kicking off discussions on these, maybe some of you want to kick off some dialogue at the next WG Chair lunch.

Just another avian carrieršŸ˜Š
(can not resist as it is a Friday, missing in the article was any discussion on our critical internet infrastructure, RFC2549, which introduced the QoS levels of Concorde, First, .., so we are no longer just pipes based on RFC1149. Interesting are the security considerations, I donā€™t think these would fly today with our current security reviewers.)

From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Sent: Thursday, February 07, 2019 10:58 AM
To: BRUNGARD, DEBORAH A <db3546@att.com>
Cc: wgchairs@ietf.org
Subject: Aw: IETF103 Plenary discussion on WG meeting conduct

A late response. I was at the plenary and listened to the discussion.

Henning published an interesting article that IMHO relates to this topic, namely
https://arxiv.org/pdf/1809.00623.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__arxiv.org_pdf_1809.00623.pdf&d=DwQBaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=12BBhXvQftv9EY658mlmqRzSTUUNdikxXGYhrg3UIoM&s=0FhJ_W8DHLt480PXi81nnqi2dQM-z4dHy2yH96Ag244&e=>

From the abstract: "Telecommunications carriers, in particular, have become akin to airlines, largely operating equipment designed by others, with emphasis on marketing, not innovation"
(While I do not agree with everything he says in that article he does have a couple of good points.)

In a nutshell, I think the problem is the following: We are seeing telco engineers with lots of great ideas coming to the IETF but unfortunately their companies are not developing new products or it takes them forever. This leads to some frustration.
On the other hand, we are also seeing new, big players emerge and they also come to the IETF. They would like to standardize technology they are planning to deploy or, often, are deploying already. Feedback from others, who have little skin in the game, is a waste of time for them. So, they are also frustrated.

In the end we have folks who "felt that they were treated inappropriately" on both sides. Think about your last few IETF meetings and you will notice that you have seen some of these situations in WG meetings, at least I did.

Ciao
Hannes

Gesendet: Donnerstag, 13. Dezember 2018 um 19:23 Uhr
Von: "BRUNGARD, DEBORAH A" <db3546@att.com<mailto:db3546@att.com>>
An: "wgchairs@ietf.org<mailto:wgchairs@ietf.org>" <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
Betreff: IETF103 Plenary discussion on WG meeting conduct
WG Chairs,

At Bangkokā€™s plenary meeting, during the IESG mike session, we had a couple of people commenting on their experience at working group meetings. Some people felt that they were treated inappropriately, that they were personally criticized vs. technically, or were simply told their idea was discussed before vs. a short summary so as to understand why it was rejected.

We are wondering what we can do to help. On the new IETF Note Well slide, we do have a bullet:
ā€¢ As a participant or attendee, you agree to work respectfully with other participants; please contact the ombudsteam
(https://www.ietf.org/contact/ombudsteam/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_contact_ombudsteam_&d=DwMBaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=12BBhXvQftv9EY658mlmqRzSTUUNdikxXGYhrg3UIoM&s=wR5Z1-oSt-VMR5pJutT6CslDW40HqyoaYqj_W2abwFI&e=>) if you have questions or concerns about this.

The slide references BCP 25.

We are considering updating the WG Chair training with guidance on how to handle difficult interactions in the meeting. Also, on the newcomers training to ensure more guidance on how to prepare for a meeting, mike interactions, bringing ā€œnew ideasā€. For both trainings, we will have information to say someone can have follow-up discussion with a chair and can also talk with an AD. We want to be sure that you as Chairs know too, you can also escalate to us.

We are planning to send a mail to the ietf-list to follow-up on the comments and would like to first have discussion with you on your perception of your meetings and possible ideas for responding.

Feel free to respond on this list, send mail to iesg@ietf.org<mailto:iesg@ietf.org>, or send mail to an individual AD with your views.

IESG (scribe ā€“ Deborah)