
From nobody Sun Aug  1 07:50:59 2021
Return-Path: <rsalz@akamai.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121483A3F3E for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 07:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 iIZD5V8akCDx for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 07:50:51 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 B25DD3A3F41 for <111attendees@ietf.org>; Sun,  1 Aug 2021 07:50:50 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 171EnnOm006899; Sun, 1 Aug 2021 15:50:48 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=3plj9O4HnaETk6e71kQu24fie6SDcbt6qLAAoaoeNkU=; b=CPL3rwh8fm5rwsISO9qO3fUzSpaoe0EF3ZzM7crwIJHkDs267VlgsnVs5tz/H3DBeQsa TtnMCsSjQYss9n2tm+sh5HAHHYitmSDspYWWG6ahGs45bO4sSLZ3CfiHLiRz4welScH1 kx4/UwwovazKMfKee6qMRnrgmC8QnFA6cb03D/VE5WT/scdVlVz/VRG42bDlyEoiGKZm MJweMrzL9hxQCgWW2+xB//JRDNic9VCiFcy0mtztMo4pCiifkZTQ8+h5QKSI19MxuvVX Fr/ytnIfSeN+eJude5aHTLlJy/f/hIHfZlvxWJ5ei8vYaoGHvK3GAMYjPh2hKrbs/XO0 tA== 
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 3a4xxecbsx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 01 Aug 2021 15:50:48 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 171EnpTa026234; Sun, 1 Aug 2021 10:50:47 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.115]) by prod-mail-ppoint7.akamai.com with ESMTP id 3a51uyper8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 01 Aug 2021 10:50:47 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.165.121) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Sun, 1 Aug 2021 09:50:46 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.023; Sun, 1 Aug 2021 09:50:46 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: John Levine <ietf@johnlevine.com>, "111attendees@ietf.org" <111attendees@ietf.org>
CC: "jmh@joelhalpern.com" <jmh@joelhalpern.com>
Thread-Topic: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
Thread-Index: AQHXhYU2DXfZ4WM+WE6D1qot4aPtwqtcYkAAgAAYYgCAATthgIAAD+GAgAAJKoCAAP/igA==
Date: Sun, 1 Aug 2021 14:50:45 +0000
Message-ID: <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy>
In-Reply-To: <20210731193455.C04E625657CF@ary.qy>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.51.21071101
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7A3C1B3E517B954ABB83EAB4DA8D7365@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-01_02:2021-07-30, 2021-08-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 spamscore=0 mlxlogscore=656 malwarescore=0 mlxscore=0 suspectscore=0 phishscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108010109
X-Proofpoint-GUID: 0Ha4vwzXfESvb82-eejWeHlIOw0y5C__
X-Proofpoint-ORIG-GUID: 0Ha4vwzXfESvb82-eejWeHlIOw0y5C__
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-01_02:2021-07-30, 2021-08-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 priorityscore=1501 impostorscore=0 bulkscore=0 suspectscore=0 mlxscore=0 adultscore=0 clxscore=1011 mlxlogscore=618 spamscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108010109
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.33) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint7
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/fug7g46_6DTEbGDtMuSLoNg5Wqg>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 14:50:56 -0000

PiAgIFRoZXNlIGFyZSB0aGUgZm9ybWFsIG1pbnV0ZXMgb2Ygb3VyIG1lZXRpbmdzLiAgSSBkb24n
dCB0aGluayBpdCdzIHVucmVhc29uYWJsZSB0byBleHBlY3QgdGhhdCBtaW5pbWFsDQogICAgbGV2
ZWwgb2YgYWNjb3VudGFiaWxpdHkgZnJvbSB0aGUgcGVvcGxlIHdyaXRpbmcgdGhlbS4NCg0KTW9y
ZSB0aGFuIHRoYXQsIHlvdSBkbyBub3Qgd2FudCBzb21lIHJhbmRvbSB1bmF1dGhlbnRpY2F0ZWQg
cGVyc29uIGNoYW5naW5nIHRoZWlyIG5hbWUgdG8gc29tZXRoaW5nIGxpa2UgdGhlIHZvbHVudGVl
ciBtaW51dGUtdGFrZXIgYW5kIG1ha2luZyBtb2RpZmljYXRpb25zLg0KDQoNCg==


From nobody Sun Aug  1 08:47:26 2021
Return-Path: <cabo@tzi.org>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D13703A4012; Sun,  1 Aug 2021 08:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 CzYHESdXzmQz; Sun,  1 Aug 2021 08:47:22 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE67A3A400A; Sun,  1 Aug 2021 08:47:21 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Gd59b3Zdrz31Ml; Sun,  1 Aug 2021 17:47:14 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
Date: Sun, 1 Aug 2021 17:47:08 +0200
Cc: "111attendees@ietf.org" <111attendees@ietf.org>
X-Mao-Original-Outgoing-Id: 649525628.790176-9ed54a48aa6675089aa655fd59178deb
Content-Transfer-Encoding: quoted-printable
Message-Id: <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
To: Tools Discussion <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/dR-dDfTmTjPSp8PLvkT_H9_bij0>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 15:47:25 -0000

OK, so the summary of the 111attendees discussion is that we don=E2=80=99t=
 want unauthenticated write access to meeting notes.  Less =
well-discussed is that the authorization rule is that anyone with a =
datatracker account has write access, but I think that implementing =
anything more granular (e.g., attendee status for the meeting that =
generated the minutes) would be actual work.

The authorization rule seems to correspond to CodiMD=E2=80=99s =
=E2=80=9Ceditable=E2=80=9D, which is therefore the setting we should =
choose for meeting notes.  Whether we can do that automatically from the =
place where the meetings are assigned codimd names or have to do this =
manually is then a procedural thing to be discussed on tools-discuss.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Aug  1 13:23:16 2021
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C18733A0D6E; Sun,  1 Aug 2021 13:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cs.tcd.ie
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 N4c3tQGewHZK; Sun,  1 Aug 2021 13:23:08 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2139.outbound.protection.outlook.com [40.107.22.139]) (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 67F3F3A0D6B; Sun,  1 Aug 2021 13:23:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bFAwKRYHjYfHgZnmiVFZvElSuB+jkMDuK67ufX5XJZOGdbZ85rIvhXj9wwgM7+Fqu6arWBRn/ye3z06GFcywknXLeqU0aduzQgwsusENgvdZ/NPwtAZQ2KPPOSjRlW6jpdIiPyNrYiIwF/bp66v7b8t3ctKECZ6hS5akAjdp73BNLwQE83chyVcaxBt3Iyln9vOdy3d1AFUuv0jzwOJ8FEH1/IXMf6ofQxpyyNprDYnkRHHxQk2EVJvmWwhqsspE0HHG54R66W/9iuvB2+KHG1RhKknc+4tEjIM2aX81MqZbHGI1I5PypwLQcGGXX4IWd1oWSot0pPj5f2SMJBwAvQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kH+TqWDEAim7JM4UelgYjWQs/rHqbsnyBrA+M8U8eCo=; b=hs66Ry84igmAdwoGHiewALTO3JuvIMAFrsnj5IGTu3k21L+iHQDpp9N95mp93n3FGaibzAFxPHKtzwMKxwZfRPRL8tQHi/ex+8TplJxiQ6DHBHDttDwO9STZBUWoDvXodqWoRo0Px12xcFMqtDW9+dymLBa3XKykSnYPcbMv0eWkt5So8tfUdEUswnIjaXO2QkZG8u48quZZBIz8WdSKGs0LC0KuCuJrHULq+O+KYdv8cYrhHhUGHa2ccFGNdLsuSaxPCfFlnUFS3fiq9ha5g0flRuandDzmsZM2VZUaes2BWFhwavDBskQHmuOKZPGmowBJCEk7LJkSGdq96OwlKg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cs.tcd.ie; dmarc=pass action=none header.from=cs.tcd.ie; dkim=pass header.d=cs.tcd.ie; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.tcd.ie; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kH+TqWDEAim7JM4UelgYjWQs/rHqbsnyBrA+M8U8eCo=; b=Yy6WcntMdMIVMMnpWQXHpgLNgfY4SxSFhWvr3hxHErGSEi3Y/eFgz8goUOw1M6v2AC3JRsL7PQSUOiL8SW9l7qGh5T4qVifaWtkbU58bIX5PFQAGsco4iQjLqnOvypf0UQRQRn8YeCxmiUVWcv8MgmsyOUiLY5gu15SA8F4KwgaRDUZzp9hkHW3bxjE3fk7aEFn2+3ceGMquBYicieSJAYJ7zQPYboJAcv6Mn26TBSyo8hTz7zXE27oMtoQAnN4IcTPB/DADFhwj/l1jpydyfsHTKIuFB3P//zfjXNXomVhUGEdrOT+AMGPnL8kN6JOoja89pDZXGUvtEsfD2Ct7gg==
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cs.tcd.ie;
Received: from DB7PR02MB5113.eurprd02.prod.outlook.com (2603:10a6:10:77::15) by DB9PR02MB6779.eurprd02.prod.outlook.com (2603:10a6:10:1f8::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.21; Sun, 1 Aug 2021 20:23:02 +0000
Received: from DB7PR02MB5113.eurprd02.prod.outlook.com ([fe80::4198:a9d1:7246:8272]) by DB7PR02MB5113.eurprd02.prod.outlook.com ([fe80::4198:a9d1:7246:8272%3]) with mapi id 15.20.4373.026; Sun, 1 Aug 2021 20:23:02 +0000
To: Carsten Bormann <cabo@tzi.org>, Tools Discussion <tools-discuss@ietf.org>
Cc: "111attendees@ietf.org" <111attendees@ietf.org>
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com> <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie>
Date: Sun, 1 Aug 2021 21:23:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
In-Reply-To: <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QG0pwmoA2zGhoG0IUhsjgMIWLx8KxYAYA"
X-ClientProxiedBy: DBBPR09CA0036.eurprd09.prod.outlook.com (2603:10a6:10:d4::24) To DB7PR02MB5113.eurprd02.prod.outlook.com (2603:10a6:10:77::15)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [10.244.2.119] (95.45.153.252) by DBBPR09CA0036.eurprd09.prod.outlook.com (2603:10a6:10:d4::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.18 via Frontend Transport; Sun, 1 Aug 2021 20:23:02 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: fe447462-dcf2-40fc-8ae9-08d9552a298d
X-MS-TrafficTypeDiagnostic: DB9PR02MB6779:
X-MS-Exchange-SharedMailbox-RoutingAgent-Processed: True
X-Microsoft-Antispam-PRVS: <DB9PR02MB6779ACE5CAF9E8D2991E43E4A8EE9@DB9PR02MB6779.eurprd02.prod.outlook.com>
X-TCD-Routed-via-EOP: Routed via EOP
X-TCD-ROUTED: Passed-Transport-Routing-Rules
X-MS-Oob-TLC-OOBClassifiers: OLM:741;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: ztnojvtQcO4xlR8t3Pplo329Bjz1csXocQfadUj6fHkjz/HoyOG4KU6nmKlybanVaTRPuMjC6DMU4Advxcyor4JYRQWFbVdzhjNRE9757CRxpgkiDgks33ccZTdDWSbxl/kkg601fGmy8KuUyFotr8Y9dlsyRxTFkY5XB3rufnRKWNFsRR1DnHUOFF0V2lvaEhQL2/EsfoHaMKAtth61GK+rF5bpC8XurfGNyDCrL25jad+hTylB+ivnC3rR4Gne/jpzJT3xWu4Xln5FwiOTJsDt1knHrvENfsRiCH3+osE+heuf5l10sx5JkHQ10H9twVUWAdcYP7A33YI/iG4Eb63WCAQnFhPsjxWQyLFlxavKtmX0LjjhGu+mZLokSUDWoaFIvpZst2tZhs9CfHBmp4twbRLgQMVv4dAeqnvJi9VaqG0o9ErCW0wryHcfEUvRXeaq1lISf+DYnq/Li/BvTPYnhrVwbSi3zdNtGJ4m9Z6oZmdOPNxa61vFVAcfPxNERF7vIwg8kEnGrErExZVA1QHUaDCaT0WGftmyGhsxAE7dLmOu4OQEQpZmWJyZOgvl3q64TjsllmR3FqRQ6DTXqM86b3j0ssf3Mfmu/n4iD9cjrkLIgumDwS34jioHOFUuxkBNNjZgxEgvUd943W+8wh2ew2PYy02+Gm7BeGIz/V1SIvVbJ+J5KbejCy8YILRTqavmSpllAFeDggapPPRFd7pLet8PouycbgePjOTD7CI=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DB7PR02MB5113.eurprd02.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(316002)(786003)(16576012)(508600001)(2616005)(956004)(8676002)(8936002)(2906002)(38100700002)(26005)(31686004)(110136005)(21480400003)(6486002)(235185007)(86362001)(53546011)(66476007)(66946007)(66556008)(66616009)(83380400001)(4326008)(186003)(5660300002)(44832011)(31696002)(36756003)(33964004)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?eE5SN2dwM3pRR0FSMlRTQjNOQVRCR3FucjZtbDc2Z25PNmJYRy92akhWa25s?= =?utf-8?B?WFFITytBdm5KNW5VeWFPTnFITzFvYVR3Vk5Wa0krTVRYcTBYM3RFQU9UeklD?= =?utf-8?B?cHpoYlVuOFlCeFk3bXZsQVF0dVk5VHpwOWFRTnVGOHV2Lzh3aVRmY2dTV3ZY?= =?utf-8?B?TDdkU2VGY0JvY3kwQ28xWmQ3ZlVibm5BSVNYQ3N0L2V0TFo5OHBFYng5M01w?= =?utf-8?B?TUpFeG1rTjA2bjJIcFhvMEtnUDRsU012N3JCR3kwajVEWDd4WDUzb3dRcXpQ?= =?utf-8?B?NHhoZk81bk5GK3JLS1FrZnNBZkFRVE9KUUdVWjB2Q09HZ0pocGxxdUE1dnJn?= =?utf-8?B?T1pveFhxZDBzMkFRS0dRLzJIQThPakYvdXhBQVhWRVI3TUNQS2ZLaUY1NVpm?= =?utf-8?B?ZnVjcUl4V2dDWkplc1F2Q0pNalZyOGMyZGNlWUNLd1hJYnc1UENiMVBEbTM5?= =?utf-8?B?RGdLMFZleEd4bS9IdTJjRVJXck4zeWtrUU5kMDBlbFdhc2c5TTdvN3l5dkVn?= =?utf-8?B?LzVJUy8vMlRrTUtRaC9CWVJxcm5Da0NUL3VDNnpoOFpyS2VsRDF1TXZnc0ts?= =?utf-8?B?R1MrNVpoeDA4UE43TDZVZjJ5UmkzWVlJSG5GMkoxZjg1MzZ5TEpZUjM2dUJF?= =?utf-8?B?bXYvMVBsVlYyMXJxTkF1VGQ3QUpUZ05KOGNCOUNmQWhPaTNJb3hiTitrRmM4?= =?utf-8?B?UzVFb05hd000SVp3VTJXd2V4V09sbEdXejRWZHFRNGZ6MndsMkRzWnFSWEZF?= =?utf-8?B?akU4M0tWRTNJZ0tvM1hTbGE4NDhaSVd0OW1Hck9lTXZkU0hCMm04TllGRHJj?= =?utf-8?B?Q3R4UEQ2Z2lkRU1RUGpLWnpiSS9MUk1QTk5KWEFkM3hZUEtMUlpTeFptZVRp?= =?utf-8?B?RzYwcHZCK0RsNnVjdFU2RVk0NEhSWGcxVXhVRzhFRStaSVk0SlRpQUNFYUlH?= =?utf-8?B?K3R2MDUvbm9oR3VxM2hYS2ptazdsZi80ZDVyaEtOV0VGVURMaVpjR0twUmxx?= =?utf-8?B?WmhNZFRXQmJ5Vml0cWd0a05XNnRyRTlXOEI1Q3JGNnVnOU5nQkkxcEYrczJN?= =?utf-8?B?ZW9PV3JVWDl1NlJhWFJncTdSaTBmeWRCckJVdEo3Q1pLeFJxblNwRXRuWDdZ?= =?utf-8?B?cVp4M251dVRDazQyV1BrVStZWlpBVFR1WTFjUk1aV0kxYXVuQXJ6MHFURXBQ?= =?utf-8?B?OEJoZm1vbytNSm84U0o4RkoybGp1dEVXYTdTenU0S3NlK3R3KzZFOVd1TU4x?= =?utf-8?B?YzQ0M3F3Smh6SkdEOUNIM3NUUnlSNXU3NTYwMTFUL0xBTWVpQWtVKzN3RG9q?= =?utf-8?B?UEUxSi9lVmFYREVHbkVNUk5neW9kYTFUME9TRzh2TVd3ZDhyaEVFdFZTSnJQ?= =?utf-8?B?RkhUSXgrM2RHSEF4cEZzRml4clNsSGVDVVpyTCtqcDlYVlhtT0kxSnJXdFdp?= =?utf-8?B?V01CbUpIRnNNU2ZWQjc4bVg4MmZWYlI5TTYvS2FVYVhGYTJneHlyWVNCRCs5?= =?utf-8?B?R3A5bmpVMXExdlJTenRwNzJzMm5qa2M3WDBTeGJsR253TlZaN3dMVGI5akNR?= =?utf-8?B?ZjJseFJwMFcxWjVURm84cm9iWkQwSDl1K0JySE94aU91MWpvdGJ5LzF2RTQy?= =?utf-8?B?aVgyL2hMSG12SWd5UXB2S3NXcHAvcnB2bFhJWWxOMzlqNUFjYnhDNWZmdVNk?= =?utf-8?B?ME52dkNOYVFBRUI3MkJnTVBhYkxNalorWmsxaU5NLzlaMTJ1ekRpNTk3UDIz?= =?utf-8?Q?PXa2O2n0Pz54N54+ShdBXadNZzMUXb1AQLPx3eb?=
X-OriginatorOrg: cs.tcd.ie
X-MS-Exchange-CrossTenant-Network-Message-Id: fe447462-dcf2-40fc-8ae9-08d9552a298d
X-MS-Exchange-CrossTenant-AuthSource: DB7PR02MB5113.eurprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Aug 2021 20:23:02.4944 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: d595be8d-b306-45f4-8064-9e5b82fbe52b
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 9U5IX2Um0K0gY/9PV2Ce4ZFXQvYiOCB+60scxgOWw6RcBqoTQxD6r5165cDsJ4TQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB9PR02MB6779
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/AuYfiZS7LNl0FImmpc8JMf0eJDo>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 20:23:15 -0000

--QG0pwmoA2zGhoG0IUhsjgMIWLx8KxYAYA
Content-Type: multipart/mixed; boundary="Lw0HBLITduhD0YIRdjvcxxkkRusILmEaJ";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Carsten Bormann <cabo@tzi.org>, Tools Discussion <tools-discuss@ietf.org>
Cc: "111attendees@ietf.org" <111attendees@ietf.org>
Message-ID: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting
 notes who are not logged in?
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com>
 <20210731193455.C04E625657CF@ary.qy>
 <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
 <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
In-Reply-To: <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>

--Lw0HBLITduhD0YIRdjvcxxkkRusILmEaJ
Content-Type: multipart/mixed;
 boundary="------------ECF88EFDDC64BFFD0996494E"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------ECF88EFDDC64BFFD0996494E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable



On 01/08/2021 16:47, Carsten Bormann wrote:
> OK, so the summary of the 111attendees discussion is that we don=E2=80=99=
t
> want unauthenticated write access to meeting notes.
Really? Seems to me the risk isn't significant enough to make
someone do work and there's plenty of opportunity to read the
draft meeting notes. I don't really object to requiring note
takers be authenticated but it doesn't seem that worthwhile.

S.

--------------ECF88EFDDC64BFFD0996494E
Content-Type: application/pgp-keys;
 name="OpenPGP_0x5AB2FAF17B172BEA.asc"
Content-Transfer-Encoding: quoted-printable
Content-Description: OpenPGP public key
Content-Disposition: attachment;
 filename="OpenPGP_0x5AB2FAF17B172BEA.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

xsFNBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh5=
Cg8
gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+QtaFq=
978
CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKrEMjmL5VGu=
D/Q
9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZUbUv0Q+DnQAB/4=
tNn
cejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqOVz+7L+WiVfxLbeVqB=
wV+
4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJgb097ZaNyuY1ETghVB5Uir=
1GC
YChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k4LyM2lp5FmBKjG7cGcpBGmWav=
ACY
Ea7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK7uB7E7HlVE1IM1zNkVTYYGkKreU8D=
VQu
8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5XiHzFPJleXc0ksb9SkJokAfwTSZzTxeQPER=
8la
5lsEEPbU/cDTcwARAQABzSFTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW5AamVsbC5pZT7CwX0EE=
wEI
ACcFAlo9UYwCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQWrL68XsXK+qGC=
xAA
pYHWYgGOIL3G6/OpkejdAkQoCVQAK8LJUSf6vzwost4iVfxIKcKW/3RqKNKkrRl8beJ7j1CWX=
Az9
+VXAOsE9+zNxXIDgGA7HlvJnhffl+qwibVgiHgUcJFhCSbBrsjC+1uULaTU8zYEyET//GOGPL=
F+X
+degkE/sesh4zcEAjF7fGPnlncdCCH3tvPZZsdTcjwOCRVonKsDgQzBTCMz/RPBfEFX44HZx4=
g1U
QAcCA4xlucY8QkJEyCrSNGpGnvGK8DcGSmnstl1/a9fnlhpdFxieX3oY2phJ1WKkYTn6Advre=
k3U
P71CKxpgtPmkd3iUUz/VZa0Cv6YxQXskspRDVEvdCMYSQBtJPQ4y2+5UxVR9GIQXenwYp9AP2=
niv
Voh+ITsDWWeWnnvYMq07rSDjq0nGdj41MJkNX+Yb2PXVyXItcj5ybE3T2+y3pSBGFEZYJGuaL=
4Nw
tBJFMOdOtBmUOPbetS2971EL3Izxb7ibOZWDwexv+8R6SWYfP1wVN3p46RyBQuXqJV8ccE11m=
6vt
ZTGSYgnLUUFZMRQYH+0hwuYe0T3AA18xDdSYsa8vovCCd3l5S4UNzIM2PMChqGrEzKapUpZg7=
+8A
CcxRU3b9Ihd7WYjJ+pQPCoWYKozvtEvenbNpE/govO/ED3B14e+R2yevRPjRrsN7PJzSf15fQ=
LvC
wFwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLrSwf+MIHbFRQ4O5cmLYR5sIByWelN3SuRN/gW8=
rpK
o9OkCz6An8uV/iCXy5tNMLzzi0BFl8f22DwBcC5qy9qnlIAdogWam1qWoTAoAD8veEqmuKhYr=
qJs
CcAyNrKYmK0hP3rpHxx1LySDmKYXmw/8qtBXKHTouMm+5tSsznhykRMTAAr2p7PSaHgo+hIVa=
W/r
KSspHjDhhZS+G9mtOZad1IH29M6G1Q1NCO0Ywe8krKLQIAQlFxtgvOqpPOZNzeKBa/+KbE8TG=
gMW
rkOhC8OeEM5PVzdDhlhD9kPzB/pCKDF5DofJ/ZRqnDpbKPQ0bsW38AOig3kOc0A27awiBEw3u=
rqR
1cLBcwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g1MSBQJbtyScAAoJEBDvedn9g1MSI/oP/=
0A9
J9nrnBMqZpm857lfYWw+rshLK+tyeP4OQeOqnDFvs9jePpcyJLG3DF2r6VbVKPQq+AE6Uf5hc=
JBD
EN6BjEhRPSbLcqG3A1cz/nNwm8rPmNp+oKhmaBBQGxwciMLmzgynsDydnjPpMyEs04zvsbsl4=
vrp
2095o105l8KcrrxQrioFjbwveGwHQK9bxJKhx9D+gIk+MouBur45UDKTZkMZrr9FGrtkyXCGA=
xvK
dcNC5Oa8z9sj1rcUJfG/OpVAMWhArdlZbFUQyoX6pU2Zb1CR2qpWAVerGSfBhmfCyStjARqaK=
xlf
tjO+Bj3Jj73Cr5eqej3qB5+V4BCsPjr4RLvVbYUCPsRdxWc+nBLlfVYkRURu21g1hFm5KFPjg=
Uky
o1s4vjUOY8DyI+xLGF7f/IhUBG6l+Vswhpwu7ydalZkeFiPx5xna5NfbEYxvsIf71DvipGvIO=
aHv
X4egWoFgm8n/9c3rcMxJtpwHPSsUt5dgLsyu6VE0IbvOAc3dN7CWJ355DVFJq9Zg2YVf0izSp=
yyz
JeGsgkfjW6xpmdvZxuT2UcN4BTcm6vYqueASGrb3lfhzC5gpeVsc/MoSjTS65vNWbpzONZWMZ=
uLE
FraxWJzC0JrDK3NCd0VN3kstqGkVbUIiYOnUm8Vu4zoVMLlGWzHLIGoPRG2nRezn1YyNfyb5w=
sDc
BBABCgAGBQJbxcflAAoJEGo7ETk8pK1gE7QL/ApC5P68W5DrI1787WJVZv1u4t/g39vTr7Xer=
3UM
TVQg10vpa7pmqOGhjIDzDMg3Pe3K3M7fVzfAlUA1qw6ne4RCueVoRKpubeF4AlYbMr0K6hNCP=
jt5
uAxmbBVuejKTc6pru5rv5gKL0nDbr+Snft5xt7juBLSSimw0/41sZnkjCxo9rF/RA/v6+uWyK=
171
RKmsEYu8fFtw1eqUNt/Xj792TUixE3pxXheNtQtZGk/9P3W83ChhG4Fh5EQsn0pIh9wZIAbMR=
Lpg
RKyW87fWHZC8/YH8h7afarvn9Thl5pFUldCe22mNJj6KLChn2aEHQd+PdY1GBpZEcmNEUPuov=
wza
tM0h64hCzTm41eDqRfihZVBT7TbfXQnv8rywa42Mk756RGzzEZcQEhwQXZcMQUfxIQQ2VyJo0=
zG3
6VdZTQF7TF/4Lz7/3cJ56jOIm+dwPXtu+C2wAQuD4USOLt4JWPYpqzDfHYJIND/497P9Z9SuQ=
eah
r2ez3DRBg3qsHEjBV80yU3RlcGhlbiBGYXJyZWxsICgyMDE3KSA8c3RlcGhlbi5mYXJyZWxsQ=
GNz
LnRjZC5pZT7CwYAEEwEIACoCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AFAlo+o=
3cC
GQEACgkQWrL68XsXK+qO0A//ZsfQzyXrZlu/eEV5jU620yeOM3P7SW3C3UQYdCgZ/TlvxGgKo=
w5o
DSXgjMiUyq9csGqbPBxlDYSxFZHNeDVKYIuP2ZK24tw5k6duTh4+sFwUualTMlcp0zBCIzn3h=
Rcs
RvuPKHfl5+6oOi0+xqx3jX/s/69L/fvHmdSKet5LIUAxoYaZkTCruFrPWb01tgAl5JExWkhmC=
Y98
iD+EeiIMAWBjMw1xV+p0uCwNbN6XDzcToK7wsm+tAIiWUy3DpP60a6WbVwdV0HNt2WZq5U5Jd=
h2k
4S+sN2CnYk4tTW7jHjsWarV3FLISCOObADZuB7ljU4kYfdwZ+WzenXY4LGlxGQSlAblGjwZe4=
EIk
CXAJUtzJhoFUuGaF/PlWjxqV3UFRcgTERZTijguVyREre8GNERNgvDxZvuXssEjvz9X5JfcIZ=
DIJ
pdzhLiEIj9noUbfx1SzB5KDPQj0O7elMHa1671/rwWcpGr/MfVPTOik4H7F8rcVJelceZTzC4=
tvy
a7M+jM4fyFWWt8Y4atTixUiP7U9o4uBZCQ0GzvsmFA4XLqn2pA5rVizMXnGbGOjufAP/efEJ4=
ul3
qvjYe8ye8DXEDjKAxo/tuHYtk19XCi83QzFhWls5TT+XQeVTMEvVqo9Wek8yoxo67qvLKKqIc=
G9g
ivQd8MxYNAbNYgSPtkbhZ8TCwFwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLzHAgAlWT6NXEGt=
w/r
1miKNGcopzvzILQ9oB8rKI9U9EL6tOf/y2V5oYee/GyQDb3ZdoPxxYYcJf+RyiH1nMoqUIZiZ=
Jaf
3bJXinDZ5+AdfE++UR2NBvqaNyC6u3r24jo1B/sagKbYtWgsYtRqHLD4IWi37MZrVyjBuF7u1=
4Q0
7+uhjq6mX2O/tHpCYw/Q82tbeTRPyUf1WQOAfD1kfBpW9PvAva5Iw9FWeXpCXRzwxnCZhYfGf=
qtu
Sw6CPBYLdbikqML6FZ7EDuTBb/8um1wK7Y9bgeIQC+CYjhYB5RXa1tDJRab2Js4luCvSR0w/C=
gHw
26293tlve2Q6UTrmHxP5U22DlsLBfQQTAQgAJwUCWj1QMgIbAwUJCZQmAAULCQgHAgYVCAkKC=
wIE
FgIDAQIeAQIXgAAKCRBasvrxexcr6tJpD/4rrILH+meP07vrx8wW5eYuqCiPGYnh/CXxIF8eL=
rfb
e5d4QRgtq+w6UeQPMyzKRIRiCoBXB2oJLBZHyxBPxZlg33dTMrEGn8QWKx2iNuz9rZMXyOSWF=
etu
O01d/aUPd5BnbLbIyK5of8xCQlXM6KH8bc+9gQ7edR9mfLTdvBf2FR522hg8BRBM1imKc3vO8=
v39
+qIHHRjuiwxBBCAOhHtHRsZXripS0uFA07dM46Oi/E8osjx6fQt/lH5z/PN+2adxYSrLSAXfr=
1oD
3RxYNhuWgyGFL64/VCQb1YGjf0Z5MBPnWm9jgUoOY5K9eNSS0L83WeJjlF5+Q/WOgB+rb49Pr=
m2D
Feo9+S9f2V53Llz1WIspXJg6f+n9lmHE94MfQj1GAHCzI0FeL19lvM+LhD8jJSCbhrC3+yoby=
y/A
UOs5Z3E+njjX1FF/VCVAs6iOa6i+XG+Y1hh3ir2y1kckJ5auT10MSU8GEZu9ayU4M3o3N9yxO=
jao
P0NuQ4MMLL/n/u4u94AeZaHPNBXn/hVfVRRmpRXtGKvJtFAEppGEYezB+bLKIm6XlpPkhnwYz=
leL
Z7AMEco2C6QM8QPB3g3JpS3sqRhA5rEP4lL16BmijmF+CHoPE/zwgKZbKpyVDqvIW5IDgvfIC=
2X4
pbZDRvGIUKaGSB4+ksZgUUnNyvfQr2p7jsLBcwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g=
1MS
BQJbtySbAAoJEBDvedn9g1MSeKkQAJm44jt1kwHgQgeDBKdjdvl0AjE0xVEQxriZ6lP/l//34=
YT0
auFfzsYIrChSpQXAEtobBAr4Ohw1Us+BZe+H5P8vm6LRuPwozC3SjwfX4Iec8+9ot6tIVg4sb=
edD
Sgb/CCFVjsmIGcQ1P73JLJTBJ6mxYCV/gn3QC6bwDOFo7kD9FDHCjRN8XfhHQ4Q9cYyt06uF3=
1qG
/aumgWYC9geCGgAwiHgwxNYb9GoJ0iZjCROwbYvLTcQgsVUW2bTmsVR13UVKDsdl02sRV7qcV=
YW6
R0a3Ra8KudX+nt25H5DRGd382KZ5W8pydsy/viTvD9z6v0ulChBYxAedIvGIClrhbxlLEPmIg=
4Im
VOLGqsUgVm32J95WOjEkk4PEZ12xSDBtwhSJqmJNboWlfmw43KdIbY8zNhffIO3N6O7FsdGxm=
qyH
eLoTpqY+ySVUPpbuyW8ujnI/J//+6hdTZ9dQsEJQlWngKuWOQ5ma58MPSN88zllsqhZAFQjNx=
qnk
SzL6ZQ+v/jvuRRe16B80AeO55DsmbWsMv/YLLD1mSi7+Khy2EtMBhgojWwrGMvdLN6X3mnzNJ=
Esc
YyLxM9tSk+iySP2sLthK0BVgpAzBSdaf/ezIz60P+neHDzteNFf8Mn7lmgYk1amvZoJ29s5+n=
2Hw
xyRL5dVMyMdyQmntubbctfqrZ0tIwsDcBBABCgAGBQJbxcflAAoJEGo7ETk8pK1gnCYMAJY4F=
eIY
jlIXGghFWzsB4fYwK1+iaFpU3fSto5qcrqVtVPjXpwqczqBWeXGyQxiB0kan4OVAXydIeaP8E=
AuF
CA7paP3s9STLJBO3KurkwyRkPW5zo0X7xVqaVToRsX2Ul98KVJoHYQD1KdezEtwlvpNwiiBr4=
2AY
R751Vm6JBVAbQXuFpB3c8bUV0OkkRxNFtL8/2PieHar58n5dntGkbPlPkztahsFqktgacIgXH=
X5v
aT+7YeeZ1DWLOYjGO0wNhkOSeroCmxwJUikU7joBp823L7r5KfpqWTPpSCzVstQKZUGmmoE1q=
Csw
Y/Ud5wvp9SccpIILkRXj0rZRtfnE5MpL3hjmtNzfDd9qIsJtBJlSB2hZwAsVm1l+EWN9hG3tq=
yA4
3niUMy2n6q690of3berSiQ+kvY/aC9Hx8I+bKzOV9/J2VUTqfaPZa4Uy2rVX5Q2p69n/PMj7m=
Eer
0rCL3j9V16J9c+s0BSkXoKdtYdB0TWVhBgUybd9qtYcwHWvhP80uU3RlcGhlbiBGYXJyZWxsI=
Dxz
dGVwaGVuQHRvbGVyYW50bmV0d29ya3MuY29tPsLBfQQTAQgAJwUCWj1RWgIbAwUJCZQmAAULC=
QgH
AgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6jscEADEcB0WQEZn2AkrzDs1RhL0Lp6cZ=
i0B
igofkbcGfdhJyMSs19C0dhvncrAFClVI6/Udw3yFtDyYtOCf2W3M3A1K6/RfEizCLzTsdFIhn=
i9g
OJLlUpXViQtgrlstjk7hqVV3Ooz4BlCqS4cG7rfqf4LQQPpTAuFUEV9I28FBUB2irqC+v4gTy=
sIg
pMw0bA1yBU9sX5jE/tRkzqnuzZrkwiobDtRFJ9qp+7O2JtcY4EsVtLAsaodJKc5cF8R4OvB1n=
66v
xxcgg9Eh4JNWZ47xsaCmAGo1Bcb2jIY35OtgAL7gCGLRSMKTtAaPy1/fEgIqhCljJ9x40Fkn/=
3r2
BX21WC9HFSPFTBz2RluLRzxdgxOrkYK8EiHUPoE5b1AEzZKw2AbeXfr57f5zYsN3IqfbQLUjM=
YtU
N1wK3Pjb+idD972wyXMWt8uOzlI7b9Ocu+nYm2whBfJv9Pmp3QYTmPz+LB9lH65VNVUSxSXVr=
5iW
XO3qx1HtEiGEqkporMQCTh3T5Ud3PvMSRBFFKNs9WhJ/Lxz+SV30WLwG6dr5mQqlzAhb4Phc/=
zek
ZyXRdS/oDKrBLUucS36O//49JeyRi1QvOfxnfmIqRIAf/k3PoYJmTo5E82//r5Qj3YGlRu78b=
a0H
Arxs+ACD6AnEHHcbswpbtVEKYzlSu0Ar0Dc7vRWM/IyQdMLAXAQQAQgABgUCWj1SoAAKCRAvP=
Ic2
gF+NosIsB/9f/29FNla3BJfGIEIDnhrqGD0i9bSa89SqBd++uG06TQgW5wsqtNcrwn81yZTq6=
XE6
i9VtD4GKfqC0d4KZJr9bnbeD81cI64VOdL8zJWJs0vj5EIXCobKyX74Kb4uePUyZqwT2Q74I1=
16u
/HwA9/FXsPo5isbh4ZqD4t0VHpWkmfq1FPT9a/JPyX46qKqB2Fce/7Qy+SQP1NfkuUlbhUH/J=
G9a
SSYvk3lznNiH41x9M+FDlL106itXOubrl3oi2fT3fsSedq7uzt+IV0DQEeNaoQAUuwEhdB8IW=
OMq
N2woDjGVKJftfsSWY9ilZrnDBNDrp0vRqcx33LUMkIw4d7iBwsFzBBABCAAdFiEEfhcKBFyEz=
0YO
K3mgEO952f2DUxIFAlu3JJwACgkQEO952f2DUxJjuw/6ApHSsVTWD4a0H6FJ23A9Ftpy+aXZ4=
vYl
zkSrfsn2ECrEfK3lXQh/uzwjJUDYZeB1/BQsFZtcYNQOJSSHbQ49BFRLwb1J/wBZG4bbmrkLx=
nNb
KDKQvzxEpclkMW0Dj0J6o7kGrmzIGGrhB+JJN99AcineHRug8ZSFIERRCmigxdhAKU0BFD7P+=
5HN
HltSL3DF1c2fFOf2JrgBKVoE+9RhMZjWNbYetFFLCkjXb5Rpay9zeMm1DxfSTGAnuOwUXW6qq=
4hn
l5+VC/48ceDZElLLfu7RQUZv44pkSTOWZs+iQoJiHMFHk9wPqyB2Vok1yJ2a2j27WhXrJlPwn=
Zbg
JO5RyWDG3p/eVmpl5Uuc2dsfIpR17KnAuWpghK6V+cyFncDoGCl/YG2MvoolsW08FiZh3Ej4d=
nJj
j25TZkeFG74JJDXLvMYpJfSBGnmETv4Dhcm2xPqVMuFuL1qJlMbVLrMo2GXeo03OzNyvbs+u8=
WLI
aGm5hC7N1CXY8wZs4jo6OJ/expvnc07dEuws4zT3AiWv3nIouWReRStZy9QkavDocqbyPmilc=
dPC
Yk4BsOlzpwwO74hNG7iyl0KdAlwTxGQ7y0rJou6HYa1TmRhIEr3vKvlW+JfUUrqtjXgsuacTX=
o4+
Ira2JUErL2cYzQMq1j4r1ZyhFnuz93s7Rsx/Nw0+0YvCwNwEEAEKAAYFAlvFx+UACgkQajsRO=
Tyk
rWCJqwv+NLVPE4sD4sDA2/6Ek7UsRIUkg+S39fhqWsLc4rtw/mDunv8Un61I3K04fZ2Ry4nF9=
hZM
0a710UvXFbStvrzRJO3EAAcdJR9LTCd19e8UeruQbIee3YT91U4NkC9JMpecfq62/teOAU2e5=
P3f
WYaLs5ZX7zCLwWuBcW2l3SyoljQczM85HhJ3XHm+FnwQ6D9xRle+lvWTcuC9d1yAyUb8IOosp=
cL2
lJTmy8e3r79R24hPlSB4LDe0wEN8AXbagrcAQZjwyaHyWxjJbTwZ0b43WGdfIqZ1ElOeoffbk=
etP
GRmWvx5xUvb2ALFBBdETzV270gs5XDJgJ1SIIKOyDADxwvroTe2jD8C/841eEql5QSow3s/U3=
zRq
k3mttto8Qw/DN71aeh6dmYSsvd2UjsHw/vofOPRBGxZLEkKTEvMnhmMW9hiKPkPia+QgevYE0=
20q
pKSxLEdWA8nprHwxmGiDNesCfXSC6vm1qfyj5g8HzxSckq9ZaMhKMCo7vxflUEDuzsFNBFo9U=
DIB
EAD6DdHQfMav8OXfhjTteoarOrlJTSdci727xiezGPuBHmpvceBRZgRasdbaMc4HJee+R9+5x=
/nL
PCuy/DxDyIjwIUeJNgc+l7LjI9WfpHTD8U4xxjvR5Mi7+ToQQUOUNuzT0O0pyuxP1uY3RehHE=
hOV
fBZO59ipSeZL5iQC6T5MsK1SKfs51pLa5ToC1rc8tBJ4zZmxRAyZiYc/AH2uZ/6rYjTTkAn1D=
VI9
DYo2D/zE4bGjXdJW5pKphFB2lX3dG4I7ODi+5e1H6A/QpCu6z8/ZkIQ+9T1xcX/YwiFeA7PbT=
uW/
eITbMbI1eV3+fyym9aT7Rsflmp31Zxtr+sZwGGZf00ooMBFmqOS//NUQ/Vf3vDUew1h5QU1yD=
aWT
3NApvi+XWPH9TPy6TMfZA2FThHf11sX/gDBa5JWQZbptPEcmoazpiKZt91CrFPOaoXDPck/Q6=
1df
mr/oPikfByYnASIM3OwEuXqyQ9JDRfKrem5r+oA/wxWb5jELElAhOpnyqMMvOh7uz1foUssL8=
MAv
2TGXmxpVJ8Nu4je6wf96Z22fQ0D38zud+CKH3bMP3ayXXJBcdPoENrzFbWP5FTg/4TTDJ3vOA=
HZR
5iCunYghx8b7Ffa4UbkwlD+dh8GiIAtvT51Ac0cO0Wc0Zjc57zPUz1zloMbf+zb1Bsn7DuEQo=
qj1
gwARAQABwsFlBBgBCAAPBQJaPVAyAhsMBQkJlCYAAAoJEFqy+vF7FyvqrC8P/1tF6TeR83xD6=
Mas
qXyrBjwcLmziaF0Mlkj8k/YUiZ/knb53n97xQnh9yxPv0TT8Wpfdn3BmvqGyh8+ouHX9jMOxi=
RkM
dNhIauVYY/8jmRfBSYWcFkfMzdYasvdLtmYJgx252HKTFdeOrszoOjWjEzwmh+tca3AFMu/nB=
++/
KAmi5UJV7zsZ7uYJ5jm97LV5SLjNJIXXM+lHqCDrjDaDhNczmq1LCRlU6/WDjvkuwaVhZG4lX=
xMD
rvKnXMkjseQ2oKjwrIdfQM86H1z5J31lfhqop+of0cimcIsBgSCPu+h96LHuAzeRBCbDKeqrf=
ZtA
ZAGsokRina9947fRWxXHh3O66ILmXKNRxxWbDkPvYnQWUat8SbSTDoPWrDIGDRIAypqYo3pcN=
2OE
0C1chqgDZQxkr+9kYZQpupOAN2TR+fM7JvbO9coKI8Uqog8CopoMeDQkd0YjcqlB1E0svODHT=
zcS
oRzogDBYDqNLP7qVkNXpcOAXSVioBgiSDf7o5RdS/qmUyXBIeq6I5z8xBcd+BQ/n/9Frkm6K7=
IKP
3ngUP4wEoiPx5ZE5+fPIScGmVUcZIMhkvMvem9XXh1yyhqN14gfjmLwPGdWbrgG8QUe0s2WeW=
Iys
s6uTiyF+ZbJSo2XOKVc3YFMVUUfgyudqAV1wWdZinUk+H3pkqOKoHAy/8fST
=3D40Nd
-----END PGP PUBLIC KEY BLOCK-----

--------------ECF88EFDDC64BFFD0996494E--

--Lw0HBLITduhD0YIRdjvcxxkkRusILmEaJ--

--QG0pwmoA2zGhoG0IUhsjgMIWLx8KxYAYA
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEW7Wm6ldl0sWGPK4nWrL68XsXK+oFAmEHAqQFAwAAAAAACgkQWrL68XsXK+oC
ZA/+K9FaCog9jXhRbNDZ5LymnKwIwsgxpKmiwdinwo+DfyA25xUSJyx7t3O/sGe56Uda6wedAxM1
p14nMjujoX51okU85e1De15yXCl69dirWkw0NJ+aiw5Pn9XuN3f0Bxa1I1FKcFJ9A2CZEm2z99qG
+g0E1zGycoKoVSdOYbAbXcxp5laH248ZxL6VRKyaRjaBJkwpDC7TMHr33VF3lFcooek3J8lyM3Cd
AXUbdq2YLccGFWDoceAmaLzSNRGm6Ep56rDzdReXvdgDtg8IeuyCj3LqktwSv4lOD3zmBb6DqKxy
tAYe7HGmxf+z+oFv9q6knJ4nHbBgIiFNbgVlmhwIcDuQA4NndudJHmHMuwQ0lnOtoGd/cpjhzwNU
TtTky+/22JTqXhRFdEZD986FLV2mVl8flkJ0r3NLpo1nXaETjcZ1eRN5WksPtvVKtBZeqhm2fkw0
XKbqRpr9ingVazuCglWJ+z5D1Pa1TNAFOJQqxlELxbQj3jy7lbrtlxGn5RBJsRnITtTXVcF3tECF
kLaXlGWQ52Esha5jeNzJaTbJ2isiN8qqy13gJqa6pA0XnTX88oWY8dAs9glvtSI6Da/35A5a/oot
4/VnlO0TU6uR2+8Yep++JwrGTHhYB0mBF+gnqnEmaIbfgY3GE2Sy6BGdz42Vfq+nQb5u7hTgSvm5
mBg=
=qBnV
-----END PGP SIGNATURE-----

--QG0pwmoA2zGhoG0IUhsjgMIWLx8KxYAYA--


From nobody Sun Aug  1 13:37:29 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEF03A0E52; Sun,  1 Aug 2021 13:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ryjQGs-waTEQ; Sun,  1 Aug 2021 13:37:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101703A0E4D; Sun,  1 Aug 2021 13:37:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 18DB038A19; Sun,  1 Aug 2021 16:41:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tbp81oT-Dr_s; Sun,  1 Aug 2021 16:41:20 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 352D238A17; Sun,  1 Aug 2021 16:41:20 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B87A1B24; Sun,  1 Aug 2021 16:37:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Bron Gondwana" <brong@fastmailteam.com>, 111attendees@ietf.org, tools-discuss@ietf.org
In-Reply-To: <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sun, 01 Aug 2021 16:37:14 -0400
Message-ID: <27783.1627850234@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/IUH_jbm7qwV7UE8NmcuvxM6V5zc>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 20:37:27 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Bron Gondwana <brong@fastmailteam.com> wrote:
    > *a "temporary mute" mode that keeps the audio stream open:*

    > This is still an issue for me.  I often mute myself while chairing so=
 I
    > can take notes without my keyboard sound interrupting the chat - but =
it
    > means that I can't easily respond to somebody because the rejigging of
    > the audio channel not only creates a hiccup in the incoming audio feed
    > which means I might miss something someone says, but it also creates
    > enough of a delay that by the time I could have responded the other
    > party's mental state has moved on.

Yes, the 3s on/off latency on the audio is a problem.
So one should use a local mute instead, which of course, then causes confus=
ion.

    > Timing is really important in conversation and we're already fighting
    > with the quarter second delay imposed by the size of the planet.
    > Additional delay makes it unwieldy.

Ah... I know of a genetically spliced lab mouse with a plan to reduce the s=
ize of the planet.

    > *allow multiple connections by the same person to the same session:*

    > I have multiple times wanted to switch device temporarily - from my
    > desktop computer to a phone / ipad so I can temporarily move to anoth=
er
    > location while continuing to follow a meeting.  Multiple connection
    > support would mean I could switch over without a break.

It seems like a stretch requirement, but I also know that some chairs want a
second laptop so that they can see whether slides are really advancing.
What I don't understand is, 16 months into pandemic, and 10 years into scre=
en
sharing, how it is that PPT people don't understand that they have to "F5"
before they share.

    > Sure it could be abused by people "sharing" a login, but that would be
    > pretty obvious if both parties tried to participate, and given that we
    > allow fee waivers anyway, it's unlikely to be abused significantly.
    > Sure there are Jabber naming issues, but we can avoid that by giving
    > each jabber name with a serial number (which I believe already happens
    > now?)

Yes. Actually, the ephermalness of the jabber names annoys me, as I can't
message people after they have left.

    > *information about who is speaking in the same place as video feeds*

The video image does do the yellow square when they are speaking.

    > See my previous email :)  Basically the "participant list" should just
    > be an ordered list of participants and only needs to be switched to
    > when seeing who is in the call or opening an individual message to th=
em
    > (and people don't get moved out of order when they're sending
    > something).  The "who is sending something" list should be all togeth=
er
    > with the video, and chairs pinned even if they're sending nothing rig=
ht
    > now.

I think that I need a picture.
As my meetecho windows are more vertical than horizontal, I'd also like to =
be
able to move the video boxes to be under the slides.
see:  https://www.sandelman.ca/mcr/IETF111-virtual-SFO-two-sessions.png

    > Along with visual indicators of "currently sending audio" on people so
    > we know who of those with their audio channel open are currently
    > speaking, this makes it easier to look in one place to see the source
    > of all sound, and eyes can generally flit between the right hand side
    > (video and audio indicators) and the slides, without needing to also
    > track via the participant list.

I think that it would also work better for the youtube recording.

    > *flexible "assign chair"**:*

    > This one hasn't come up in practice, but the chairs for meetings are
    > pre-assigned from datatracker.  It would be great for ADs and the
    > meetecho reps in each meeting to be able to upgrade anybody to a chair
    > role or remove a chair role with a simple click.

That's a good idea.
And with that power, they should be able to advance slides, no matter who
activated them.

    > This has become less important with the ability for individuals to tu=
rn
    > on both audio and video themselves, so the chair is going less busywo=
rk
    > just approving access, but it would be good to make it possible for
    > someone else to step into the chair if the regular chairs are unable =
to
    > attend or lose network, rather than making the meeting less able to
    > run.

I'd like the chair to be able to pre-authorize sharing and slides.
Actually, the way I'd implement is that the chair(s) just get to decide who
of the possibly many screen-sharing/slides that are occuring, who is actual=
ly
shared.

That lets people (a) test their setup in advance of their slot,
(b) reduce the time to switch.

=2D-
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        |    IoT architect =
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmEHBfoACgkQgItw+93Q
3WWb6QgAuqzwQODO1U8V1CIg7vQHbgO8+hJBirNEtSRdxfcOC0ikqzppAcO317VE
zVg2gTDwq+8H8oglRfc6Fa4mAFt7YT9491Y90q+GRvDxI+e3JdvcSaIr1cd9XPdE
6Ys7qw41icMrSIV32NQVW051krsQt9if5uxyMyJzL/6Lq0LORvKW7WIicmxM3C2p
IhMdy85QEwbLa2CefdfN5TFR0ocmAfygQHsi8fI0pHnZYB186VZG5Ws9tHF5IzPB
xGFicePDJfkFxhnijElao0qOQbPL7xmd0vkmK1Cv/RMaVwVwc+kHf+RouzXKQ+cg
EHkm31XQm8RKhDX2sqsjr1WRMNXeRg==
=xMXh
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Aug  1 13:41:29 2021
Return-Path: <ekr@rtfm.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 286B33A0EAA for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 13:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 RnxOLabD0mN8 for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 13:41:12 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80E9C3A0E92 for <111attendees@ietf.org>; Sun,  1 Aug 2021 13:41:12 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id f11so17964563ioj.3 for <111attendees@ietf.org>; Sun, 01 Aug 2021 13:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uNU6DfSXBnyLSHwyzi8FvXLz8C1Lw+HCSa/R7ogIHKg=; b=Rrn5a7XPJqv6kI3JTjaT51q5ygxVOQkAixQ6e6/D95cn5roYpvJFTbVVGcQsUNHceM 61HgwE+z712B3dL53WfAHwThs8qXkT7HWN8UK6r12dqpCSPq4nl86q312WaIKbcNDmj4 wXB7PmD6geYRhOGpQNXE3DND3qmuZMwCpI4jVZadiNCDsJS+nNK6N+qGgi3aUfmC2sfL XBz2RrX93YkxSbtII/cCI/gNMD2NGiMI40Hd1ApjG87pXtViD3cdPDm2AA8WUk22Ga9a yCBZ7X8Bjy+DckL+J9QYqOJHFmlYYXYCQBSz4+cMfg7Z1CTETdpBU/JyYYXrrlzAR5Sa Wgyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uNU6DfSXBnyLSHwyzi8FvXLz8C1Lw+HCSa/R7ogIHKg=; b=aDMDoF9dAKIOfbinFX8KAevkwIj6ACUMaruHVZ/HCzAOXc8y2IsQCJyUr9F3s52glq O51J8i+ApbKK5w5HUopHtvaSg74U43lgwP3dQQ+haxX88cNDPYc7aPs03e4cM+vhPnMP YRWZuBtE5TZVwvCqJReTAuloO2J4qgWkt3wQQJjsZl+SP9Vg+8JdNtPxBU/1rCTdgzPP d2vg4GNFwO0Bws6CzFaBTjvdOJ5n7x+u2HD+qGFo5hruNCqfuP39vEmp9SF/0oWztbZ+ 2XWgvOkE1q2s7up2W2cAYbigOUHk3kawwb+yFuuJ2XPIvIsqspSVBRiJcV0szwHKtOfn reuA==
X-Gm-Message-State: AOAM531wlWqlKlAf/by5EoInMGFbuCeVxGBWZ+5M3lfLugrwSrhV6xdH uD7hqOWh1WP+G+lP/j3+fGiS6Z3CQdu2Nr7Jf8e+uw==
X-Google-Smtp-Source: ABdhPJyeMb4iJgqzZ73uxvZJJKNnZlbNxHxW/KKmyLizmccGIDEIbJ+bkrchYo+vJuulanqvsjWHPm/drr3EgeJCWGU=
X-Received: by 2002:a05:6638:338f:: with SMTP id h15mr11576669jav.135.1627850471088;  Sun, 01 Aug 2021 13:41:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost>
In-Reply-To: <27783.1627850234@localhost>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 1 Aug 2021 13:40:34 -0700
Message-ID: <CABcZeBPjvRSdLjHUCXYDhE8Ls03w2M4iS-eS_YKkrRrMyN1kwA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org,  tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000013b4ec05c8857922"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/97hWyT96udognjT19kzbTwal3A0>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 20:41:25 -0000

--00000000000013b4ec05c8857922
Content-Type: text/plain; charset="UTF-8"

On Sun, Aug 1, 2021 at 1:38 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Bron Gondwana <brong@fastmailteam.com> wrote:
>     > *a "temporary mute" mode that keeps the audio stream open:*
>
>     > This is still an issue for me.  I often mute myself while chairing
> so I
>     > can take notes without my keyboard sound interrupting the chat - but
> it
>     > means that I can't easily respond to somebody because the rejigging
> of
>     > the audio channel not only creates a hiccup in the incoming audio
> feed
>     > which means I might miss something someone says, but it also creates
>     > enough of a delay that by the time I could have responded the other
>     > party's mental state has moved on.
>
> Yes, the 3s on/off latency on the audio is a problem.
> So one should use a local mute instead, which of course, then causes
> confusion.
>

Actually, this is not necessary. WebRTC contains APIs which allow you to
mute
the media locally. The delay in Meetecho is a result of the decision to
release
the MediaStream which then needs to be re-acquired, which is not what
Meet, Zoom, etc. do.

-Ekr

--00000000000013b4ec05c8857922
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sun, Aug 1, 2021 at 1:38 PM Michae=
l Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sandel=
man.ca</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><br>
Bron Gondwana &lt;<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blan=
k">brong@fastmailteam.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; *a &quot;temporary mute&quot; mode that keeps the audio =
stream open:*<br>
<br>
=C2=A0 =C2=A0 &gt; This is still an issue for me.=C2=A0 I often mute myself=
 while chairing so I<br>
=C2=A0 =C2=A0 &gt; can take notes without my keyboard sound interrupting th=
e chat - but it<br>
=C2=A0 =C2=A0 &gt; means that I can&#39;t easily respond to somebody becaus=
e the rejigging of<br>
=C2=A0 =C2=A0 &gt; the audio channel not only creates a hiccup in the incom=
ing audio feed<br>
=C2=A0 =C2=A0 &gt; which means I might miss something someone says, but it =
also creates<br>
=C2=A0 =C2=A0 &gt; enough of a delay that by the time I could have responde=
d the other<br>
=C2=A0 =C2=A0 &gt; party&#39;s mental state has moved on.<br>
<br>
Yes, the 3s on/off latency on the audio is a problem.<br>
So one should use a local mute instead, which of course, then causes confus=
ion.<br></blockquote><div><br></div><div>Actually, this is not necessary. W=
ebRTC contains APIs which allow you to mute</div><div>the media locally. Th=
e delay in Meetecho is a result of the decision to release</div><div>the Me=
diaStream which then needs to be re-acquired, which is not what</div><div>M=
eet, Zoom, etc. do.</div><div><br></div><div>-Ekr</div><div><br></div></div=
></div>

--00000000000013b4ec05c8857922--


From nobody Sun Aug  1 13:56:35 2021
Return-Path: <johnl@iecc.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19E13A1028 for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 13:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=BZonWogn; dkim=pass (2048-bit key) header.d=johnlevine.com header.b=D/jfBVuv
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 QM0AIXqJlx_5 for <111attendees@ietfa.amsl.com>; Sun,  1 Aug 2021 13:56:23 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 4AE8A3A1027 for <111attendees@ietf.org>; Sun,  1 Aug 2021 13:56:23 -0700 (PDT)
Received: (qmail 18664 invoked from network); 1 Aug 2021 20:56:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=48e6.61070a76.k2108; bh=7FSg5f7Fzw/8j7I3LvNcN1TcWralperYsN1v1OGpVv8=; b=BZonWognNofz5u1vLJypHTsssx1YkjtEt8aP0Mn9mOpho7+k2brGSBCqeMTvClICxgr2DHZO/OsN8RAX2PdY+Oo4nbLo0AWuQ366NKpd5FtiYEN9AOLkre7iMEUbLoPMCunfq5k1sBLehwH7LpUtARjfDwwf1fXDEz7VuZHhgmnyu7El4Sj0pYbj1yzbYZq7Gy4kywMt+HvQq81ZNNbvDwLhZgdV/h3P0ENS/VrQ6krEjQp2kFJZHH+7+FbOzx7QZ1TbAHNn3sGq0eLzdOnHOfL/FE78197YbIKCGMbqyONmwAbPREGCaWdC8B7eoTPno8D5zwkzxc+rpQ9OvszyXw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=johnlevine.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=48e6.61070a76.k2108; bh=7FSg5f7Fzw/8j7I3LvNcN1TcWralperYsN1v1OGpVv8=; b=D/jfBVuvDzYOlXMrfVkWvh8fBz7cnY9VFCDFycK/mFki0jw9n/G06D+ls0gcXZKreipEpgPWPm5myP83Qyz+DvuerhnU8QNl5u5MQqC6ZWkhHrzsVK/z2bf5l+6+IPMSk2dTXIGpTrZkKD6DWBvoWwqHDGMWhNwop22sc1LdkZUruvKo9BMOD8DPGyBjTNYjAmINHv80ssES5B7VdjFEihCUcW4UQ5MTo9pDsat6dX3dORiaArccPaauSgNhAPoi2lkkjdbJ2TNGKFe3ApZRm8uQp+UCqWy4DaiSjiO7ONjZ/02Ed7BLbTPyzJVdiscz93EL3zK+C9ekZUwvMpYHOw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 01 Aug 2021 20:56:21 -0000
Received: by ary.qy (Postfix, from userid 501) id 427F0257240C; Sun,  1 Aug 2021 16:56:20 -0400 (EDT)
Date: 1 Aug 2021 16:56:20 -0400
Message-Id: <20210801205621.427F0257240C@ary.qy>
From: "John Levine" <ietf@johnlevine.com>
To: tools-discuss@ietf.org, 111attendees@ietf.org
Cc: stephen.farrell@cs.tcd.ie
In-Reply-To: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/_eyervdA8vnLjcMN05ozG5GS3bM>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 20:56:30 -0000

It appears that Stephen Farrell  <stephen.farrell@cs.tcd.ie> said:
>
>On 01/08/2021 16:47, Carsten Bormann wrote:
>> OK, so the summary of the 111attendees discussion is that we don’t
>> want unauthenticated write access to meeting notes.

>Really? Seems to me the risk isn't significant enough to make
>someone do work and there's plenty of opportunity to read the
>draft meeting notes. I don't really object to requiring note
>takers be authenticated but it doesn't seem that worthwhile.

If they're in the meetecho session, they're already authenticated, so I'm having
a little trouble coming up with a scenario in which someone who isn't there needs
to change he minutes.

R's,
John


From nobody Mon Aug  2 01:08:12 2021
Return-Path: <robin.marx@kuleuven.be>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1803A1286 for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 01:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 EQNiDmyIPrpd for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 01:08:06 -0700 (PDT)
Received: from icts-p-cavuit-3.kulnet.kuleuven.be (icts-p-cavuit-3.kulnet.kuleuven.be [IPv6:2a02:2c40:0:c0::25:133]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD36D3A0D06 for <111attendees@ietf.org>; Mon,  2 Aug 2021 01:08:04 -0700 (PDT)
X-KULeuven-Envelope-From: robin.marx@kuleuven.be
X-KULeuven-Scanned: Found to be clean
X-KULeuven-ID: 5916220829.A3A02
X-KULeuven-Information: Katholieke Universiteit Leuven
Received: from icts-p-ceifnet-smtps-1.kuleuven.be (icts-p-ceifnet-smtps.service.icts.svcd [IPv6:2a02:2c40:0:51:141:242:ac11:1d]) by icts-p-cavuit-3.kulnet.kuleuven.be (Postfix) with ESMTP id 5916220829 for <111attendees@ietf.org>; Mon,  2 Aug 2021 10:07:57 +0200 (CEST)
X-CAV-Cluster: smtps
Received: from ICTS-S-EXMBX25.luna.kuleuven.be (icts-s-exmbx25.luna.kuleuven.be [10.112.11.60]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by icts-p-ceifnet-smtps-1.kuleuven.be (Postfix) with ESMTPS id 32B1AD4F71BD3;  Mon,  2 Aug 2021 10:07:57 +0200 (CEST)
Received: from ICTS-S-EXMBX25.luna.kuleuven.be (10.112.11.60) by ICTS-S-EXMBX25.luna.kuleuven.be (10.112.11.60) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 2 Aug 2021 10:07:56 +0200
Received: from ICTS-S-EXMBX25.luna.kuleuven.be ([fe80::95e5:f544:83cb:4f98]) by ICTS-S-EXMBX25.luna.kuleuven.be ([fe80::95e5:f544:83cb:4f98%19]) with mapi id 15.00.1497.015; Mon, 2 Aug 2021 10:07:56 +0200
X-Kuleuven: This mail passed the K.U.Leuven mailcluster
From: Robin Marx <robin.marx@kuleuven.be>
To: John Levine <ietf@johnlevine.com>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>, "111attendees@ietf.org" <111attendees@ietf.org>
CC: "stephen.farrell@cs.tcd.ie" <stephen.farrell@cs.tcd.ie>
Thread-Topic: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
Thread-Index: AQHXhYVF3Y3PSlmN1EW2J9yE70IWGKtb7OcAgAAYYgCAATthgIAAD+GAgAAJKoCAAULwgIAAD8EAgABNEwCAAAlQAIAA3Kow
Date: Mon, 2 Aug 2021 08:07:56 +0000
Message-ID: <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be>
References: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie> <20210801205621.427F0257240C@ary.qy>
In-Reply-To: <20210801205621.427F0257240C@ary.qy>
Accept-Language: en-GB, nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.112.50.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/DlWfE72zlK6Y44sbTlzvdfeABI8>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 08:08:11 -0000

SW4gbXkgZXhwZXJpZW5jZSBhcyBhIGZyZXF1ZW50IG1pbnV0ZXMgdGFrZXIsIGl0IHdvdWxkIGFs
c28gYmUgaGVscGZ1bCB0byBoYXZlIGEgImxvZ2luIHdpdGggZGF0YXRyYWNrZXIiIGJ1dHRvbiAN
CnNvbWV3aGVyZSBlYXNpbHkgYWNjZXNzaWJsZSB3aGVuIGxhbmRpbmcgb24gdGhlIHBhZ2UgZm9y
IGEgc3BlY2lmaWMgc2Vzc2lvbiAobGlua2VkIGZyb20gdGhlIGFnZW5kYSksIA0Kd2l0aG91dCBo
YXZpbmcgdG8gZ28gdG8gdGhlIG1haW4gQ29kaU1EIGxhbmRpbmcgcGFnZSBmaXJzdA0KKGFzc3Vt
aW5nIHRoYXQgcG9wdXAgd29uJ3QgYXV0by1zaG93IGlmIHRoZSBiZWhhdmlvciB3b3VsZCBjaGFu
Z2Ugb3IgaWYgdGhlIGN1cnJlbnQgYmVoYXZpb3IgaXMga2VwdCkuIA0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogMTExYXR0ZW5kZWVzIDwxMTFhdHRlbmRlZXMtYm91bmNlc0Bp
ZXRmLm9yZz4gT24gQmVoYWxmIE9mIEpvaG4gTGV2aW5lDQpTZW50OiB6b25kYWcgMSBhdWd1c3R1
cyAyMDIxIDIyOjU2DQpUbzogdG9vbHMtZGlzY3Vzc0BpZXRmLm9yZzsgMTExYXR0ZW5kZWVzQGll
dGYub3JnDQpDYzogc3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZQ0KU3ViamVjdDogUmU6IFsxMTFh
dHRlbmRlZXNdIFdoeSBkbyB3ZSBhbGxvdyBwZW9wbGUgdG8gZWRpdCBDb2RpTUQgbWVldGluZyBu
b3RlcyB3aG8gYXJlIG5vdCBsb2dnZWQgaW4/DQoNCkl0IGFwcGVhcnMgdGhhdCBTdGVwaGVuIEZh
cnJlbGwgIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPiBzYWlkOg0KPg0KPk9uIDAxLzA4LzIw
MjEgMTY6NDcsIENhcnN0ZW4gQm9ybWFubiB3cm90ZToNCj4+IE9LLCBzbyB0aGUgc3VtbWFyeSBv
ZiB0aGUgMTExYXR0ZW5kZWVzIGRpc2N1c3Npb24gaXMgdGhhdCB3ZSBkb27igJl0IA0KPj4gd2Fu
dCB1bmF1dGhlbnRpY2F0ZWQgd3JpdGUgYWNjZXNzIHRvIG1lZXRpbmcgbm90ZXMuDQoNCj5SZWFs
bHk/IFNlZW1zIHRvIG1lIHRoZSByaXNrIGlzbid0IHNpZ25pZmljYW50IGVub3VnaCB0byBtYWtl
IHNvbWVvbmUgDQo+ZG8gd29yayBhbmQgdGhlcmUncyBwbGVudHkgb2Ygb3Bwb3J0dW5pdHkgdG8g
cmVhZCB0aGUgZHJhZnQgbWVldGluZyANCj5ub3Rlcy4gSSBkb24ndCByZWFsbHkgb2JqZWN0IHRv
IHJlcXVpcmluZyBub3RlIHRha2VycyBiZSBhdXRoZW50aWNhdGVkIA0KPmJ1dCBpdCBkb2Vzbid0
IHNlZW0gdGhhdCB3b3J0aHdoaWxlLg0KDQpJZiB0aGV5J3JlIGluIHRoZSBtZWV0ZWNobyBzZXNz
aW9uLCB0aGV5J3JlIGFscmVhZHkgYXV0aGVudGljYXRlZCwgc28gSSdtIGhhdmluZyBhIGxpdHRs
ZSB0cm91YmxlIGNvbWluZyB1cCB3aXRoIGEgc2NlbmFyaW8gaW4gd2hpY2ggc29tZW9uZSB3aG8g
aXNuJ3QgdGhlcmUgbmVlZHMgdG8gY2hhbmdlIGhlIG1pbnV0ZXMuDQoNClIncywNCkpvaG4NCg0K
LS0NCjExMWF0dGVuZGVlcyBtYWlsaW5nIGxpc3QNCjExMWF0dGVuZGVlc0BpZXRmLm9yZw0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby8xMTFhdHRlbmRlZXMNCg==


From nobody Mon Aug  2 04:10:40 2021
Return-Path: <chromatix99@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 028533A18C4; Mon,  2 Aug 2021 04:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TKv5VuN-DVaI; Mon,  2 Aug 2021 04:10:29 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34D7B3A18BF; Mon,  2 Aug 2021 04:10:29 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id c18so16180164qke.2; Mon, 02 Aug 2021 04:10:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=frU8NqLt8uq1sYs0GmLDlSqZ2N1C6m66BkaW4yp3P34=; b=pKPYvOJ0b7ZGf4ZzJhnvixChoONhVOHiOM+7MEva/NAygpFWCdPaDkV47ekWn7f/Fd 5lN/QME9qXLdpSM/flurmbtEo8EiOPKcgOhedrnCao6YHIGh3iRH2SD8qvmR8IFqqrQv sLm+yvjiQv5P2gnEDbJ3zIY/d1s7MioMAIhCWj/E36dspkknxT6SnEzdKzg/olylbUlO I3ou0HYDy6QEotIMBUMwCXQFQoV4jQGHBB3S/MuYcD8ztk+syP9R4rRnKDRyjUpqmokT O2mHZ6mBXyohEyGESVqxRwM4irWHyLMpKOqOfqpOZwWtfZSgNBJfx5RbY8tI9sKknyxt ax4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=frU8NqLt8uq1sYs0GmLDlSqZ2N1C6m66BkaW4yp3P34=; b=g/LErwzgUpoxY8f1RqsQOaRJ20c6us1T7+5OHpnCd4jbPQneFi38Wem5/8PMwrfIN+ ybjsvPFpx/MDTGoDNiNyFys6uuk6QgHoID2ipAGWjYQUMjHeHuMurmU3juNJXMZJV99T rZSNa1+MaLkYuBroCCXhj4g9+77tJC2T+3WWGLTOMlk+SrgZJzaY1nvH2dytVVo0lzX7 xzoCy4S30OUvaT/gAeY4Wk81NYiIoPf+HctlxuTCZJvvSdadHSxTtJQbwAdo1Ft+fD+v aXcoTJpJwBzNovZuLG03rd+tyIVuxFSGfcK8Bd2M7KuTNalIgkEnneIGJzkhCBGwIGZ4 Atsg==
X-Gm-Message-State: AOAM533tT7EQHn9KiOB3x+L/2yT0W3WSfRfgObQbJzcn+DnZaz4Wrguw zGeeuflsOxJXn14WWRmfpwNQuxA7ZrQyYXC79RM=
X-Google-Smtp-Source: ABdhPJx3rjZaovTWXAeiSEFnE4Gv9Vka0TlnooZRH7bFa+RjZUNqUCHgUf/5U4762i6Giu0W1uhVLNsHC6xdIAXHWE4=
X-Received: by 2002:a37:2d04:: with SMTP id t4mr15755975qkh.160.1627902626810;  Mon, 02 Aug 2021 04:10:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost>
In-Reply-To: <27783.1627850234@localhost>
From: Jonathan Morton <chromatix99@gmail.com>
Date: Mon, 2 Aug 2021 14:10:15 +0300
Message-ID: <CAJq5cE3He3n-2920KkfKqRd0VShSFQRC9w0vLyrfL=-DsosChQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org, tools-discuss@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/HU6UnsQKVzIXvDPrNOB2Ks02KVw>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 11:10:34 -0000

On Sun, 1 Aug 2021 at 23:37, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

>     > *information about who is speaking in the same place as video feeds*
>
> The video image does do the yellow square when they are speaking.
>
>     > See my previous email :)  Basically the "participant list" should just
>     > be an ordered list of participants and only needs to be switched to
>     > when seeing who is in the call or opening an individual message to them
>     > (and people don't get moved out of order when they're sending
>     > something).  The "who is sending something" list should be all together
>     > with the video, and chairs pinned even if they're sending nothing right
>     > now.
>
> I think that I need a picture.

So, currently we have the Chairs and any "active" participants (hand
up, mic and/or camera open, presenting slides or screen) moving
dynamically to the top of the Participants list on the left.  This
makes it easy to find the Chairs, but if looking for a particular
person in the list, you have to check both the top of the list and
their alphabetical position, since their dynamic status could place
them either way.  By default the Participants list is also hidden when
you're reading the chat, and vice versa.  And currently the list of
video thumbnails on the right is *strictly* those people with a camera
open, whether or not they have the mic open or are active in some
other way.

The proposal here is to include *anyone* who would normally be moved
to the top of the Participants list in the list of video thumbnails,
and make the Participants list mostly static (only Chairs at the top).
The thumbnail for people without a camera on would be the profile pic
if they have one, supplemented by the appropriate participation icons
(hand, microphone, screen, slides).  This gives a natural place to
show speaking cues, so you can see at a glance who is actually
speaking.

> As my meetecho windows are more vertical than horizontal, I'd also like to be
> able to move the video boxes to be under the slides.

This also seems like a valid optimisation of screen real estate.  The
thumbnail list should lie along the edge of the window that is least
pressured by the presentation area.

 - Jonathan Morton


From nobody Mon Aug  2 10:03:07 2021
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28F133A0EC6; Mon,  2 Aug 2021 10:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9R_hx3IlwgUp; Mon,  2 Aug 2021 10:02:58 -0700 (PDT)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79C5B3A0ED1; Mon,  2 Aug 2021 10:02:58 -0700 (PDT)
Received: by mail-vs1-xe2e.google.com with SMTP id x144so1096368vsx.3; Mon, 02 Aug 2021 10:02:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aHSje7vno++d9DNH0ZomnoHpCfvcxamAO0z+X5xeI5Q=; b=CANPni9bBrtr9GXUcMUmCEOe9cetjE7AgHUTApADWGbRb3ILdP425HbbF9X99ciXt3 tjqkVEs+4pIgcwuqIhg7sR/V784EgoaDVU1MsANnA1/VULJNIhEmY6dWjWiUoCmiTjJl z8spnTdyOrYZfhbGuXcGaGpUsQXr52PX6ADKgrpPaWEdFIrU8HVq6Cy079YsBn7rCVge EZBom/YqMbJsXXX+aH2UhD0MlqTUz6WDqS74i4aT8gpfYzpN0lyYQT834QvfDgY1ZZRo H1vkMo+csurCC2dQtFo0bt292guW+uiTaNuJHSdQ+7HkQWE+XE4wMyNijG81GHRCxWN9 hiHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aHSje7vno++d9DNH0ZomnoHpCfvcxamAO0z+X5xeI5Q=; b=bSMlZiRMr+Lt8c5jVfAMjo8BBV1w3lftmgiaCGZudXzzgsr2gRZdX9DNVUO2FNe7P1 8o6Oc6iT4mj8dyph16yGXimt7FhDTzbkTylecyfcYNzYJw/lcEPqiCKS0Z24CLVRsHhV 5UI4KyIwFGFfPAXBYFYSNuZuSk4URPhuPVqIFJCKZFw9D5Z6QL+mo+qSt7vYSCk2to0k eACVHtZxzZbjj5YlAov/3v25RyNji7YWc4CqKINfPxEiRn3tKUZn9e4WDdydFNd6P/2Z IBtN1KRNcBRhtLB40cTixq1ulRfUVWxyshCuE39Kf+0DQMnLtW6yJfeUrXWrCiBlfK9q DSXA==
X-Gm-Message-State: AOAM533mbehvRCMnCiaYO76CbW6COLAl1zFTOABbXVzXttjHA27L0bsa D5HiHrS0W9I5wyWeg56/Uw0ACESfDeK75DiS2bqpzSRwBvM=
X-Google-Smtp-Source: ABdhPJz4wjdTY8xc8PtqugjcuQ0tmGZ9Xr6nI9KA90IoD6DsRmo/wvY30Se+s3+h9VE84J9AUKi9CtfzVmRQ9YREHXM=
X-Received: by 2002:a67:f7ca:: with SMTP id a10mr2940782vsp.7.1627923776459; Mon, 02 Aug 2021 10:02:56 -0700 (PDT)
MIME-Version: 1.0
References: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie> <20210801205621.427F0257240C@ary.qy> <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be>
In-Reply-To: <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 2 Aug 2021 12:02:29 -0500
Message-ID: <CAKKJt-fuOCifVkGY3yfikV6RetYmrv51SF809Si=wPzkL3g4Qg@mail.gmail.com>
To: "111attendees@ietf.org" <111attendees@ietf.org>
Cc: "tools-discuss@ietf.org" <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006ad7bf05c8968a32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/ZCjrjEwX68kN3YpPRxtb8JvKJtk>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 17:03:01 -0000

--0000000000006ad7bf05c8968a32
Content-Type: text/plain; charset="UTF-8"

Just to back up slightly in this thread,

Knowing who the (other) note-takers are is valuable, especially if you
suddenly realize that the (other) note-taker is presenting, or involved in
a long mike exchange (not naming names here).

Whether or not I'm officially taking notes, I always log in to make sure
that the unfortunate note-takers have been able to translate Spencer-speak
to What Spencer Meant. That does mean I often make edits on things other
people said, because I was pretty sure that the notes missed something
significant.

I had no idea that I could change permissions on pages I created.
https://codimd.ietf.org/features#Permissions was enlightening.

While we're chatting here - I created ComiMD pages for at least two or
three side meetings, which were really useful in every case. That's not a
problem, is it? And if it's OK, is a name like
https://codimd.ietf.org/notes-ietf-111-SATCOM-side-meeting good enough?

Best,

Spencer

--0000000000006ad7bf05c8968a32
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Just to back up slightly in this thread,=
=C2=A0</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Knowing who the (ot=
her) note-takers are is valuable, especially if you suddenly realize that t=
he (other) note-taker is presenting, or involved in a long mike exchange (n=
ot naming names here).=C2=A0</div><div dir=3D"ltr"><br></div><div>Whether o=
r not I&#39;m officially taking notes, I always log in to make sure that th=
e unfortunate note-takers have been able to translate Spencer-speak to What=
 Spencer Meant. That does mean I often make edits on things other people sa=
id, because I was pretty sure that the notes missed something significant.<=
/div><div><br></div><div>I had no idea that I could change permissions on p=
ages I created. <a href=3D"https://codimd.ietf.org/features#Permissions">ht=
tps://codimd.ietf.org/features#Permissions</a> was enlightening.</div><div>=
<br></div><div>While we&#39;re chatting here - I created ComiMD pages for a=
t least two or three side meetings, which were really useful=C2=A0in every =
case. That&#39;s not a problem, is it? And if it&#39;s OK, is a name like=
=C2=A0<a href=3D"https://codimd.ietf.org/notes-ietf-111-SATCOM-side-meeting=
">https://codimd.ietf.org/notes-ietf-111-SATCOM-side-meeting</a> good enoug=
h?</div><div><br></div><div>Best,</div><div><br></div><div>Spencer</div></d=
iv>

--0000000000006ad7bf05c8968a32--


From nobody Mon Aug  2 10:26:06 2021
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52E03A10E6; Mon,  2 Aug 2021 10:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BlOlSvDd2MLQ; Mon,  2 Aug 2021 10:25:56 -0700 (PDT)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17E313A10DD; Mon,  2 Aug 2021 10:25:55 -0700 (PDT)
Received: by mail-ua1-x929.google.com with SMTP id 105so7242133uac.7; Mon, 02 Aug 2021 10:25:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JuusGEReZ6QZnqYGOyaJWiIXQ3QPxHkWB3eqZKjk8vA=; b=DxjcfYccKDANVAJEr6mtSxxmcg4k8t0LzJUb16Ww6da51FXxf9dAqF6Lx3O5eTx8/t kkuAaL82ELrp+zXyTnZ9AoIoVSd7dEKxIEsh73CZND2YzApgfTicZWsYqdIGMxPanNC6 YU/JStmT5UJAXafv8sDE6fqQyVzcuqYqPk/KqA7FvyWzljMRRrFDcx31ERK49rER4X2s mIrOzFqJ5BFCAMqWa2x0yuKFrsFSv/fX+TOF0JOgSJDpNikbD1UkI1GAMOYb+Cb/8+kL fiAQkBzYCjww7gbybzu6mzBOPjCSkA17lGDH2t78Q01k3VhXgFJDTMvRVYOs6pZkMPh3 eHlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JuusGEReZ6QZnqYGOyaJWiIXQ3QPxHkWB3eqZKjk8vA=; b=rGVeTJNNjOLfiL8VaqTGLl2uzQ1dYfDB+5BgyZ2sJKrXc9mNH1kXN6XZa/S12Z7K6o 7k/vVjrwaKr8BDpHbfSyFy7bpcL4r4NLDKXLXy3pZolHetsOijP9knpzoi5aZ9oYjk2s N1mhDxLAFlmeh4wszZWPKZObCrUKR0DFyMLVnRefKegM5Oo/bdeCymHsOgfstWfMKNwF YLam7Ns0wQnc0r5yFM54TlUi1ymx01uElw8bLQ8ZRlfsXioG7Fuj95zxQ6VBIulAmVKh OASWprzPHzWxxbr8+MK3KCwi8+oP50ubPADTGwbGZ/qVplMMngdEnKHdHh9hQoTskEwR R/ng==
X-Gm-Message-State: AOAM533ljxXl4NuuztupH0wBbvX4JhvgubInSg/sbJ1rqaQxW/vzZ0Z+ 0bH+84vGM+Ok3X4AkSG3Kls5XLRIZYnnesXsXMQ+1Aib
X-Google-Smtp-Source: ABdhPJx+oti5bykuu1B17sjhJt/aiqQgZG8g8Cejd8ZK6UCq3LbdtgLD/P2RVbMO379qC2JVF2V7TagXNKUVGSUnZC4=
X-Received: by 2002:ab0:6f4b:: with SMTP id r11mr2401002uat.104.1627925154804;  Mon, 02 Aug 2021 10:25:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
In-Reply-To: <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 2 Aug 2021 12:25:27 -0500
Message-ID: <CAKKJt-eKTxugtk+cY9vApfr9ubufuOvi9QS=Se8pUqphj-YocA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org,  tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000092b96f05c896dc68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/6DXY_U-nR5IXoq0prXDtrD0pKwg>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 17:26:01 -0000

--00000000000092b96f05c896dc68
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 30, 2021 at 4:14 PM Eric Rescorla <ekr@rtfm.com> wrote:

>
> To your list, I would add auto-unmuting (and even more importantly,
> muting) when people enter and exit the head of the queue. This would remove
> a lot of goofy behavior.
>

Yeah, and I'd suggest auto-muting video when you leave the queue, just
because "lowering your hand" could mean "I'm out of the line, I don't have
anything else to say, and you don't need to see me any more".

That would have fixed all *my *goofy Meetecho behavior. Fixing goofy things
I say with audio enabled is, of course, harder ...

Best,

Spencer

--00000000000092b96f05c896dc68
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jul 30, 2021 at 4:14 PM Eric Resc=
orla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt; wrote:<br></d=
iv><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><br></div><div class=3D"gm=
ail_quote">To your list, I would add auto-unmuting (and even more important=
ly, muting) when people enter and exit the head of the queue. This would re=
move a lot of goofy behavior.</div></div></blockquote><div><br></div><div>Y=
eah, and I&#39;d suggest auto-muting video when you leave the queue, just b=
ecause &quot;lowering your hand&quot; could mean &quot;I&#39;m out of the l=
ine, I don&#39;t have anything else to say, and you don&#39;t need to see m=
e any more&quot;.=C2=A0</div><div><br></div><div>That would have fixed all =
<b>my </b>goofy Meetecho behavior. Fixing goofy things I say with audio ena=
bled=C2=A0is, of course, harder ...</div><div><br></div><div>Best,</div><di=
v><br></div><div>Spencer</div></div></div>

--00000000000092b96f05c896dc68--


From nobody Mon Aug  2 10:48:13 2021
Return-Path: <marc@petit-huguenin.org>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7EB73A1228; Mon,  2 Aug 2021 10:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 hEVp2bR4bDmL; Mon,  2 Aug 2021 10:48:08 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (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 03D373A1225; Mon,  2 Aug 2021 10:48:07 -0700 (PDT)
Received: from [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd] (unknown [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id E9753AE269; Mon,  2 Aug 2021 19:48:03 +0200 (CEST)
To: tools-discuss@ietf.org, Meetecho IETF support <ietf@meetecho.com>, 111attendees@ietf.org
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com>
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
Message-ID: <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
Date: Mon, 2 Aug 2021 10:48:01 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/CJioo2xZlX74AvYPi3QHZQmvn24>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 17:48:13 -0000

One use of the Meetecho recording is to prepare minutes by double checking notes.  One issue with that is that sometimes a presenter answers comments made in the chat, but the chat log does not appear in the recording.  The person preparing the minutes now has to open the minutes, try to synchronize then with the recording and update the minutes to reflect the question/comment that triggers the response by the presenter.  There is two issues with that:

1. Someone watching only the recording only have access to half of that conversation and may not know where the chat logs are, or even that they was a chat running along the session.
2. People taking notes must follow both the chat and the presenter, which could be a bit too much.

I do not think that recording the chat at the same time than the presenter would be a good idea (OTOH displaying the name of the person talking in the recording even if they did not turn on video would help).  The reason is that not all the content of the chat log is relevant for the WG business (that's an understatement).

Having a jabber scribe and some discipline may help: The jabber scribe repeats the chat comment/question, and the presenters does not try to look at the chat, and so now the whole context is captured.

But that's still a bit clunky -- a presenter may want to comment on something that someone said in the chat room even if it was not marked as a question that the Jabber scribe must relay.  After all the chat logs are under NOTE WELL, so they are part of the WG session -- and should be part of the minutes, at least the relevant parts.

My suggestion would be to use TTS to supplement or replace the Jabber scribe.  A remote presenter who want to answer/comment on a chat message triggers TTS on the message itself, which now becomes part of the recording -- and of the minutes.  With a local presenter the Jabber scribe could also use that TTS feature.

On 7/30/21 12:38 PM, Meetecho IETF support wrote:
> All,
> 
> chiming in just to say that we at Meetecho appreciate and value your feedback. We'll definitely take it into account when developing the future releases of the platform. We'll provide comments on the points raised as soon as we get the chance to parse them, i.e., when the meeting is over.
> 
> Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to header to that list as well, as that's the right place to discuss enhancements and provide feedback that would be easier for us to collect.
> 
> Best,
> Alessandro
> 
[...]

-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


From nobody Mon Aug  2 11:45:26 2021
Return-Path: <mcr@sandelman.ca>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E593A1652; Mon,  2 Aug 2021 11:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 IiL2_3pBky6A; Mon,  2 Aug 2021 11:45:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DECED3A1655; Mon,  2 Aug 2021 11:45:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9576B389B4; Mon,  2 Aug 2021 14:49:10 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SIn871D68FRN; Mon,  2 Aug 2021 14:49:07 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C1D023899C; Mon,  2 Aug 2021 14:49:07 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id F123515B; Mon,  2 Aug 2021 14:44:58 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Jonathan Morton <chromatix99@gmail.com>
cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org, tools-discuss@ietf.org
In-Reply-To: <CAJq5cE3He3n-2920KkfKqRd0VShSFQRC9w0vLyrfL=-DsosChQ@mail.gmail.com>
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost> <CAJq5cE3He3n-2920KkfKqRd0VShSFQRC9w0vLyrfL=-DsosChQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29710.1627929898.1@localhost>
Date: Mon, 02 Aug 2021 14:44:58 -0400
Message-ID: <29711.1627929898@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/-4bxG7GDoveb307QrlYa-QWzsrw>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 18:45:25 -0000

Jonathan Morton <chromatix99@gmail.com> wrote:
    > The proposal here is to include *anyone* who would normally be moved to
    > the top of the Participants list in the list of video thumbnails, and
    > make the Participants list mostly static (only Chairs at the top).  The
    > thumbnail for people without a camera on would be the profile pic if
    > they have one, supplemented by the appropriate participation icons
    > (hand, microphone, screen, slides).  This gives a natural place to show
    > speaking cues, so you can see at a glance who is actually speaking.

I understand now. This would be good.

    >> As my meetecho windows are more vertical than horizontal, I'd also
    >> like to be able to move the video boxes to be under the slides.

    > This also seems like a valid optimisation of screen real estate.  The
    > thumbnail list should lie along the edge of the window that is least
    > pressured by the presentation area.

+1



From nobody Mon Aug  2 11:56:14 2021
Return-Path: <nigel.hickson@dcms.gov.uk>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3653A1622 for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 11:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level: 
X-Spam-Status: No, score=-3.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_GOV_DKIM_AU=-0.612, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcms.gov.uk
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 legb4qvGFw0q for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 11:56:07 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CB713A1669 for <111attendees@ietf.org>; Mon,  2 Aug 2021 11:56:05 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id c16so5993328lfc.2 for <111attendees@ietf.org>; Mon, 02 Aug 2021 11:56:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcms.gov.uk; s=google;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=7EsLEj1Cj2iHuVBnn2cGWGyQcdC2HXpf6dTI81+u1N4=; b=OjGWff7k3UzVaFqDH/Z0ftmhrTXIGrRCLTUqmIj+UTuKGeGD/HW3MHjX4hDhX+RV7t UB0KmrdYkzIMxXLwqujYip9/Tun9y1o75GHxzRa/U4PONj9dj/01KAGHCRhrr7dFopZT DW55LB07sl64lbMqJQrNi/nD/eoqQ3FYz3UpqlcF7Fn5PpVVtqkHL7f2A6eOSlcDHNzI hwrm/lt+sHFcig0pwYYFaLnQf7q0bRiLCYRwZG/AKeOFd8XbW8XIZUpX7OdjveXBsBfA imy6ZJk6M0Yk++qOsO7MP671Zci+lAlgm1CTpR5DMIvEiA+0A44IMKTK4r4b7rXzRFQc kKmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7EsLEj1Cj2iHuVBnn2cGWGyQcdC2HXpf6dTI81+u1N4=; b=VfToxmtHSLCPS+Q36P/tYPQgiqRwWXH985KiD1qreU58b0bpPdG2QoT2HFKxMXbQCN arqFRb7jQ1XMHsVgK8sNkYfUaNZh6YmUrKjXLPaNMzXM86JwUWj8e8ahwwaYUmNjaPjd x62ksjPaLDZDsnmgBES2h9a4TUw/S1IiH2vGw6S7u9WWhWIQk2A621qnECHo+M02rBIj XGq+H8eJi+0Gxr8Xk+c/D83IGAVrSqIHO1lt1xDUbvdgiJ5h+Q6knOujTvZ5yDJqO6/Q /zAYXNcY175jloAoZZVsrX9Lh9nyTO1h6cd549ioCbqwMxJ3D13bRNq0Umih2HPfv3uR 94Bw==
X-Gm-Message-State: AOAM530rhog8UWeGr52GydtrNUPiJ9AaibMOZLwp9TqjaXgyc/CEXGAl NNLwxS0BK8og1q+1YRSG/r6UF2NY1K3a0Ksj9JmUZrVMwSgvlg==
X-Google-Smtp-Source: ABdhPJz3sbMcmsFVxEhloF1oIkntwm9JjK6kJRjXENJmtSjr1qqWqZDcFl1Tu3OJn5mwH+Fs8FCKtVacJnwC4K94UPs=
X-Received: by 2002:a19:dc08:: with SMTP id t8mr13496490lfg.523.1627930558402;  Mon, 02 Aug 2021 11:55:58 -0700 (PDT)
MIME-Version: 1.0
References: <7B4B465C-722E-4FC6-BAC1-9C1F18CF01AF@ietf.org> <CAAm_rSLRb3+qirZO9kg1FY16o7DDcukrp3WU5yVtzagOSu7TnQ@mail.gmail.com>
In-Reply-To: <CAAm_rSLRb3+qirZO9kg1FY16o7DDcukrp3WU5yVtzagOSu7TnQ@mail.gmail.com>
From: Nigel Hickson <nigel.hickson@dcms.gov.uk>
Date: Mon, 2 Aug 2021 19:55:33 +0100
Message-ID: <CAAm_rS+=a89=-KvHS2q0S-EUFUE-mczQRR_UYLSU29moXvfG7g@mail.gmail.com>
To: 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a72b6c05c8981e91"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/nFeGO4SWSVuFUnK9U-2eq7lUOH0>
Subject: [111attendees] Fwd: [111all] IETF 111 - Post-meeting follow up, survey and special thanks
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 18:56:12 -0000

--000000000000a72b6c05c8981e91
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Jay

Good afternoon.  Thank you for this. While there was a lot of substance for
consideration and further thought, I did just want to make a couple of
non-policy observations as a newcomer to IETF Meetings.

The first would be to thank the IETF Secretariat (and no doubt others) for
making us so welcome, not least in Newcomer sessions and during the meeting
itself.  Additionally the platform used was pretty user friendly and
encouraged interaction and dialogue.

The second would be to encourage some thinking (and perhaps this has
already taken place) on how the sessions themselves might be structured in
a way to make them more user friendly for both newcomers and those joining
the discussion in a working group after a time away.  Some form of summary
/ update at the start of a session setting out where the Group has reached
and the expectations of the dialogue to take place might be useful. This
could, one supposes, be effected in a couple of opening slides or in the
"chat".  Thought could also be given to the conduct of the chat itself,
often very informative and useful in supplementing the presentations, but
sometimes riddled with historical references, obscure acronyms and some
pretty hostile exchanges.

Many regards

Nigel

On Sun, 1 Aug 2021 at 23:20, IETF Executive Director <exec-director@ietf.or=
g>
wrote:

> IETF 111
> 26-30 July 2021
> Hosted by Juniper
>
> IETF 111 has concluded.  Thank you all participants, chairs, presenters,
> contractors and staff who worked hard to put this meeting together.  This
> was our largest fully online meeting to date with over 1300 observed
> participants.  Full stats will follow in a later blog post.
>
> Recordings of IETF 111 sessions are at
>
>
> https://www.youtube.com/playlist?list=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi=
6
>
>
> This meeting has sparked a great discussion about the features of the
> services we provide to support participation, including the Datatracker
> agenda, Meetecho and CodiMD, all of which will be followed up on to impro=
ve
> the experience further.
>
> We would really like to get more feedback through our short post-meeting
> survey that will only take you a few minutes to complete:
>
>         https://ietf.iad1.qualtrics.com/jfe/form/SV_6PR0tAZvEidoY7A
>
> I hope it=E2=80=99s becoming clear to people who have attended multiple m=
eetings
> that we really do listen to the feedback in this survey and use that to
> drive improvements to the meeting experience.
>
>
> A final big thanks to Juniper for hosting this meeting and thank you also
> to our Gold Diversity and Inclusivity sponsors, Akamai and Cisco, and to
> our Bronze sponsors, Comcast, Donuts, ICANN and Verisign.
>
>
> --
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
>
>
>
> --
> 111all mailing list
> 111all@ietf.org
> https://www.ietf.org/mailman/listinfo/111all
>

--000000000000a72b6c05c8981e91
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr"><br></div><br><div dir=3D"ltr"><div dir=3D"ltr">Jay=C2=A0<div><br></=
div><div>Good afternoon.=C2=A0 Thank you for this. While there was a lot of=
 substance for consideration=C2=A0and=C2=A0further thought, I did just want=
 to make a couple of non-policy observations as a newcomer to IETF Meetings=
.=C2=A0</div><div><br></div><div>The first would be to thank the IETF Secre=
tariat (and no doubt others) for making us so welcome, not least in Newcome=
r sessions and during the meeting itself.=C2=A0 Additionally the platform=
=C2=A0used was pretty user friendly and encouraged interaction and dialogue=
.=C2=A0</div><div><br></div><div>The second would be to encourage some thin=
king (and=C2=A0perhaps this has already taken place) on how the=C2=A0sessio=
ns=C2=A0themselves might be structured=C2=A0in a way to make them more user=
 friendly=C2=A0for both newcomers and those joining the discussion in a wor=
king group after a time away.=C2=A0 Some form of summary / update at the st=
art of a session setting out where the Group has reached and the expectatio=
ns=C2=A0of the dialogue to take place might be useful. This could, one supp=
oses, be effected in a couple=C2=A0of opening slides or in the &quot;chat&q=
uot;.=C2=A0 Thought could also be given to the conduct of the chat itself, =
often very informative and useful in supplementing the presentations, but s=
ometimes riddled with historical references, obscure=C2=A0acronyms and some=
 pretty hostile exchanges.=C2=A0</div><div><br></div><div>Many regards=C2=
=A0</div><div><br></div><div>Nigel=C2=A0</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, 1 Aug 2021 at 23:20, =
IETF Executive Director &lt;<a href=3D"mailto:exec-director@ietf.org" targe=
t=3D"_blank">exec-director@ietf.org</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">IETF 111<br>
26-30 July 2021<br>
Hosted by Juniper<br>
<br>
IETF 111 has concluded.=C2=A0 Thank you all participants, chairs, presenter=
s, contractors and staff who worked hard to put this meeting together.=C2=
=A0 This was our largest fully online meeting to date with over 1300 observ=
ed participants.=C2=A0 Full stats will follow in a later blog post.<br>
<br>
Recordings of IETF 111 sessions are at<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.youtube.com/playlist?lis=
t=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi6" rel=3D"noreferrer" target=3D"_blank=
">https://www.youtube.com/playlist?list=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi=
6</a><br>
<br>
<br>
This meeting has sparked a great discussion about the features of the servi=
ces we provide to support participation, including the Datatracker agenda, =
Meetecho and CodiMD, all of which will be followed up on to improve the exp=
erience further.<br>
<br>
We would really like to get more feedback through our short post-meeting su=
rvey that will only take you a few minutes to complete:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://ietf.iad1.qualtrics.com/jfe/=
form/SV_6PR0tAZvEidoY7A" rel=3D"noreferrer" target=3D"_blank">https://ietf.=
iad1.qualtrics.com/jfe/form/SV_6PR0tAZvEidoY7A</a> <br>
<br>
I hope it=E2=80=99s becoming clear to people who have attended multiple mee=
tings that we really do listen to the feedback in this survey and use that =
to drive improvements to the meeting experience.<br>
<br>
<br>
A final big thanks to Juniper for hosting this meeting and thank you also t=
o our Gold Diversity and Inclusivity sponsors, Akamai and Cisco, and to our=
 Bronze sponsors, Comcast, Donuts, ICANN and Verisign.<br>
<br>
<br>
-- <br>
Jay Daley<br>
IETF Executive Director<br>
<a href=3D"mailto:exec-director@ietf.org" target=3D"_blank">exec-director@i=
etf.org</a><br>
<br>
<br>
<br>
-- <br>
111all mailing list<br>
<a href=3D"mailto:111all@ietf.org" target=3D"_blank">111all@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/111all" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/111all</a><br>
</blockquote></div>
</div>
</div></div>

--000000000000a72b6c05c8981e91--


From nobody Mon Aug  2 12:27:02 2021
Return-Path: <rjsparks@nostrum.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D35333A1827; Mon,  2 Aug 2021 12:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level: 
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 lYW_nLs-KOJM; Mon,  2 Aug 2021 12:26:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17EC13A181D; Mon,  2 Aug 2021 12:26:53 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 172JQq6Z094896 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 2 Aug 2021 14:26:53 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1627932413; bh=hABfY5B/xLwT30/QzMAh8lsf9WWFnHQntSFMZ9+w0DE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=MuRxxofXviR32LdrKVaXxxX7eUmPtq7mJ/bxg0hQ+9Q6cKYcWUnjxRy9C6zdsxy2D XMbjiFF3JprbqFXhZeIiilS7xJ3QePtzWc2S9tNklkS6CoI8JXKsP1hkNz2muITDW4 rihGtEWusDM5Y35sESDKyS9OZAAUFG1oZNH5qoU0=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
To: Greg Wood <ghwood@ietf.org>, Sean Turner <sean@sn3rd.com>
Cc: "111attendees@ietf.org" <111attendees@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
References: <4108FC97-82EC-4F91-B359-EAAC71889CC4@akamai.com> <C1F9B8B1-320B-47F0-B3EA-3AB0278D5381@sn3rd.com> <5C6F4506-C253-4F13-A972-5135A3920625@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com>
Date: Mon, 2 Aug 2021 14:26:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <5C6F4506-C253-4F13-A972-5135A3920625@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/2m4fyqwHiw8tLnxRsnB9vA8vjeY>
Subject: Re: [111attendees] where will ANRW video's be?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 19:26:59 -0000

When the youtube videos are uploaded, links to them are provided to the 
datatracker. They show up on the agenda/proceedings page for the meeting 
(look at the last icon on the row on the agenda page).

Note that they can take some time, typically less than a day, after the 
session ends before they are uploaded.

RjS

On 7/28/21 12:00 PM, Greg Wood wrote:
> Hi,
>
> All the recordings from sessions during IETF meeting week will be available on the IETF YouTube channel:
>
> https://www.youtube.com/user/ietf
>
> There’s an IETF 111 play list:
>
> https://www.youtube.com/watch?v=CdP0TGoEjvs&list=PLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi6
>
> And there *will* be an ANRW playlist, but for now they can be found at:
>
> https://www.youtube.com/user/ietf/search?query=ANRW
>
> Let me know if I can provide more info.
>
> Thanks,
>
> -Greg
>
>
>> On Jul 28, 2021, at 12:46 PM, Sean Turner <sean@sn3rd.com> wrote:
>>
>> I think there’s a IETF youtube channel:
>> https://www.youtube.com/channel/UC8dtK9njBLdFnBahHFp0eZQ
>>
>>> On Jul 28, 2021, at 12:14, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>>>
>>> Because of TLS I can’t attend today’s ANRW session, and I really want to see the video’s once uploaded.  Anyone know where they will be, or how I can find that out?
>>> -- 
>>> 111attendees mailing list
>>> 111attendees@ietf.org
>>> https://www.ietf.org/mailman/listinfo/111attendees
>> -- 
>> 111attendees mailing list
>> 111attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/111attendees
>
>
>
> --
> Greg Wood
> IETF LLC
> +1-703-625-3917
>


From nobody Mon Aug  2 12:38:34 2021
Return-Path: <rjsparks@nostrum.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC8F3A18C3; Mon,  2 Aug 2021 12:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level: 
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 Bn2_a3zjb8b2; Mon,  2 Aug 2021 12:38:27 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E9443A18C2; Mon,  2 Aug 2021 12:38:27 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 172JcQwQ099139 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 2 Aug 2021 14:38:26 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1627933107; bh=laHyfBdeugYRelsexQsws/giSrPVZipYFOja+Q9uWKQ=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=N0UWjA9uEzcg9A8hyE7cleLpJ0an7IlPqvQiIFjSVx1yh1Dq3at1biMxjAa2CKpsx +AC18h5UJd1sXdLABBjP4hrkLGdZfvZbNyZPZFVgJm8z6A18fISxg6SFJ9Pltx/0DT GYrL8ahKu9txyoftOX1XL+WClpJLbVXh5xo9AG54=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
From: Robert Sparks <rjsparks@nostrum.com>
To: Greg Wood <ghwood@ietf.org>, Sean Turner <sean@sn3rd.com>
Cc: "111attendees@ietf.org" <111attendees@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
References: <4108FC97-82EC-4F91-B359-EAAC71889CC4@akamai.com> <C1F9B8B1-320B-47F0-B3EA-3AB0278D5381@sn3rd.com> <5C6F4506-C253-4F13-A972-5135A3920625@ietf.org> <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com>
Message-ID: <355982aa-106e-7f9f-2b45-c02db759c1ee@nostrum.com>
Date: Mon, 2 Aug 2021 14:38:21 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/bSeS-2kHNsuWcRmYQhHQr6FymZ4>
Subject: Re: [111attendees] where will ANRW video's be?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 19:38:32 -0000

Ah, but I see that the agenda is still pointing into meetecho instead of 
youtube, leading, after redirection, to a channel list and not the 
desired recording. Known issue that will be addressed, sorry it isn't 
fixed already.

RjS

On 8/2/21 2:26 PM, Robert Sparks wrote:
> When the youtube videos are uploaded, links to them are provided to 
> the datatracker. They show up on the agenda/proceedings page for the 
> meeting (look at the last icon on the row on the agenda page).
>
> Note that they can take some time, typically less than a day, after 
> the session ends before they are uploaded.
>
> RjS
>
> On 7/28/21 12:00 PM, Greg Wood wrote:
>> Hi,
>>
>> All the recordings from sessions during IETF meeting week will be 
>> available on the IETF YouTube channel:
>>
>> https://www.youtube.com/user/ietf
>>
>> There’s an IETF 111 play list:
>>
>> https://www.youtube.com/watch?v=CdP0TGoEjvs&list=PLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi6 
>>
>>
>> And there *will* be an ANRW playlist, but for now they can be found at:
>>
>> https://www.youtube.com/user/ietf/search?query=ANRW
>>
>> Let me know if I can provide more info.
>>
>> Thanks,
>>
>> -Greg
>>
>>
>>> On Jul 28, 2021, at 12:46 PM, Sean Turner <sean@sn3rd.com> wrote:
>>>
>>> I think there’s a IETF youtube channel:
>>> https://www.youtube.com/channel/UC8dtK9njBLdFnBahHFp0eZQ
>>>
>>>> On Jul 28, 2021, at 12:14, Salz, Rich 
>>>> <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>>>>
>>>> Because of TLS I can’t attend today’s ANRW session, and I really 
>>>> want to see the video’s once uploaded.  Anyone know where they will 
>>>> be, or how I can find that out?
>>>> -- 
>>>> 111attendees mailing list
>>>> 111attendees@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/111attendees
>>> -- 
>>> 111attendees mailing list
>>> 111attendees@ietf.org
>>> https://www.ietf.org/mailman/listinfo/111attendees
>>
>>
>>
>> -- 
>> Greg Wood
>> IETF LLC
>> +1-703-625-3917
>>


From nobody Mon Aug  2 15:23:13 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDED3A1F08; Mon,  2 Aug 2021 15:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4-JcF78XANNb; Mon,  2 Aug 2021 15:23:06 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB9163A1F07; Mon,  2 Aug 2021 15:23:05 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id gs8so33229989ejc.13; Mon, 02 Aug 2021 15:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bGRRL8qo+r3nNWvdeY2JfBTSMtToYUIPs+GfaAap0zk=; b=f9e5nNvwoZOQW2rzI/xx+YlCChYWH4wuG4L+q2ir7sd30iQoSidq9TMy0pm/zzSYRu irPlCM8EUGbXJGa+hNs21NynRwPou2wYEUwA8dk83hWk/C5+75m2XrfpZcNkh+Jr3Sqf RoEDkpZED9QHKMsceaQv8N0Loub9qD0ddRFKmx9BC0snT301mADcTX+iMr1DkOwrI9PV GVQ4jIoEbnxkyxdV0m+UeWYmcmimvAXk1EfBLbjj0N+JOEToG4hxd88B7u6HdUWTAoKN EXJNM12m36s50+vk/I9wtHNcxcRvjm2EPJWo115SLkrlLJI8bEWQe9zel/c3YFdE5BN2 xCuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bGRRL8qo+r3nNWvdeY2JfBTSMtToYUIPs+GfaAap0zk=; b=C0je0FA0owdQGc42YIQJNgQp1P6A9EnlH9ZrQdI+jvfi+TAnx+KwQvGWEcQnujNuy0 aWTbr3grdEsTwZg6o3fGUG+j+/x8GGBYspn6n5tkB8ZZsRA3drMVnJtg9iBlbPOQRIy8 H/qGjC3tJDv7uSWOa/Z01qJkT6bh0/kTiTpQAzbXHxVQMTm1um6KHlizBX8/swj8wF/7 FUgj55fpgzE2Js0AxdgTaJQcaOubIyMsdjQZ2UlH5r8vmNZC6SaKl2v4NCSDlBW9t4zo yKfUkaNHYN9/4I+ZtCvGV2y5rQo9coj2trD8PxFjtGm61EwBQvhxYJtzeARFsXBEe8X0 10rw==
X-Gm-Message-State: AOAM531E2yeVEWa9GjuKerdy6LmPfdK9B7GFe3xkPfRH2deLkVyKxqBr ODQZvF4c6OqBUYRYEwUQDPcEH2QOsh9z9VnJBvE=
X-Google-Smtp-Source: ABdhPJxuXZvpwl76dFxM9SHXIDaHcj/FeB3Cfp/M3x7FrRQiJvyBmHNSpOyksX+4kdx62T7qGJ+pftGXL6sWWea1i9I=
X-Received: by 2002:a17:906:d105:: with SMTP id b5mr17909672ejz.340.1627942979262;  Mon, 02 Aug 2021 15:22:59 -0700 (PDT)
MIME-Version: 1.0
References: <4108FC97-82EC-4F91-B359-EAAC71889CC4@akamai.com> <C1F9B8B1-320B-47F0-B3EA-3AB0278D5381@sn3rd.com> <5C6F4506-C253-4F13-A972-5135A3920625@ietf.org> <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com> <355982aa-106e-7f9f-2b45-c02db759c1ee@nostrum.com>
In-Reply-To: <355982aa-106e-7f9f-2b45-c02db759c1ee@nostrum.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:52:47 +0430
Message-ID: <CA+d13g0B669muDVKsawyMbvixcAhJQBu712v8DDjr2ipmRK-Tg@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Greg Wood <ghwood@ietf.org>, Sean Turner <sean@sn3rd.com>, 111attendees@ietf.org, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fe5df405c89b02ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/LdT7IzieSxrf4Qjb9PI6wh3RZDE>
Subject: Re: [111attendees] where will ANRW video's be?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:23:11 -0000

--000000000000fe5df405c89b02ed
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B3=D9=87=E2=80=8C=D8=B4=D9=
=86=D8=A8=D9=87 =DB=B3 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=
=80=8F =DB=B0:=DB=B0=DB=B8 Robert Sparks <rjsparks@nostrum.com>
=D9=86=D9=88=D8=B4=D8=AA:

> Ah, but I see that the agenda is still pointing into meetecho instead of
> youtube, leading, after redirection, to a channel list and not the
> desired recording. Known issue that will be addressed, sorry it isn't
> fixed already.
>
> RjS
>
> On 8/2/21 2:26 PM, Robert Sparks wrote:
> > When the youtube videos are uploaded, links to them are provided to
> > the datatracker. They show up on the agenda/proceedings page for the
> > meeting (look at the last icon on the row on the agenda page).
> >
> > Note that they can take some time, typically less than a day, after
> > the session ends before they are uploaded.
> >
> > RjS
> >
> > On 7/28/21 12:00 PM, Greg Wood wrote:
> >> Hi,
> >>
> >> All the recordings from sessions during IETF meeting week will be
> >> available on the IETF YouTube channel:
> >>
> >> https://www.youtube.com/user/ietf
> >>
> >> There=E2=80=99s an IETF 111 play list:
> >>
> >>
> https://www.youtube.com/watch?v=3DCdP0TGoEjvs&list=3DPLC86T-6ZTP5ik187oPf=
RrOUaMw1AuLLi6
> >>
> >>
> >> And there *will* be an ANRW playlist, but for now they can be found at=
:
> >>
> >> https://www.youtube.com/user/ietf/search?query=3DANRW
> >>
> >> Let me know if I can provide more info.
> >>
> >> Thanks,
> >>
> >> -Greg
> >>
> >>
> >>> On Jul 28, 2021, at 12:46 PM, Sean Turner <sean@sn3rd.com> wrote:
> >>>
> >>> I think there=E2=80=99s a IETF youtube channel:
> >>> https://www.youtube.com/channel/UC8dtK9njBLdFnBahHFp0eZQ
> >>>
> >>>> On Jul 28, 2021, at 12:14, Salz, Rich
> >>>> <rsalz=3D40akamai.com@dmarc.ietf.org> wrote:
> >>>>
> >>>> Because of TLS I can=E2=80=99t attend today=E2=80=99s ANRW session, =
and I really
> >>>> want to see the video=E2=80=99s once uploaded.  Anyone know where th=
ey will
> >>>> be, or how I can find that out?
> >>>> --
> >>>> 111attendees mailing list
> >>>> 111attendees@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/111attendees
> >>> --
> >>> 111attendees mailing list
> >>> 111attendees@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/111attendees
> >>
> >>
> >>
> >> --
> >> Greg Wood
> >> IETF LLC
> >> +1-703-625-3917
> >>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000fe5df405c89b02ed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B3=D9=87=
=E2=80=8C=D8=B4=D9=86=D8=A8=D9=87 =DB=B3 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=
=B2=DB=B1=D8=8C=E2=80=8F =DB=B0:=DB=B0=DB=B8 Robert Sparks &lt;<a href=3D"m=
ailto:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt; =D9=86=D9=88=D8=B4=
=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">Ah, but I see that the agen=
da is still pointing into meetecho instead of <br>
youtube, leading, after redirection, to a channel list and not the <br>
desired recording. Known issue that will be addressed, sorry it isn&#39;t <=
br>
fixed already.<br>
<br>
RjS<br>
<br>
On 8/2/21 2:26 PM, Robert Sparks wrote:<br>
&gt; When the youtube videos are uploaded, links to them are provided to <b=
r>
&gt; the datatracker. They show up on the agenda/proceedings page for the <=
br>
&gt; meeting (look at the last icon on the row on the agenda page).<br>
&gt;<br>
&gt; Note that they can take some time, typically less than a day, after <b=
r>
&gt; the session ends before they are uploaded.<br>
&gt;<br>
&gt; RjS<br>
&gt;<br>
&gt; On 7/28/21 12:00 PM, Greg Wood wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; All the recordings from sessions during IETF meeting week will be =
<br>
&gt;&gt; available on the IETF YouTube channel:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.youtube.com/user/ietf" rel=3D"noreferrer no=
referrer" target=3D"_blank">https://www.youtube.com/user/ietf</a><br>
&gt;&gt;<br>
&gt;&gt; There=E2=80=99s an IETF 111 play list:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.youtube.com/watch?v=3DCdP0TGoEjvs&amp;list=
=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi6" rel=3D"noreferrer noreferrer" target=
=3D"_blank">https://www.youtube.com/watch?v=3DCdP0TGoEjvs&amp;list=3DPLC86T=
-6ZTP5ik187oPfRrOUaMw1AuLLi6</a> <br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; And there *will* be an ANRW playlist, but for now they can be foun=
d at:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.youtube.com/user/ietf/search?query=3DANRW" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.youtube.com/use=
r/ietf/search?query=3DANRW</a><br>
&gt;&gt;<br>
&gt;&gt; Let me know if I can provide more info.<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt;<br>
&gt;&gt; -Greg<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Jul 28, 2021, at 12:46 PM, Sean Turner &lt;<a href=3D"mailt=
o:sean@sn3rd.com" target=3D"_blank" rel=3D"noreferrer">sean@sn3rd.com</a>&g=
t; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think there=E2=80=99s a IETF youtube channel:<br>
&gt;&gt;&gt; <a href=3D"https://www.youtube.com/channel/UC8dtK9njBLdFnBahHF=
p0eZQ" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.youtube.=
com/channel/UC8dtK9njBLdFnBahHFp0eZQ</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Jul 28, 2021, at 12:14, Salz, Rich <br>
&gt;&gt;&gt;&gt; &lt;rsalz=3D<a href=3D"mailto:40akamai.com@dmarc.ietf.org"=
 target=3D"_blank" rel=3D"noreferrer">40akamai.com@dmarc.ietf.org</a>&gt; w=
rote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Because of TLS I can=E2=80=99t attend today=E2=80=99s ANRW=
 session, and I really <br>
&gt;&gt;&gt;&gt; want to see the video=E2=80=99s once uploaded.=C2=A0 Anyon=
e know where they will <br>
&gt;&gt;&gt;&gt; be, or how I can find that out?<br>
&gt;&gt;&gt;&gt; -- <br>
&gt;&gt;&gt;&gt; 111attendees mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:111attendees@ietf.org" target=3D"_blank"=
 rel=3D"noreferrer">111attendees@ietf.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/111attend=
ees" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/111attendees</a><br>
&gt;&gt;&gt; -- <br>
&gt;&gt;&gt; 111attendees mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=
=3D"noreferrer">111attendees@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/111attendees"=
 rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/111attendees</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -- <br>
&gt;&gt; Greg Wood<br>
&gt;&gt; IETF LLC<br>
&gt;&gt; +1-703-625-3917<br>
&gt;&gt;<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000fe5df405c89b02ed--


From nobody Mon Aug  2 15:23:25 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B47053A1F33; Mon,  2 Aug 2021 15:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 roVYdy1hK6SW; Mon,  2 Aug 2021 15:23:12 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B47313A1F0D; Mon,  2 Aug 2021 15:23:11 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id e19so33295991ejs.9; Mon, 02 Aug 2021 15:23:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WlCowOBLR0FN7Ttz51YgkkpNlpPKGpLKk6k5UWo4N/E=; b=ZPPEUsgg7KuH7aUUnaT311L+9Wlrf9pIDSbkInQxrFxTGMxH4WCSUajohbN8aE/WjI LbCvrj8tx2P+M0XP6rZgSYefqPliYNVsqGBlytB2agDVjHj/92B7GUcjF2K64wX2Mu0z x0nSpGFlf9f5qsl21L62g2JJ14tE5yiitX1ykLipD7EpPfkZW4M/Gq2lHmo6cLpBs+cF JHsq+LpWQ3H5DOR7V78zwxyxtgwrpo8RSkkLiqk99PzTRM10xTiyW4KLBCILgPYF2Pev ulD98+wRKsBcTL8DRMrViBA1JtEABLgGRPftY4AuDsn255mButCW7iGpSoZhBvfiusdr deow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WlCowOBLR0FN7Ttz51YgkkpNlpPKGpLKk6k5UWo4N/E=; b=BOp4iF3HWExVoi/SXA65ysfR8Id/mitqnOcdj83q+RmB1hF5gGsrgZ6adZelOxqhom L5xz+mLPF9H1Q7xQXCKMcqG5DdabBBP5OId3Sso+d/iftsRkZrgLW4QiURr4gTvHWDzl +s2ps4avdKBE788BeCBvysgF6bqV1jE4hT1/NzGV4zGSKmMjVfx0QHYiVQ9Pe1dlZ0W9 awXaeoM1a5B36yiphingssalZhFcDalF5oLIOKucgPAFso7X1KlECfxjfX+JGesb9Nf7 X+VoNVzQQMgw5ZpNIrS/K5168CaE0uMwmxPKYHUFd8LqatexAPk5Q5i0ckhuh3EoH1UL ekOQ==
X-Gm-Message-State: AOAM531peMxfMHzCsHBQlKbHyk8dHCHF86ytseeq4l9H212Du0mAF/6e DjBtOiDdhb4Thi8NWHXswaSIYf/GkbQKHFZpeKk=
X-Google-Smtp-Source: ABdhPJx1j0UmLeyMplF/T7yFNS1iJyKJtOc3OzHnl6/Tx704IBiJ88GCCMRamvTxiW9qLYcafGoRDyE5E9rrFYYDACk=
X-Received: by 2002:a17:906:2dc5:: with SMTP id h5mr6935565eji.515.1627942988531;  Mon, 02 Aug 2021 15:23:08 -0700 (PDT)
MIME-Version: 1.0
References: <4108FC97-82EC-4F91-B359-EAAC71889CC4@akamai.com> <C1F9B8B1-320B-47F0-B3EA-3AB0278D5381@sn3rd.com> <5C6F4506-C253-4F13-A972-5135A3920625@ietf.org> <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com>
In-Reply-To: <412f82d4-19a3-4e2d-8b8e-c3ff5602176d@nostrum.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:52:57 +0430
Message-ID: <CA+d13g29=nAnKP0hSJLebOHGghuwb83Lo-5PDa9=C6FtM3q8TQ@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Greg Wood <ghwood@ietf.org>, Sean Turner <sean@sn3rd.com>, 111attendees@ietf.org, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008bcbfa05c89b03ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/NoByaYg3u1aoeRYmWUhXKJ9eB80>
Subject: Re: [111attendees] where will ANRW video's be?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:23:23 -0000

--0000000000008bcbfa05c89b03ad
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B3:=DB=B5=DB=B7 Robert Sparks <rjsparks@nostrum.com>
=D9=86=D9=88=D8=B4=D8=AA:

> When the youtube videos are uploaded, links to them are provided to the
> datatracker. They show up on the agenda/proceedings page for the meeting
> (look at the last icon on the row on the agenda page).
>
> Note that they can take some time, typically less than a day, after the
> session ends before they are uploaded.
>
> RjS
>
> On 7/28/21 12:00 PM, Greg Wood wrote:
> > Hi,
> >
> > All the recordings from sessions during IETF meeting week will be
> available on the IETF YouTube channel:
> >
> > https://www.youtube.com/user/ietf
> >
> > There=E2=80=99s an IETF 111 play list:
> >
> >
> https://www.youtube.com/watch?v=3DCdP0TGoEjvs&list=3DPLC86T-6ZTP5ik187oPf=
RrOUaMw1AuLLi6
> >
> > And there *will* be an ANRW playlist, but for now they can be found at:
> >
> > https://www.youtube.com/user/ietf/search?query=3DANRW
> >
> > Let me know if I can provide more info.
> >
> > Thanks,
> >
> > -Greg
> >
> >
> >> On Jul 28, 2021, at 12:46 PM, Sean Turner <sean@sn3rd.com> wrote:
> >>
> >> I think there=E2=80=99s a IETF youtube channel:
> >> https://www.youtube.com/channel/UC8dtK9njBLdFnBahHFp0eZQ
> >>
> >>> On Jul 28, 2021, at 12:14, Salz, Rich <rsalz=3D
> 40akamai.com@dmarc.ietf.org> wrote:
> >>>
> >>> Because of TLS I can=E2=80=99t attend today=E2=80=99s ANRW session, a=
nd I really want
> to see the video=E2=80=99s once uploaded.  Anyone know where they will be=
, or how I
> can find that out?
> >>> --
> >>> 111attendees mailing list
> >>> 111attendees@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/111attendees
> >> --
> >> 111attendees mailing list
> >> 111attendees@ietf.org
> >> https://www.ietf.org/mailman/listinfo/111attendees
> >
> >
> >
> > --
> > Greg Wood
> > IETF LLC
> > +1-703-625-3917
> >
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000008bcbfa05c89b03ad
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B3:=DB=B5=DB=B7 Robert Sparks &lt;<a href=3D"mail=
to:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt; =D9=86=D9=88=D8=B4=D8=
=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">When the youtube videos are up=
loaded, links to them are provided to the <br>
datatracker. They show up on the agenda/proceedings page for the meeting <b=
r>
(look at the last icon on the row on the agenda page).<br>
<br>
Note that they can take some time, typically less than a day, after the <br=
>
session ends before they are uploaded.<br>
<br>
RjS<br>
<br>
On 7/28/21 12:00 PM, Greg Wood wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; All the recordings from sessions during IETF meeting week will be avai=
lable on the IETF YouTube channel:<br>
&gt;<br>
&gt; <a href=3D"https://www.youtube.com/user/ietf" rel=3D"noreferrer norefe=
rrer" target=3D"_blank">https://www.youtube.com/user/ietf</a><br>
&gt;<br>
&gt; There=E2=80=99s an IETF 111 play list:<br>
&gt;<br>
&gt; <a href=3D"https://www.youtube.com/watch?v=3DCdP0TGoEjvs&amp;list=3DPL=
C86T-6ZTP5ik187oPfRrOUaMw1AuLLi6" rel=3D"noreferrer noreferrer" target=3D"_=
blank">https://www.youtube.com/watch?v=3DCdP0TGoEjvs&amp;list=3DPLC86T-6ZTP=
5ik187oPfRrOUaMw1AuLLi6</a><br>
&gt;<br>
&gt; And there *will* be an ANRW playlist, but for now they can be found at=
:<br>
&gt;<br>
&gt; <a href=3D"https://www.youtube.com/user/ietf/search?query=3DANRW" rel=
=3D"noreferrer noreferrer" target=3D"_blank">https://www.youtube.com/user/i=
etf/search?query=3DANRW</a><br>
&gt;<br>
&gt; Let me know if I can provide more info.<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; -Greg<br>
&gt;<br>
&gt;<br>
&gt;&gt; On Jul 28, 2021, at 12:46 PM, Sean Turner &lt;<a href=3D"mailto:se=
an@sn3rd.com" target=3D"_blank" rel=3D"noreferrer">sean@sn3rd.com</a>&gt; w=
rote:<br>
&gt;&gt;<br>
&gt;&gt; I think there=E2=80=99s a IETF youtube channel:<br>
&gt;&gt; <a href=3D"https://www.youtube.com/channel/UC8dtK9njBLdFnBahHFp0eZ=
Q" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.youtube.com/=
channel/UC8dtK9njBLdFnBahHFp0eZQ</a><br>
&gt;&gt;<br>
&gt;&gt;&gt; On Jul 28, 2021, at 12:14, Salz, Rich &lt;rsalz=3D<a href=3D"m=
ailto:40akamai.com@dmarc.ietf.org" target=3D"_blank" rel=3D"noreferrer">40a=
kamai.com@dmarc.ietf.org</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Because of TLS I can=E2=80=99t attend today=E2=80=99s ANRW ses=
sion, and I really want to see the video=E2=80=99s once uploaded.=C2=A0 Any=
one know where they will be, or how I can find that out?<br>
&gt;&gt;&gt; -- <br>
&gt;&gt;&gt; 111attendees mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=
=3D"noreferrer">111attendees@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/111attendees"=
 rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/111attendees</a><br>
&gt;&gt; -- <br>
&gt;&gt; 111attendees mailing list<br>
&gt;&gt; <a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"=
noreferrer">111attendees@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=
=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/111attendees</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Greg Wood<br>
&gt; IETF LLC<br>
&gt; +1-703-625-3917<br>
&gt;<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000008bcbfa05c89b03ad--


From nobody Mon Aug  2 15:23:53 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85F903A1F45 for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VU1vjpdmgjKM for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:23:38 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C47D73A1F4F for <111attendees@ietf.org>; Mon,  2 Aug 2021 15:23:37 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id oz16so33266001ejc.7 for <111attendees@ietf.org>; Mon, 02 Aug 2021 15:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gUlaxamg21lTx2Wl9YoqDSyC87XgmgOZ8MfSW6hOQHE=; b=TlJAnomGwNIZN9hvVbMZxDf1ykWOd4UR5jK3WKlzzCpKTTLC2fhsSGIv4169/uoCJ2 GW+ulfW3jrA3vd6bqLeAPWYQysf6qCqmuM6/AS8ecWpzpecfNLAAzpR5xuMVBYaY3/TG jhUNbsGE8sKbd+k0gCueGeHT5gFiFixGG7nSzVu7ZBqs4gkEn047qafunZpbRT7AEgHL eJBFK/AzU+z//yrny9KzbXTVJ23ozmC0ZkWLK18k2LrvI53aOgZkUo0eQMPNg2Rj5pSL fEC02X7mbEyAtFT6IU2LgerfNGkB3TdhhzyEmjs4tSKD+X3dSfzXjGqcvu13A5wSSzD+ sJpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gUlaxamg21lTx2Wl9YoqDSyC87XgmgOZ8MfSW6hOQHE=; b=LcBJl27HwVafBZUSVFTgfRjuNHOUtwR12jHkTWTAhnCo7f4y0Yln5NWTZLsWEImihS qr8DGG1BfNS0dvr1pMwl+OLD2iY/RxiBjntZpzWue3ok+2y7OOwzU8FvxGfVmNMiq8t0 7bbayaVLWY8WjRAEvAwy1WDNUm1iy8Yru+o17H8nvr27sgq+k9qCtKPU3dyK1DnwnDW2 9yGSVkw7Gof7wzWw6bV2YaFhT2pEKRS4InSVLKr2N/gONnv0MG0bybopAeH5vIK8d3i1 A5bgBU9IfJSHFBNtePnRBXn5hRcbDQck1OWJhUMqUoDXLEgfPfXSXL3SZaAgv1KnJXVz hpSA==
X-Gm-Message-State: AOAM531VXmR+xy/9sdcisn/J1QN7m2J34yzBe7HBi8dy5sBoikKFwPjR mjibeqBnRg1MjzQKgS57H6Ym8vmsM7lXrrTbJZA=
X-Google-Smtp-Source: ABdhPJwGTMNlMfET8Q0BPqd1Ix5bFuLALKd+aYItS/hfBlCz1rVwb/UuCR2YvOMFyF+ZESyM9b6C4m59J13Kmdm7CaE=
X-Received: by 2002:a17:906:ed1:: with SMTP id u17mr17210338eji.304.1627943015710;  Mon, 02 Aug 2021 15:23:35 -0700 (PDT)
MIME-Version: 1.0
References: <7B4B465C-722E-4FC6-BAC1-9C1F18CF01AF@ietf.org> <CAAm_rSLRb3+qirZO9kg1FY16o7DDcukrp3WU5yVtzagOSu7TnQ@mail.gmail.com> <CAAm_rS+=a89=-KvHS2q0S-EUFUE-mczQRR_UYLSU29moXvfG7g@mail.gmail.com>
In-Reply-To: <CAAm_rS+=a89=-KvHS2q0S-EUFUE-mczQRR_UYLSU29moXvfG7g@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:53:24 +0430
Message-ID: <CA+d13g361HbQNEAoCLE5i-n=FrgjSAdCFWXE7DOy_4mXtNLoGw@mail.gmail.com>
To: Nigel Hickson <nigel.hickson=40dcms.gov.uk@dmarc.ietf.org>
Cc: 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002a84df05c89b0584"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/DkaDf0W-MM0wyg-3nblhBhU-x7Q>
Subject: Re: [111attendees] Fwd: [111all] IETF 111 - Post-meeting follow up, survey and special thanks
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:23:51 -0000

--0000000000002a84df05c89b0584
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B3:=DB=B2=DB=B6 Nigel Hickson <nigel.hickson=3D
40dcms.gov.uk@dmarc.ietf.org> =D9=86=D9=88=D8=B4=D8=AA:

>
>
> Jay
>
> Good afternoon.  Thank you for this. While there was a lot of substance
> for consideration and further thought, I did just want to make a couple o=
f
> non-policy observations as a newcomer to IETF Meetings.
>
> The first would be to thank the IETF Secretariat (and no doubt others) fo=
r
> making us so welcome, not least in Newcomer sessions and during the meeti=
ng
> itself.  Additionally the platform used was pretty user friendly and
> encouraged interaction and dialogue.
>
> The second would be to encourage some thinking (and perhaps this has
> already taken place) on how the sessions themselves might be structured i=
n
> a way to make them more user friendly for both newcomers and those joinin=
g
> the discussion in a working group after a time away.  Some form of summar=
y
> / update at the start of a session setting out where the Group has reache=
d
> and the expectations of the dialogue to take place might be useful. This
> could, one supposes, be effected in a couple of opening slides or in the
> "chat".  Thought could also be given to the conduct of the chat itself,
> often very informative and useful in supplementing the presentations, but
> sometimes riddled with historical references, obscure acronyms and some
> pretty hostile exchanges.
>
> Many regards
>
> Nigel
>
> On Sun, 1 Aug 2021 at 23:20, IETF Executive Director <
> exec-director@ietf.org> wrote:
>
>> IETF 111
>> 26-30 July 2021
>> Hosted by Juniper
>>
>> IETF 111 has concluded.  Thank you all participants, chairs, presenters,
>> contractors and staff who worked hard to put this meeting together.  Thi=
s
>> was our largest fully online meeting to date with over 1300 observed
>> participants.  Full stats will follow in a later blog post.
>>
>> Recordings of IETF 111 sessions are at
>>
>>
>> https://www.youtube.com/playlist?list=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLL=
i6
>>
>>
>> This meeting has sparked a great discussion about the features of the
>> services we provide to support participation, including the Datatracker
>> agenda, Meetecho and CodiMD, all of which will be followed up on to impr=
ove
>> the experience further.
>>
>> We would really like to get more feedback through our short post-meeting
>> survey that will only take you a few minutes to complete:
>>
>>         https://ietf.iad1.qualtrics.com/jfe/form/SV_6PR0tAZvEidoY7A
>>
>> I hope it=E2=80=99s becoming clear to people who have attended multiple =
meetings
>> that we really do listen to the feedback in this survey and use that to
>> drive improvements to the meeting experience.
>>
>>
>> A final big thanks to Juniper for hosting this meeting and thank you als=
o
>> to our Gold Diversity and Inclusivity sponsors, Akamai and Cisco, and to
>> our Bronze sponsors, Comcast, Donuts, ICANN and Verisign.
>>
>>
>> --
>> Jay Daley
>> IETF Executive Director
>> exec-director@ietf.org
>>
>>
>>
>> --
>> 111all mailing list
>> 111all@ietf.org
>> https://www.ietf.org/mailman/listinfo/111all
>>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000002a84df05c89b0584
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B3:=DB=B2=DB=B6 Nigel Hickson &lt;nigel.hickson=
=3D<a href=3D"mailto:40dcms.gov.uk@dmarc.ietf.org">40dcms.gov.uk@dmarc.ietf=
.org</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr"><br></div><br><div dir=3D"ltr"><div dir=3D"ltr">Jay=C2=A0<div><b=
r></div><div>Good afternoon.=C2=A0 Thank you for this. While there was a lo=
t of substance for consideration=C2=A0and=C2=A0further thought, I did just =
want to make a couple of non-policy observations as a newcomer to IETF Meet=
ings.=C2=A0</div><div><br></div><div>The first would be to thank the IETF S=
ecretariat (and no doubt others) for making us so welcome, not least in New=
comer sessions and during the meeting itself.=C2=A0 Additionally the platfo=
rm=C2=A0used was pretty user friendly and encouraged interaction and dialog=
ue.=C2=A0</div><div><br></div><div>The second would be to encourage some th=
inking (and=C2=A0perhaps this has already taken place) on how the=C2=A0sess=
ions=C2=A0themselves might be structured=C2=A0in a way to make them more us=
er friendly=C2=A0for both newcomers and those joining the discussion in a w=
orking group after a time away.=C2=A0 Some form of summary / update at the =
start of a session setting out where the Group has reached and the expectat=
ions=C2=A0of the dialogue to take place might be useful. This could, one su=
pposes, be effected in a couple=C2=A0of opening slides or in the &quot;chat=
&quot;.=C2=A0 Thought could also be given to the conduct of the chat itself=
, often very informative and useful in supplementing the presentations, but=
 sometimes riddled with historical references, obscure=C2=A0acronyms and so=
me pretty hostile exchanges.=C2=A0</div><div><br></div><div>Many regards=C2=
=A0</div><div><br></div><div>Nigel=C2=A0</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, 1 Aug 2021 at 23:20, =
IETF Executive Director &lt;<a href=3D"mailto:exec-director@ietf.org" targe=
t=3D"_blank" rel=3D"noreferrer">exec-director@ietf.org</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">IETF 111<br>
26-30 July 2021<br>
Hosted by Juniper<br>
<br>
IETF 111 has concluded.=C2=A0 Thank you all participants, chairs, presenter=
s, contractors and staff who worked hard to put this meeting together.=C2=
=A0 This was our largest fully online meeting to date with over 1300 observ=
ed participants.=C2=A0 Full stats will follow in a later blog post.<br>
<br>
Recordings of IETF 111 sessions are at<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.youtube.com/playlist?lis=
t=3DPLC86T-6ZTP5ik187oPfRrOUaMw1AuLLi6" rel=3D"noreferrer noreferrer" targe=
t=3D"_blank">https://www.youtube.com/playlist?list=3DPLC86T-6ZTP5ik187oPfRr=
OUaMw1AuLLi6</a><br>
<br>
<br>
This meeting has sparked a great discussion about the features of the servi=
ces we provide to support participation, including the Datatracker agenda, =
Meetecho and CodiMD, all of which will be followed up on to improve the exp=
erience further.<br>
<br>
We would really like to get more feedback through our short post-meeting su=
rvey that will only take you a few minutes to complete:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://ietf.iad1.qualtrics.com/jfe/=
form/SV_6PR0tAZvEidoY7A" rel=3D"noreferrer noreferrer" target=3D"_blank">ht=
tps://ietf.iad1.qualtrics.com/jfe/form/SV_6PR0tAZvEidoY7A</a> <br>
<br>
I hope it=E2=80=99s becoming clear to people who have attended multiple mee=
tings that we really do listen to the feedback in this survey and use that =
to drive improvements to the meeting experience.<br>
<br>
<br>
A final big thanks to Juniper for hosting this meeting and thank you also t=
o our Gold Diversity and Inclusivity sponsors, Akamai and Cisco, and to our=
 Bronze sponsors, Comcast, Donuts, ICANN and Verisign.<br>
<br>
<br>
-- <br>
Jay Daley<br>
IETF Executive Director<br>
<a href=3D"mailto:exec-director@ietf.org" target=3D"_blank" rel=3D"noreferr=
er">exec-director@ietf.org</a><br>
<br>
<br>
<br>
-- <br>
111all mailing list<br>
<a href=3D"mailto:111all@ietf.org" target=3D"_blank" rel=3D"noreferrer">111=
all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111all" rel=3D"noreferrer =
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/111all<=
/a><br>
</blockquote></div>
</div>
</div></div>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000002a84df05c89b0584--


From nobody Mon Aug  2 15:24:27 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5336F3A1F2A; Mon,  2 Aug 2021 15:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xjkbT-HJKfOz; Mon,  2 Aug 2021 15:24:12 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DFD83A1F3B; Mon,  2 Aug 2021 15:24:12 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id f13so26476944edq.13; Mon, 02 Aug 2021 15:24:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c3qnhkilVEk0ftQSvutgn33T5xytt4BrWeTMIl7euuc=; b=m8LcCkSpXKE7cG4AS1jrJcGpbfKRIVLRO4umuHu1wkYiadIKBGRKdqT4TX2t0c9ebY vzqLyh46Abr31HkKqZEE+4gOTl1lkHK0AwhEhec8c4bBFHa9q3d1YU8553aeQJNdqVdk acfvniCfDbVtc1ayYw4k9oIs7N8wZLjeNzghPilStX9UcgeNCZ1kU2dmp0CTLZDQMMDl sBH0M/GwC3rRHfwmGBtBzXOO3ZKyILrk4I9GrskAbb0ucw/fRPOKC0y0ExHx1+AWa4RD 3spWLCJQISBLOttLiWIdxTB78gw4I1aqQTSAewBBOzYG4jLzSfOvbLOBXyu0pW1ERoB6 q2MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c3qnhkilVEk0ftQSvutgn33T5xytt4BrWeTMIl7euuc=; b=Jt0hrsX0HxwgVrAk8LpQrPmYio/SBWSYVcrTTIsdA0Lxg1sdncq0/aYR5CpIl3j1Dv xibQa25QtjUyx3dfds3dy8chpqTkK5b2EFHmZ8I27zLQ0DjLhwStyc2+P3GrLz3pbph6 x/ZvwIB/B8QIt5hfNHE+6DQvYM1ozsIf7UUmq+2R5tzaewoteoD7kVte0hz8SltXvx5m iXxXyUA2xz9sSxMjLTvVvDxgWXiGflKTj9FVZ19QXSiVt49Oi98zz8aq/lTEmGzXurXH eNy8VAcSsrWmsbdEUqk1y15OwbKNg0uJniFglskW3fMxieWEtEPLwASnE7muNVafp3hs fsNw==
X-Gm-Message-State: AOAM532nA1YkeCUIzfiA3Dpxix39KYKYgms0rLqb9kYfjKj579IS4Oto MoxD9JVL9XRZPfc0vIcN8MjnAai1n/pIdmYrhJUZ0wWykS+qGw==
X-Google-Smtp-Source: ABdhPJzz1gDGncwBlUA1TNXg8XmD51lVj6pjsVgeKb0RkD/3MVs785c0dSYChH5KWpJa/o/hkpANxhNTGMNpDY6+ou0=
X-Received: by 2002:a05:6402:1e96:: with SMTP id f22mr16214455edf.189.1627943045521;  Mon, 02 Aug 2021 15:24:05 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
In-Reply-To: <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:53:54 +0430
Message-ID: <CA+d13g3GGfFstzFwn-1400GLagMg1W8Ei4kZ-5tnKCvJk6kU2A@mail.gmail.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: tools-discuss@ietf.org, Meetecho IETF support <ietf@meetecho.com>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f1642c05c89b0657"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/VafR1CyjZYJlcluxdsUjC7D9dPY>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:24:26 -0000

--000000000000f1642c05c89b0657
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B2:=DB=B1=DB=B8 Marc Petit-Huguenin <
marc@petit-huguenin.org> =D9=86=D9=88=D8=B4=D8=AA:

> One use of the Meetecho recording is to prepare minutes by double checkin=
g
> notes.  One issue with that is that sometimes a presenter answers comment=
s
> made in the chat, but the chat log does not appear in the recording.  The
> person preparing the minutes now has to open the minutes, try to
> synchronize then with the recording and update the minutes to reflect the
> question/comment that triggers the response by the presenter.  There is t=
wo
> issues with that:
>
> 1. Someone watching only the recording only have access to half of that
> conversation and may not know where the chat logs are, or even that they
> was a chat running along the session.
> 2. People taking notes must follow both the chat and the presenter, which
> could be a bit too much.
>
> I do not think that recording the chat at the same time than the presente=
r
> would be a good idea (OTOH displaying the name of the person talking in t=
he
> recording even if they did not turn on video would help).  The reason is
> that not all the content of the chat log is relevant for the WG business
> (that's an understatement).
>
> Having a jabber scribe and some discipline may help: The jabber scribe
> repeats the chat comment/question, and the presenters does not try to loo=
k
> at the chat, and so now the whole context is captured.
>
> But that's still a bit clunky -- a presenter may want to comment on
> something that someone said in the chat room even if it was not marked as=
 a
> question that the Jabber scribe must relay.  After all the chat logs are
> under NOTE WELL, so they are part of the WG session -- and should be part
> of the minutes, at least the relevant parts.
>
> My suggestion would be to use TTS to supplement or replace the Jabber
> scribe.  A remote presenter who want to answer/comment on a chat message
> triggers TTS on the message itself, which now becomes part of the recordi=
ng
> -- and of the minutes.  With a local presenter the Jabber scribe could al=
so
> use that TTS feature.
>
> On 7/30/21 12:38 PM, Meetecho IETF support wrote:
> > All,
> >
> > chiming in just to say that we at Meetecho appreciate and value your
> feedback. We'll definitely take it into account when developing the futur=
e
> releases of the platform. We'll provide comments on the points raised as
> soon as we get the chance to parse them, i.e., when the meeting is over.
> >
> > Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to header
> to that list as well, as that's the right place to discuss enhancements a=
nd
> provide feedback that would be easier for us to collect.
> >
> > Best,
> > Alessandro
> >
> [...]
>
> --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: https://marc.petit-huguenin.org
> Profile: https://www.linkedin.com/in/petithug
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000f1642c05c89b0657
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B2:=DB=B1=DB=B8 Marc Petit-Huguenin &lt;<a href=
=3D"mailto:marc@petit-huguenin.org">marc@petit-huguenin.org</a>&gt; =D9=86=
=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One use of the =
Meetecho recording is to prepare minutes by double checking notes.=C2=A0 On=
e issue with that is that sometimes a presenter answers comments made in th=
e chat, but the chat log does not appear in the recording.=C2=A0 The person=
 preparing the minutes now has to open the minutes, try to synchronize then=
 with the recording and update the minutes to reflect the question/comment =
that triggers the response by the presenter.=C2=A0 There is two issues with=
 that:<br>
<br>
1. Someone watching only the recording only have access to half of that con=
versation and may not know where the chat logs are, or even that they was a=
 chat running along the session.<br>
2. People taking notes must follow both the chat and the presenter, which c=
ould be a bit too much.<br>
<br>
I do not think that recording the chat at the same time than the presenter =
would be a good idea (OTOH displaying the name of the person talking in the=
 recording even if they did not turn on video would help).=C2=A0 The reason=
 is that not all the content of the chat log is relevant for the WG busines=
s (that&#39;s an understatement).<br>
<br>
Having a jabber scribe and some discipline may help: The jabber scribe repe=
ats the chat comment/question, and the presenters does not try to look at t=
he chat, and so now the whole context is captured.<br>
<br>
But that&#39;s still a bit clunky -- a presenter may want to comment on som=
ething that someone said in the chat room even if it was not marked as a qu=
estion that the Jabber scribe must relay.=C2=A0 After all the chat logs are=
 under NOTE WELL, so they are part of the WG session -- and should be part =
of the minutes, at least the relevant parts.<br>
<br>
My suggestion would be to use TTS to supplement or replace the Jabber scrib=
e.=C2=A0 A remote presenter who want to answer/comment on a chat message tr=
iggers TTS on the message itself, which now becomes part of the recording -=
- and of the minutes.=C2=A0 With a local presenter the Jabber scribe could =
also use that TTS feature.<br>
<br>
On 7/30/21 12:38 PM, Meetecho IETF support wrote:<br>
&gt; All,<br>
&gt; <br>
&gt; chiming in just to say that we at Meetecho appreciate and value your f=
eedback. We&#39;ll definitely take it into account when developing the futu=
re releases of the platform. We&#39;ll provide comments on the points raise=
d as soon as we get the chance to parse them, i.e., when the meeting is ove=
r.<br>
&gt; <br>
&gt; Also, I&#39;m cc&#39;ing <a href=3D"mailto:tools-discuss@ietf.org" tar=
get=3D"_blank" rel=3D"noreferrer">tools-discuss@ietf.org</a> and setting th=
e reply-to header to that list as well, as that&#39;s the right place to di=
scuss enhancements and provide feedback that would be easier for us to coll=
ect.<br>
&gt; <br>
&gt; Best,<br>
&gt; Alessandro<br>
&gt; <br>
[...]<br>
<br>
-- <br>
Marc Petit-Huguenin<br>
Email: <a href=3D"mailto:marc@petit-huguenin.org" target=3D"_blank" rel=3D"=
noreferrer">marc@petit-huguenin.org</a><br>
Blog: <a href=3D"https://marc.petit-huguenin.org" rel=3D"noreferrer norefer=
rer" target=3D"_blank">https://marc.petit-huguenin.org</a><br>
Profile: <a href=3D"https://www.linkedin.com/in/petithug" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">https://www.linkedin.com/in/petithug</a><br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000f1642c05c89b0657--


From nobody Mon Aug  2 15:24:43 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 076473A1F3A; Mon,  2 Aug 2021 15:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yhdBpyPkAPi3; Mon,  2 Aug 2021 15:24:30 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92EF03A1F2E; Mon,  2 Aug 2021 15:24:26 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id x11so32388991ejj.8; Mon, 02 Aug 2021 15:24:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I47v8MmCjhFhg5iuGwftPPWKGGWBKTsxPsq6rAxZqm8=; b=LmgPA0G/ekUnzXVkIfhnSC8H4SEtVUPGFnRIy8ev3aXA0ir0eQ/+z2bKOBPp1J99d2 syokatgdKj9xF/FOz4fYICEhKinAEg9Wy1CYAl4SSCciUw6Y8/oo2xZe81H9ledDaMa0 XidktfPSQyeiyFn4+4ZQMfboDWW/I4nFjqVHTAkJP3k0GnbD8yFxVgvEa3i1O2Q9DKE2 oMed1k6nXqbtuigvSLF9MfNnRZvNa1oXjuOmcAXAYOof1n6W39bXNnRUTNh81uWIpw+I BJvagHSdU7KLqF9V7678wQJHTjRQ0MxcnE98oLEB/I+2XgHuagZHjgvqz5u2zPro9zVi JRZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I47v8MmCjhFhg5iuGwftPPWKGGWBKTsxPsq6rAxZqm8=; b=XCsP9DLTzdztpgUc2vo2niOvANiQJGyZGUXZT9EljhMewwQWT7247Mtxda/oA6y5Li 6agkMcYojrFeHlVAW4dvb8sMqehj8Vnl8zdI/V85IOMUzomK5s8xHgFiO0vsk0Fft6WB cw3MsQd40J5gHOjI288Ngm/+RU+SsMRziQ+EYxogkabcNRs510JtGWBSQ5HpbNEq37H0 JsTUOfSkanSz+sq7vCv0Nr0URXD4QI9c0J1nnG9uqZq6QmSI6ylq3l6WHVd5i9Zh2i8b GdluGvGmX3cZfuRztYXV6HMn/FKLfbfU1ip+wMFeJ5S7udC7ygDDD6/xBl3r/P+r3MqZ ilbw==
X-Gm-Message-State: AOAM53121SYgo0RDiMifmxdl72hjgreH+yCuJSfVHiSV13RtWCt4u1vZ YJ7R/p+tOl6qQxod8Dp8tfuDGcm39DaHkcRjnY8=
X-Google-Smtp-Source: ABdhPJxwq4sbSa5nh4y6ACKmds+Ehy+V9ad/H00BPQyt76eaB2+qd7A2Ylve9GXCyWm6gBbrPUywZLKtk08nwnJmXTY=
X-Received: by 2002:a17:906:190c:: with SMTP id a12mr17875258eje.141.1627943063424;  Mon, 02 Aug 2021 15:24:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com> <CAKKJt-eKTxugtk+cY9vApfr9ubufuOvi9QS=Se8pUqphj-YocA@mail.gmail.com>
In-Reply-To: <CAKKJt-eKTxugtk+cY9vApfr9ubufuOvi9QS=Se8pUqphj-YocA@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:54:11 +0430
Message-ID: <CA+d13g39a4z+0Ow++5LMCdQtw_MoEHetDozRt-sGm47F=_DjoQ@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Bron Gondwana <brong@fastmailteam.com>,  tools-discuss <tools-discuss@ietf.org>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000293ea05c89b088d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/wr6ZuJyWZ3K5uAt1FWaaDPvFkD8>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:24:42 -0000

--0000000000000293ea05c89b088d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B1:=DB=B5=DB=B6 Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> =D9=86=D9=88=D8=B4=D8=AA:

> On Fri, Jul 30, 2021 at 4:14 PM Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>> To your list, I would add auto-unmuting (and even more importantly,
>> muting) when people enter and exit the head of the queue. This would rem=
ove
>> a lot of goofy behavior.
>>
>
> Yeah, and I'd suggest auto-muting video when you leave the queue, just
> because "lowering your hand" could mean "I'm out of the line, I don't hav=
e
> anything else to say, and you don't need to see me any more".
>
> That would have fixed all *my *goofy Meetecho behavior. Fixing goofy
> things I say with audio enabled is, of course, harder ...
>
> Best,
>
> Spencer
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000000293ea05c89b088d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B1:=DB=B5=DB=B6 Spencer Dawkins at IETF &lt;<a hr=
ef=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</=
a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr">On Fri, Jul 30, 2021 at 4:14 PM Eric Rescor=
la &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank" rel=3D"noreferrer"=
>ekr@rtfm.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmai=
l_quote"><br></div><div class=3D"gmail_quote">To your list, I would add aut=
o-unmuting (and even more importantly, muting) when people enter and exit t=
he head of the queue. This would remove a lot of goofy behavior.</div></div=
></blockquote><div><br></div><div>Yeah, and I&#39;d suggest auto-muting vid=
eo when you leave the queue, just because &quot;lowering your hand&quot; co=
uld mean &quot;I&#39;m out of the line, I don&#39;t have anything else to s=
ay, and you don&#39;t need to see me any more&quot;.=C2=A0</div><div><br></=
div><div>That would have fixed all <b>my </b>goofy Meetecho behavior. Fixin=
g goofy things I say with audio enabled=C2=A0is, of course, harder ...</div=
><div><br></div><div>Best,</div><div><br></div><div>Spencer</div></div></di=
v>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000000293ea05c89b088d--


From nobody Mon Aug  2 15:25:05 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B21473A1FB7; Mon,  2 Aug 2021 15:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UCwt8f9fys1C; Mon,  2 Aug 2021 15:24:49 -0700 (PDT)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20BCA3A1F8F; Mon,  2 Aug 2021 15:24:42 -0700 (PDT)
Received: by mail-ej1-x630.google.com with SMTP id yk17so25624531ejb.11; Mon, 02 Aug 2021 15:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/t3bs5rRJ5RLs6uJhJ864iSW9Aj5Lzve87/xc+RdLK0=; b=dPqzWan1sIVQZumr23c8eWHHb97HoJIY1HaWaPWcCTK7l+fOD0Luskr/XaC+KuPBuQ WZcAqBw1ABdiR4YfgNkjLdv7+GTfych8Upx68NMrcTxq8iuhN6kT6CdKAN2mWHkrYykL B9F5ezyJvGUCTo6lMRhJBXCOhECrIpCAecFedyuMG6t24V4L/CDxXDrNGMZG38Sas+o+ XSC9GUDU9SQP2P6H7ePPBmvRsnbSe4Znesm34dI23UycPW2ZuEqECDz+zJDQXXIglWkT Tu/hjUft7kafCGpfhbVB8S6yIEfGZMWXFt5XOH9JwvgL862VuvXjpZYCAuK36/7KTLJK PK8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/t3bs5rRJ5RLs6uJhJ864iSW9Aj5Lzve87/xc+RdLK0=; b=CMG1a8rJjEtdhSSqps+fGrJC+Qiqn/mjWe4xtkYKq5fGAhcSOW6H4jGpO0Nhlry1g4 q8BkBBnl3ntyFfSz+erEJXjdTAjN6OH/5ov4AWRUdaeMuGP3yGMtHiCWod/AVa4+3xxi 9iv7IlIphgoF92ov8h5VB7BrhdTbsVseRnwPxw2x5gKFIKyJtuA9ZVcqGTit9hC8KUPe dCwf/PMyLBi5DaI+6Plijg8oVpEI4ZOYYk5MegUSmvZWQO16QANq5PuixySfsbUF4L/v G50/f/gtLGKn2nz1ABZU5X9KeJ/sPnBCnZ3Ih3VbQYDFqntTYSs5/ptgSKhbawEsvC71 emWQ==
X-Gm-Message-State: AOAM5332Dcd37bKpQwGeZmYbeBWOV91ICI71ucW/dnyEsuoZtHXnTgaB qvMN4fknYjCIByMiRQUhzyhmojfB4wwIZxYiObU=
X-Google-Smtp-Source: ABdhPJzH3xYADYbt00OJ+QulKr2wN2DONEZtftSh0y+X7hyF9knhEzlrGetLjw28JC+b1DNnUBJb5kEGAs6hOnMhVTI=
X-Received: by 2002:a17:906:2dc5:: with SMTP id h5mr6941036eji.515.1627943080770;  Mon, 02 Aug 2021 15:24:40 -0700 (PDT)
MIME-Version: 1.0
References: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie> <20210801205621.427F0257240C@ary.qy> <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be> <CAKKJt-fuOCifVkGY3yfikV6RetYmrv51SF809Si=wPzkL3g4Qg@mail.gmail.com>
In-Reply-To: <CAKKJt-fuOCifVkGY3yfikV6RetYmrv51SF809Si=wPzkL3g4Qg@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:54:29 +0430
Message-ID: <CA+d13g2J4ekfH7xtF3n1wiBAWoMmMC53WmbOkdfL0sxkno6Qvg@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: 111attendees@ietf.org, tools-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000b3eda05c89b099d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/2Ptld9U_WpAK5AFePmTo4-Af2Ac>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:25:02 -0000

--0000000000000b3eda05c89b099d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B1:=DB=B3=DB=B3 Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> =D9=86=D9=88=D8=B4=D8=AA:

> Just to back up slightly in this thread,
>
> Knowing who the (other) note-takers are is valuable, especially if you
> suddenly realize that the (other) note-taker is presenting, or involved i=
n
> a long mike exchange (not naming names here).
>
> Whether or not I'm officially taking notes, I always log in to make sure
> that the unfortunate note-takers have been able to translate Spencer-spea=
k
> to What Spencer Meant. That does mean I often make edits on things other
> people said, because I was pretty sure that the notes missed something
> significant.
>
> I had no idea that I could change permissions on pages I created.
> https://codimd.ietf.org/features#Permissions was enlightening.
>
> While we're chatting here - I created ComiMD pages for at least two or
> three side meetings, which were really useful in every case. That's not a
> problem, is it? And if it's OK, is a name like
> https://codimd.ietf.org/notes-ietf-111-SATCOM-side-meeting good enough?
>
> Best,
>
> Spencer
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000000b3eda05c89b099d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B1:=DB=B3=DB=B3 Spencer Dawkins at IETF &lt;<a hr=
ef=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</=
a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr">Just to back up slightly in this thread,=C2=
=A0</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Knowing who the (other=
) note-takers are is valuable, especially if you suddenly realize that the =
(other) note-taker is presenting, or involved in a long mike exchange (not =
naming names here).=C2=A0</div><div dir=3D"ltr"><br></div><div>Whether or n=
ot I&#39;m officially taking notes, I always log in to make sure that the u=
nfortunate note-takers have been able to translate Spencer-speak to What Sp=
encer Meant. That does mean I often make edits on things other people said,=
 because I was pretty sure that the notes missed something significant.</di=
v><div><br></div><div>I had no idea that I could change permissions on page=
s I created. <a href=3D"https://codimd.ietf.org/features#Permissions" targe=
t=3D"_blank" rel=3D"noreferrer">https://codimd.ietf.org/features#Permission=
s</a> was enlightening.</div><div><br></div><div>While we&#39;re chatting h=
ere - I created ComiMD pages for at least two or three side meetings, which=
 were really useful=C2=A0in every case. That&#39;s not a problem, is it? An=
d if it&#39;s OK, is a name like=C2=A0<a href=3D"https://codimd.ietf.org/no=
tes-ietf-111-SATCOM-side-meeting" target=3D"_blank" rel=3D"noreferrer">http=
s://codimd.ietf.org/notes-ietf-111-SATCOM-side-meeting</a> good enough?</di=
v><div><br></div><div>Best,</div><div><br></div><div>Spencer</div></div>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000000b3eda05c89b099d--


From nobody Mon Aug  2 15:25:35 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8AEC3A1F91; Mon,  2 Aug 2021 15:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ip8WBTDi_QWR; Mon,  2 Aug 2021 15:25:20 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA853A1F86; Mon,  2 Aug 2021 15:25:14 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id oz16so33271774ejc.7; Mon, 02 Aug 2021 15:25:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LyKQq+SeBaZANx6RL3BXq78lqxBQynn+dQNBRGv588Y=; b=f+nRqk9UkcYMw6vAw3EGHy+Gg+j5ZZCMU116UJEQJLhgpv8PNrpl5CbdmtH8J5SJPi qzYee/Jvn0yVsi+PiWRhojewiAB8lLlsRra7OM0jLD80j1X/DaDE1sxWAykUlaI/F8ka 5Kd8Z9QGDUFGxKOzoZdEjMZhUyHTnyc4qRaPex238bIcP0J9nW2sb+cYhCy0UsO4+T8P xTmvzV4MhAmS8kRJXDouO9mdksvJzNNlY5Kd4YD5InwOI1G09FGCCj8C+4URoSTaEfS9 UyWeuxFk/S7TMtIlHtVCbZQGEcYNtr6EVl0kuUTgogL2ATky9wG3kdx2ltvQ75ZjM1cc SJLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LyKQq+SeBaZANx6RL3BXq78lqxBQynn+dQNBRGv588Y=; b=f/0ADhrpTA6fflufXf7mWMTmFrVDVHOCtdib1Q76sUnINFJ5W7cEJ2Ke8x22m2qQM7 UxpVbCSTgBL0WTfqRTLmJQJ/ocjsqwclqU6JUi64QE5RszIawSS7yavJhlB243uB4aTi HvWcw69tcrABSgV2+d1/7QdeW4/3vs/nxbEz49hEg+tcd4UaRGSTR3tf8qf0aYj0s2TL TC/s50ry4/gLJ+wj0o38f96jbVCtIx9bL+fG/WmHCE586k+Ewg3YgT6Z49snbXbl8xya aq4otndVx+D5fJHIozVo05OwTawst9yXy+Fffpz9i9IUC4uBYCM5x4S4FjML2RAii51z +xgA==
X-Gm-Message-State: AOAM533JMPOIN+Z1Ub3VQBIUMZ28IHSliIWld+HtGw/iQNwB1uQPKIX/ vtLiM6aBRDsRfLZAkzVyvNHhNKD1GnKNw5MKZnc=
X-Google-Smtp-Source: ABdhPJwwRWx0Rt0Kkd6jJwrDHnRodyrsERwI0gN1Zhh97ANteI3glpXgWTHq2pIj9J/lKnN4cyMQI0Bz1/98/FFrwzI=
X-Received: by 2002:a17:906:c251:: with SMTP id bl17mr17644309ejb.219.1627943112248;  Mon, 02 Aug 2021 15:25:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost> <CAJq5cE3He3n-2920KkfKqRd0VShSFQRC9w0vLyrfL=-DsosChQ@mail.gmail.com>
In-Reply-To: <CAJq5cE3He3n-2920KkfKqRd0VShSFQRC9w0vLyrfL=-DsosChQ@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:55:00 +0430
Message-ID: <CA+d13g1UTsrcPD0RnRODwkk4Yds3EZVEwfwV3O1sENBq2Ku0WQ@mail.gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Bron Gondwana <brong@fastmailteam.com>,  tools-discuss@ietf.org, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000eb904b05c89b0a7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/ZdQp1a6jbZnv7gvAwGAPDiJgChk>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:25:34 -0000

--000000000000eb904b05c89b0a7d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1=DB=B5:=DB=B4=DB=B0 Jonathan Morton <chromatix99@gmail.com>
=D9=86=D9=88=D8=B4=D8=AA:

> On Sun, 1 Aug 2021 at 23:37, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
> >     > *information about who is speaking in the same place as video
> feeds*
> >
> > The video image does do the yellow square when they are speaking.
> >
> >     > See my previous email :)  Basically the "participant list" should
> just
> >     > be an ordered list of participants and only needs to be switched =
to
> >     > when seeing who is in the call or opening an individual message t=
o
> them
> >     > (and people don't get moved out of order when they're sending
> >     > something).  The "who is sending something" list should be all
> together
> >     > with the video, and chairs pinned even if they're sending nothing
> right
> >     > now.
> >
> > I think that I need a picture.
>
> So, currently we have the Chairs and any "active" participants (hand
> up, mic and/or camera open, presenting slides or screen) moving
> dynamically to the top of the Participants list on the left.  This
> makes it easy to find the Chairs, but if looking for a particular
> person in the list, you have to check both the top of the list and
> their alphabetical position, since their dynamic status could place
> them either way.  By default the Participants list is also hidden when
> you're reading the chat, and vice versa.  And currently the list of
> video thumbnails on the right is *strictly* those people with a camera
> open, whether or not they have the mic open or are active in some
> other way.
>
> The proposal here is to include *anyone* who would normally be moved
> to the top of the Participants list in the list of video thumbnails,
> and make the Participants list mostly static (only Chairs at the top).
> The thumbnail for people without a camera on would be the profile pic
> if they have one, supplemented by the appropriate participation icons
> (hand, microphone, screen, slides).  This gives a natural place to
> show speaking cues, so you can see at a glance who is actually
> speaking.
>
> > As my meetecho windows are more vertical than horizontal, I'd also like
> to be
> > able to move the video boxes to be under the slides.
>
> This also seems like a valid optimisation of screen real estate.  The
> thumbnail list should lie along the edge of the window that is least
> pressured by the presentation area.
>
>  - Jonathan Morton
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000eb904b05c89b0a7d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1=DB=B5:=DB=B4=DB=B0 Jonathan Morton &lt;<a href=3D"ma=
ilto:chromatix99@gmail.com">chromatix99@gmail.com</a>&gt; =D9=86=D9=88=D8=
=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, 1 Aug 2021 at 23=
:37, Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca" targ=
et=3D"_blank" rel=3D"noreferrer">mcr+ietf@sandelman.ca</a>&gt; wrote:<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; *information about who is speaking in the same=
 place as video feeds*<br>
&gt;<br>
&gt; The video image does do the yellow square when they are speaking.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; See my previous email :)=C2=A0 Basically the &=
quot;participant list&quot; should just<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; be an ordered list of participants and only ne=
eds to be switched to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; when seeing who is in the call or opening an i=
ndividual message to them<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; (and people don&#39;t get moved out of order w=
hen they&#39;re sending<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; something).=C2=A0 The &quot;who is sending som=
ething&quot; list should be all together<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; with the video, and chairs pinned even if they=
&#39;re sending nothing right<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; now.<br>
&gt;<br>
&gt; I think that I need a picture.<br>
<br>
So, currently we have the Chairs and any &quot;active&quot; participants (h=
and<br>
up, mic and/or camera open, presenting slides or screen) moving<br>
dynamically to the top of the Participants list on the left.=C2=A0 This<br>
makes it easy to find the Chairs, but if looking for a particular<br>
person in the list, you have to check both the top of the list and<br>
their alphabetical position, since their dynamic status could place<br>
them either way.=C2=A0 By default the Participants list is also hidden when=
<br>
you&#39;re reading the chat, and vice versa.=C2=A0 And currently the list o=
f<br>
video thumbnails on the right is *strictly* those people with a camera<br>
open, whether or not they have the mic open or are active in some<br>
other way.<br>
<br>
The proposal here is to include *anyone* who would normally be moved<br>
to the top of the Participants list in the list of video thumbnails,<br>
and make the Participants list mostly static (only Chairs at the top).<br>
The thumbnail for people without a camera on would be the profile pic<br>
if they have one, supplemented by the appropriate participation icons<br>
(hand, microphone, screen, slides).=C2=A0 This gives a natural place to<br>
show speaking cues, so you can see at a glance who is actually<br>
speaking.<br>
<br>
&gt; As my meetecho windows are more vertical than horizontal, I&#39;d also=
 like to be<br>
&gt; able to move the video boxes to be under the slides.<br>
<br>
This also seems like a valid optimisation of screen real estate.=C2=A0 The<=
br>
thumbnail list should lie along the edge of the window that is least<br>
pressured by the presentation area.<br>
<br>
=C2=A0- Jonathan Morton<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000eb904b05c89b0a7d--


From nobody Mon Aug  2 15:25:48 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49F73A1F2D; Mon,  2 Aug 2021 15:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FXsqc1uOiRm2; Mon,  2 Aug 2021 15:25:32 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47AE03A1F57; Mon,  2 Aug 2021 15:25:26 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id yk17so25627083ejb.11; Mon, 02 Aug 2021 15:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Vxt7fI0kHH1ulo8QG8XWiqUNxeUAIbuiUd8gh3QHJ2I=; b=eeBvxVIW7vYsWS/GE5fdsoKW9k4MzGz87GRnj+9yJW8llwSVTUeSHPDdLxvv/toPoU YR+O7MC0Jyxun/lscrDjnTobmpRPAzbgo2oSZ77AVaBqw69CnsZ58oQQBp9Dbd8q+Ean Zs4gufhRQ7ZW581kOwpXDmTKU+3KB3WRA8u/RwV6YKaW3ClrtsDT93hom214IXhxwgJ1 qLV/ceBB0tMWJfm1a+OnXZ//FdKEFfU4I7fqAhwoafYeVSBhszauQnPh3miGLxttoMLP JRRtLIqYyrTurY3ytVJaq8C+KgJqE6VxLyVJcBPqXovsgjoL9/9TW/bqeDzeu553QR1C P95g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Vxt7fI0kHH1ulo8QG8XWiqUNxeUAIbuiUd8gh3QHJ2I=; b=LzS4M7y03XG0z7tJAEtbc+2TOXIfaVM0msRrbFzqbg6OFpfaye3yAzUIOoHkZISaq6 W9T0or7R2ShhCzEecqKqxHR3xWAptJ/6qAihpqFFAyMlo/mWwv4Sugg4XvaWurgC6Z9K XoONl/AZLgkoreuxHY/BnbFM/+pxI27q3GfKLasuQXuMcOq8xbhGmqg3d6bjiXpYx9h/ hzxNe4EndUQ4RxmQBQKacXVWIrdwLN1Xw7wQDFm5gW+JW4jwsiPBThfkiZIciNEWNXsR oOwDEqDW48k/1usf2XDvTZIw2PpHdFd/CC2W5GmRXxLVOEg1gMtzHPVjK3TfkdJfimtJ nFUA==
X-Gm-Message-State: AOAM530RBJgAH12f8qV8G3aKa1Sj+uhAjEE9YxocPUubxT2ZOBCMXHUj y9NcxVnIr1r1dyu9UTVZmxN/0ZzmRkGNa5S2J+A=
X-Google-Smtp-Source: ABdhPJwcmySNABBzW/ViQmECx2atvwCYRo/JvfMv+m1qXGtI+c7akMJEDT7ddsgnJi82O5b40knukuhjTymYcX9wJ40=
X-Received: by 2002:a17:906:a98e:: with SMTP id jr14mr17537677ejb.450.1627943124453;  Mon, 02 Aug 2021 15:25:24 -0700 (PDT)
MIME-Version: 1.0
References: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie> <20210801205621.427F0257240C@ary.qy> <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be>
In-Reply-To: <49976630e58949fca366641118be302f@ICTS-S-EXMBX25.luna.kuleuven.be>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:55:12 +0430
Message-ID: <CA+d13g3Bw5ACvNgDgRq7tkVZh8GONjh3hVU-eraQUDwLgebESQ@mail.gmail.com>
To: Robin Marx <robin.marx@kuleuven.be>
Cc: John Levine <ietf@johnlevine.com>, tools-discuss@ietf.org, 111attendees@ietf.org, stephen.farrell@cs.tcd.ie
Content-Type: multipart/alternative; boundary="000000000000a5cb9105c89b0b22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/T8143j_Pa_L-4aIfqx6hXGq43DM>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:25:46 -0000

--000000000000a5cb9105c89b0b22
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1=DB=B2:=DB=B3=DB=B8 Robin Marx <robin.marx@kuleuven.be> =D9=86=D9=88=
=D8=B4=D8=AA:

> In my experience as a frequent minutes taker, it would also be helpful to
> have a "login with datatracker" button
> somewhere easily accessible when landing on the page for a specific
> session (linked from the agenda),
> without having to go to the main CodiMD landing page first
> (assuming that popup won't auto-show if the behavior would change or if
> the current behavior is kept).
>
> -----Original Message-----
> From: 111attendees <111attendees-bounces@ietf.org> On Behalf Of John
> Levine
> Sent: zondag 1 augustus 2021 22:56
> To: tools-discuss@ietf.org; 111attendees@ietf.org
> Cc: stephen.farrell@cs.tcd.ie
> Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting
> notes who are not logged in?
>
> It appears that Stephen Farrell  <stephen.farrell@cs.tcd.ie> said:
> >
> >On 01/08/2021 16:47, Carsten Bormann wrote:
> >> OK, so the summary of the 111attendees discussion is that we don=E2=80=
=99t
> >> want unauthenticated write access to meeting notes.
>
> >Really? Seems to me the risk isn't significant enough to make someone
> >do work and there's plenty of opportunity to read the draft meeting
> >notes. I don't really object to requiring note takers be authenticated
> >but it doesn't seem that worthwhile.
>
> If they're in the meetecho session, they're already authenticated, so I'm
> having a little trouble coming up with a scenario in which someone who
> isn't there needs to change he minutes.
>
> R's,
> John
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000a5cb9105c89b0b22
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1=DB=B2:=DB=B3=DB=B8 Robin Marx &lt;<a href=3D"mailto:=
robin.marx@kuleuven.be">robin.marx@kuleuven.be</a>&gt; =D9=86=D9=88=D8=B4=
=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">In my experience as a frequ=
ent minutes taker, it would also be helpful to have a &quot;login with data=
tracker&quot; button <br>
somewhere easily accessible when landing on the page for a specific session=
 (linked from the agenda), <br>
without having to go to the main CodiMD landing page first<br>
(assuming that popup won&#39;t auto-show if the behavior would change or if=
 the current behavior is kept). <br>
<br>
-----Original Message-----<br>
From: 111attendees &lt;<a href=3D"mailto:111attendees-bounces@ietf.org" tar=
get=3D"_blank" rel=3D"noreferrer">111attendees-bounces@ietf.org</a>&gt; On =
Behalf Of John Levine<br>
Sent: zondag 1 augustus 2021 22:56<br>
To: <a href=3D"mailto:tools-discuss@ietf.org" target=3D"_blank" rel=3D"nore=
ferrer">tools-discuss@ietf.org</a>; <a href=3D"mailto:111attendees@ietf.org=
" target=3D"_blank" rel=3D"noreferrer">111attendees@ietf.org</a><br>
Cc: <a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank" rel=3D"n=
oreferrer">stephen.farrell@cs.tcd.ie</a><br>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting n=
otes who are not logged in?<br>
<br>
It appears that Stephen Farrell=C2=A0 &lt;<a href=3D"mailto:stephen.farrell=
@cs.tcd.ie" target=3D"_blank" rel=3D"noreferrer">stephen.farrell@cs.tcd.ie<=
/a>&gt; said:<br>
&gt;<br>
&gt;On 01/08/2021 16:47, Carsten Bormann wrote:<br>
&gt;&gt; OK, so the summary of the 111attendees discussion is that we don=
=E2=80=99t <br>
&gt;&gt; want unauthenticated write access to meeting notes.<br>
<br>
&gt;Really? Seems to me the risk isn&#39;t significant enough to make someo=
ne <br>
&gt;do work and there&#39;s plenty of opportunity to read the draft meeting=
 <br>
&gt;notes. I don&#39;t really object to requiring note takers be authentica=
ted <br>
&gt;but it doesn&#39;t seem that worthwhile.<br>
<br>
If they&#39;re in the meetecho session, they&#39;re already authenticated, =
so I&#39;m having a little trouble coming up with a scenario in which someo=
ne who isn&#39;t there needs to change he minutes.<br>
<br>
R&#39;s,<br>
John<br>
<br>
--<br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000a5cb9105c89b0b22--


From nobody Mon Aug  2 15:26:21 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C20453A1F36; Mon,  2 Aug 2021 15:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9ZBw3c8SahO9; Mon,  2 Aug 2021 15:26:05 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89ACA3A1F6E; Mon,  2 Aug 2021 15:26:01 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id gs8so33239871ejc.13; Mon, 02 Aug 2021 15:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LUpxGsGyrmqHnqY2ehUtEF5YTIhHAYd0RQ6Yrdf470g=; b=UIb5PmA4QKK7vkjLxxSFBaxPtku+p2Nb3RGDGLkEBUzyaY3AqDmGagFXQmBqCm5JXO kddyk1jFilZJ4/wWS8/FJEJqZcgHAr11Dv6iMlRs7pi+7iqroPwHBUHNdDwApjjgsy5K 7LLW2KKgM7O4JRlU7gvl2XXsAvosfy47P9Tyub+hLE0+KZFTkoPi3Y9n2WvOVbo+hfWQ rF2epYmgdG22e11oYZkq0Rzcb6jCgK7a5t57mzMRrt5MYSfCicmU6mvtuv0q/Qn0QjEz hgPCGsOh27Qs3LHi/vgob0gIBMAVjZvVrh4F0kiwzMblBl9eghbNiYpoN2UVkwlDgCae 4p2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LUpxGsGyrmqHnqY2ehUtEF5YTIhHAYd0RQ6Yrdf470g=; b=O/kpSyVVNjF2N9tT8kmifqxU5DbH9LcNyNCFw3XnCq/IJPKrBzBu4LyEQFj1wvHYv8 1ItGlmyejUn/KXvVWIdjQrzLhyJO/+NDooOcXQWx+i1MzqIaAiMdKShXN8UM1QMFDQwJ TSCIVDQAzTF7EOKSGanDoV3xHBgaqjliF7Y2NDQG8pYTBdowXlmtwE+pzU84DasnArS9 gk2huM5PhnXV4BURB2syTVwGtBwbPeyuwXe1dZ829RPAAYILBRWbK/3XSdXrE2q/jqLc LN3a3F//IC49T5UlQ+IG4IW98LPRFlr0bhoZ0/rX0hueyHuQW5J4HnHl1OJ/Y2gOwUIa hIlg==
X-Gm-Message-State: AOAM532KcTjHlIyWGT6fA4EtKfCW5Xu2nLT4dA2lXxIi1tbauf+lUQ9A e/FVASLlfRJslRfaV+v5Ku3cdPAuPejw1a8Ao/LBK5nUUDdmEA==
X-Google-Smtp-Source: ABdhPJxF9QyoWB7RoFyovQAkkW8LRd5MoS/BnyqWRbzSuk0slumFOsMvcJPXE/6CzqXIoADVMfb/kNqtpVCzJMIcXb4=
X-Received: by 2002:a17:906:190c:: with SMTP id a12mr17880912eje.141.1627943154958;  Mon, 02 Aug 2021 15:25:54 -0700 (PDT)
MIME-Version: 1.0
References: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie> <20210801205621.427F0257240C@ary.qy>
In-Reply-To: <20210801205621.427F0257240C@ary.qy>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:55:43 +0430
Message-ID: <CA+d13g2O7ePRW_6UAXP73W_zXAcfVT8PGtgNVP+V+Nd73yCSSQ@mail.gmail.com>
To: John Levine <ietf@johnlevine.com>
Cc: tools-discuss@ietf.org, 111attendees@ietf.org, stephen.farrell@cs.tcd.ie
Content-Type: multipart/alternative; boundary="00000000000077434605c89b0da1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/sX6SoWdsuDF7QxodB5dIbJi_014>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:26:20 -0000

--00000000000077434605c89b0da1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1:=DB=B2=DB=B6 John Levine <ietf@johnlevine.com> =D9=86=D9=88=D8=B4=D8=
=AA:

> It appears that Stephen Farrell  <stephen.farrell@cs.tcd.ie> said:
> >
> >On 01/08/2021 16:47, Carsten Bormann wrote:
> >> OK, so the summary of the 111attendees discussion is that we don=E2=80=
=99t
> >> want unauthenticated write access to meeting notes.
>
> >Really? Seems to me the risk isn't significant enough to make
> >someone do work and there's plenty of opportunity to read the
> >draft meeting notes. I don't really object to requiring note
> >takers be authenticated but it doesn't seem that worthwhile.
>
> If they're in the meetecho session, they're already authenticated, so I'm
> having
> a little trouble coming up with a scenario in which someone who isn't
> there needs
> to change he minutes.
>
> R's,
> John
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--00000000000077434605c89b0da1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1:=DB=B2=DB=B6 John Levine &lt;<a href=3D"mailto:ietf@=
johnlevine.com">ietf@johnlevine.com</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">It appears that Stephen Farrell=C2=A0 &l=
t;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank" rel=3D"nor=
eferrer">stephen.farrell@cs.tcd.ie</a>&gt; said:<br>
&gt;<br>
&gt;On 01/08/2021 16:47, Carsten Bormann wrote:<br>
&gt;&gt; OK, so the summary of the 111attendees discussion is that we don=
=E2=80=99t<br>
&gt;&gt; want unauthenticated write access to meeting notes.<br>
<br>
&gt;Really? Seems to me the risk isn&#39;t significant enough to make<br>
&gt;someone do work and there&#39;s plenty of opportunity to read the<br>
&gt;draft meeting notes. I don&#39;t really object to requiring note<br>
&gt;takers be authenticated but it doesn&#39;t seem that worthwhile.<br>
<br>
If they&#39;re in the meetecho session, they&#39;re already authenticated, =
so I&#39;m having<br>
a little trouble coming up with a scenario in which someone who isn&#39;t t=
here needs<br>
to change he minutes.<br>
<br>
R&#39;s,<br>
John<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--00000000000077434605c89b0da1--


From nobody Mon Aug  2 15:26:31 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BECC3A1F12; Mon,  2 Aug 2021 15:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6iK2Q_gKz70y; Mon,  2 Aug 2021 15:26:15 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36D583A1F5A; Mon,  2 Aug 2021 15:26:11 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id z11so4121665edb.11; Mon, 02 Aug 2021 15:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j3JKcDQOO7I98CBk/JTqQekI9fK7WDF1+W7Btq1GXZM=; b=jIMCWJreGwS0iQgkMTK9khiJJLjrzWmmsHuq5vy0rGNBjY4L00Q4pItWipsxde6SWB JPCXqvOZ0LBcISNVAChqIAio6JNr8J9e+z8h9cEMZTVUEPLzr/uc8HIJxOrjoMmlDGwG YTZ/3MejegZvb3zeWNyYh6ZLvEXNFpc/6azaPfBhz7h7ePCkSayLh0BL9rgxCvkINEhn dDu2Z0leYw9h6uAr5fXw3RXSJO6kYbtUd/OwP1HgfpCGccuE1D4GowLCencJvyBp7WLi 3bEP63Mx1t4oawgm168DTEkV24unSPh4sGV7EUo0K2LD1z+MCAl9MP4QwgUtbBlPu1qP DhiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j3JKcDQOO7I98CBk/JTqQekI9fK7WDF1+W7Btq1GXZM=; b=nB1jyC64hhil6z8QFZdcL0IxEVQmKzgZpBqtngg8jTRWwxN5qCo+LtyVm0hnXlgTGc kaAFXBZYWkWESSnXEEzU+OuoRV9eYoGW/upr/+6DvN56eyPza9Laq8oo62qK6LHk/gm/ bGzit5ihR5Hd66MeV6lxcwfSQKLNcw/3D5gBiX9iWJoycq/rYdOikTNu/t7gCzI0m+Cy khJdOkMz3wTTEOryTQ/D0Yo3JyzNy7CP1y1Rk7BoV+j7mrT2NSrJDJ8FUuJwH5jEuW0b 5BHamDDzqGAxW2FfzcQqpknNHg2QGsZiiI4wQD68UTcz9OkqMe0lkgHPTDxLKUiMYRiB IyiA==
X-Gm-Message-State: AOAM5317qYjMlCrBU5+ooVWh5M9dnLkOoX7U5iZrjvHns4TPs6sUsOdd FCiImYWAZi+Wbo5Y4IPQmj1n4h9RoN3OV8UNmEw=
X-Google-Smtp-Source: ABdhPJybURnMNl0JTllte8DEFmjkVlTD535R7O+xnKtyfuDR4lXRA/ZL+92Qtj17CYN+EKHNv60J2uJdZYxxrAR70+o=
X-Received: by 2002:a05:6402:4d1:: with SMTP id n17mr21637566edw.337.1627943164551;  Mon, 02 Aug 2021 15:26:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost> <CABcZeBPjvRSdLjHUCXYDhE8Ls03w2M4iS-eS_YKkrRrMyN1kwA@mail.gmail.com>
In-Reply-To: <CABcZeBPjvRSdLjHUCXYDhE8Ls03w2M4iS-eS_YKkrRrMyN1kwA@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:55:52 +0430
Message-ID: <CA+d13g3XCkvX1yV952yaSv6qckq-_4NFNHuDwY2DHRuM1WTDTw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Bron Gondwana <brong@fastmailteam.com>,  tools-discuss <tools-discuss@ietf.org>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="00000000000009a41305c89b0ed7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/evYEUiQhQ4HbzKZLtd-XXAWNX6A>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:26:29 -0000

--00000000000009a41305c89b0ed7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1:=DB=B1=DB=B2 Eric Rescorla <ekr@rtfm.com> =D9=86=D9=88=D8=B4=D8=AA:

>
>
> On Sun, Aug 1, 2021 at 1:38 PM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>>
>> Bron Gondwana <brong@fastmailteam.com> wrote:
>>     > *a "temporary mute" mode that keeps the audio stream open:*
>>
>>     > This is still an issue for me.  I often mute myself while chairing
>> so I
>>     > can take notes without my keyboard sound interrupting the chat -
>> but it
>>     > means that I can't easily respond to somebody because the rejiggin=
g
>> of
>>     > the audio channel not only creates a hiccup in the incoming audio
>> feed
>>     > which means I might miss something someone says, but it also creat=
es
>>     > enough of a delay that by the time I could have responded the othe=
r
>>     > party's mental state has moved on.
>>
>> Yes, the 3s on/off latency on the audio is a problem.
>> So one should use a local mute instead, which of course, then causes
>> confusion.
>>
>
> Actually, this is not necessary. WebRTC contains APIs which allow you to
> mute
> the media locally. The delay in Meetecho is a result of the decision to
> release
> the MediaStream which then needs to be re-acquired, which is not what
> Meet, Zoom, etc. do.
>
> -Ekr
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--00000000000009a41305c89b0ed7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1:=DB=B1=DB=B2 Eric Rescorla &lt;<a href=3D"mailto:ekr=
@rtfm.com">ekr@rtfm.com</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Aug 1,=
 2021 at 1:38 PM Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandel=
man.ca" target=3D"_blank" rel=3D"noreferrer">mcr+ietf@sandelman.ca</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Bron Gondwana &lt;<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blan=
k" rel=3D"noreferrer">brong@fastmailteam.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; *a &quot;temporary mute&quot; mode that keeps the audio =
stream open:*<br>
<br>
=C2=A0 =C2=A0 &gt; This is still an issue for me.=C2=A0 I often mute myself=
 while chairing so I<br>
=C2=A0 =C2=A0 &gt; can take notes without my keyboard sound interrupting th=
e chat - but it<br>
=C2=A0 =C2=A0 &gt; means that I can&#39;t easily respond to somebody becaus=
e the rejigging of<br>
=C2=A0 =C2=A0 &gt; the audio channel not only creates a hiccup in the incom=
ing audio feed<br>
=C2=A0 =C2=A0 &gt; which means I might miss something someone says, but it =
also creates<br>
=C2=A0 =C2=A0 &gt; enough of a delay that by the time I could have responde=
d the other<br>
=C2=A0 =C2=A0 &gt; party&#39;s mental state has moved on.<br>
<br>
Yes, the 3s on/off latency on the audio is a problem.<br>
So one should use a local mute instead, which of course, then causes confus=
ion.<br></blockquote><div><br></div><div>Actually, this is not necessary. W=
ebRTC contains APIs which allow you to mute</div><div>the media locally. Th=
e delay in Meetecho is a result of the decision to release</div><div>the Me=
diaStream which then needs to be re-acquired, which is not what</div><div>M=
eet, Zoom, etc. do.</div><div><br></div><div>-Ekr</div><div><br></div></div=
></div>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--00000000000009a41305c89b0ed7--


From nobody Mon Aug  2 15:26:38 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C029B3A1F47; Mon,  2 Aug 2021 15:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 O4536hmuJdIk; Mon,  2 Aug 2021 15:26:22 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6BBA3A1F31; Mon,  2 Aug 2021 15:26:20 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id y12so26565759edo.6; Mon, 02 Aug 2021 15:26:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iJIaXQtNgTRhhfKotS5A6DDTIlzPQaMA3kMdoNYQN0Q=; b=O26cWD/ny94x8w/j3S3836OJ/xEUcHFJNVvw4a1F5GfaD9X009l6JiORSrzSUIQ2iX zmL605u9nN2MU7Euz4lgwAK3aEYsY6cLwJbH7Hbbtx92y5zyZlQoT5v6sqy9FH7Gkx1b 6scuTfP7EvIPYjkqJkIO69q4tC+dhT5DzA8eMCPPaySd5w6mar+xDFea0QE+3tmYff5c FrS5Whxw2bSxIwX2GcIULWIKDQiv+1mASIvhVZJPs10Gbvt4Z05gAOkwuCy194o+JZOD Q9iI/DKEzDkUDi89XHxUroR/2Wn6qSQ9yqKIQHMHYoK8/zjJcx7B9ItpRozf2h7+D5qR +nng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iJIaXQtNgTRhhfKotS5A6DDTIlzPQaMA3kMdoNYQN0Q=; b=Qknq7RgR5TSXRIVNZACA868KUBtDb2sGHhz5Skm+9epd89ozX7hr58Txm30/lOAyQO lCabpcGbHHREX0p/R4cscHJ4SrsKa811cUFlkrygStcOkqFenRucNrzPoWiA0YQXNuWs dL0E6xpQEBAmBkXWYMJF9/9keW3tMRX4mws9s9JQMxXp0IohvgbNKptOom3fAvBk4Mv6 zRPc0BfVCeIsOCceMMn1bLnhfFmo95Bkey2qtznYmnWGPXyaAZlcC7o88C1elpX+P1Qp q7Plw35d3DUc/pEvtVFoV/11PYtAJSaCyFlwzNeKD5+q30pYK8KZu4U7yLkNf+E9TjEJ 0fag==
X-Gm-Message-State: AOAM531ZyB65eXJxOsvcUPU9mN4WIDCf1bbZz4AMQVgHGnsegv0/G9nT ijEncHUP5HqrAkub7uRPUXWnaSMTkz4rMzNeMkk=
X-Google-Smtp-Source: ABdhPJz1chtygAteNWkv3Ff6XjqH2LYHO9v9EbgWrxzMt2F3Zde4MFazVWwSn9+MH4cgmRtSaJJ2HWFhMv8hKk2JYUc=
X-Received: by 2002:aa7:cac6:: with SMTP id l6mr1024549edt.37.1627943178427; Mon, 02 Aug 2021 15:26:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <27783.1627850234@localhost>
In-Reply-To: <27783.1627850234@localhost>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:56:06 +0430
Message-ID: <CA+d13g1OErK0qKvBtGwybrMQEKONGoZfsYNp__sDe0gc5n0qig@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org, tools-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dd608005c89b0ec2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/onmns7x3Yx4mvomQiUAHXbsanKQ>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:26:36 -0000

--000000000000dd608005c89b0ec2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1:=DB=B0=DB=B7 Michael Richardson <mcr+ietf@sandelman.ca>
=D9=86=D9=88=D8=B4=D8=AA:

>
> Bron Gondwana <brong@fastmailteam.com> wrote:
>     > *a "temporary mute" mode that keeps the audio stream open:*
>
>     > This is still an issue for me.  I often mute myself while chairing
> so I
>     > can take notes without my keyboard sound interrupting the chat - bu=
t
> it
>     > means that I can't easily respond to somebody because the rejigging
> of
>     > the audio channel not only creates a hiccup in the incoming audio
> feed
>     > which means I might miss something someone says, but it also create=
s
>     > enough of a delay that by the time I could have responded the other
>     > party's mental state has moved on.
>
> Yes, the 3s on/off latency on the audio is a problem.
> So one should use a local mute instead, which of course, then causes
> confusion.
>
>     > Timing is really important in conversation and we're already fighti=
ng
>     > with the quarter second delay imposed by the size of the planet.
>     > Additional delay makes it unwieldy.
>
> Ah... I know of a genetically spliced lab mouse with a plan to reduce the
> size of the planet.
>
>     > *allow multiple connections by the same person to the same session:=
*
>
>     > I have multiple times wanted to switch device temporarily - from my
>     > desktop computer to a phone / ipad so I can temporarily move to
> another
>     > location while continuing to follow a meeting.  Multiple connection
>     > support would mean I could switch over without a break.
>
> It seems like a stretch requirement, but I also know that some chairs wan=
t
> a
> second laptop so that they can see whether slides are really advancing.
> What I don't understand is, 16 months into pandemic, and 10 years into
> screen
> sharing, how it is that PPT people don't understand that they have to "F5=
"
> before they share.
>
>     > Sure it could be abused by people "sharing" a login, but that would
> be
>     > pretty obvious if both parties tried to participate, and given that
> we
>     > allow fee waivers anyway, it's unlikely to be abused significantly.
>     > Sure there are Jabber naming issues, but we can avoid that by givin=
g
>     > each jabber name with a serial number (which I believe already
> happens
>     > now?)
>
> Yes. Actually, the ephermalness of the jabber names annoys me, as I can't
> message people after they have left.
>
>     > *information about who is speaking in the same place as video feeds=
*
>
> The video image does do the yellow square when they are speaking.
>
>     > See my previous email :)  Basically the "participant list" should
> just
>     > be an ordered list of participants and only needs to be switched to
>     > when seeing who is in the call or opening an individual message to
> them
>     > (and people don't get moved out of order when they're sending
>     > something).  The "who is sending something" list should be all
> together
>     > with the video, and chairs pinned even if they're sending nothing
> right
>     > now.
>
> I think that I need a picture.
> As my meetecho windows are more vertical than horizontal, I'd also like t=
o
> be
> able to move the video boxes to be under the slides.
> see:  https://www.sandelman.ca/mcr/IETF111-virtual-SFO-two-sessions.png
>
>     > Along with visual indicators of "currently sending audio" on people
> so
>     > we know who of those with their audio channel open are currently
>     > speaking, this makes it easier to look in one place to see the sour=
ce
>     > of all sound, and eyes can generally flit between the right hand si=
de
>     > (video and audio indicators) and the slides, without needing to als=
o
>     > track via the participant list.
>
> I think that it would also work better for the youtube recording.
>
>     > *flexible "assign chair"**:*
>
>     > This one hasn't come up in practice, but the chairs for meetings ar=
e
>     > pre-assigned from datatracker.  It would be great for ADs and the
>     > meetecho reps in each meeting to be able to upgrade anybody to a
> chair
>     > role or remove a chair role with a simple click.
>
> That's a good idea.
> And with that power, they should be able to advance slides, no matter who
> activated them.
>
>     > This has become less important with the ability for individuals to
> turn
>     > on both audio and video themselves, so the chair is going less
> busywork
>     > just approving access, but it would be good to make it possible for
>     > someone else to step into the chair if the regular chairs are unabl=
e
> to
>     > attend or lose network, rather than making the meeting less able to
>     > run.
>
> I'd like the chair to be able to pre-authorize sharing and slides.
> Actually, the way I'd implement is that the chair(s) just get to decide w=
ho
> of the possibly many screen-sharing/slides that are occuring, who is
> actually
> shared.
>
> That lets people (a) test their setup in advance of their slot,
> (b) reduce the time to switch.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT
> architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consul=
ting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000dd608005c89b0ec2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1:=DB=B0=DB=B7 Michael Richardson &lt;<a href=3D"mailt=
o:mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt; =D9=86=D9=88=D8=B4=
=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Bron Gondwana &lt;<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blan=
k" rel=3D"noreferrer">brong@fastmailteam.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; *a &quot;temporary mute&quot; mode that keeps the audio =
stream open:*<br>
<br>
=C2=A0 =C2=A0 &gt; This is still an issue for me.=C2=A0 I often mute myself=
 while chairing so I<br>
=C2=A0 =C2=A0 &gt; can take notes without my keyboard sound interrupting th=
e chat - but it<br>
=C2=A0 =C2=A0 &gt; means that I can&#39;t easily respond to somebody becaus=
e the rejigging of<br>
=C2=A0 =C2=A0 &gt; the audio channel not only creates a hiccup in the incom=
ing audio feed<br>
=C2=A0 =C2=A0 &gt; which means I might miss something someone says, but it =
also creates<br>
=C2=A0 =C2=A0 &gt; enough of a delay that by the time I could have responde=
d the other<br>
=C2=A0 =C2=A0 &gt; party&#39;s mental state has moved on.<br>
<br>
Yes, the 3s on/off latency on the audio is a problem.<br>
So one should use a local mute instead, which of course, then causes confus=
ion.<br>
<br>
=C2=A0 =C2=A0 &gt; Timing is really important in conversation and we&#39;re=
 already fighting<br>
=C2=A0 =C2=A0 &gt; with the quarter second delay imposed by the size of the=
 planet.<br>
=C2=A0 =C2=A0 &gt; Additional delay makes it unwieldy.<br>
<br>
Ah... I know of a genetically spliced lab mouse with a plan to reduce the s=
ize of the planet.<br>
<br>
=C2=A0 =C2=A0 &gt; *allow multiple connections by the same person to the sa=
me session:*<br>
<br>
=C2=A0 =C2=A0 &gt; I have multiple times wanted to switch device temporaril=
y - from my<br>
=C2=A0 =C2=A0 &gt; desktop computer to a phone / ipad so I can temporarily =
move to another<br>
=C2=A0 =C2=A0 &gt; location while continuing to follow a meeting.=C2=A0 Mul=
tiple connection<br>
=C2=A0 =C2=A0 &gt; support would mean I could switch over without a break.<=
br>
<br>
It seems like a stretch requirement, but I also know that some chairs want =
a<br>
second laptop so that they can see whether slides are really advancing.<br>
What I don&#39;t understand is, 16 months into pandemic, and 10 years into =
screen<br>
sharing, how it is that PPT people don&#39;t understand that they have to &=
quot;F5&quot;<br>
before they share.<br>
<br>
=C2=A0 =C2=A0 &gt; Sure it could be abused by people &quot;sharing&quot; a =
login, but that would be<br>
=C2=A0 =C2=A0 &gt; pretty obvious if both parties tried to participate, and=
 given that we<br>
=C2=A0 =C2=A0 &gt; allow fee waivers anyway, it&#39;s unlikely to be abused=
 significantly.<br>
=C2=A0 =C2=A0 &gt; Sure there are Jabber naming issues, but we can avoid th=
at by giving<br>
=C2=A0 =C2=A0 &gt; each jabber name with a serial number (which I believe a=
lready happens<br>
=C2=A0 =C2=A0 &gt; now?)<br>
<br>
Yes. Actually, the ephermalness of the jabber names annoys me, as I can&#39=
;t<br>
message people after they have left.<br>
<br>
=C2=A0 =C2=A0 &gt; *information about who is speaking in the same place as =
video feeds*<br>
<br>
The video image does do the yellow square when they are speaking.<br>
<br>
=C2=A0 =C2=A0 &gt; See my previous email :)=C2=A0 Basically the &quot;parti=
cipant list&quot; should just<br>
=C2=A0 =C2=A0 &gt; be an ordered list of participants and only needs to be =
switched to<br>
=C2=A0 =C2=A0 &gt; when seeing who is in the call or opening an individual =
message to them<br>
=C2=A0 =C2=A0 &gt; (and people don&#39;t get moved out of order when they&#=
39;re sending<br>
=C2=A0 =C2=A0 &gt; something).=C2=A0 The &quot;who is sending something&quo=
t; list should be all together<br>
=C2=A0 =C2=A0 &gt; with the video, and chairs pinned even if they&#39;re se=
nding nothing right<br>
=C2=A0 =C2=A0 &gt; now.<br>
<br>
I think that I need a picture.<br>
As my meetecho windows are more vertical than horizontal, I&#39;d also like=
 to be<br>
able to move the video boxes to be under the slides.<br>
see:=C2=A0 <a href=3D"https://www.sandelman.ca/mcr/IETF111-virtual-SFO-two-=
sessions.png" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.s=
andelman.ca/mcr/IETF111-virtual-SFO-two-sessions.png</a><br>
<br>
=C2=A0 =C2=A0 &gt; Along with visual indicators of &quot;currently sending =
audio&quot; on people so<br>
=C2=A0 =C2=A0 &gt; we know who of those with their audio channel open are c=
urrently<br>
=C2=A0 =C2=A0 &gt; speaking, this makes it easier to look in one place to s=
ee the source<br>
=C2=A0 =C2=A0 &gt; of all sound, and eyes can generally flit between the ri=
ght hand side<br>
=C2=A0 =C2=A0 &gt; (video and audio indicators) and the slides, without nee=
ding to also<br>
=C2=A0 =C2=A0 &gt; track via the participant list.<br>
<br>
I think that it would also work better for the youtube recording.<br>
<br>
=C2=A0 =C2=A0 &gt; *flexible &quot;assign chair&quot;**:*<br>
<br>
=C2=A0 =C2=A0 &gt; This one hasn&#39;t come up in practice, but the chairs =
for meetings are<br>
=C2=A0 =C2=A0 &gt; pre-assigned from datatracker.=C2=A0 It would be great f=
or ADs and the<br>
=C2=A0 =C2=A0 &gt; meetecho reps in each meeting to be able to upgrade anyb=
ody to a chair<br>
=C2=A0 =C2=A0 &gt; role or remove a chair role with a simple click.<br>
<br>
That&#39;s a good idea.<br>
And with that power, they should be able to advance slides, no matter who<b=
r>
activated them.<br>
<br>
=C2=A0 =C2=A0 &gt; This has become less important with the ability for indi=
viduals to turn<br>
=C2=A0 =C2=A0 &gt; on both audio and video themselves, so the chair is goin=
g less busywork<br>
=C2=A0 =C2=A0 &gt; just approving access, but it would be good to make it p=
ossible for<br>
=C2=A0 =C2=A0 &gt; someone else to step into the chair if the regular chair=
s are unable to<br>
=C2=A0 =C2=A0 &gt; attend or lose network, rather than making the meeting l=
ess able to<br>
=C2=A0 =C2=A0 &gt; run.<br>
<br>
I&#39;d like the chair to be able to pre-authorize sharing and slides.<br>
Actually, the way I&#39;d implement is that the chair(s) just get to decide=
 who<br>
of the possibly many screen-sharing/slides that are occuring, who is actual=
ly<br>
shared.<br>
<br>
That lets people (a) test their setup in advance of their slot,<br>
(b) reduce the time to switch.<br>
<br>
--<br>
]=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Never tell me the o=
dds!=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| ipv6 me=
sh networks [<br>
]=C2=A0 =C2=A0Michael Richardson, Sandelman Software Works=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 |=C2=A0 =C2=A0 IoT architect=C2=A0 =C2=A0[<br>
]=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:mcr@sandelman.ca" target=3D"_blank" =
rel=3D"noreferrer">mcr@sandelman.ca</a>=C2=A0 <a href=3D"http://www.sandelm=
an.ca/" rel=3D"noreferrer noreferrer" target=3D"_blank">http://www.sandelma=
n.ca/</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0ruby on rails=C2=A0 =C2=
=A0 [<br>
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" target=3D=
"_blank" rel=3D"noreferrer">mcr+IETF@sandelman.ca</a>&gt;=C2=A0 =C2=A0. o O=
 ( IPv6 I=C3=B8T consulting )<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sandelman Software Works Inc, Otta=
wa and Worldwide<br>
<br>
<br>
<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000dd608005c89b0ec2--


From nobody Mon Aug  2 15:26:52 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B233A1F30; Mon,  2 Aug 2021 15:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zpdv4jLhEsMO; Mon,  2 Aug 2021 15:26:37 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9A433A1DEE; Mon,  2 Aug 2021 15:26:36 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id v20so12513512eda.1; Mon, 02 Aug 2021 15:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y/wDFkcEUDgT40Nkmo2CxgmGVqbaw1jG5oT6unTmfe4=; b=atcfozWRj/nk/BJA9DvmNErpHTpbNv78SE00ypRGEBspp79/uL4t42X2Bhj7Os9nXZ 66c/U8MDJaBZxj8Hd4rFH31hO959R158/gXHycvmCg4ksZ+muTrriapzV/TKeMZCBFLK Bw3auSbWo/nbFShVLbWE4XC3ls4VHlR1j+ZW9qweJOzGtIZsA3YdyfxcNMWp6MZe4GI+ SX50hGARf25aii4LGco+Fh+bhKQ8ILcZfdR3ldLxKU95JVQ20C165y457fiPrZGVqcxu uHLfhGPq/bB/LuX8VtUdCdNxVqbslQYhWZxa5fziAskpf7Rr4xQbNe7kDb++ql2U5O7+ TrPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y/wDFkcEUDgT40Nkmo2CxgmGVqbaw1jG5oT6unTmfe4=; b=j7IzBYbCLDpz9xiwqtYonwAcVtfzOG5N5nPdXWNPbgOzk3CFN18fYwBA1uZ3df8pKq PdcReaHnNfStPwDDIUGVu/VElwSQNn+m0hu+pvCZNaqis2FoU0SrLk3QMNkJWXlvA265 L3Lc+t5yeM/JSV/wJftSmt4E4YHi8JkuWAoBbA9z5wdFZgUnAbr4nCSKcabDQ/tzaTyf jSP+/RKJrtUq3ruAnIUGBEueysHV7kHN2sVI0v2TFlO1eD99Zz7BZs0hcVGxlfcEq43C Er6lmwHSba/ZxoBIIA5gO0Lh9NPiSbWlvclosU8gKHfSP5RM+odppFmlifxv+UJeDduw 4rgQ==
X-Gm-Message-State: AOAM533T+6kwTEEGfgSeeUGwpfVcQhSI/qx1o+IrMHwpx/cz11wz/Xov o7rXUk020cgncfPlyv+jGD3saGGZ6KwejIMCxyo=
X-Google-Smtp-Source: ABdhPJznBvp8QyPpieOD1LEA55hFeRKBRwa+Zjv0wgbPIOMPfNZht14lLsk3Hs/ctFuOh72ryCNVtKpRS83T7iO/DzM=
X-Received: by 2002:a05:6402:1e96:: with SMTP id f22mr16223993edf.189.1627943190200;  Mon, 02 Aug 2021 15:26:30 -0700 (PDT)
MIME-Version: 1.0
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com> <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org> <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie>
In-Reply-To: <daaf0898-fcaf-341b-a710-9c459edebdc1@cs.tcd.ie>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:56:18 +0430
Message-ID: <CA+d13g3E3dcbRmqhWz_bxv-nioCHyp9i+_7KrbzJTOsk0TdzpA@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Carsten Bormann <cabo@tzi.org>, Tools Discussion <tools-discuss@ietf.org>,  111attendees@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009105a105c89b0fbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/eX7UbwEYj3jb24QpbnGTk7M1emA>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:26:51 -0000

--0000000000009105a105c89b0fbc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B0:=DB=B5=DB=B3 Stephen Farrell <stephen.farrell@cs.tcd.ie>
=D9=86=D9=88=D8=B4=D8=AA:

>
>
> On 01/08/2021 16:47, Carsten Bormann wrote:
> > OK, so the summary of the 111attendees discussion is that we don=E2=80=
=99t
> > want unauthenticated write access to meeting notes.
> Really? Seems to me the risk isn't significant enough to make
> someone do work and there's plenty of opportunity to read the
> draft meeting notes. I don't really object to requiring note
> takers be authenticated but it doesn't seem that worthwhile.
>
> S.
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000009105a105c89b0fbc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=AF=D9=88=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B2 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B0:=DB=B5=DB=B3 Stephen Farrell &lt;<a href=3D"mailto:s=
tephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>&gt; =D9=86=D9=88=D8=
=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 01/08/2021 16:47, Carsten Bormann wrote:<br>
&gt; OK, so the summary of the 111attendees discussion is that we don=E2=80=
=99t<br>
&gt; want unauthenticated write access to meeting notes.<br>
Really? Seems to me the risk isn&#39;t significant enough to make<br>
someone do work and there&#39;s plenty of opportunity to read the<br>
draft meeting notes. I don&#39;t really object to requiring note<br>
takers be authenticated but it doesn&#39;t seem that worthwhile.<br>
<br>
S.<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000009105a105c89b0fbc--


From nobody Mon Aug  2 15:28:13 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C17613A1F17; Mon,  2 Aug 2021 15:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cjIjGf-x_TWK; Mon,  2 Aug 2021 15:27:58 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9823A1F12; Mon,  2 Aug 2021 15:27:58 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id cf5so15015743edb.2; Mon, 02 Aug 2021 15:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6erbueBYOZ+ecsGbl6hnn6ZBr4xZ2JKf8BQ5d5R45VE=; b=pDdraJiYKjw8O1mgU+UL9z6JE8cWWTWjv4MKjVByCzcx8WkQPQuRgc4vM142Fedof0 YNSZ3QcBUQxcw2JDbBpPSJnBcVHk981fwOG0wvL8xHeH89R+7VabxhZTKsnMAISO45Ek bDJkWjqd4D6WtPLlntC+tJH1UjEpvqwBWrg07meUajrg8tQal8GcijRDGbmP5+PmnSEy qJz+JWQ0APfXlpaPyYBjyJhFOMzF+zxBnCHQG06OS6WWWaMyCWj7tQKDzetqm2IPbTvw 2z8FBsNaa8w9V6TNdlNK/M1dCI3daVKtKqNFu7BiNxS+6wYD9Ma1N3R0BngeXH05mlvz 0blw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6erbueBYOZ+ecsGbl6hnn6ZBr4xZ2JKf8BQ5d5R45VE=; b=IOLdOX8cHIDXC89CnBvEjlulXfgny77mcOdgD0q3q07DSmonQRC8hbEkUtgT+d+Qa5 94FCyfx62wpIw+M7VHDREP/dXg1vVaxabXBXXftXe6l/i3LHrIx0CC9FKLhCXnUNwKGy pGtwLyag2BHduOkc3VDLVDigLwle1xCAIzM8X+gw+0qF/2er/yVWseYfgh1Pu4C0TkoU W8bbuZL8BOpdpszUOVcSJBC/sDxwZvL/T3+ARvgQZ7peQmjxm4if44OlDS8Pqzcoggw0 tmrmIjlNpmGDhyE5Cqpg3hnW/MkrKEwEZhbQ3yZOnH4sRUPThAUacaOt1Nl9rk7mvGrF RBgw==
X-Gm-Message-State: AOAM531Bl5AZ573TI0lYb8o4v3iFISHB+EKJH1tXKSt9WdyVDcUuvymi 7VHauON48JHxPkMsByybn0j+Emwo9nzCwcSdm2vjFAxMuzmpaA==
X-Google-Smtp-Source: ABdhPJzm+PrklSeyEevflG7SYugV0qdzikaghHWkef7vQMAikAYB9gPL+8Rl3expIsxTAiqiyL8sayue7WmwJD0OZ9U=
X-Received: by 2002:a05:6402:14da:: with SMTP id f26mr22521491edx.259.1627943275627;  Mon, 02 Aug 2021 15:27:55 -0700 (PDT)
MIME-Version: 1.0
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com> <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
In-Reply-To: <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:57:44 +0430
Message-ID: <CA+d13g1DNaUbeMONH=SzgOPUcd7yrmu=h-o+0+yQRtXT+nhKZg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Tools Discussion <tools-discuss@ietf.org>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a88ba205c89b147b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/tftW8uvruVmkL9N9dTuZN4BZYdE>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:28:12 -0000

--000000000000a88ba205c89b147b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =DB=8C=DA=A9=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B1 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B2=DB=B0:=DB=B1=DB=B7 Carsten Bormann <cabo@tzi.org> =D9=86=D9=88=D8=B4=
=D8=AA:

> OK, so the summary of the 111attendees discussion is that we don=E2=80=99=
t want
> unauthenticated write access to meeting notes.  Less well-discussed is th=
at
> the authorization rule is that anyone with a datatracker account has writ=
e
> access, but I think that implementing anything more granular (e.g.,
> attendee status for the meeting that generated the minutes) would be actu=
al
> work.
>
> The authorization rule seems to correspond to CodiMD=E2=80=99s =E2=80=9Ce=
ditable=E2=80=9D, which
> is therefore the setting we should choose for meeting notes.  Whether we
> can do that automatically from the place where the meetings are assigned
> codimd names or have to do this manually is then a procedural thing to be
> discussed on tools-discuss.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000a88ba205c89b147b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =DB=8C=DA=A9=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B1 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B2=DB=B0:=DB=B1=DB=B7 Carsten Bormann &lt;<a href=3D"ma=
ilto:cabo@tzi.org">cabo@tzi.org</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">OK, so the summary of the 111attendees discu=
ssion is that we don=E2=80=99t want unauthenticated write access to meeting=
 notes.=C2=A0 Less well-discussed is that the authorization rule is that an=
yone with a datatracker account has write access, but I think that implemen=
ting anything more granular (e.g., attendee status for the meeting that gen=
erated the minutes) would be actual work.<br>
<br>
The authorization rule seems to correspond to CodiMD=E2=80=99s =E2=80=9Cedi=
table=E2=80=9D, which is therefore the setting we should choose for meeting=
 notes.=C2=A0 Whether we can do that automatically from the place where the=
 meetings are assigned codimd names or have to do this manually is then a p=
rocedural thing to be discussed on tools-discuss.<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000a88ba205c89b147b--


From nobody Mon Aug  2 15:28:24 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446B53A1F5F for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tM7nUTY9FOPL for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:10 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB0D53A1F2E for <111attendees@ietf.org>; Mon,  2 Aug 2021 15:28:09 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id hs10so24664852ejc.0 for <111attendees@ietf.org>; Mon, 02 Aug 2021 15:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FGgNZEDsn5RwlNgDAaRn7sKzZQM4l+LALh6dF99ID88=; b=Tz9ilUrypQd8wPpc6jUOsN54DunPNh+krn5rq54LRMR0vL0W52BzrAUKZMN8Ja/6j9 +8+IgMG/Y1bP/HSumhIp8VsS7Uo7khZGP3ouAdILwlUKEPuaENdNJYpIiKVHnLwvm4v4 UWBPX6T481xvISh9IHA1GZLldCtwRLxIWuVl2CnTk0U0WtJIFtBSYM62rFUDkNRvxOU2 /qCQ14jxFEjvthrmKSm3T6xISaPi4F9tHrDUSZ20KirbbjkHqFFVPlgyLc+un7atc/8y TWm4Hy0ASPmwGBkpErYkaoLCE8uvjs6SoHsHp102bNY3Fb9gzeovk7aGZfiXnLz6CMtD GOew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FGgNZEDsn5RwlNgDAaRn7sKzZQM4l+LALh6dF99ID88=; b=AD4emHLe0AQdhoO7D9MNBM03nUakN+8EHGN9Nm1hbIieRvDkCrAEGYwRHkdeoRxw/A KvBB1A+aLQOdEvFsC6PDxnTRw1LE1SCWTLoEnq05G/TRYGwuv5APGDZZIZWCHvamWyK9 kj1GdG0a8x93LqAjPe+5aC/7IXlYQWiUXy1pmtWCM7uZ3bSyA2PX4Ki7U/+K4kkd1RrY 9BzXGNJvmNsbxqbQIZQmp7Pyvcv8rec93DEFAm/3uEn9C29KLPQJjRhv/EAzwU1YHoC3 hr8QZXI2DawGlc1j/0knlXXALt9bweDEONEEUW9mIdbdBjDq4XXB5+NrQAIG3QKZTiFw Xm7Q==
X-Gm-Message-State: AOAM533LvIZH9Xihngq0LJlogNWodvPspf1PUJ1Nbp795b+7RNfL5ELd j5qW0Uqr0KuAK7itb7mp7XKLPZscTBsfnHOyhRPGhMXBVcozLA==
X-Google-Smtp-Source: ABdhPJyUcwy1rXpd92QVFlLdBz8/TVbnWwSje+V420yu1WQsf4AbuRn2ebERsPv/HGDxNYHc+GKqVHnG9jSonY4gmgA=
X-Received: by 2002:a17:906:a98e:: with SMTP id jr14mr17547361ejb.450.1627943288165;  Mon, 02 Aug 2021 15:28:08 -0700 (PDT)
MIME-Version: 1.0
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
In-Reply-To: <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:57:56 +0430
Message-ID: <CA+d13g3q5fN4u5nPk6UoWiOYt+P43Z4CjHjMMu7WJBrV_J5nvQ@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: John Levine <ietf@johnlevine.com>, 111attendees@ietf.org, jmh@joelhalpern.com
Content-Type: multipart/alternative; boundary="00000000000067da1405c89b1524"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/H6Lcursbci3psOAE3aOHGiQdOG0>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:28:23 -0000

--00000000000067da1405c89b1524
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =DB=8C=DA=A9=D8=B4=D9=86=D8=A8=
=D9=87 =DB=B1 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=E2=80=8F =
=DB=B1=DB=B9:=DB=B2=DB=B1 Salz, Rich <rsalz=3D
40akamai.com@dmarc.ietf.org> =D9=86=D9=88=D8=B4=D8=AA:

> >   These are the formal minutes of our meetings.  I don't think it's
> unreasonable to expect that minimal
>     level of accountability from the people writing them.
>
> More than that, you do not want some random unauthenticated person
> changing their name to something like the volunteer minute-taker and maki=
ng
> modifications.
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--00000000000067da1405c89b1524
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =DB=8C=DA=A9=
=D8=B4=D9=86=D8=A8=D9=87 =DB=B1 =D8=A7=D9=88=D8=AA =DB=B2=DB=B0=DB=B2=DB=B1=
=D8=8C=E2=80=8F =DB=B1=DB=B9:=DB=B2=DB=B1 Salz, Rich &lt;rsalz=3D<a href=3D=
"mailto:40akamai.com@dmarc.ietf.org">40akamai.com@dmarc.ietf.org</a>&gt; =
=D9=86=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt;=C2=
=A0 =C2=A0These are the formal minutes of our meetings.=C2=A0 I don&#39;t t=
hink it&#39;s unreasonable to expect that minimal<br>
=C2=A0 =C2=A0 level of accountability from the people writing them.<br>
<br>
More than that, you do not want some random unauthenticated person changing=
 their name to something like the volunteer minute-taker and making modific=
ations.<br>
<br>
<br>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--00000000000067da1405c89b1524--


From nobody Mon Aug  2 15:28:49 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97183A1F34 for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 7TC0P13wETvx for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:34 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 761C43A1F12 for <111attendees@ietf.org>; Mon,  2 Aug 2021 15:28:34 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id f13so26487767edq.13 for <111attendees@ietf.org>; Mon, 02 Aug 2021 15:28:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wx733t7GuX26fXbLSU2Sm1loVr02hmjXIbbhUcbaCQA=; b=j8HmcmleMfNdcOH5iVC9wVitHi7kfat5bhqlguUQL5bbyfjlI5WAu8RdDoEL2e4Gqc Irbr+QCw9IU53lQkg3xDZ31/meeIBbdSmhlGW1RHYK+EBGOoRbHW6tGpcsLU1+/7RKtE z08cS/IeH65P6uPS1WwlDCrgHg4bmJCsYHPhiBW4nj5u6GFmErWzFHGsD3OGtVaIkJcg Rl60p2WCc9zQQSGe+MQ+lAyQIbAG6SA8JlPI5x9hEf1qMMfIFBOZ+L6hr96kZoOghMp0 3MzNyjjzF5dNgdX8tujq8mdEbQibjVrURc/h9FtohA6FXNHWAFgXnaXoxHOSEiaOF0jt ElsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wx733t7GuX26fXbLSU2Sm1loVr02hmjXIbbhUcbaCQA=; b=Tl5zJZHKAsquGUBnCp1csqm5rLHBDsRTutAqHKysXJPjDCoUQFOTFPdL453aTJ+Ef/ /lZeJnWcp7zVwfCOTbkIyXjQbhgjR1iaDnJ4xbb36VrYXRhnITbvAtbOCoBSQrovVugI 5o8nTHthgOEXw3MkzkioEFpUORvi2vdEE/NSL14mM2VJegGf6k+bSKnxvXOR9wMobMU6 lnY34HWm1D1BPxreXZl7g056nr1limnfPjAgQPYhfkWHx0gVb24Kw3lxGdlEX4PxlbJn my6dAn5nTCwkB1xj56mX6LSqIFBi6kqiN73MOjHGGERrQTfRqN+fBUCxxn+VYVHzMvtZ NCbQ==
X-Gm-Message-State: AOAM533SSUcgOVCOi7vJO6av+TcyTmlqYGQK7y3uwj3yMdeXQtXrZNQ3 xEEf2Ns+BOhAv6R3pKLLCwPHEbcq1IZK3pm3fXsqv2bp11wGTw==
X-Google-Smtp-Source: ABdhPJwajhfwRHY8zcIbNhW5cqhsKlZdiwIdDZBCtip3QIL+1Rn4Nl+1dfPBB0FrbSycff+VCLBJvFYg9IDHv4cOr+A=
X-Received: by 2002:a05:6402:4d1:: with SMTP id n17mr21646888edw.337.1627943312989;  Mon, 02 Aug 2021 15:28:32 -0700 (PDT)
MIME-Version: 1.0
References: <AM8P193MB078821D4A3EBB38216268A10FAEC9@AM8P193MB0788.EURP193.PROD.OUTLOOK.COM> <F46F0A1E-F427-4C0E-BB89-C9BD645A995D@xagsolutions.com>
In-Reply-To: <F46F0A1E-F427-4C0E-BB89-C9BD645A995D@xagsolutions.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:58:21 +0430
Message-ID: <CA+d13g3BvUwm8=xBkswgFrL+Ou2WOEvbTuu1iZs=fTYz3ygg4A@mail.gmail.com>
To: Sean Croghan <sean@xagsolutions.com>
Cc: Ulrich Wisser <ulrich.wisser@internetstiftelsen.se>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e2a16805c89b16c8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/iWF-sBcG7joSiCOMLotsuywz8x0>
Subject: Re: [111attendees] Network measurements
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:28:48 -0000

--000000000000e2a16805c89b16c8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=D8=A8=D9=87 =DB=B3=
=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=
=E2=80=8F =DB=B4:=DB=B3=DB=B9 Sean Croghan <sean@xagsolutions.com>
=D9=86=D9=88=D8=B4=D8=AA:

> We do have a couple of dashboard locations in gather. One is next to the
> help desk and the other is close to the NOC.
>
> You can also go directly to the dashboard
>
> https://dashboard.meeting.ietf.org/dashboard
>
> This will let you see session attendance for each day, region and session
> participation counts for the last 4 virtual meetings. The monitoring page
> will show the health of the services, along with the traffic stats. Also =
if
> you hover over the Ping, CPU, and Memory indicators additional details wi=
ll
> be displayed.
>
>
>
>
> On Jul 30, 2021, at 16:56, Ulrich Wisser <
> ulrich.wisser@internetstiftelsen.se> wrote:
>
> Hi,
>
> Thanks for another great conference.
> At the physical meetings the noc team sets out stations which show networ=
k
> statistics.
> Is there any documentation on this? I would like to try to recreate some
> of it.
> Maybe someone has a picture or screen dumps?
>
> Kind regards from Stockholm
>
> /Ulrich
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000e2a16805c89b16c8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=
=D8=A8=D9=87 =DB=B3=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=
=DB=B2=DB=B1=D8=8C=E2=80=8F =DB=B4:=DB=B3=DB=B9 Sean Croghan &lt;<a href=3D=
"mailto:sean@xagsolutions.com">sean@xagsolutions.com</a>&gt; =D9=86=D9=88=
=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;line-break:after-white-space">
We do have a couple of dashboard locations in gather. One is next to the he=
lp desk and the other is close to the NOC.
<div><br>
</div>
<div>You can also go directly to the dashboard=C2=A0</div>
<div><br>
</div>
<div><a href=3D"https://dashboard.meeting.ietf.org/dashboard" target=3D"_bl=
ank" rel=3D"noreferrer">https://dashboard.meeting.ietf.org/dashboard</a></d=
iv>
<div><br>
</div>
<div>This will let you see session attendance for each day, region and sess=
ion participation counts for the last 4 virtual meetings. The monitoring pa=
ge will show the health of the services, along with the traffic stats. Also=
 if you hover over the
 Ping, CPU, and Memory indicators additional details will be displayed.=C2=
=A0</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div><br>
<blockquote type=3D"cite">
<div>On Jul 30, 2021, at 16:56, Ulrich Wisser &lt;<a href=3D"mailto:ulrich.=
wisser@internetstiftelsen.se" target=3D"_blank" rel=3D"noreferrer">ulrich.w=
isser@internetstiftelsen.se</a>&gt; wrote:</div>
<br>
<div>
<div style=3D"font-family:Poppins-Regular;font-size:12px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;text-decoration:none">
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"SV">Hi,<u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"SV"><u></u>=C2=A0<u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Thanks for another great conference.<span>=C2=A0</span=
><u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">At the physical meetings the noc team sets out station=
s which show network statistics.<u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Is there any documentation on this? I would like to tr=
y to recreate some of it.<u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Maybe someone has a picture or screen dumps?<u></u><u>=
</u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Kind regards from Stockholm<u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US">/Ulrich<u></u><u></u></span></div>
<div style=3D"margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></div>
</div>
<span style=3D"font-family:Poppins-Regular;font-size:12px;font-style:normal=
;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;text-decoration:none;float:none;display:inline!important">--<span>=C2=
=A0</span></span><br style=3D"font-family:Poppins-Regular;font-size:12px;fo=
nt-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:=
normal;text-align:start;text-indent:0px;text-transform:none;white-space:nor=
mal;word-spacing:0px;text-decoration:none">
<span style=3D"font-family:Poppins-Regular;font-size:12px;font-style:normal=
;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;text-decoration:none;float:none;display:inline!important">111attendee=
s
 mailing list</span><br style=3D"font-family:Poppins-Regular;font-size:12px=
;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;text-decoration:none">
<a href=3D"mailto:111attendees@ietf.org" style=3D"font-family:Poppins-Regul=
ar;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:no=
rmal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px" target=3D"_blank" rel=3D"noreferr=
er">111attendees@ietf.org</a><br style=3D"font-family:Poppins-Regular;font-=
size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;text-decoration:none">
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" style=3D"fon=
t-family:Poppins-Regular;font-size:12px;font-style:normal;font-variant-caps=
:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px" target=3D"_=
blank" rel=3D"noreferrer">https://www.ietf.org/mailman/listinfo/111attendee=
s</a></div>
</blockquote>
</div>
<br>
</div>
</div>

-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000e2a16805c89b16c8--


From nobody Mon Aug  2 15:29:08 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFF33A1F75 for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0A_Uvb6E_nnw for <111attendees@ietfa.amsl.com>; Mon,  2 Aug 2021 15:28:55 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51EF93A1F17 for <111attendees@ietf.org>; Mon,  2 Aug 2021 15:28:55 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id z11so4128353edb.11 for <111attendees@ietf.org>; Mon, 02 Aug 2021 15:28:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Sb46xJKCKoShH1tJQDM84rCu+l9yepb2+auspPyAMY=; b=tHynbfZWT4rfcDQ4nrvq0lyMBspkvAdZf210PrH9ZhbScce4N18HkSQPgczs35V/B3 5XYMlyP/AOeXLCKRizk6/98lzGxd3u7K8Wfby5NQIyU4/ujYSg9OvdYB1ErE2Fk/SQzS 13nV9AcdnWU3/CkqvlQvLVwuNKEORSyLS9TxkERvYOQjUmF69KvvZs6V06HsWTvA62d4 BJD8s2MPSUf6sn8fgvr6C3DHK23MEP7prAt+OX8qi1HNyXmB5qw2AzIVCoqpmROwqNH7 LvQNnUfWHkAEf2JKvySG9vi87vp+CnEg8BprruYDfOObhg4dbgITrURYY5BCkWu4SD6N H1lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0Sb46xJKCKoShH1tJQDM84rCu+l9yepb2+auspPyAMY=; b=DixmicPGMoCa2Vai9yI3QyAOdq8n3mpyHd1u4Nfx/bgvP5BG4z/iiyyoHZT+MK/JW7 V0f+/bGKFmLIjvKdsYQry8MuVYpRaousI8AZtDrFTf5roXr9z1aycXn8iAfpAfQMuJdW ZZLwgDQZuhc/uwwAzUu7kI9KYw2NgeSredWMFl0Oy7q6mP/juR6HMfM3pYBG4lRQgsbM rcqxeRZyFSTXDCwthSqFEWvKDogHNKl8heP1y2r0iYYH4btweKzyNOqetvGfJx2k0opg VZ5VlRAI06EJ1LwVaP6rOvhcGS2HVlKOmXhXtxToiHyTKuAUsChzLwHLO87iyJDeuwt5 VLsg==
X-Gm-Message-State: AOAM531c91i+1gr7dHb8ftUopelWWpzSX/Ma4cbZVrtZ1YFy9rIC3RCl n0KSf3smGYII/kOxNJrwfCUmSSoPH6Zvho5ENn8=
X-Google-Smtp-Source: ABdhPJwns1fovd9zN2vQVeh6ktrIH28Y78nUfYiezqcKZxDU2cUp87axCMho5wROxQjcOEVIM3biutgtWIHB4LODyzo=
X-Received: by 2002:aa7:cac6:: with SMTP id l6mr1034246edt.37.1627943333696; Mon, 02 Aug 2021 15:28:53 -0700 (PDT)
MIME-Version: 1.0
References: <AM8P193MB078821D4A3EBB38216268A10FAEC9@AM8P193MB0788.EURP193.PROD.OUTLOOK.COM>
In-Reply-To: <AM8P193MB078821D4A3EBB38216268A10FAEC9@AM8P193MB0788.EURP193.PROD.OUTLOOK.COM>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:58:42 +0430
Message-ID: <CA+d13g2oKpNX6xYxX07uCqFXUwDuEkVFpn2r625X5hCzrv0ajw@mail.gmail.com>
To: Ulrich Wisser <ulrich.wisser@internetstiftelsen.se>
Cc: 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001e98c505c89b18c5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/819WjCsX9PNYUnOW51FX61_ZDg4>
Subject: Re: [111attendees] Network measurements
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:29:08 -0000

--0000000000001e98c505c89b18c5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=D8=A8=D9=87 =DB=B3=
=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=
=E2=80=8F =DB=B4:=DB=B2=DB=B8 Ulrich Wisser <
ulrich.wisser@internetstiftelsen.se> =D9=86=D9=88=D8=B4=D8=AA:

> Hi,
>
>
>
> Thanks for another great conference.
>
> At the physical meetings the noc team sets out stations which show networ=
k
> statistics.
>
> Is there any documentation on this? I would like to try to recreate some
> of it.
>
> Maybe someone has a picture or screen dumps?
>
>
>
> Kind regards from Stockholm
>
>
>
> /Ulrich
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000001e98c505c89b18c5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=
=D8=A8=D9=87 =DB=B3=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=
=DB=B2=DB=B1=D8=8C=E2=80=8F =DB=B4:=DB=B2=DB=B8 Ulrich Wisser &lt;<a href=
=3D"mailto:ulrich.wisser@internetstiftelsen.se">ulrich.wisser@internetstift=
elsen.se</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">





<div lang=3D"en-SE" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:b=
reak-word">
<div class=3D"m_2486554350700895421WordSection1">
<p class=3D"MsoNormal"><span lang=3D"SV">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"SV"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks for another great confer=
ence. <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">At the physical meetings the no=
c team sets out stations which show network statistics.<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Is there any documentation on t=
his? I would like to try to recreate some of it.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Maybe someone has a picture or =
screen dumps?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Kind regards from Stockholm<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">/Ulrich<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
</div>

-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000001e98c505c89b18c5--


From nobody Mon Aug  2 15:29:25 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA313A1A47; Mon,  2 Aug 2021 15:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 znF6KwnfICyO; Mon,  2 Aug 2021 15:29:09 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E2F3A1C54; Mon,  2 Aug 2021 15:29:08 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id u3so706881ejz.1; Mon, 02 Aug 2021 15:29:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MwUl3YaPFtJ+hlF70Egsj2z+R03l61KhbLMRmISZ75Y=; b=cvr5BQlR0C2gqTh8RPnIXHu4+QW9z5gij9Q1+iCOEDRtWQOLESRLIWMjC8c+SdahsR UgBfhFxUxtwj+D61C6afez9mZbMPLW9WGtQ4AfYDKuv6feKsnPKTDFzjCZ4if1L+t5HD rCEsejPKstgGnumFx4cY6dyYiCoDvsBf8+0P+i7RyQBIpJ+HlNOKyOuTOWSqgGr7hXiU xcFErgoZo3nYDY/SviJ911UzOfLegMsNb+jAg4Pi+qNZQWq4hEVA2b/lDyZ5NyICyzEg VOUajvJydpGLHyupg1dOZGeyumQl7DGah/j3glEQR6GxH+XL1shvjf2CyMaq/i4cT0RH bn9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MwUl3YaPFtJ+hlF70Egsj2z+R03l61KhbLMRmISZ75Y=; b=HFp+wyid0Hhvse9Ty44R+7d3fkmwYr5NfzdBU6coPFHK9wRGhIaX/1B6z82y3TshT2 eTBSYnUexiMGZUJh0NjyU3GKcwVkyX3adJntLXimvbKhtdJkokTfVyP3p7wSmDhK5izY wra+QTTZwJBLL87GBcIMvkFGacHIv2Id2sUnFo9Pw5so6jWo4YAZAvpAp1lcF4Hf14kE SlFiPSlUOalQhX2SeT7HyR21yDJ0X3jrVccqGtIFVQJVrmU51kjBZr/5Eym2+zkkZTcG 6PjSRsPJ8yS/2s9NbnQndlld6T4n9Lj+fWG0z3y1VHCySd370E7YgOfyFLZMKkiGQ1Jd 18nQ==
X-Gm-Message-State: AOAM5335FEOdGlHjCg553lw8qvM5obb9FC833fCOPRyl4dnXOVcb2vno pfFnH+ApY61L4X8ho66GGlwjGKcVuQ6+4j7yfdQ=
X-Google-Smtp-Source: ABdhPJxJqUb72XkhoKUpMV5WY2auNH9zhFqQ0Pg+StPOR4MaozM8yp1lNaU5BasiuU5rxOafUOysVq3aW0aBzj//FUs=
X-Received: by 2002:a17:906:2dc5:: with SMTP id h5mr6957441eji.515.1627943346820;  Mon, 02 Aug 2021 15:29:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
In-Reply-To: <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:58:54 +0430
Message-ID: <CA+d13g17a-UtWDEcUNYUNrDf8+bgGCWptsu3PN17n_OQyrdQDg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org,  tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e6dafc05c89b1836"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/hCbH1xHAbnq_ApZ-DMgu9EPSz88>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:29:23 -0000

--000000000000e6dafc05c89b1836
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=D8=A8=D9=87 =DB=B3=
=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=
=E2=80=8F =DB=B1:=DB=B4=DB=B5 Eric Rescorla <ekr@rtfm.com> =D9=86=D9=88=D8=
=B4=D8=AA:

>
>
> On Fri, Jul 30, 2021 at 2:03 PM Bron Gondwana <brong@fastmailteam.com>
> wrote:
>
>> Ooh, we're going a full "suggestions for meetecho" thread?  I'd like to
>> propose some things!
>>
>> *that we replace the current "raise hands" tool:*
>>
>> *... *which is based on an expired draft which isn't going to be
>> refreshed - with a better tool that allows the chairs to:
>>
>> a) label each option
>> b) have more than 2 options (max 9 maybe)
>> c) select between "choose one" and "choose N" modes (checkbox vs radio
>> button)
>>
>> ... and which appears IN PLACE of the slides when enabled, so that
>> meeting participants don't have to navigate to a separate tab to interac=
t.
>>
>> More generally, it's too easy for some participants to be lost on
>> different tabs where they can't see the slides.  The multiple views wher=
e
>> you can see individual talking heads in more detail are not actually
>> valuable I don't think - if slides are showing they should be the bulk o=
f
>> the screen because they need to be read - and if a poll is showing then =
for
>> sure it should be taking over the screen.
>>
>
> EKR Raises Hand.
>
>
> *a "temporary mute" mode that keeps the audio stream open:*
>>
>> This is still an issue for me.  I often mute myself while chairing so I
>> can take notes without my keyboard sound interrupting the chat - but it
>> means that I can't easily respond to somebody because the rejigging of t=
he
>> audio channel not only creates a hiccup in the incoming audio feed which
>> means I might miss something someone says, but it also creates enough of=
 a
>> delay that by the time I could have responded the other party's mental
>> state has moved on.
>>
>> Timing is really important in conversation and we're already fighting
>> with the quarter second delay imposed by the size of the planet.
>> Additional delay makes it unwieldy.
>>
>
> Note that this is a respect in which Meetecho is unusual. Most other VC
> systems which I am familiar with just stop sending on the track but keep
> the microphone open rather than dropping the media stream and re-calling
> getUserMedia().
>
> To your list, I would add auto-unmuting (and even more importantly,
> muting) when people enter and exit the head of the queue. This would remo=
ve
> a lot of goofy behavior.
>
> -Ekr
>
>
>
>
> *allow multiple connections by the same person to the same session:*
>>
>> I have multiple times wanted to switch device temporarily - from my
>> desktop computer to a phone / ipad so I can temporarily move to another
>> location while continuing to follow a meeting.  Multiple connection supp=
ort
>> would mean I could switch over without a break.
>>
>> Sure it could be abused by people "sharing" a login, but that would be
>> pretty obvious if both parties tried to participate, and given that we
>> allow fee waivers anyway, it's unlikely to be abused significantly.  Sur=
e
>> there are Jabber naming issues, but we can avoid that by giving each jab=
ber
>> name with a serial number (which I believe already happens now?)
>>
>> ...
>>
>> I've already written these up separately in the past, but:
>>
>> *information about who is speaking in the same place as video feeds*
>>
>> See my previous email :)  Basically the "participant list" should just b=
e
>> an ordered list of participants and only needs to be switched to when
>> seeing who is in the call or opening an individual message to them (and
>> people don't get moved out of order when they're sending something).  Th=
e
>> "who is sending something" list should be all together with the video, a=
nd
>> chairs pinned even if they're sending nothing right now.
>>
>> Along with visual indicators of "currently sending audio" on people so w=
e
>> know who of those with their audio channel open are currently speaking,
>> this makes it easier to look in one place to see the source of all sound=
,
>> and eyes can generally flit between the right hand side (video and audio
>> indicators) and the slides, without needing to also track via the
>> participant list.
>>
>> *flexible "assign chair"**:*
>>
>> This one hasn't come up in practice, but the chairs for meetings are
>> pre-assigned from datatracker.  It would be great for ADs and the meetec=
ho
>> reps in each meeting to be able to upgrade anybody to a chair role or
>> remove a chair role with a simple click.
>>
>> In real rooms, anyone can go sit in the chair at the front of the room,
>> and it's not abused because of social convention.  I believe that we can
>> map that to this virtual space and still have it work sensibly.  People
>> won't take the chair unless there's a legitimate reason to do it, and so
>> long as it's logged - if someone does consistently abuse it we have
>> processes to eject them from the IETF for misbehaviour.
>>
>> This has become less important with the ability for individuals to turn
>> on both audio and video themselves, so the chair is going less busywork
>> just approving access, but it would be good to make it possible for some=
one
>> else to step into the chair if the regular chairs are unable to attend o=
r
>> lose network, rather than making the meeting less able to run.
>>
>> Bron.
>>
>> On Sat, Jul 31, 2021, at 05:38, Meetecho IETF support wrote:
>>
>> All,
>>
>> chiming in just to say that we at Meetecho appreciate and value your
>> feedback. We'll definitely take it into account when developing the
>> future releases of the platform. We'll provide comments on the points
>> raised as soon as we get the chance to parse them, i.e., when the
>> meeting is over.
>>
>> Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to header
>> to that list as well, as that's the right place to discuss enhancements
>> and provide feedback that would be easier for us to collect.
>>
>> Best,
>> Alessandro
>>
>> Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto:
>> > I should have changed the Subject a LONG time ago! But this thread has
>> > morphed into helpful observations and suggestions, so, if I might add =
a
>> > couple of things ...
>> >
>> > I agree that Meetecho has been improving (and just for fun, the
>> Meetecho
>> > guys were participants in the MEDIACTL session I was co-chairing in
>> > Hiroshima at IETF 76 in November 2009, and they roped in a team member
>> > from Italy during the discussion using whatever the toolset was back
>> > then, so many of you have no idea how MUCH they've improved =F0=9F=98=
=80).
>> >
>> > I see that we've already mentioned detaching the chat window, and
>> > usually I remember that we can detach the chat by Tuesday of each IETF
>> > meeting week at the latest, which is almost certainly a result of not
>> > having THAT much experience with Meetecho during the four months
>> between
>> > meetings. Now that we can use Meetecho for interim meetings, that will
>> > help me remember more clearly, so good there, too.
>> >
>> > The one thing I've noticed this week is how difficult it is to figure
>> > out who is speaking if they aren't sending video, and there's a long
>> > list of people in the queue. The suggestion to move the speakers above
>> > the queue would improve that, and so would simply displaying the activ=
e
>> > speaker names in the screen space where their video would have gone, i=
f
>> > the person had been sending video.One reason that matters, is that it'=
s
>> > helpful for everyone to get the speaker's name right in the minutes.
>> > That's not just for new attendees, I'm starting to forget what people
>> > sound like, unless I'm talking to them regularly, or they have a very
>> > distinctive speech pattern, so I've definitely depending on seeing
>> names
>> > when I'm taking minutes. .
>> >
>> > The one thing I was thinking about, as I read through this thread, was
>> > that we are kinda *not *talking about what the IETF thinks the target
>> > audience for our conferencing tool is.
>> >
>> >   * For probably the last couple of IETFs, I have a GREAT setup for
>> >     remote participation (my laptop screen, plus two 25-inch monitors)=
.
>> >     But I do have tiled windows on all three screens.
>> >   * If we think people who can't throw a few hundred dollars at monito=
r
>> >     screens are part of our target audience, that's worth noting.
>> >   * If we think we're going to have hybrid meetings, in at least some
>> >     scenarios, it's going to be good to use Meetecho in the conference
>> >     rooms (especially if we need to be distancing, so more spread out,
>> >     front to back in the conference rooms).
>> >   * Even if we aren't doing hybrid meetings, I've participated in some
>> >     working group meetings from my hotel room, but I wasn't tryng to
>> >     co-chair a meeting, or even to present at a meeting.
>> >   * When Michael Richardson and I talked to the Cellar working group
>> >     participants about switching to Meetecho for our (monthy) interims=
,
>> >     the first question we got was, "is there an iOS/Adroid client?" I
>> >     haven't checked Meetecho on my phone in years, but I'd bet offhand
>> >     that (1) it would work, but (2) it might not be as easy to use as
>> >     some other conferencing systems, on those devices. Do people have
>> >     experience with that?
>> >
>> > I'll let you folks continue to share these positive observations and
>> > proposals. Make Good Choices, of course.
>> >
>> > Best,
>> >
>> > Spencer
>> >
>> > On Thu, Jul 29, 2021 at 6:15 PM Jay Daley <jay@ietf.org
>> > <mailto:jay@ietf.org>> wrote:
>> >
>> >     Thanks Bron.  Personally I think that=E2=80=99s a great usability =
adjustment
>> >     and will forward to the Meetecho team for them to consider.
>> >
>> >     Jay
>> >
>> >      > On 30/07/2021, at 10:58 AM, Bron Gondwana <
>> brong@fastmailteam.com
>> >     <mailto:brong@fastmailteam.com>> wrote:
>> >      >
>> >      > On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:
>> >      >> No we have absolutely not pushed Meetecho into being "just a
>> >     contractor", they are a valued partner and we work very well
>> >     together.  If you have any doubts about that then ask them directl=
y.
>> >      >>
>> >      >> It is disappointing that you have escalated a personal concern
>> >     that you have with our services into such a strong criticism when
>> >     that is entirely unsupported by any evidence.
>> >      >
>> >      > Jay, I agree with your sentiment here - this attitude to Meetec=
ho
>> >     is counterproductive.  They've done great work for the last couple
>> >     of IETFs and the experience is improving each time.  I have
>> >     particularly appreciated the embedded slide management, and I'm su=
re
>> >     that will be even better next time too.
>> >      >
>> >      > Regarding the specific interface issues that remain, I do think
>> >     there's a question of "where do we propose improvements in a way
>> >     that will be noticed"?  I've seen the suggestion made very many
>> >     times that the "speaker" area (where the video shows) should have
>> >     additional lines for each person sending anything, rather than tha=
t
>> >     information being at the top of the participant list.  This is muc=
h
>> >     more like the experience with other chat systems, for example Zoom
>> >     shows either a photo or a blank item for somebody who isn't
>> >     currently sending video, but they're otherwise treated "the same" =
as
>> >     a person sending video in terms of real-estate and where to look f=
or
>> >     their presence by default.
>> >      >
>> >      > Right now with meetecho, my eyes are normally at the video are
>> >     when people are speaking, but if a non-video person is speaking I
>> >     need to look across to the other side of the screen to see the aud=
io
>> >     indication.
>> >      >
>> >      > And as was also suggested in this thread, you can't scroll the
>> >     participant list to find someone to chat to, because they jump to
>> >     the top when they are sending, then back to alphabetical position.
>> >     This is also a usability pain.  Separating "the list of
>> >     participants" (which wouldn't move about) and "the list of people
>> >     sending something" with the video and audio indications being
>> >     together in one place would be a significant improvement.  And as =
an
>> >     additional benefit, when you're looking at the chat window, you
>> >     would still be able to see all the details of who is sending
>> >     (including yourself - if you're sending then the indicator of your
>> >     own audio should be the same as the indicator of everyone else's
>> >     audio, rather than being in yet a third location up under your own
>> >     name).
>> >      >
>> >      > <image.png>
>> >      > So those two names would appear in the right hand side, and als=
o
>> >     still have their name in the participant list, and the video feeds
>> >     would each have a "here's what's being sent".  Chairs would always
>> >     have a presence on the right, with whatever they were currently
>> >     sending - and the "participants" tab would only have the list of
>> >     participants, and not be a place you needed to go to see activity,
>> >     so you could mostly keep the chat tab open.
>> >      >
>> >      > Bron.
>> >      >
>> >      >
>> >      > --
>> >      >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >      > brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>> >      >
>> >      >
>> >      > --
>> >      > 111attendees mailing list
>> >      > 111attendees@ietf.org <mailto:111attendees@ietf.org>
>> >      > https://www.ietf.org/mailman/listinfo/111attendees
>> >     <https://www.ietf.org/mailman/listinfo/111attendees>
>> >
>> >     --
>> >     Jay Daley
>> >     IETF Executive Director
>> >     jay@ietf.org <mailto:jay@ietf.org>
>> >
>> >     --
>> >     111attendees mailing list
>> >     111attendees@ietf.org <mailto:111attendees@ietf.org>
>> >     https://www.ietf.org/mailman/listinfo/111attendees
>> >     <https://www.ietf.org/mailman/listinfo/111attendees>
>> >
>> >
>>
>> --
>> 111attendees mailing list
>> 111attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/111attendees
>>
>>
>> --
>>   Bron Gondwana, CEO, Fastmail Pty Ltd
>>   brong@fastmailteam.com
>>
>>
>> ___________________________________________________________
>> Tools-discuss mailing list - Tools-discuss@ietf.org
>> This list is for discussion, not for action requests or bug reports.
>> * Report datatracker and mailarchive bugs to:
>> datatracker-project@ietf.org
>> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
>> * Report all other bugs or issues to: ietf-action@ietf.org
>> List info (including how to Unsubscribe):
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--000000000000e6dafc05c89b1836
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=
=D8=A8=D9=87 =DB=B3=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=
=DB=B2=DB=B1=D8=8C=E2=80=8F =DB=B1:=DB=B4=DB=B5 Eric Rescorla &lt;<a href=
=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt; =D9=86=D9=88=D8=B4=D8=AA:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Fri, Jul 30, 2021 at 2:03 PM Bron Gondwana &lt;<a href=3D"mailto:brong@f=
astmailteam.com" target=3D"_blank" rel=3D"noreferrer">brong@fastmailteam.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div><div style=3D"font-family:Arial">Ooh, we&#39;re going a full &quot;su=
ggestions for meetecho&quot; thread?=C2=A0 I&#39;d like to propose some thi=
ngs!<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font=
-family:Arial"><b>that we replace the current &quot;raise hands&quot; tool:=
</b><br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font=
-family:Arial"><b>... </b>which is based on an expired draft which isn&#39;=
t going to be refreshed - with a better tool that allows the chairs to:<br>=
</div><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:=
Arial">a) label each option<br></div><div style=3D"font-family:Arial">b) ha=
ve more than 2 options (max 9 maybe)<br></div><div style=3D"font-family:Ari=
al">c) select between &quot;choose one&quot; and &quot;choose N&quot; modes=
 (checkbox vs radio button)<br></div><div style=3D"font-family:Arial"><br><=
/div><div style=3D"font-family:Arial">... and which appears IN PLACE of the=
 slides when enabled, so that meeting participants don&#39;t have to naviga=
te to a separate tab to interact.=C2=A0<br></div><div style=3D"font-family:=
Arial"><br></div><div style=3D"font-family:Arial">More generally, it&#39;s =
too easy for some participants to be lost on different tabs where they can&=
#39;t see the slides.=C2=A0 The multiple views where you can see individual=
 talking heads in more detail are not actually valuable I don&#39;t think -=
 if slides are showing they should be the bulk of the screen because they n=
eed to be read - and if a poll is showing then for sure it should be taking=
 over the screen.<br></div></div></blockquote><div><br></div><div>EKR Raise=
s Hand.</div><div><br></div><div> <br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div><div style=3D"font-family:Arial"><b>a &quot;tempora=
ry mute&quot; mode that keeps the audio stream open:</b><br></div><div styl=
e=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">This is =
still an issue for me.=C2=A0 I often mute myself while chairing so I can ta=
ke notes without my keyboard sound interrupting the chat - but it means tha=
t I can&#39;t easily respond to somebody because the rejigging of the audio=
 channel not only creates a hiccup in the incoming audio feed which means I=
 might miss something someone says, but it also creates enough of a delay t=
hat by the time I could have responded the other party&#39;s mental state h=
as moved on.<br></div><div style=3D"font-family:Arial"><br></div><div style=
=3D"font-family:Arial">Timing is really important in conversation and we&#3=
9;re already fighting with the quarter second delay imposed by the size of =
the planet.=C2=A0 Additional delay makes it unwieldy.<br></div></div></bloc=
kquote></div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote=
">Note that this is a respect in which Meetecho is unusual. Most other VC s=
ystems which I am familiar with just stop sending on the track but keep the=
 microphone open rather than dropping the media stream and re-calling getUs=
erMedia().</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_qu=
ote">To your list, I would add auto-unmuting (and even more importantly, mu=
ting) when people enter and exit the head of the queue. This would remove a=
 lot of goofy behavior.<br></div><div class=3D"gmail_quote"><br></div><div =
class=3D"gmail_quote">-Ekr</div><div class=3D"gmail_quote"><br></div><div c=
lass=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><div><br></div><d=
iv><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div st=
yle=3D"font-family:Arial"><b>allow multiple connections by the same person =
to the same session:</b><br></div><div style=3D"font-family:Arial"><br></di=
v><div style=3D"font-family:Arial">I have multiple times wanted to switch d=
evice temporarily - from my desktop computer to a phone / ipad so I can tem=
porarily move to another location while continuing to follow a meeting.=C2=
=A0 Multiple connection support would mean I could switch over without a br=
eak.<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font=
-family:Arial">Sure it could be abused by people &quot;sharing&quot; a logi=
n, but that would be pretty obvious if both parties tried to participate, a=
nd given that we allow fee waivers anyway, it&#39;s unlikely to be abused s=
ignificantly.=C2=A0 Sure there are Jabber naming issues, but we can avoid t=
hat by giving each jabber name with a serial number (which I believe alread=
y happens now?)<br></div><div style=3D"font-family:Arial"><br></div><div st=
yle=3D"font-family:Arial">...<br></div><div style=3D"font-family:Arial"><br=
></div><div style=3D"font-family:Arial">I&#39;ve already written these up s=
eparately in the past, but:<br></div><div style=3D"font-family:Arial"><br><=
/div><div style=3D"font-family:Arial"><b>information about who is speaking =
in the same place as video feeds</b><br></div><div style=3D"font-family:Ari=
al"><br></div><div style=3D"font-family:Arial">See my previous email :)=C2=
=A0 Basically the &quot;participant list&quot; should just be an ordered li=
st of participants and only needs to be switched to when seeing who is in t=
he call or opening an individual message to them (and people don&#39;t get =
moved out of order when they&#39;re sending something).=C2=A0 The &quot;who=
 is sending something&quot; list should be all together with the video, and=
 chairs pinned even if they&#39;re sending nothing right now.<br></div><div=
 style=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">Alo=
ng with visual indicators of &quot;currently sending audio&quot; on people =
so we know who of those with their audio channel open are currently speakin=
g, this makes it easier to look in one place to see the source of all sound=
, and eyes can generally flit between the right hand side (video and audio =
indicators) and the slides, without needing to also track via the participa=
nt list.<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"=
font-family:Arial"><b>flexible &quot;assign chair&quot;</b><b>:</b><br></di=
v><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:Aria=
l">This one hasn&#39;t come up in practice, but the chairs for meetings are=
 pre-assigned from datatracker.=C2=A0 It would be great for ADs and the mee=
techo reps in each meeting to be able to upgrade anybody to a chair role or=
 remove a chair role with a simple click.<br></div><div style=3D"font-famil=
y:Arial"><br></div><div style=3D"font-family:Arial">In real rooms, anyone c=
an go sit in the chair at the front of the room, and it&#39;s not abused be=
cause of social convention.=C2=A0 I believe that we can map that to this vi=
rtual space and still have it work sensibly.=C2=A0 People won&#39;t take th=
e chair unless there&#39;s a legitimate reason to do it, and so long as it&=
#39;s logged - if someone does consistently abuse it we have processes to e=
ject them from the IETF for misbehaviour.<br></div><div style=3D"font-famil=
y:Arial"><br></div><div style=3D"font-family:Arial">This has become less im=
portant with the ability for individuals to turn on both audio and video th=
emselves, so the chair is going less busywork just approving access, but it=
 would be good to make it possible for someone else to step into the chair =
if the regular chairs are unable to attend or lose network, rather than mak=
ing the meeting less able to run.<br></div><div style=3D"font-family:Arial"=
><br></div><div style=3D"font-family:Arial">Bron.<br></div><div style=3D"fo=
nt-family:Arial"><br></div><div>On Sat, Jul 31, 2021, at 05:38, Meetecho IE=
TF support wrote:<br></div><blockquote type=3D"cite" id=3D"m_-1745021874871=
855191gmail-m_7509767322605381934qt"><div style=3D"font-family:Arial">All,<=
br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font-fami=
ly:Arial">chiming in just to say that we at Meetecho appreciate and value y=
our=C2=A0<br></div><div style=3D"font-family:Arial">feedback. We&#39;ll def=
initely take it into account when developing the=C2=A0<br></div><div style=
=3D"font-family:Arial">future releases of the platform. We&#39;ll provide c=
omments on the points=C2=A0<br></div><div style=3D"font-family:Arial">raise=
d as soon as we get the chance to parse them, i.e., when the=C2=A0<br></div=
><div style=3D"font-family:Arial">meeting is over.<br></div><div style=3D"f=
ont-family:Arial"><br></div><div style=3D"font-family:Arial">Also, I&#39;m =
cc&#39;ing=C2=A0<a href=3D"mailto:tools-discuss@ietf.org" target=3D"_blank"=
 rel=3D"noreferrer">tools-discuss@ietf.org</a> and setting the reply-to hea=
der=C2=A0<br></div><div style=3D"font-family:Arial">to that list as well, a=
s that&#39;s the right place to discuss enhancements=C2=A0<br></div><div st=
yle=3D"font-family:Arial">and provide feedback that would be easier for us =
to collect.<br></div><div style=3D"font-family:Arial"><br></div><div style=
=3D"font-family:Arial">Best,<br></div><div style=3D"font-family:Arial">Ales=
sandro<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"fo=
nt-family:Arial">Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto:<br>=
</div><div style=3D"font-family:Arial">&gt; I should have changed the Subje=
ct a LONG time ago! But this thread has=C2=A0<br></div><div style=3D"font-f=
amily:Arial">&gt; morphed into helpful observations and suggestions, so, if=
 I might add a=C2=A0<br></div><div style=3D"font-family:Arial">&gt; couple =
of things ...<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div=
><div style=3D"font-family:Arial">&gt; I agree that Meetecho has been impro=
ving (and just for fun, the Meetecho=C2=A0<br></div><div style=3D"font-fami=
ly:Arial">&gt; guys were participants in the MEDIACTL session I was co-chai=
ring in=C2=A0<br></div><div style=3D"font-family:Arial">&gt; Hiroshima at I=
ETF 76 in November 2009, and they roped in a team member=C2=A0<br></div><di=
v style=3D"font-family:Arial">&gt; from Italy during the discussion using w=
hatever the toolset was back=C2=A0<br></div><div style=3D"font-family:Arial=
">&gt; then, so many of you have no idea how MUCH they&#39;ve improved=C2=
=A0=F0=9F=98=80).<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br><=
/div><div style=3D"font-family:Arial">&gt; I see that we&#39;ve already men=
tioned detaching the chat window, and=C2=A0<br></div><div style=3D"font-fam=
ily:Arial">&gt; usually I remember that we can detach the chat by Tuesday o=
f each IETF=C2=A0<br></div><div style=3D"font-family:Arial">&gt; meeting we=
ek at the latest, which is almost certainly a result of not=C2=A0<br></div>=
<div style=3D"font-family:Arial">&gt; having THAT much experience with=C2=
=A0Meetecho during the four months between=C2=A0<br></div><div style=3D"fon=
t-family:Arial">&gt; meetings. Now that we can use Meetecho for interim mee=
tings, that will=C2=A0<br></div><div style=3D"font-family:Arial">&gt; help =
me remember more clearly, so good there, too.<br></div><div style=3D"font-f=
amily:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt; The =
one thing I&#39;ve noticed this week is how difficult it is to figure=C2=A0=
<br></div><div style=3D"font-family:Arial">&gt; out who is speaking if they=
 aren&#39;t sending video, and there&#39;s a long=C2=A0<br></div><div style=
=3D"font-family:Arial">&gt; list of people in the queue. The suggestion to =
move the speakers above=C2=A0<br></div><div style=3D"font-family:Arial">&gt=
; the queue would improve that, and so would simply displaying the active=
=C2=A0<br></div><div style=3D"font-family:Arial">&gt; speaker names in the =
screen space where their video would have gone, if=C2=A0<br></div><div styl=
e=3D"font-family:Arial">&gt; the person had been sending video.One reason t=
hat matters, is that it&#39;s=C2=A0<br></div><div style=3D"font-family:Aria=
l">&gt; helpful for everyone to get the speaker&#39;s name right in the min=
utes.=C2=A0<br></div><div style=3D"font-family:Arial">&gt; That&#39;s not j=
ust for new attendees, I&#39;m starting to forget what people=C2=A0<br></di=
v><div style=3D"font-family:Arial">&gt; sound like, unless I&#39;m talking =
to them regularly, or they have a very=C2=A0<br></div><div style=3D"font-fa=
mily:Arial">&gt; distinctive speech pattern, so I&#39;ve definitely dependi=
ng on seeing names=C2=A0<br></div><div style=3D"font-family:Arial">&gt; whe=
n I&#39;m taking minutes. .<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0<br></div><div style=3D"font-family:Arial">&gt; The one thing I was t=
hinking about, as I read through this thread, was=C2=A0<br></div><div style=
=3D"font-family:Arial">&gt; that we are kinda *not *talking about what the =
IETF thinks the target=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=
 audience for our conferencing tool is.<br></div><div style=3D"font-family:=
Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0 * For probably the last couple of IETFs, I have a GREAT setup for<br></=
div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 remote pa=
rticipation (my laptop screen, plus two 25-inch monitors).<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 But I do have tiled =
windows on all three screens.<br></div><div style=3D"font-family:Arial">&gt=
;=C2=A0=C2=A0 * If we think people who can&#39;t throw a few hundred dollar=
s at monitor<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0 screens are part of our target audience, that&#39;s worth noting.=
<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0 * If we think w=
e&#39;re going to have hybrid meetings, in at least some<br></div><div styl=
e=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 scenarios, it&#39;s go=
ing to be good to use Meetecho in the conference<br></div><div style=3D"fon=
t-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 rooms (especially if we need t=
o be distancing, so more spread out,<br></div><div style=3D"font-family:Ari=
al">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 front to back in the conference rooms).<br=
></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0 * Even if we aren&=
#39;t doing hybrid meetings, I&#39;ve participated in some<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 working group meetin=
gs from my hotel room, but I wasn&#39;t tryng to<br></div><div style=3D"fon=
t-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 co-chair a meeting, or even to=
 present at a meeting.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0 * When Michael Richardson and I talked to the Cellar working group<b=
r></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 parti=
cipants about switching to Meetecho for our (monthy) interims,<br></div><di=
v style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 the first questi=
on we got was, &quot;is there an iOS/Adroid client?&quot; I<br></div><div s=
tyle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 haven&#39;t checked=
 Meetecho on my phone in years, but I&#39;d bet offhand<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that (1) it would work,=
 but (2) it might not be as easy to use as<br></div><div style=3D"font-fami=
ly:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 some other conferencing systems, on =
those devices. Do people have<br></div><div style=3D"font-family:Arial">&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0 experience with that?<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt; I&=
#39;ll let you folks continue to share these positive observations and=C2=
=A0<br></div><div style=3D"font-family:Arial">&gt; proposals. Make Good Cho=
ices, of course.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></=
div><div style=3D"font-family:Arial">&gt; Best,<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt; Sp=
encer<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div st=
yle=3D"font-family:Arial">&gt; On Thu, Jul 29, 2021 at 6:15 PM Jay Daley &l=
t;<a href=3D"mailto:jay@ietf.org" target=3D"_blank" rel=3D"noreferrer">jay@=
ietf.org</a>=C2=A0<br></div><div style=3D"font-family:Arial">&gt; &lt;mailt=
o:<a href=3D"mailto:jay@ietf.org" target=3D"_blank" rel=3D"noreferrer">jay@=
ietf.org</a>&gt;&gt; wrote:<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 Thanks Bron.=C2=A0 Personally I think that=E2=80=99s a great usability =
adjustment<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0 and will forward to the Meetecho team for them to consider.<br></div=
><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 Jay<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &gt; On 30/07/2021, at 10:58 AM, Bron Gondwana &lt=
;<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank" rel=3D"norefer=
rer">brong@fastmailteam.com</a><br></div><div style=3D"font-family:Arial">&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0 &lt;mailto:<a href=3D"mailto:brong@fastmailteam=
.com" target=3D"_blank" rel=3D"noreferrer">brong@fastmailteam.com</a>&gt;&g=
t; wrote:<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 &gt; On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:=
<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 &gt;&gt; No we have absolutely not pushed Meetecho into being &quot;jus=
t a<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 =
contractor&quot;, they are a valued partner and we work very well<br></div>=
<div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 together.=C2=
=A0 If you have any doubts about that then ask them directly.<br></div><div=
 style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;&gt;<br=
></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&gt;&gt; It is disappointing that you have escalated a personal concern<br>=
</div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that yo=
u have with our services into such a strong criticism when<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that is entirely uns=
upported by any evidence.<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Jay, I agree with your sentiment he=
re - this attitude to Meetecho<br></div><div style=3D"font-family:Arial">&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0 is counterproductive.=C2=A0 They&#39;ve done gre=
at work for the last couple<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 of IETFs and the experience is improving each time=
.=C2=A0 I have<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 particularly appreciated the embedded slide management, and I&=
#39;m sure<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0 that will be even better next time too.<br></div><div style=3D"font-=
family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Regarding th=
e specific interface issues that remain, I do think<br></div><div style=3D"=
font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 there&#39;s a question of &=
quot;where do we propose improvements in a way<br></div><div style=3D"font-=
family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that will be noticed&quot;?=C2=
=A0 I&#39;ve seen the suggestion made very many<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 times that the &quot;speaker&qu=
ot; area (where the video shows) should have<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 additional lines for each person s=
ending anything, rather than that<br></div><div style=3D"font-family:Arial"=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0 information being at the top of the participa=
nt list.=C2=A0 This is much<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 more like the experience with other chat systems, =
for example Zoom<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 shows either a photo or a blank item for somebody who isn&#39;=
t<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 cu=
rrently sending video, but they&#39;re otherwise treated &quot;the same&quo=
t; as<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 a person sending video in terms of real-estate and where to look for<br=
></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 their =
presence by default.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Right now with meetecho, my eyes are n=
ormally at the video are<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0 when people are speaking, but if a non-video person i=
s speaking I<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0 need to look across to the other side of the screen to see the au=
dio<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 =
indication.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &gt; And as was also suggested in this thread, you=
 can&#39;t scroll the<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 participant list to find someone to chat to, because the=
y jump to<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0 the top when they are sending, then back to alphabetical position.=
=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 This is also a usability pain.=C2=A0 Separating &quot;the list of<br></=
div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 participa=
nts&quot; (which wouldn&#39;t move about) and &quot;the list of people<br><=
/div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 sending =
something&quot; with the video and audio indications being<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 together in one plac=
e would be a significant improvement.=C2=A0 And as an<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 additional benefit, whe=
n you&#39;re looking at the chat window, you<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 would still be able to see all the=
 details of who is sending<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 (including yourself - if you&#39;re sending then t=
he indicator of your<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 own audio should be the same as the indicator of everyon=
e else&#39;s<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0 audio, rather than being in yet a third location up under your ow=
n<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 na=
me).<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &gt; &lt;image.png&gt;<br></div><div style=3D"font-family:A=
rial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; So those two names would appe=
ar in the right hand side, and also<br></div><div style=3D"font-family:Aria=
l">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 still have their name in the participant li=
st, and the video feeds<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0 would each have a &quot;here&#39;s what&#39;s being s=
ent&quot;.=C2=A0 Chairs would always<br></div><div style=3D"font-family:Ari=
al">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 have a presence on the right, with whateve=
r they were currently<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 sending - and the &quot;participants&quot; tab would onl=
y have the list of<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 participants, and not be a place you needed to go to see ac=
tivity,<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 so you could mostly keep the chat tab open.<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Bron.<br></d=
iv><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=
<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &gt; --<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty =
Ltd<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &gt;=C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank=
" rel=3D"noreferrer">brong@fastmailteam.com</a> &lt;mailto:<a href=3D"mailt=
o:brong@fastmailteam.com" target=3D"_blank" rel=3D"noreferrer">brong@fastma=
ilteam.com</a>&gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Aria=
l">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; --<br></div><div style=3D"font-f=
amily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; 111attendees mailing l=
ist<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &gt;=C2=A0<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank"=
 rel=3D"noreferrer">111attendees@ietf.org</a> &lt;mailto:<a href=3D"mailto:=
111attendees@ietf.org" target=3D"_blank" rel=3D"noreferrer">111attendees@ie=
tf.org</a>&gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 &gt;=C2=A0<a href=3D"https://www.ietf.org/mailman/listin=
fo/111attendees" target=3D"_blank" rel=3D"noreferrer">https://www.ietf.org/=
mailman/listinfo/111attendees</a><br></div><div style=3D"font-family:Arial"=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &lt;<a href=3D"https://www.ietf.org/mailman/l=
istinfo/111attendees" target=3D"_blank" rel=3D"noreferrer">https://www.ietf=
.org/mailman/listinfo/111attendees</a>&gt;<br></div><div style=3D"font-fami=
ly:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 --=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 Jay Daley<br></div><div style=3D"font-family:Arial=
">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 IETF Executive Director<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"mailto:=
jay@ietf.org" target=3D"_blank" rel=3D"noreferrer">jay@ietf.org</a> &lt;mai=
lto:<a href=3D"mailto:jay@ietf.org" target=3D"_blank" rel=3D"noreferrer">ja=
y@ietf.org</a>&gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br>=
</div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 --=C2=
=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 =
111attendees mailing list<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"mailto:111attendees@ietf.org" target=
=3D"_blank" rel=3D"noreferrer">111attendees@ietf.org</a> &lt;mailto:<a href=
=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferrer">111a=
ttendees@ietf.org</a>&gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo=
/111attendees" target=3D"_blank" rel=3D"noreferrer">https://www.ietf.org/ma=
ilman/listinfo/111attendees</a><br></div><div style=3D"font-family:Arial">&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0 &lt;<a href=3D"https://www.ietf.org/mailman/lis=
tinfo/111attendees" target=3D"_blank" rel=3D"noreferrer">https://www.ietf.o=
rg/mailman/listinfo/111attendees</a>&gt;<br></div><div style=3D"font-family=
:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br>=
</div><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:=
Arial">--=C2=A0<br></div><div style=3D"font-family:Arial">111attendees mail=
ing list<br></div><div style=3D"font-family:Arial"><a href=3D"mailto:111att=
endees@ietf.org" target=3D"_blank" rel=3D"noreferrer">111attendees@ietf.org=
</a><br></div><div style=3D"font-family:Arial"><a href=3D"https://www.ietf.=
org/mailman/listinfo/111attendees" target=3D"_blank" rel=3D"noreferrer">htt=
ps://www.ietf.org/mailman/listinfo/111attendees</a><br></div><div style=3D"=
font-family:Arial"><br></div></blockquote><div style=3D"font-family:Arial">=
<br></div><div id=3D"m_-1745021874871855191gmail-m_7509767322605381934sig56=
629417"><div>--<br></div><div>=C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd<b=
r></div><div>=C2=A0 <a href=3D"mailto:brong@fastmailteam.com" target=3D"_bl=
ank" rel=3D"noreferrer">brong@fastmailteam.com</a><br></div><div><br></div>=
</div><div style=3D"font-family:Arial"><br></div></div>____________________=
_______________________________________<br>
Tools-discuss mailing list - <a href=3D"mailto:Tools-discuss@ietf.org" targ=
et=3D"_blank" rel=3D"noreferrer">Tools-discuss@ietf.org</a><br>
This list is for discussion, not for action requests or bug reports.<br>
* Report datatracker and mailarchive bugs to: <a href=3D"mailto:datatracker=
-project@ietf.org" target=3D"_blank" rel=3D"noreferrer">datatracker-project=
@ietf.org</a><br>
* Report <a href=3D"http://tools.ietf.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">tools.ietf.org</a> bugs to: <a href=3D"mailto:webmaster@too=
ls.ietf.org" target=3D"_blank" rel=3D"noreferrer">webmaster@tools.ietf.org<=
/a><br>
* Report all other bugs or issues to: <a href=3D"mailto:ietf-action@ietf.or=
g" target=3D"_blank" rel=3D"noreferrer">ietf-action@ietf.org</a><br>
List info (including how to Unsubscribe): <a href=3D"https://www.ietf.org/m=
ailman/listinfo/tools-discuss" rel=3D"noreferrer noreferrer" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/tools-discuss</a><br>
</blockquote></div></div>
-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--000000000000e6dafc05c89b1836--


From nobody Mon Aug  2 15:29:34 2021
Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37A233A1F80; Mon,  2 Aug 2021 15:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WLn4dVPN9Qek; Mon,  2 Aug 2021 15:29:20 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F83F3A1F2A; Mon,  2 Aug 2021 15:29:19 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id g21so7292877edb.4; Mon, 02 Aug 2021 15:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xFRMUDOg2JjCu8juhN6oNjBBHhTZB+LEqyArDTLGdss=; b=Ys2WOOrhs/O8b0SZCGtpwEIwH+sBgmmn/uh113gVre7SItfgxT1gogllj7IvxjBCN6 RymDDEsFDMi9eJ0aV6nMnTkikpSQu0/ooKtwP84uOqAkH8hS0NgWbvd1uE75VK297VAC p93oQ4jeRZRnsqjWLOtjqwDpTIOXxvxRWRctWHUaEe8sBWTeK367+/vhAwPgDx0/Ibux shZnxwlHpkEYcpmaYemPXly9IOUwO9roiW4jHOkfyd7Dd9p+DnXMlwbkvjjQrlPq/on0 D93TfHwleCk2xe7E+Q5pThBUMjGmxi/rH0W4X2RlxhaPAc7Rk1Ga1xMao7vX7IF8ImtJ U+mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xFRMUDOg2JjCu8juhN6oNjBBHhTZB+LEqyArDTLGdss=; b=fUSYyM+gXlS8EOjTQNMkGq85cTIzOTNPhQ6jS9lSXbmzGnl9+tDXDob64XupPxuVmi NBZ/meoL5Z9j8ArzZxW26gxGSkaPtORmYYSbykpWTxUNB7fEduPtTYWNa5EbPhR02lGr skpOKWv/b4MTEyQ0cHe0x6KBcfvANwWPDqfYONeBcxB0I2QnTgjv7yfojuuIbv9ISbG1 gGoYHADN02bvj8FI39WMk0kkh9dzWmCAvba/DK6SvguHUurK6ahv4J601xDTnHCJBfc5 XhEsQDWShFbeSVwr1BuKMh2BMKXS9YxGptaiZ+6r6FWRyva9E7q66sXIiH7Pj1BlfRHW CKbw==
X-Gm-Message-State: AOAM5306rgHpFvagl1CoiwfwnMIDRNYJCjsId4doPvLgqv0M2EeEX/ww Ap/9GaCBLhmCxt8hYwh9lv0piwb0FuYnBDJPS320youTAZ2VBA==
X-Google-Smtp-Source: ABdhPJxVgJbbHcW+PKJ8AMfKZNCN8BnkCnSlgrcCb5yI3edQWlxuxOZ/eXW9thH09sOINfdFAb07XTHaPL/f7C2sVrQ=
X-Received: by 2002:aa7:c799:: with SMTP id n25mr21185545eds.16.1627943356480;  Mon, 02 Aug 2021 15:29:16 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
In-Reply-To: <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:59:04 +0430
Message-ID: <CA+d13g3OB8+b-Hyz9thwpr62=mhM4-nT5WsWdAp5-E53ufRotg@mail.gmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Cc: 111attendees@ietf.org, tools-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007a3ebd05c89b190f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/tZbpoaqvISYjjhPZ10GSJBpdLKU>
Subject: Re: [111attendees] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:29:33 -0000

--0000000000007a3ebd05c89b190f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=D8=A8=D9=87 =DB=B3=
=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=DB=B2=DB=B1=D8=8C=
=E2=80=8F =DB=B1:=DB=B3=DB=B3 Bron Gondwana <brong@fastmailteam.com>
=D9=86=D9=88=D8=B4=D8=AA:

> Ooh, we're going a full "suggestions for meetecho" thread?  I'd like to
> propose some things!
>
> *that we replace the current "raise hands" tool:*
>
> *... *which is based on an expired draft which isn't going to be
> refreshed - with a better tool that allows the chairs to:
>
> a) label each option
> b) have more than 2 options (max 9 maybe)
> c) select between "choose one" and "choose N" modes (checkbox vs radio
> button)
>
> ... and which appears IN PLACE of the slides when enabled, so that meetin=
g
> participants don't have to navigate to a separate tab to interact.
>
> More generally, it's too easy for some participants to be lost on
> different tabs where they can't see the slides.  The multiple views where
> you can see individual talking heads in more detail are not actually
> valuable I don't think - if slides are showing they should be the bulk of
> the screen because they need to be read - and if a poll is showing then f=
or
> sure it should be taking over the screen.
>
> *a "temporary mute" mode that keeps the audio stream open:*
>
> This is still an issue for me.  I often mute myself while chairing so I
> can take notes without my keyboard sound interrupting the chat - but it
> means that I can't easily respond to somebody because the rejigging of th=
e
> audio channel not only creates a hiccup in the incoming audio feed which
> means I might miss something someone says, but it also creates enough of =
a
> delay that by the time I could have responded the other party's mental
> state has moved on.
>
> Timing is really important in conversation and we're already fighting wit=
h
> the quarter second delay imposed by the size of the planet.  Additional
> delay makes it unwieldy.
>
> *allow multiple connections by the same person to the same session:*
>
> I have multiple times wanted to switch device temporarily - from my
> desktop computer to a phone / ipad so I can temporarily move to another
> location while continuing to follow a meeting.  Multiple connection suppo=
rt
> would mean I could switch over without a break.
>
> Sure it could be abused by people "sharing" a login, but that would be
> pretty obvious if both parties tried to participate, and given that we
> allow fee waivers anyway, it's unlikely to be abused significantly.  Sure
> there are Jabber naming issues, but we can avoid that by giving each jabb=
er
> name with a serial number (which I believe already happens now?)
>
> ...
>
> I've already written these up separately in the past, but:
>
> *information about who is speaking in the same place as video feeds*
>
> See my previous email :)  Basically the "participant list" should just be
> an ordered list of participants and only needs to be switched to when
> seeing who is in the call or opening an individual message to them (and
> people don't get moved out of order when they're sending something).  The
> "who is sending something" list should be all together with the video, an=
d
> chairs pinned even if they're sending nothing right now.
>
> Along with visual indicators of "currently sending audio" on people so we
> know who of those with their audio channel open are currently speaking,
> this makes it easier to look in one place to see the source of all sound,
> and eyes can generally flit between the right hand side (video and audio
> indicators) and the slides, without needing to also track via the
> participant list.
>
> *flexible "assign chair"**:*
>
> This one hasn't come up in practice, but the chairs for meetings are
> pre-assigned from datatracker.  It would be great for ADs and the meetech=
o
> reps in each meeting to be able to upgrade anybody to a chair role or
> remove a chair role with a simple click.
>
> In real rooms, anyone can go sit in the chair at the front of the room,
> and it's not abused because of social convention.  I believe that we can
> map that to this virtual space and still have it work sensibly.  People
> won't take the chair unless there's a legitimate reason to do it, and so
> long as it's logged - if someone does consistently abuse it we have
> processes to eject them from the IETF for misbehaviour.
>
> This has become less important with the ability for individuals to turn o=
n
> both audio and video themselves, so the chair is going less busywork just
> approving access, but it would be good to make it possible for someone el=
se
> to step into the chair if the regular chairs are unable to attend or lose
> network, rather than making the meeting less able to run.
>
> Bron.
>
> On Sat, Jul 31, 2021, at 05:38, Meetecho IETF support wrote:
>
> All,
>
> chiming in just to say that we at Meetecho appreciate and value your
> feedback. We'll definitely take it into account when developing the
> future releases of the platform. We'll provide comments on the points
> raised as soon as we get the chance to parse them, i.e., when the
> meeting is over.
>
> Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to header
> to that list as well, as that's the right place to discuss enhancements
> and provide feedback that would be easier for us to collect.
>
> Best,
> Alessandro
>
> Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto:
> > I should have changed the Subject a LONG time ago! But this thread has
> > morphed into helpful observations and suggestions, so, if I might add a
> > couple of things ...
> >
> > I agree that Meetecho has been improving (and just for fun, the Meetech=
o
> > guys were participants in the MEDIACTL session I was co-chairing in
> > Hiroshima at IETF 76 in November 2009, and they roped in a team member
> > from Italy during the discussion using whatever the toolset was back
> > then, so many of you have no idea how MUCH they've improved =F0=9F=98=
=80).
> >
> > I see that we've already mentioned detaching the chat window, and
> > usually I remember that we can detach the chat by Tuesday of each IETF
> > meeting week at the latest, which is almost certainly a result of not
> > having THAT much experience with Meetecho during the four months betwee=
n
> > meetings. Now that we can use Meetecho for interim meetings, that will
> > help me remember more clearly, so good there, too.
> >
> > The one thing I've noticed this week is how difficult it is to figure
> > out who is speaking if they aren't sending video, and there's a long
> > list of people in the queue. The suggestion to move the speakers above
> > the queue would improve that, and so would simply displaying the active
> > speaker names in the screen space where their video would have gone, if
> > the person had been sending video.One reason that matters, is that it's
> > helpful for everyone to get the speaker's name right in the minutes.
> > That's not just for new attendees, I'm starting to forget what people
> > sound like, unless I'm talking to them regularly, or they have a very
> > distinctive speech pattern, so I've definitely depending on seeing name=
s
> > when I'm taking minutes. .
> >
> > The one thing I was thinking about, as I read through this thread, was
> > that we are kinda *not *talking about what the IETF thinks the target
> > audience for our conferencing tool is.
> >
> >   * For probably the last couple of IETFs, I have a GREAT setup for
> >     remote participation (my laptop screen, plus two 25-inch monitors).
> >     But I do have tiled windows on all three screens.
> >   * If we think people who can't throw a few hundred dollars at monitor
> >     screens are part of our target audience, that's worth noting.
> >   * If we think we're going to have hybrid meetings, in at least some
> >     scenarios, it's going to be good to use Meetecho in the conference
> >     rooms (especially if we need to be distancing, so more spread out,
> >     front to back in the conference rooms).
> >   * Even if we aren't doing hybrid meetings, I've participated in some
> >     working group meetings from my hotel room, but I wasn't tryng to
> >     co-chair a meeting, or even to present at a meeting.
> >   * When Michael Richardson and I talked to the Cellar working group
> >     participants about switching to Meetecho for our (monthy) interims,
> >     the first question we got was, "is there an iOS/Adroid client?" I
> >     haven't checked Meetecho on my phone in years, but I'd bet offhand
> >     that (1) it would work, but (2) it might not be as easy to use as
> >     some other conferencing systems, on those devices. Do people have
> >     experience with that?
> >
> > I'll let you folks continue to share these positive observations and
> > proposals. Make Good Choices, of course.
> >
> > Best,
> >
> > Spencer
> >
> > On Thu, Jul 29, 2021 at 6:15 PM Jay Daley <jay@ietf.org
> > <mailto:jay@ietf.org>> wrote:
> >
> >     Thanks Bron.  Personally I think that=E2=80=99s a great usability a=
djustment
> >     and will forward to the Meetecho team for them to consider.
> >
> >     Jay
> >
> >      > On 30/07/2021, at 10:58 AM, Bron Gondwana <brong@fastmailteam.co=
m
> >     <mailto:brong@fastmailteam.com>> wrote:
> >      >
> >      > On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:
> >      >> No we have absolutely not pushed Meetecho into being "just a
> >     contractor", they are a valued partner and we work very well
> >     together.  If you have any doubts about that then ask them directly=
.
> >      >>
> >      >> It is disappointing that you have escalated a personal concern
> >     that you have with our services into such a strong criticism when
> >     that is entirely unsupported by any evidence.
> >      >
> >      > Jay, I agree with your sentiment here - this attitude to Meetech=
o
> >     is counterproductive.  They've done great work for the last couple
> >     of IETFs and the experience is improving each time.  I have
> >     particularly appreciated the embedded slide management, and I'm sur=
e
> >     that will be even better next time too.
> >      >
> >      > Regarding the specific interface issues that remain, I do think
> >     there's a question of "where do we propose improvements in a way
> >     that will be noticed"?  I've seen the suggestion made very many
> >     times that the "speaker" area (where the video shows) should have
> >     additional lines for each person sending anything, rather than that
> >     information being at the top of the participant list.  This is much
> >     more like the experience with other chat systems, for example Zoom
> >     shows either a photo or a blank item for somebody who isn't
> >     currently sending video, but they're otherwise treated "the same" a=
s
> >     a person sending video in terms of real-estate and where to look fo=
r
> >     their presence by default.
> >      >
> >      > Right now with meetecho, my eyes are normally at the video are
> >     when people are speaking, but if a non-video person is speaking I
> >     need to look across to the other side of the screen to see the audi=
o
> >     indication.
> >      >
> >      > And as was also suggested in this thread, you can't scroll the
> >     participant list to find someone to chat to, because they jump to
> >     the top when they are sending, then back to alphabetical position.
> >     This is also a usability pain.  Separating "the list of
> >     participants" (which wouldn't move about) and "the list of people
> >     sending something" with the video and audio indications being
> >     together in one place would be a significant improvement.  And as a=
n
> >     additional benefit, when you're looking at the chat window, you
> >     would still be able to see all the details of who is sending
> >     (including yourself - if you're sending then the indicator of your
> >     own audio should be the same as the indicator of everyone else's
> >     audio, rather than being in yet a third location up under your own
> >     name).
> >      >
> >      > <image.png>
> >      > So those two names would appear in the right hand side, and also
> >     still have their name in the participant list, and the video feeds
> >     would each have a "here's what's being sent".  Chairs would always
> >     have a presence on the right, with whatever they were currently
> >     sending - and the "participants" tab would only have the list of
> >     participants, and not be a place you needed to go to see activity,
> >     so you could mostly keep the chat tab open.
> >      >
> >      > Bron.
> >      >
> >      >
> >      > --
> >      >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >      > brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> >      >
> >      >
> >      > --
> >      > 111attendees mailing list
> >      > 111attendees@ietf.org <mailto:111attendees@ietf.org>
> >      > https://www.ietf.org/mailman/listinfo/111attendees
> >     <https://www.ietf.org/mailman/listinfo/111attendees>
> >
> >     --
> >     Jay Daley
> >     IETF Executive Director
> >     jay@ietf.org <mailto:jay@ietf.org>
> >
> >     --
> >     111attendees mailing list
> >     111attendees@ietf.org <mailto:111attendees@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/111attendees
> >     <https://www.ietf.org/mailman/listinfo/111attendees>
> >
> >
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

--0000000000007a3ebd05c89b190f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">=D8=AF=D8=B1 =D8=AA=D8=A7=D8=B1=DB=8C=D8=AE =D8=B4=D9=86=
=D8=A8=D9=87 =DB=B3=DB=B1 =DA=98=D9=88=D8=A6=DB=8C=D9=87=D9=94 =DB=B2=DB=B0=
=DB=B2=DB=B1=D8=8C=E2=80=8F =DB=B1:=DB=B3=DB=B3 Bron Gondwana &lt;<a href=
=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a>&gt; =D9=86=D9=
=88=D8=B4=D8=AA:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u><div><div s=
tyle=3D"font-family:Arial">Ooh, we&#39;re going a full &quot;suggestions fo=
r meetecho&quot; thread?=C2=A0 I&#39;d like to propose some things!<br></di=
v><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:Aria=
l"><b>that we replace the current &quot;raise hands&quot; tool:</b><br></di=
v><div style=3D"font-family:Arial"><br></div><div style=3D"font-family:Aria=
l"><b>... </b>which is based on an expired draft which isn&#39;t going to b=
e refreshed - with a better tool that allows the chairs to:<br></div><div s=
tyle=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">a) la=
bel each option<br></div><div style=3D"font-family:Arial">b) have more than=
 2 options (max 9 maybe)<br></div><div style=3D"font-family:Arial">c) selec=
t between &quot;choose one&quot; and &quot;choose N&quot; modes (checkbox v=
s radio button)<br></div><div style=3D"font-family:Arial"><br></div><div st=
yle=3D"font-family:Arial">... and which appears IN PLACE of the slides when=
 enabled, so that meeting participants don&#39;t have to navigate to a sepa=
rate tab to interact.=C2=A0<br></div><div style=3D"font-family:Arial"><br><=
/div><div style=3D"font-family:Arial">More generally, it&#39;s too easy for=
 some participants to be lost on different tabs where they can&#39;t see th=
e slides.=C2=A0 The multiple views where you can see individual talking hea=
ds in more detail are not actually valuable I don&#39;t think - if slides a=
re showing they should be the bulk of the screen because they need to be re=
ad - and if a poll is showing then for sure it should be taking over the sc=
reen.<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"fon=
t-family:Arial"><b>a &quot;temporary mute&quot; mode that keeps the audio s=
tream open:</b><br></div><div style=3D"font-family:Arial"><br></div><div st=
yle=3D"font-family:Arial">This is still an issue for me.=C2=A0 I often mute=
 myself while chairing so I can take notes without my keyboard sound interr=
upting the chat - but it means that I can&#39;t easily respond to somebody =
because the rejigging of the audio channel not only creates a hiccup in the=
 incoming audio feed which means I might miss something someone says, but i=
t also creates enough of a delay that by the time I could have responded th=
e other party&#39;s mental state has moved on.<br></div><div style=3D"font-=
family:Arial"><br></div><div style=3D"font-family:Arial">Timing is really i=
mportant in conversation and we&#39;re already fighting with the quarter se=
cond delay imposed by the size of the planet.=C2=A0 Additional delay makes =
it unwieldy.<br></div><div style=3D"font-family:Arial"><br></div><div style=
=3D"font-family:Arial"><b>allow multiple connections by the same person to =
the same session:</b><br></div><div style=3D"font-family:Arial"><br></div><=
div style=3D"font-family:Arial">I have multiple times wanted to switch devi=
ce temporarily - from my desktop computer to a phone / ipad so I can tempor=
arily move to another location while continuing to follow a meeting.=C2=A0 =
Multiple connection support would mean I could switch over without a break.=
<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font-fam=
ily:Arial">Sure it could be abused by people &quot;sharing&quot; a login, b=
ut that would be pretty obvious if both parties tried to participate, and g=
iven that we allow fee waivers anyway, it&#39;s unlikely to be abused signi=
ficantly.=C2=A0 Sure there are Jabber naming issues, but we can avoid that =
by giving each jabber name with a serial number (which I believe already ha=
ppens now?)<br></div><div style=3D"font-family:Arial"><br></div><div style=
=3D"font-family:Arial">...<br></div><div style=3D"font-family:Arial"><br></=
div><div style=3D"font-family:Arial">I&#39;ve already written these up sepa=
rately in the past, but:<br></div><div style=3D"font-family:Arial"><br></di=
v><div style=3D"font-family:Arial"><b>information about who is speaking in =
the same place as video feeds</b><br></div><div style=3D"font-family:Arial"=
><br></div><div style=3D"font-family:Arial">See my previous email :)=C2=A0 =
Basically the &quot;participant list&quot; should just be an ordered list o=
f participants and only needs to be switched to when seeing who is in the c=
all or opening an individual message to them (and people don&#39;t get move=
d out of order when they&#39;re sending something).=C2=A0 The &quot;who is =
sending something&quot; list should be all together with the video, and cha=
irs pinned even if they&#39;re sending nothing right now.<br></div><div sty=
le=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">Along w=
ith visual indicators of &quot;currently sending audio&quot; on people so w=
e know who of those with their audio channel open are currently speaking, t=
his makes it easier to look in one place to see the source of all sound, an=
d eyes can generally flit between the right hand side (video and audio indi=
cators) and the slides, without needing to also track via the participant l=
ist.<br></div><div style=3D"font-family:Arial"><br></div><div style=3D"font=
-family:Arial"><b>flexible &quot;assign chair&quot;</b><b>:</b><br></div><d=
iv style=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">T=
his one hasn&#39;t come up in practice, but the chairs for meetings are pre=
-assigned from datatracker.=C2=A0 It would be great for ADs and the meetech=
o reps in each meeting to be able to upgrade anybody to a chair role or rem=
ove a chair role with a simple click.<br></div><div style=3D"font-family:Ar=
ial"><br></div><div style=3D"font-family:Arial">In real rooms, anyone can g=
o sit in the chair at the front of the room, and it&#39;s not abused becaus=
e of social convention.=C2=A0 I believe that we can map that to this virtua=
l space and still have it work sensibly.=C2=A0 People won&#39;t take the ch=
air unless there&#39;s a legitimate reason to do it, and so long as it&#39;=
s logged - if someone does consistently abuse it we have processes to eject=
 them from the IETF for misbehaviour.<br></div><div style=3D"font-family:Ar=
ial"><br></div><div style=3D"font-family:Arial">This has become less import=
ant with the ability for individuals to turn on both audio and video themse=
lves, so the chair is going less busywork just approving access, but it wou=
ld be good to make it possible for someone else to step into the chair if t=
he regular chairs are unable to attend or lose network, rather than making =
the meeting less able to run.<br></div><div style=3D"font-family:Arial"><br=
></div><div style=3D"font-family:Arial">Bron.<br></div><div style=3D"font-f=
amily:Arial"><br></div><div>On Sat, Jul 31, 2021, at 05:38, Meetecho IETF s=
upport wrote:<br></div><blockquote type=3D"cite" id=3D"m_-23799281633664165=
99qt"><div style=3D"font-family:Arial">All,<br></div><div style=3D"font-fam=
ily:Arial"><br></div><div style=3D"font-family:Arial">chiming in just to sa=
y that we at Meetecho appreciate and value your=C2=A0<br></div><div style=
=3D"font-family:Arial">feedback. We&#39;ll definitely take it into account =
when developing the=C2=A0<br></div><div style=3D"font-family:Arial">future =
releases of the platform. We&#39;ll provide comments on the points=C2=A0<br=
></div><div style=3D"font-family:Arial">raised as soon as we get the chance=
 to parse them, i.e., when the=C2=A0<br></div><div style=3D"font-family:Ari=
al">meeting is over.<br></div><div style=3D"font-family:Arial"><br></div><d=
iv style=3D"font-family:Arial">Also, I&#39;m cc&#39;ing=C2=A0<a href=3D"mai=
lto:tools-discuss@ietf.org" target=3D"_blank" rel=3D"noreferrer">tools-disc=
uss@ietf.org</a> and setting the reply-to header=C2=A0<br></div><div style=
=3D"font-family:Arial">to that list as well, as that&#39;s the right place =
to discuss enhancements=C2=A0<br></div><div style=3D"font-family:Arial">and=
 provide feedback that would be easier for us to collect.<br></div><div sty=
le=3D"font-family:Arial"><br></div><div style=3D"font-family:Arial">Best,<b=
r></div><div style=3D"font-family:Arial">Alessandro<br></div><div style=3D"=
font-family:Arial"><br></div><div style=3D"font-family:Arial">Il 30/07/21 1=
9:37, Spencer Dawkins at IETF ha scritto:<br></div><div style=3D"font-famil=
y:Arial">&gt; I should have changed the Subject a LONG time ago! But this t=
hread has=C2=A0<br></div><div style=3D"font-family:Arial">&gt; morphed into=
 helpful observations and suggestions, so, if I might add a=C2=A0<br></div>=
<div style=3D"font-family:Arial">&gt; couple of things ...<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Ari=
al">&gt; I agree that Meetecho has been improving (and just for fun, the Me=
etecho=C2=A0<br></div><div style=3D"font-family:Arial">&gt; guys were parti=
cipants in the MEDIACTL session I was co-chairing in=C2=A0<br></div><div st=
yle=3D"font-family:Arial">&gt; Hiroshima at IETF 76 in November 2009, and t=
hey roped in a team member=C2=A0<br></div><div style=3D"font-family:Arial">=
&gt; from Italy during the discussion using whatever the toolset was back=
=C2=A0<br></div><div style=3D"font-family:Arial">&gt; then, so many of you =
have no idea how MUCH they&#39;ve improved=C2=A0=F0=9F=98=80).<br></div><di=
v style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family=
:Arial">&gt; I see that we&#39;ve already mentioned detaching the chat wind=
ow, and=C2=A0<br></div><div style=3D"font-family:Arial">&gt; usually I reme=
mber that we can detach the chat by Tuesday of each IETF=C2=A0<br></div><di=
v style=3D"font-family:Arial">&gt; meeting week at the latest, which is alm=
ost certainly a result of not=C2=A0<br></div><div style=3D"font-family:Aria=
l">&gt; having THAT much experience with=C2=A0Meetecho during the four mont=
hs between=C2=A0<br></div><div style=3D"font-family:Arial">&gt; meetings. N=
ow that we can use Meetecho for interim meetings, that will=C2=A0<br></div>=
<div style=3D"font-family:Arial">&gt; help me remember more clearly, so goo=
d there, too.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div=
><div style=3D"font-family:Arial">&gt; The one thing I&#39;ve noticed this =
week is how difficult it is to figure=C2=A0<br></div><div style=3D"font-fam=
ily:Arial">&gt; out who is speaking if they aren&#39;t sending video, and t=
here&#39;s a long=C2=A0<br></div><div style=3D"font-family:Arial">&gt; list=
 of people in the queue. The suggestion to move the speakers above=C2=A0<br=
></div><div style=3D"font-family:Arial">&gt; the queue would improve that, =
and so would simply displaying the active=C2=A0<br></div><div style=3D"font=
-family:Arial">&gt; speaker names in the screen space where their video wou=
ld have gone, if=C2=A0<br></div><div style=3D"font-family:Arial">&gt; the p=
erson had been sending video.One reason that matters, is that it&#39;s=C2=
=A0<br></div><div style=3D"font-family:Arial">&gt; helpful for everyone to =
get the speaker&#39;s name right in the minutes.=C2=A0<br></div><div style=
=3D"font-family:Arial">&gt; That&#39;s not just for new attendees, I&#39;m =
starting to forget what people=C2=A0<br></div><div style=3D"font-family:Ari=
al">&gt; sound like, unless I&#39;m talking to them regularly, or they have=
 a very=C2=A0<br></div><div style=3D"font-family:Arial">&gt; distinctive sp=
eech pattern, so I&#39;ve definitely depending on seeing names=C2=A0<br></d=
iv><div style=3D"font-family:Arial">&gt; when I&#39;m taking minutes. .<br>=
</div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"fo=
nt-family:Arial">&gt; The one thing I was thinking about, as I read through=
 this thread, was=C2=A0<br></div><div style=3D"font-family:Arial">&gt; that=
 we are kinda *not *talking about what the IETF thinks the target=C2=A0<br>=
</div><div style=3D"font-family:Arial">&gt; audience for our conferencing t=
ool is.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div =
style=3D"font-family:Arial">&gt;=C2=A0=C2=A0 * For probably the last couple=
 of IETFs, I have a GREAT setup for<br></div><div style=3D"font-family:Aria=
l">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 remote participation (my laptop screen, plu=
s two 25-inch monitors).<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0 But I do have tiled windows on all three screens.<br>=
</div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0 * If we think peopl=
e who can&#39;t throw a few hundred dollars at monitor<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 screens are part of our=
 target audience, that&#39;s worth noting.<br></div><div style=3D"font-fami=
ly:Arial">&gt;=C2=A0=C2=A0 * If we think we&#39;re going to have hybrid mee=
tings, in at least some<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0 scenarios, it&#39;s going to be good to use Meetecho =
in the conference<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 rooms (especially if we need to be distancing, so more spre=
ad out,<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 front to back in the conference rooms).<br></div><div style=3D"font-fam=
ily:Arial">&gt;=C2=A0=C2=A0 * Even if we aren&#39;t doing hybrid meetings, =
I&#39;ve participated in some<br></div><div style=3D"font-family:Arial">&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0 working group meetings from my hotel room, but I =
wasn&#39;t tryng to<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 co-chair a meeting, or even to present at a meeting.<br></d=
iv><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0 * When Michael Richard=
son and I talked to the Cellar working group<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 participants about switching to Me=
etecho for our (monthy) interims,<br></div><div style=3D"font-family:Arial"=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0 the first question we got was, &quot;is there=
 an iOS/Adroid client?&quot; I<br></div><div style=3D"font-family:Arial">&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0 haven&#39;t checked Meetecho on my phone in year=
s, but I&#39;d bet offhand<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 that (1) it would work, but (2) it might not be as=
 easy to use as<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 some other conferencing systems, on those devices. Do people h=
ave<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 =
experience with that?<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<=
br></div><div style=3D"font-family:Arial">&gt; I&#39;ll let you folks conti=
nue to share these positive observations and=C2=A0<br></div><div style=3D"f=
ont-family:Arial">&gt; proposals. Make Good Choices, of course.<br></div><d=
iv style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-famil=
y:Arial">&gt; Best,<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br=
></div><div style=3D"font-family:Arial">&gt; Spencer<br></div><div style=3D=
"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&g=
t; On Thu, Jul 29, 2021 at 6:15 PM Jay Daley &lt;<a href=3D"mailto:jay@ietf=
.org" target=3D"_blank" rel=3D"noreferrer">jay@ietf.org</a>=C2=A0<br></div>=
<div style=3D"font-family:Arial">&gt; &lt;mailto:<a href=3D"mailto:jay@ietf=
.org" target=3D"_blank" rel=3D"noreferrer">jay@ietf.org</a>&gt;&gt; wrote:<=
br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D=
"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 Thanks Bron.=C2=A0 Persona=
lly I think that=E2=80=99s a great usability adjustment<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 and will forward to the=
 Meetecho team for them to consider.<br></div><div style=3D"font-family:Ari=
al">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 Jay<br></div><div style=3D"font-family:Arial">&gt;=C2=A0<br></=
div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt=
; On 30/07/2021, at 10:58 AM, Bron Gondwana &lt;<a href=3D"mailto:brong@fas=
tmailteam.com" target=3D"_blank" rel=3D"noreferrer">brong@fastmailteam.com<=
/a><br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 =
&lt;mailto:<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank" rel=
=3D"noreferrer">brong@fastmailteam.com</a>&gt;&gt; wrote:<br></div><div sty=
le=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><=
div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; On =
Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:<br></div><div style=3D"font-f=
amily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;&gt; No we have absolut=
ely not pushed Meetecho into being &quot;just a<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 contractor&quot;, they are a va=
lued partner and we work very well<br></div><div style=3D"font-family:Arial=
">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 together.=C2=A0 If you have any doubts about=
 that then ask them directly.<br></div><div style=3D"font-family:Arial">&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;&gt;<br></div><div style=3D"font-family=
:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;&gt; It is disappointing tha=
t you have escalated a personal concern<br></div><div style=3D"font-family:=
Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that you have with our services into su=
ch a strong criticism when<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0 that is entirely unsupported by any evidence.<br><=
/div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &g=
t;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &gt; Jay, I agree with your sentiment here - this attitude to Meetec=
ho<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 i=
s counterproductive.=C2=A0 They&#39;ve done great work for the last couple<=
br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 of I=
ETFs and the experience is improving each time.=C2=A0 I have<br></div><div =
style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 particularly appre=
ciated the embedded slide management, and I&#39;m sure<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 that will be even bette=
r next time too.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Regarding the specific interface issues th=
at remain, I do think<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 there&#39;s a question of &quot;where do we propose impr=
ovements in a way<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 that will be noticed&quot;?=C2=A0 I&#39;ve seen the suggest=
ion made very many<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 times that the &quot;speaker&quot; area (where the video sh=
ows) should have<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 additional lines for each person sending anything, rather than=
 that<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0 information being at the top of the participant list.=C2=A0 This is muc=
h<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 mo=
re like the experience with other chat systems, for example Zoom<br></div><=
div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 shows either a=
 photo or a blank item for somebody who isn&#39;t<br></div><div style=3D"fo=
nt-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 currently sending video, but =
they&#39;re otherwise treated &quot;the same&quot; as<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 a person sending video =
in terms of real-estate and where to look for<br></div><div style=3D"font-f=
amily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 their presence by default.<br></d=
iv><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=
<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 &gt; Right now with meetecho, my eyes are normally at the video are<br>=
</div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 when pe=
ople are speaking, but if a non-video person is speaking I<br></div><div st=
yle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 need to look across =
to the other side of the screen to see the audio<br></div><div style=3D"fon=
t-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 indication.<br></div><div styl=
e=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><d=
iv style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; And =
as was also suggested in this thread, you can&#39;t scroll the<br></div><di=
v style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 participant list=
 to find someone to chat to, because they jump to<br></div><div style=3D"fo=
nt-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 the top when they are sending=
, then back to alphabetical position.=C2=A0<br></div><div style=3D"font-fam=
ily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 This is also a usability pain.=C2=
=A0 Separating &quot;the list of<br></div><div style=3D"font-family:Arial">=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0 participants&quot; (which wouldn&#39;t move ab=
out) and &quot;the list of people<br></div><div style=3D"font-family:Arial"=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0 sending something&quot; with the video and au=
dio indications being<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0 together in one place would be a significant improvement=
.=C2=A0 And as an<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 additional benefit, when you&#39;re looking at the chat win=
dow, you<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0 would still be able to see all the details of who is sending<br></di=
v><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 (including =
yourself - if you&#39;re sending then the indicator of your<br></div><div s=
tyle=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 own audio should be=
 the same as the indicator of everyone else&#39;s<br></div><div style=3D"fo=
nt-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 audio, rather than being in y=
et a third location up under your own<br></div><div style=3D"font-family:Ar=
ial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 name).<br></div><div style=3D"font-family=
:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; &lt;image.png&gt;<br=
></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&gt; So those two names would appear in the right hand side, and also<br></=
div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 still hav=
e their name in the participant list, and the video feeds<br></div><div sty=
le=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 would each have a &qu=
ot;here&#39;s what&#39;s being sent&quot;.=C2=A0 Chairs would always<br></d=
iv><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 have a pre=
sence on the right, with whatever they were currently<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 sending - and the &quot=
;participants&quot; tab would only have the list of<br></div><div style=3D"=
font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 participants, and not be a =
place you needed to go to see activity,<br></div><div style=3D"font-family:=
Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 so you could mostly keep the chat tab o=
pen.<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &gt;<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &gt; Bron.<br></div><div style=3D"font-family:Arial">&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-family:Aria=
l">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=3D"font-fami=
ly:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; --<br></div><div style=3D=
"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=C2=A0 =C2=A0Bro=
n Gondwana, CEO, Fastmail Pty Ltd<br></div><div style=3D"font-family:Arial"=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=C2=A0<a href=3D"mailto:brong@fastm=
ailteam.com" target=3D"_blank" rel=3D"noreferrer">brong@fastmailteam.com</a=
> &lt;mailto:<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank" re=
l=3D"noreferrer">brong@fastmailteam.com</a>&gt;<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;<br></div><di=
v style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt; --<br=
></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&gt; 111attendees mailing list<br></div><div style=3D"font-family:Arial">&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=C2=A0<a href=3D"mailto:111attendees@i=
etf.org" target=3D"_blank" rel=3D"noreferrer">111attendees@ietf.org</a> &lt=
;mailto:<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"n=
oreferrer">111attendees@ietf.org</a>&gt;<br></div><div style=3D"font-family=
:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &gt;=C2=A0<a href=3D"https://www=
.ietf.org/mailman/listinfo/111attendees" target=3D"_blank" rel=3D"noreferre=
r">https://www.ietf.org/mailman/listinfo/111attendees</a><br></div><div sty=
le=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &lt;<a href=3D"https:=
//www.ietf.org/mailman/listinfo/111attendees" target=3D"_blank" rel=3D"nore=
ferrer">https://www.ietf.org/mailman/listinfo/111attendees</a>&gt;<br></div=
><div style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-fa=
mily:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 --=C2=A0<br></div><div style=3D"fo=
nt-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 Jay Daley<br></div><div style=
=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 IETF Executive Director=
<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0<a href=3D"mailto:jay@ietf.org" target=3D"_blank" rel=3D"noreferrer">jay=
@ietf.org</a> &lt;mailto:<a href=3D"mailto:jay@ietf.org" target=3D"_blank" =
rel=3D"noreferrer">jay@ietf.org</a>&gt;<br></div><div style=3D"font-family:=
Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0 --=C2=A0<br></div><div style=3D"font-family:Arial">&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0 111attendees mailing list<br></div><div style=3D"font=
-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"mailto:111atten=
dees@ietf.org" target=3D"_blank" rel=3D"noreferrer">111attendees@ietf.org</=
a> &lt;mailto:<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" re=
l=3D"noreferrer">111attendees@ietf.org</a>&gt;<br></div><div style=3D"font-=
family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"https://www.ietf=
.org/mailman/listinfo/111attendees" target=3D"_blank" rel=3D"noreferrer">ht=
tps://www.ietf.org/mailman/listinfo/111attendees</a><br></div><div style=3D=
"font-family:Arial">&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &lt;<a href=3D"https://www=
.ietf.org/mailman/listinfo/111attendees" target=3D"_blank" rel=3D"noreferre=
r">https://www.ietf.org/mailman/listinfo/111attendees</a>&gt;<br></div><div=
 style=3D"font-family:Arial">&gt;=C2=A0<br></div><div style=3D"font-family:=
Arial">&gt;=C2=A0<br></div><div style=3D"font-family:Arial"><br></div><div =
style=3D"font-family:Arial">--=C2=A0<br></div><div style=3D"font-family:Ari=
al">111attendees mailing list<br></div><div style=3D"font-family:Arial"><a =
href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferrer">=
111attendees@ietf.org</a><br></div><div style=3D"font-family:Arial"><a href=
=3D"https://www.ietf.org/mailman/listinfo/111attendees" target=3D"_blank" r=
el=3D"noreferrer">https://www.ietf.org/mailman/listinfo/111attendees</a><br=
></div><div style=3D"font-family:Arial"><br></div></blockquote><div style=
=3D"font-family:Arial"><br></div><div id=3D"m_-2379928163366416599sig566294=
17"><div>--<br></div><div>=C2=A0 Bron Gondwana, CEO, Fastmail Pty Ltd<br></=
div><div>=C2=A0 <a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank"=
 rel=3D"noreferrer">brong@fastmailteam.com</a><br></div><div><br></div></di=
v><div style=3D"font-family:Arial"><br></div></div>-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank" rel=3D"noreferre=
r">111attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/1=
11attendees</a><br>
</blockquote></div>

--0000000000007a3ebd05c89b190f--


From nobody Tue Aug  3 06:46:22 2021
Return-Path: <ietf@meetecho.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86E513A2480 for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 06:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
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 MJzzJO_ceKIw for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 06:46:15 -0700 (PDT)
Received: from smtpcmd10102.aruba.it (smtpcmd10102.aruba.it [62.149.156.102]) by ietfa.amsl.com (Postfix) with ESMTP id 05FEE3A247D for <111attendees@ietf.org>; Tue,  3 Aug 2021 06:46:14 -0700 (PDT)
Received: from [192.168.1.62] ([93.40.13.11]) by Aruba Outgoing Smtp  with ESMTPSA id AukFm6TFVnyXHAukFmTNE8; Tue, 03 Aug 2021 15:46:12 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1627998372; bh=Hc2/f7ge7K2UoPGtqgS+PnA3P8V1UwqxF5kPwPdF5gI=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=RaEuD6ALLwKHE2ZrDylCYmQddFbALLxVEctuYf+m/LlGj5vPyFvxLUdHKxtmHk+G+ Kh+vY6SfkxrKLdok4ys84Y/VawMCegApIDvxtezviU8EHlQcYQYOxAGso2QA84VIeP qLY4Oc0ttBUSG111wlJFViq/QvQqHNzzznSbGyyob6sQt/r8+1vwyT8dDjuEnJJHiL b8K/FF8ZNguYb1JaSwc9CRxGdAzQgcPqmk1MMhTikKNrM0hdzMRoF/LPIa/gOucZhJ gqNELnk7YooqjyxCOQ+NDCNozzo9AFSNb81uYrMJWqULbfMdFEc8YEzmScgXiBbhSk KPqkPw8txU56Q==
To: Bron Gondwana <brong@fastmailteam.com>, tools-discuss@ietf.org
Cc: 111attendees@ietf.org
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <da253a5f-9e1a-afc2-5ba7-1412ff597f40@meetecho.com>
Date: Tue, 3 Aug 2021 15:46:11 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfILMjM5tXHGIc0B8W4aYeJ7zHE/Vzg8iDI0hxuatmNOwgumcR8+ncxJnC+OAPntfbvSKtcvcATjB7PzoMVEEfFIforwAYEaGJsywflnAAs1Y4lX46X7j Z0ulp6t0SPtYotMYyVvGDOhApfmTIPoft/t/HXxQMorZTytC2B2XN7YLd3CvRNEc6sdPYgzhy7fzCPMZsLmGTMA+jm+Xq1cqYvDhEcbnpTJ1ccL5DQi871Qa
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/RAnAWQIFKpRv7Igg60arWlxqOI4>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 13:46:21 -0000

Hi Bron,

Il 30/07/21 23:02, Bron Gondwana ha scritto:
> Ooh, we're going a full "suggestions for meetecho" thread?  I'd like to 
> propose some things!
> 
> *that we replace the current "raise hands" tool:*
> 
> *... *which is based on an expired draft which isn't going to be 
> refreshed - with a better tool that allows the chairs to:
> 
> a) label each option
> b) have more than 2 options (max 9 maybe)
> c) select between "choose one" and "choose N" modes (checkbox vs radio 
> button)
> 
> ... and which appears IN PLACE of the slides when enabled, so that 
> meeting participants don't have to navigate to a separate tab to interact.

I agree this would improve usability.

> More generally, it's too easy for some participants to be lost on 
> different tabs where they can't see the slides.  The multiple views 
> where you can see individual talking heads in more detail are not 
> actually valuable I don't think - if slides are showing they should be 
> the bulk of the screen because they need to be read - 

This is not always true. As you may have noticed, when a new slide 
deck/screen share is started you are automatically brought to the 
"presentation view", i.e., the one that shows it. But I think you should 
still have the power to manually switch to the "gallery view" at 
anytime. A good example are the open mic sessions during the Plenary: a 
static slide is always up just saying, e.g., "IAB Open Mic", and I 
usually switch to gallery view to focus on the faces answering 
questions. I've seen the same pattern also in several WG meeting 
sessions, where the last slide of a deck is displayed for a long time 
while discussing how to move forward with the draft.

> and if a poll is showing then for sure it should be taking over the screen.

Agreed.

> *a "temporary mute" mode that keeps the audio stream open:*
> 
> This is still an issue for me.  I often mute myself while chairing so I 
> can take notes without my keyboard sound interrupting the chat - but it 
> means that I can't easily respond to somebody because the rejigging of 
> the audio channel not only creates a hiccup in the incoming audio feed 
> which means I might miss something someone says, but it also creates 
> enough of a delay that by the time I could have responded the other 
> party's mental state has moved on.
> 
> Timing is really important in conversation and we're already fighting 
> with the quarter second delay imposed by the size of the planet.  
> Additional delay makes it unwieldy.

Noted. I personally like the idea of a temporary mute mode which just 
stops sending audio on the track without affecting the underlying WebRTC 
PeerConnection. We'll look into that.

> *allow multiple connections by the same person to the same session:*
> 
> I have multiple times wanted to switch device temporarily - from my 
> desktop computer to a phone / ipad so I can temporarily move to another 
> location while continuing to follow a meeting.  Multiple connection 
> support would mean I could switch over without a break.
> 
> Sure it could be abused by people "sharing" a login, but that would be 
> pretty obvious if both parties tried to participate, and given that we 
> allow fee waivers anyway, it's unlikely to be abused significantly.  
> Sure there are Jabber naming issues, but we can avoid that by giving 
> each jabber name with a serial number (which I believe already happens now?)
> 
> ...
> 
> I've already written these up separately in the past, but:
> 
> *information about who is speaking in the same place as video feeds*
> 
> See my previous email :)  Basically the "participant list" should just 
> be an ordered list of participants and only needs to be switched to when 
> seeing who is in the call or opening an individual message to them (and 
> people don't get moved out of order when they're sending something).  
> The "who is sending something" list should be all together with the 
> video, and chairs pinned even if they're sending nothing right now.
> 
> Along with visual indicators of "currently sending audio" on people so 
> we know who of those with their audio channel open are currently 
> speaking, this makes it easier to look in one place to see the source of 
> all sound, and eyes can generally flit between the right hand side 
> (video and audio indicators) and the slides, without needing to also 
> track via the participant list.

I agree that we should make it easier to find who's speaking when they 
have not video turned on.

> *flexible "assign chair"**:*
> 
> This one hasn't come up in practice, but the chairs for meetings are 
> pre-assigned from datatracker.  It would be great for ADs and the 
> meetecho reps in each meeting to be able to upgrade anybody to a chair 
> role or remove a chair role with a simple click.
> 
> In real rooms, anyone can go sit in the chair at the front of the room, 
> and it's not abused because of social convention.  I believe that we can 
> map that to this virtual space and still have it work sensibly.  People 
> won't take the chair unless there's a legitimate reason to do it, and so 
> long as it's logged - if someone does consistently abuse it we have 
> processes to eject them from the IETF for misbehaviour.
> 
> This has become less important with the ability for individuals to turn 
> on both audio and video themselves, so the chair is going less busywork 
> just approving access, but it would be good to make it possible for 
> someone else to step into the chair if the regular chairs are unable to 
> attend or lose network, rather than making the meeting less able to run.

I personally don't agree on this. I think that chairing a WG meeting 
session requires a minimum of preparation in order to be effective, so I 
think it needs to be arranged at least a few hours in advance. In this 
way the acting chairs can be aware of which button to press to, e.g., 
pre-load slide decks, start a poll, manage the queue, etc.. Within such 
minimum preparation there can be the request to add the acting chairs to 
the Datatracker, so that they can be recognized as chairs when they join.

Please note that the Meetecho team already has a button that allows them 
to upgrade/demote roles within a session, so it would be super easy to 
also provide ADs with such powers. I just don't think it's the right 
thing to do: the Datatracker is where roles are stored and retrieved, 
and it's where such roles should be changed (even temporarily) IMO.

Cheers,
Alessandro

> Bron.
> 
> On Sat, Jul 31, 2021, at 05:38, Meetecho IETF support wrote:
>> All,
>>
>> chiming in just to say that we at Meetecho appreciate and value your
>> feedback. We'll definitely take it into account when developing the
>> future releases of the platform. We'll provide comments on the points
>> raised as soon as we get the chance to parse them, i.e., when the
>> meeting is over.
>>
>> Also, I'm cc'ing tools-discuss@ietf.org 
>> <mailto:tools-discuss@ietf.org> and setting the reply-to header
>> to that list as well, as that's the right place to discuss enhancements
>> and provide feedback that would be easier for us to collect.
>>
>> Best,
>> Alessandro
>>
>> Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto:
>> > I should have changed the Subject a LONG time ago! But this thread has
>> > morphed into helpful observations and suggestions, so, if I might add a
>> > couple of things ...
>> >
>> > I agree that Meetecho has been improving (and just for fun, the 
>> Meetecho
>> > guys were participants in the MEDIACTL session I was co-chairing in
>> > Hiroshima at IETF 76 in November 2009, and they roped in a team member
>> > from Italy during the discussion using whatever the toolset was back
>> > then, so many of you have no idea how MUCH they've improved 😀).
>> >
>> > I see that we've already mentioned detaching the chat window, and
>> > usually I remember that we can detach the chat by Tuesday of each IETF
>> > meeting week at the latest, which is almost certainly a result of not
>> > having THAT much experience with Meetecho during the four months 
>> between
>> > meetings. Now that we can use Meetecho for interim meetings, that will
>> > help me remember more clearly, so good there, too.
>> >
>> > The one thing I've noticed this week is how difficult it is to figure
>> > out who is speaking if they aren't sending video, and there's a long
>> > list of people in the queue. The suggestion to move the speakers above
>> > the queue would improve that, and so would simply displaying the active
>> > speaker names in the screen space where their video would have gone, if
>> > the person had been sending video.One reason that matters, is that it's
>> > helpful for everyone to get the speaker's name right in the minutes.
>> > That's not just for new attendees, I'm starting to forget what people
>> > sound like, unless I'm talking to them regularly, or they have a very
>> > distinctive speech pattern, so I've definitely depending on seeing 
>> names
>> > when I'm taking minutes. .
>> >
>> > The one thing I was thinking about, as I read through this thread, was
>> > that we are kinda *not *talking about what the IETF thinks the target
>> > audience for our conferencing tool is.
>> >
>> >   * For probably the last couple of IETFs, I have a GREAT setup for
>> >     remote participation (my laptop screen, plus two 25-inch monitors).
>> >     But I do have tiled windows on all three screens.
>> >   * If we think people who can't throw a few hundred dollars at monitor
>> >     screens are part of our target audience, that's worth noting.
>> >   * If we think we're going to have hybrid meetings, in at least some
>> >     scenarios, it's going to be good to use Meetecho in the conference
>> >     rooms (especially if we need to be distancing, so more spread out,
>> >     front to back in the conference rooms).
>> >   * Even if we aren't doing hybrid meetings, I've participated in some
>> >     working group meetings from my hotel room, but I wasn't tryng to
>> >     co-chair a meeting, or even to present at a meeting.
>> >   * When Michael Richardson and I talked to the Cellar working group
>> >     participants about switching to Meetecho for our (monthy) interims,
>> >     the first question we got was, "is there an iOS/Adroid client?" I
>> >     haven't checked Meetecho on my phone in years, but I'd bet offhand
>> >     that (1) it would work, but (2) it might not be as easy to use as
>> >     some other conferencing systems, on those devices. Do people have
>> >     experience with that?
>> >
>> > I'll let you folks continue to share these positive observations and
>> > proposals. Make Good Choices, of course.
>> >
>> > Best,
>> >
>> > Spencer
>> >
>> > On Thu, Jul 29, 2021 at 6:15 PM Jay Daley <jay@ietf.org 
>> <mailto:jay@ietf.org>
>> > <mailto:jay@ietf.org <mailto:jay@ietf.org>>> wrote:
>> >
>> >     Thanks Bron.  Personally I think that’s a great usability adjustment
>> >     and will forward to the Meetecho team for them to consider.
>> >
>> >     Jay
>> >
>> >      > On 30/07/2021, at 10:58 AM, Bron Gondwana 
>> <brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>> >     <mailto:brong@fastmailteam.com <mailto:brong@fastmailteam.com>>> 
>> wrote:
>> >      >
>> >      > On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:
>> >      >> No we have absolutely not pushed Meetecho into being "just a
>> >     contractor", they are a valued partner and we work very well
>> >     together.  If you have any doubts about that then ask them directly.
>> >      >>
>> >      >> It is disappointing that you have escalated a personal concern
>> >     that you have with our services into such a strong criticism when
>> >     that is entirely unsupported by any evidence.
>> >      >
>> >      > Jay, I agree with your sentiment here - this attitude to Meetecho
>> >     is counterproductive.  They've done great work for the last couple
>> >     of IETFs and the experience is improving each time.  I have
>> >     particularly appreciated the embedded slide management, and I'm sure
>> >     that will be even better next time too.
>> >      >
>> >      > Regarding the specific interface issues that remain, I do think
>> >     there's a question of "where do we propose improvements in a way
>> >     that will be noticed"?  I've seen the suggestion made very many
>> >     times that the "speaker" area (where the video shows) should have
>> >     additional lines for each person sending anything, rather than that
>> >     information being at the top of the participant list.  This is much
>> >     more like the experience with other chat systems, for example Zoom
>> >     shows either a photo or a blank item for somebody who isn't
>> >     currently sending video, but they're otherwise treated "the same" as
>> >     a person sending video in terms of real-estate and where to look for
>> >     their presence by default.
>> >      >
>> >      > Right now with meetecho, my eyes are normally at the video are
>> >     when people are speaking, but if a non-video person is speaking I
>> >     need to look across to the other side of the screen to see the audio
>> >     indication.
>> >      >
>> >      > And as was also suggested in this thread, you can't scroll the
>> >     participant list to find someone to chat to, because they jump to
>> >     the top when they are sending, then back to alphabetical position.
>> >     This is also a usability pain.  Separating "the list of
>> >     participants" (which wouldn't move about) and "the list of people
>> >     sending something" with the video and audio indications being
>> >     together in one place would be a significant improvement.  And as an
>> >     additional benefit, when you're looking at the chat window, you
>> >     would still be able to see all the details of who is sending
>> >     (including yourself - if you're sending then the indicator of your
>> >     own audio should be the same as the indicator of everyone else's
>> >     audio, rather than being in yet a third location up under your own
>> >     name).
>> >      >
>> >      > <image.png>
>> >      > So those two names would appear in the right hand side, and also
>> >     still have their name in the participant list, and the video feeds
>> >     would each have a "here's what's being sent".  Chairs would always
>> >     have a presence on the right, with whatever they were currently
>> >     sending - and the "participants" tab would only have the list of
>> >     participants, and not be a place you needed to go to see activity,
>> >     so you could mostly keep the chat tab open.
>> >      >
>> >      > Bron.
>> >      >
>> >      >
>> >      > --
>> >      >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >      > brong@fastmailteam.com <mailto:brong@fastmailteam.com> 
>> <mailto:brong@fastmailteam.com <mailto:brong@fastmailteam.com>>
>> >      >
>> >      >
>> >      > --
>> >      > 111attendees mailing list
>> >      > 111attendees@ietf.org <mailto:111attendees@ietf.org> 
>> <mailto:111attendees@ietf.org <mailto:111attendees@ietf.org>>
>> >      > https://www.ietf.org/mailman/listinfo/111attendees 
>> <https://www.ietf.org/mailman/listinfo/111attendees>
>> >     <https://www.ietf.org/mailman/listinfo/111attendees 
>> <https://www.ietf.org/mailman/listinfo/111attendees>>
>> >
>> >     --
>> >     Jay Daley
>> >     IETF Executive Director
>> > jay@ietf.org <mailto:jay@ietf.org> <mailto:jay@ietf.org 
>> <mailto:jay@ietf.org>>
>> >
>> >     --
>> >     111attendees mailing list
>> > 111attendees@ietf.org <mailto:111attendees@ietf.org> 
>> <mailto:111attendees@ietf.org <mailto:111attendees@ietf.org>>
>> > https://www.ietf.org/mailman/listinfo/111attendees 
>> <https://www.ietf.org/mailman/listinfo/111attendees>
>> >     <https://www.ietf.org/mailman/listinfo/111attendees 
>> <https://www.ietf.org/mailman/listinfo/111attendees>>
>> >
>> >
>>
>> -- 
>> 111attendees mailing list
>> 111attendees@ietf.org <mailto:111attendees@ietf.org>
>> https://www.ietf.org/mailman/listinfo/111attendees 
>> <https://www.ietf.org/mailman/listinfo/111attendees>
>>
> 
> --
>    Bron Gondwana, CEO, Fastmail Pty Ltd
>    brong@fastmailteam.com
> 
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss
> 


From nobody Tue Aug  3 07:04:23 2021
Return-Path: <ietf@meetecho.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A833A24F6 for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 07:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
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 q4DUQSzX4l6F for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 07:04:11 -0700 (PDT)
Received: from smtpcmd10102.aruba.it (smtpcmd10102.aruba.it [62.149.156.102]) by ietfa.amsl.com (Postfix) with ESMTP id C1A9C3A24F4 for <111attendees@ietf.org>; Tue,  3 Aug 2021 07:04:10 -0700 (PDT)
Received: from [192.168.1.62] ([93.40.13.11]) by Aruba Outgoing Smtp  with ESMTPSA id Av1cm6oeonyXHAv1cmTYja; Tue, 03 Aug 2021 16:04:09 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1627999449; bh=LMCCSn0hSKNKVKj1x8tGpUpShpVd7eeYV9CJk0ntJ9c=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=bewsw0mcW92pQdYcrTXPoDsLRji5nBB/FMfHFmxtTXU1IPuA6WNMTOS4ISKTjTXNL lsVRiDNCrnirZKXhlI8ctjEqlWsCV8yBErUqCXQX8ngYcMuUcEnLUMSNlcgd1v34l6 8ezqiD9bDlPAzPLvZ3jyQUyfwzk6p1ddVubc7EA5LGz2QpK4wy3b3ZdCbBkxNJ4Gqu IOv+47tejkVExwPoJwxw6r2amm43X91WKsTJUw2mgJB9TAPXFW4RTfEwTO13SF+dAe 5W2UDEeSnCug+prCuU2Q7WR3kpYfznTrgKZB4i5MKPslwgqYMjU4nB58LTY704bIdx p7ZmVwpeGvp/g==
To: Eric Rescorla <ekr@rtfm.com>, tools-discuss <tools-discuss@ietf.org>
Cc: 111attendees@ietf.org, Bron Gondwana <brong@fastmailteam.com>
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com> <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <8723f74d-92b6-3835-397c-710fea654f08@meetecho.com>
Date: Tue, 3 Aug 2021 16:04:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBP40naMrJQPrxYDG6mefFSOgTM6f6wTYkS4_c7_HF4SGg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfAoPoApZm2ySl/PDJNTXtm0hx2Q7UWShVXeu52nQHxXHrZg6tUsFL8FEDm9bsfwFoTqDDwBn1P6L+h5pEDL6tBu6Ad3f3JkXKCeWS3x8Pr6DEZnuIkhh 1bCMeC+c5jT1+AGKqRkLXi0vI+7c9Nv4qM6HZH4AANqYoxz9HayAjllxIo5scqVsddnWE1P9bAHz2TD4DIPzWHS9bX4af4DwZZ99bRakPV3MqrqwEh/+eG9o EwAASj+Tjer1UpUzKyggNw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/6YZ2AKSwfKziFVSIgvc8z_g_NTE>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 14:04:18 -0000

Hi EKR,

Il 30/07/21 23:13, Eric Rescorla ha scritto:
> 
> 
> On Fri, Jul 30, 2021 at 2:03 PM Bron Gondwana <brong@fastmailteam.com 
> <mailto:brong@fastmailteam.com>> wrote:
> 
>     Ooh, we're going a full "suggestions for meetecho" thread?  I'd like
>     to propose some things!
> 
>     *that we replace the current "raise hands" tool:*
> 
>     *... *which is based on an expired draft which isn't going to be
>     refreshed - with a better tool that allows the chairs to:
> 
>     a) label each option
>     b) have more than 2 options (max 9 maybe)
>     c) select between "choose one" and "choose N" modes (checkbox vs
>     radio button)
> 
>     ... and which appears IN PLACE of the slides when enabled, so that
>     meeting participants don't have to navigate to a separate tab to
>     interact.
> 
>     More generally, it's too easy for some participants to be lost on
>     different tabs where they can't see the slides.  The multiple views
>     where you can see individual talking heads in more detail are not
>     actually valuable I don't think - if slides are showing they should
>     be the bulk of the screen because they need to be read - and if a
>     poll is showing then for sure it should be taking over the screen.
> 
> 
> EKR Raises Hand.
> 
> 
>     *a "temporary mute" mode that keeps the audio stream open:*
> 
>     This is still an issue for me.  I often mute myself while chairing
>     so I can take notes without my keyboard sound interrupting the chat
>     - but it means that I can't easily respond to somebody because the
>     rejigging of the audio channel not only creates a hiccup in the
>     incoming audio feed which means I might miss something someone says,
>     but it also creates enough of a delay that by the time I could have
>     responded the other party's mental state has moved on.
> 
>     Timing is really important in conversation and we're already
>     fighting with the quarter second delay imposed by the size of the
>     planet.  Additional delay makes it unwieldy.
> 
> 
> Note that this is a respect in which Meetecho is unusual. Most other VC 
> systems which I am familiar with just stop sending on the track but keep 
> the microphone open rather than dropping the media stream and re-calling 
> getUserMedia().

we have been actually required to implement such behavior a long time 
ago by the IETF, as we have been told that the tool should not have 
access to your mic or webcam devices if you're just an "observer" and 
not really intend to send media. I understand things and needs might 
have changed now, so we're happy to explore alternatives (see the 
"temporary mute" suggested by Bron).

> To your list, I would add auto-unmuting (and even more importantly, 
> muting) when people enter and exit the head of the queue. This would 
> remove a lot of goofy behavior.

I personally don't agree on this. My opinion is that that unmuting 
should never be triggered by somebody else's action, e.g., when you're 
second in line and the person ahead of you leaves the queue. A long time 
might have passed since you joined the queue, you might be doing 
something completely different of even speaking to a different WG 
session, and you don't want your mic to be turned on automatically.

Cheers,
Alessandro

> -Ekr
> 
> 
> 
> 
>     *allow multiple connections by the same person to the same session:*
> 
>     I have multiple times wanted to switch device temporarily - from my
>     desktop computer to a phone / ipad so I can temporarily move to
>     another location while continuing to follow a meeting.  Multiple
>     connection support would mean I could switch over without a break.
> 
>     Sure it could be abused by people "sharing" a login, but that would
>     be pretty obvious if both parties tried to participate, and given
>     that we allow fee waivers anyway, it's unlikely to be abused
>     significantly.  Sure there are Jabber naming issues, but we can
>     avoid that by giving each jabber name with a serial number (which I
>     believe already happens now?)
> 
>     ...
> 
>     I've already written these up separately in the past, but:
> 
>     *information about who is speaking in the same place as video feeds*
> 
>     See my previous email :)  Basically the "participant list" should
>     just be an ordered list of participants and only needs to be
>     switched to when seeing who is in the call or opening an individual
>     message to them (and people don't get moved out of order when
>     they're sending something).  The "who is sending something" list
>     should be all together with the video, and chairs pinned even if
>     they're sending nothing right now.
> 
>     Along with visual indicators of "currently sending audio" on people
>     so we know who of those with their audio channel open are currently
>     speaking, this makes it easier to look in one place to see the
>     source of all sound, and eyes can generally flit between the right
>     hand side (video and audio indicators) and the slides, without
>     needing to also track via the participant list.
> 
>     *flexible "assign chair"**:*
> 
>     This one hasn't come up in practice, but the chairs for meetings are
>     pre-assigned from datatracker.  It would be great for ADs and the
>     meetecho reps in each meeting to be able to upgrade anybody to a
>     chair role or remove a chair role with a simple click.
> 
>     In real rooms, anyone can go sit in the chair at the front of the
>     room, and it's not abused because of social convention.  I believe
>     that we can map that to this virtual space and still have it work
>     sensibly.  People won't take the chair unless there's a legitimate
>     reason to do it, and so long as it's logged - if someone does
>     consistently abuse it we have processes to eject them from the IETF
>     for misbehaviour.
> 
>     This has become less important with the ability for individuals to
>     turn on both audio and video themselves, so the chair is going less
>     busywork just approving access, but it would be good to make it
>     possible for someone else to step into the chair if the regular
>     chairs are unable to attend or lose network, rather than making the
>     meeting less able to run.
> 
>     Bron.
> 
>     On Sat, Jul 31, 2021, at 05:38, Meetecho IETF support wrote:
>>     All,
>>
>>     chiming in just to say that we at Meetecho appreciate and value your
>>     feedback. We'll definitely take it into account when developing the
>>     future releases of the platform. We'll provide comments on the points
>>     raised as soon as we get the chance to parse them, i.e., when the
>>     meeting is over.
>>
>>     Also, I'm cc'ing tools-discuss@ietf.org
>>     <mailto:tools-discuss@ietf.org> and setting the reply-to header
>>     to that list as well, as that's the right place to discuss
>>     enhancements
>>     and provide feedback that would be easier for us to collect.
>>
>>     Best,
>>     Alessandro
>>
>>     Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto:
>>     > I should have changed the Subject a LONG time ago! But this
>>     thread has
>>     > morphed into helpful observations and suggestions, so, if I
>>     might add a
>>     > couple of things ...
>>     >
>>     > I agree that Meetecho has been improving (and just for fun, the
>>     Meetecho
>>     > guys were participants in the MEDIACTL session I was co-chairing in
>>     > Hiroshima at IETF 76 in November 2009, and they roped in a team
>>     member
>>     > from Italy during the discussion using whatever the toolset was
>>     back
>>     > then, so many of you have no idea how MUCH they've improved 😀).
>>     >
>>     > I see that we've already mentioned detaching the chat window, and
>>     > usually I remember that we can detach the chat by Tuesday of
>>     each IETF
>>     > meeting week at the latest, which is almost certainly a result
>>     of not
>>     > having THAT much experience with Meetecho during the four months
>>     between
>>     > meetings. Now that we can use Meetecho for interim meetings,
>>     that will
>>     > help me remember more clearly, so good there, too.
>>     >
>>     > The one thing I've noticed this week is how difficult it is to
>>     figure
>>     > out who is speaking if they aren't sending video, and there's a
>>     long
>>     > list of people in the queue. The suggestion to move the speakers
>>     above
>>     > the queue would improve that, and so would simply displaying the
>>     active
>>     > speaker names in the screen space where their video would have
>>     gone, if
>>     > the person had been sending video.One reason that matters, is
>>     that it's
>>     > helpful for everyone to get the speaker's name right in the
>>     minutes.
>>     > That's not just for new attendees, I'm starting to forget what
>>     people
>>     > sound like, unless I'm talking to them regularly, or they have a
>>     very
>>     > distinctive speech pattern, so I've definitely depending on
>>     seeing names
>>     > when I'm taking minutes. .
>>     >
>>     > The one thing I was thinking about, as I read through this
>>     thread, was
>>     > that we are kinda *not *talking about what the IETF thinks the
>>     target
>>     > audience for our conferencing tool is.
>>     >
>>     >   * For probably the last couple of IETFs, I have a GREAT setup for
>>     >     remote participation (my laptop screen, plus two 25-inch
>>     monitors).
>>     >     But I do have tiled windows on all three screens.
>>     >   * If we think people who can't throw a few hundred dollars at
>>     monitor
>>     >     screens are part of our target audience, that's worth noting.
>>     >   * If we think we're going to have hybrid meetings, in at least
>>     some
>>     >     scenarios, it's going to be good to use Meetecho in the
>>     conference
>>     >     rooms (especially if we need to be distancing, so more
>>     spread out,
>>     >     front to back in the conference rooms).
>>     >   * Even if we aren't doing hybrid meetings, I've participated
>>     in some
>>     >     working group meetings from my hotel room, but I wasn't tryng to
>>     >     co-chair a meeting, or even to present at a meeting.
>>     >   * When Michael Richardson and I talked to the Cellar working group
>>     >     participants about switching to Meetecho for our (monthy)
>>     interims,
>>     >     the first question we got was, "is there an iOS/Adroid
>>     client?" I
>>     >     haven't checked Meetecho on my phone in years, but I'd bet
>>     offhand
>>     >     that (1) it would work, but (2) it might not be as easy to
>>     use as
>>     >     some other conferencing systems, on those devices. Do people
>>     have
>>     >     experience with that?
>>     >
>>     > I'll let you folks continue to share these positive observations
>>     and
>>     > proposals. Make Good Choices, of course.
>>     >
>>     > Best,
>>     >
>>     > Spencer
>>     >
>>     > On Thu, Jul 29, 2021 at 6:15 PM Jay Daley <jay@ietf.org
>>     <mailto:jay@ietf.org>
>>     > <mailto:jay@ietf.org <mailto:jay@ietf.org>>> wrote:
>>     >
>>     >     Thanks Bron.  Personally I think that’s a great usability
>>     adjustment
>>     >     and will forward to the Meetecho team for them to consider.
>>     >
>>     >     Jay
>>     >
>>     >      > On 30/07/2021, at 10:58 AM, Bron Gondwana
>>     <brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>>     >     <mailto:brong@fastmailteam.com
>>     <mailto:brong@fastmailteam.com>>> wrote:
>>     >      >
>>     >      > On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:
>>     >      >> No we have absolutely not pushed Meetecho into being "just a
>>     >     contractor", they are a valued partner and we work very well
>>     >     together.  If you have any doubts about that then ask them
>>     directly.
>>     >      >>
>>     >      >> It is disappointing that you have escalated a personal
>>     concern
>>     >     that you have with our services into such a strong criticism
>>     when
>>     >     that is entirely unsupported by any evidence.
>>     >      >
>>     >      > Jay, I agree with your sentiment here - this attitude to
>>     Meetecho
>>     >     is counterproductive.  They've done great work for the last
>>     couple
>>     >     of IETFs and the experience is improving each time.  I have
>>     >     particularly appreciated the embedded slide management, and
>>     I'm sure
>>     >     that will be even better next time too.
>>     >      >
>>     >      > Regarding the specific interface issues that remain, I do
>>     think
>>     >     there's a question of "where do we propose improvements in a way
>>     >     that will be noticed"?  I've seen the suggestion made very many
>>     >     times that the "speaker" area (where the video shows) should
>>     have
>>     >     additional lines for each person sending anything, rather
>>     than that
>>     >     information being at the top of the participant list.  This
>>     is much
>>     >     more like the experience with other chat systems, for
>>     example Zoom
>>     >     shows either a photo or a blank item for somebody who isn't
>>     >     currently sending video, but they're otherwise treated "the
>>     same" as
>>     >     a person sending video in terms of real-estate and where to
>>     look for
>>     >     their presence by default.
>>     >      >
>>     >      > Right now with meetecho, my eyes are normally at the
>>     video are
>>     >     when people are speaking, but if a non-video person is
>>     speaking I
>>     >     need to look across to the other side of the screen to see
>>     the audio
>>     >     indication.
>>     >      >
>>     >      > And as was also suggested in this thread, you can't
>>     scroll the
>>     >     participant list to find someone to chat to, because they
>>     jump to
>>     >     the top when they are sending, then back to alphabetical
>>     position.
>>     >     This is also a usability pain.  Separating "the list of
>>     >     participants" (which wouldn't move about) and "the list of
>>     people
>>     >     sending something" with the video and audio indications being
>>     >     together in one place would be a significant improvement. 
>>     And as an
>>     >     additional benefit, when you're looking at the chat window, you
>>     >     would still be able to see all the details of who is sending
>>     >     (including yourself - if you're sending then the indicator
>>     of your
>>     >     own audio should be the same as the indicator of everyone else's
>>     >     audio, rather than being in yet a third location up under
>>     your own
>>     >     name).
>>     >      >
>>     >      > <image.png>
>>     >      > So those two names would appear in the right hand side,
>>     and also
>>     >     still have their name in the participant list, and the video
>>     feeds
>>     >     would each have a "here's what's being sent".  Chairs would
>>     always
>>     >     have a presence on the right, with whatever they were currently
>>     >     sending - and the "participants" tab would only have the list of
>>     >     participants, and not be a place you needed to go to see
>>     activity,
>>     >     so you could mostly keep the chat tab open.
>>     >      >
>>     >      > Bron.
>>     >      >
>>     >      >
>>     >      > --
>>     >      >   Bron Gondwana, CEO, Fastmail Pty Ltd
>>     >      > brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>>     <mailto:brong@fastmailteam.com <mailto:brong@fastmailteam.com>>
>>     >      >
>>     >      >
>>     >      > --
>>     >      > 111attendees mailing list
>>     >      > 111attendees@ietf.org <mailto:111attendees@ietf.org>
>>     <mailto:111attendees@ietf.org <mailto:111attendees@ietf.org>>
>>     >      > https://www.ietf.org/mailman/listinfo/111attendees
>>     <https://www.ietf.org/mailman/listinfo/111attendees>
>>     >     <https://www.ietf.org/mailman/listinfo/111attendees
>>     <https://www.ietf.org/mailman/listinfo/111attendees>>
>>     >
>>     >     --
>>     >     Jay Daley
>>     >     IETF Executive Director
>>     > jay@ietf.org <mailto:jay@ietf.org> <mailto:jay@ietf.org
>>     <mailto:jay@ietf.org>>
>>     >
>>     >     --
>>     >     111attendees mailing list
>>     > 111attendees@ietf.org <mailto:111attendees@ietf.org>
>>     <mailto:111attendees@ietf.org <mailto:111attendees@ietf.org>>
>>     > https://www.ietf.org/mailman/listinfo/111attendees
>>     <https://www.ietf.org/mailman/listinfo/111attendees>
>>     >     <https://www.ietf.org/mailman/listinfo/111attendees
>>     <https://www.ietf.org/mailman/listinfo/111attendees>>
>>     >
>>     >
>>
>>     -- 
>>     111attendees mailing list
>>     111attendees@ietf.org <mailto:111attendees@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/111attendees
>>     <https://www.ietf.org/mailman/listinfo/111attendees>
>>
> 
>     --
>        Bron Gondwana, CEO, Fastmail Pty Ltd
>     brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> 
> 
>     ___________________________________________________________
>     Tools-discuss mailing list - Tools-discuss@ietf.org
>     <mailto:Tools-discuss@ietf.org>
>     This list is for discussion, not for action requests or bug reports.
>     * Report datatracker and mailarchive bugs to:
>     datatracker-project@ietf.org <mailto:datatracker-project@ietf.org>
>     * Report tools.ietf.org <http://tools.ietf.org> bugs to:
>     webmaster@tools.ietf.org <mailto:webmaster@tools.ietf.org>
>     * Report all other bugs or issues to: ietf-action@ietf.org
>     <mailto:ietf-action@ietf.org>
>     List info (including how to Unsubscribe):
>     https://www.ietf.org/mailman/listinfo/tools-discuss
>     <https://www.ietf.org/mailman/listinfo/tools-discuss>
> 
> 


From nobody Tue Aug  3 07:36:49 2021
Return-Path: <ietf@meetecho.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 341BF3A25E4 for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 07:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
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 VXQ5jppz-KKT for <111attendees@ietfa.amsl.com>; Tue,  3 Aug 2021 07:36:42 -0700 (PDT)
Received: from smtpcmd10101.aruba.it (smtpcmd10101.aruba.it [62.149.156.101]) by ietfa.amsl.com (Postfix) with ESMTP id 643503A25E0 for <111attendees@ietf.org>; Tue,  3 Aug 2021 07:36:42 -0700 (PDT)
Received: from [192.168.1.62] ([93.40.13.11]) by Aruba Outgoing Smtp  with ESMTPSA id AvX6m7PpUnyXHAvX6mTuIu; Tue, 03 Aug 2021 16:36:41 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1628001401; bh=Ek3uBrSSN1UTQqBq/QOl28ZQlGBH2XB1NP+5aLO5NeM=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=UiFqc19YUEQqMhDHiWjzZE3hcmsU+YaoBlwW+yHfQRq+Rw+IQ2jvU7kRvabceUph9 O637IxBm2sPf5YrQ94qS9tKILJTZSknlOj3irJvWc03zx83csc0kTa837JgPMYs2Ou uEi/35mHDN5mw8fiOPRwaZiQGHGkB4oh31eIaXnlMfvw88y0cBJ9j4Rw2ULvuSsGOn CER8/HRiP8JQol/FUMp+WN3uxJDxAzFbb9BKYOejYanIqHS5Kb7LVIF9zgI5NtwKWn 64rDBw7k3mQhId3SCw9sAOzUgI51MDw3PkmYEmnFdZWfr8NvZEbl9Obftk1B14EB8K VcObejlQELzQg==
To: Marc Petit-Huguenin <marc@petit-huguenin.org>, tools-discuss@ietf.org
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
Cc: 111attendees@ietf.org
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <beceacb0-491d-a44c-a160-875bc1ca85ad@meetecho.com>
Date: Tue, 3 Aug 2021 16:36:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfPieQXzZC6Gx1fLdGCZ9ODgEQbrlcA3Jg4DBMgA3Fh8lWoxy/Fgm4bOlnr+pc/4cNp+uBylK4SLedcjHV94tNprN5N8w3PKTHu3yUbV2m1+ySjzU/dL6 9khN2Soiwbq8IXq4FBQgCPgwhxWu80cCVmBY+QCT7hBMFAFaNfEqPL2JCcU2JqBye/UiZ40LCtoiKKtGxP/waToOpbwM5/7/H8x+wFCkDqPswykIY3lIOEUV
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/zgJIRlGvYS1v82dapStT5uwwo7k>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 14:36:48 -0000

Hi Marc,

while the TTS suggestion is interesting and worth exploring, in the 
short run I think it might be worth revamping the custom recording 
player we had in the past, which integrated the YouTube video, the 
Jabber logs and also the audio transcripts automatically generated by 
YouTube. See for instance:

	https://play.conf.meetecho.com/Playout/?session=IETF106-DISPATCH-20191118-1000

Cheers,
Alessandro

Il 02/08/21 19:48, Marc Petit-Huguenin ha scritto:
> One use of the Meetecho recording is to prepare minutes by double 
> checking notes.  One issue with that is that sometimes a presenter 
> answers comments made in the chat, but the chat log does not appear in 
> the recording.  The person preparing the minutes now has to open the 
> minutes, try to synchronize then with the recording and update the 
> minutes to reflect the question/comment that triggers the response by 
> the presenter.  There is two issues with that:
> 
> 1. Someone watching only the recording only have access to half of that 
> conversation and may not know where the chat logs are, or even that they 
> was a chat running along the session.
> 2. People taking notes must follow both the chat and the presenter, 
> which could be a bit too much.
> 
> I do not think that recording the chat at the same time than the 
> presenter would be a good idea (OTOH displaying the name of the person 
> talking in the recording even if they did not turn on video would 
> help).  The reason is that not all the content of the chat log is 
> relevant for the WG business (that's an understatement).
> 
> Having a jabber scribe and some discipline may help: The jabber scribe 
> repeats the chat comment/question, and the presenters does not try to 
> look at the chat, and so now the whole context is captured.
> 
> But that's still a bit clunky -- a presenter may want to comment on 
> something that someone said in the chat room even if it was not marked 
> as a question that the Jabber scribe must relay.  After all the chat 
> logs are under NOTE WELL, so they are part of the WG session -- and 
> should be part of the minutes, at least the relevant parts.
> 
> My suggestion would be to use TTS to supplement or replace the Jabber 
> scribe.  A remote presenter who want to answer/comment on a chat message 
> triggers TTS on the message itself, which now becomes part of the 
> recording -- and of the minutes.  With a local presenter the Jabber 
> scribe could also use that TTS feature.
> 
> On 7/30/21 12:38 PM, Meetecho IETF support wrote:
>> All,
>>
>> chiming in just to say that we at Meetecho appreciate and value your 
>> feedback. We'll definitely take it into account when developing the 
>> future releases of the platform. We'll provide comments on the points 
>> raised as soon as we get the chance to parse them, i.e., when the 
>> meeting is over.
>>
>> Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to 
>> header to that list as well, as that's the right place to discuss 
>> enhancements and provide feedback that would be easier for us to collect.
>>
>> Best,
>> Alessandro
>>
> [...]
> 


From nobody Tue Aug  3 18:26:10 2021
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 944123A3AAD; Tue,  3 Aug 2021 18:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kGCajkKfXhhT; Tue,  3 Aug 2021 18:25:59 -0700 (PDT)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF0463A3AAB; Tue,  3 Aug 2021 18:25:58 -0700 (PDT)
Received: by mail-ua1-x931.google.com with SMTP id v3so328712uau.3; Tue, 03 Aug 2021 18:25:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uNxLxPOCKPPheDnSpHjG/BBr07qwP5+781nqDg7DQY0=; b=CMvjItLc7EDHMdE9bKROrPiV8yhjMi9njMDofPwbmrEdFR+Uub3wMf44OABYrGzTr8 Cu2zvf02xy5FgKinOPVmtKSQ0Ty10LFdYBa2gGC5bKRQNvT+L3bjb+CTx5FZUWyuua+k U0sPulWKEEZzzTotGGns9zGRQNvvF6pIH6PTc24DrE+sGX35AeLcTnv2K1Uo3EoSgN/7 yB3FnWH6kluF+P1akHkiRuRJeNwrnaPX8xuTF5f7MiltJsLd9BhVkK9F3RrBXoCh/hPk /HFxq6Ldv8Yopg69Jynhh4hEPoF4XlsKiRH97GMIPiR5OAROS1TSrPPraaqKZUmvDG3i VtEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uNxLxPOCKPPheDnSpHjG/BBr07qwP5+781nqDg7DQY0=; b=DcP9V0IQRmDNeDQjkoj/a/QrN+VjpS+fU/5iJNBRkqIGzlvxbRzKxn+1t67A763o+F QoeEwdJ4pPB/rjJ+0UBsZqmJadSP/O1sDtBRjZRbZxLzpnW4q1bPiw2sNmCRoVYaIUtX S8S4+e+yKuTZRhw4a2W4A9fZmgm8RmNWaN31eryWOSMn9wLk/Ax72nsQ5Q5HiPHw8N4A dDWuN+tVtECeIF5J19kXDcDUCPfTlweqwM1JKE8hvYZpszNXBk+zY1f/FlAV57CyEftr G2CUGB9q3cHafzjKArFMpwfwJzA3ZQ5F5vB+8XP3DBbPJN6Y83HleYGd+kU1xF3SatrG 6Pjw==
X-Gm-Message-State: AOAM530AwF8pfqFjeuob6/9LWhJg8ypUQY7sDPmIA+F6RAmg66LGdL9M Ql+vGm6+/PSJEf3KjpzQ18k6B6eUThhxsTrFak6VQJy7
X-Google-Smtp-Source: ABdhPJwDnH+rby6Rbs3vLx32im4Alvgg2Q/Cbloq2HhPCYRWz3llFXKyh8p/FI9Fcg5i1nOHwvlTg0Q7MxTsoO/nG4o=
X-Received: by 2002:ab0:3011:: with SMTP id f17mr17261433ual.118.1628040357601;  Tue, 03 Aug 2021 18:25:57 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org> <beceacb0-491d-a44c-a160-875bc1ca85ad@meetecho.com>
In-Reply-To: <beceacb0-491d-a44c-a160-875bc1ca85ad@meetecho.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 3 Aug 2021 20:25:31 -0500
Message-ID: <CAKKJt-d6qSy7y5dWVtsUw143RyBgy_c1zZJM99Xa=BkQQSXW9g@mail.gmail.com>
To: Meetecho IETF support <ietf@meetecho.com>
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, Tools Team Discussion <tools-discuss@ietf.org>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="00000000000031e4ad05c8b1af36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/j_n-95pesWrEA9sX87TIv0LEgYc>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2021 01:26:04 -0000

--00000000000031e4ad05c8b1af36
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Alessandro,

On Tue, Aug 3, 2021 at 9:37 AM Meetecho IETF support <ietf@meetecho.com>
wrote:

> Hi Marc,
>
> while the TTS suggestion is interesting and worth exploring, in the
> short run I think it might be worth revamping the custom recording
> player we had in the past, which integrated the YouTube video, the
> Jabber logs and also the audio transcripts automatically generated by
> YouTube. See for instance:
>
>
> https://play.conf.meetecho.com/Playout/?session=3DIETF106-DISPATCH-201911=
18-1000
>

I'm sending Meetecho more email in the past 24 hours than in the previous
24 months. But YES YES YES! The audio transcript was the part that I
couldn't remember!

Having spent a LOT of time wandering through Jabber conversations for
several years, including a couple of working group sessions where the
Jabber scribe was asked to say at the Mic:, "you folks should probably be
in Jabber, because that's where the REAL meeting is going on" (=F0=9F=98=89=
, and I'm
not naming names), I often find the side conversations incredibly helpful,
but Context Also Matters, so seeing someone make a terse comment in Jabber
that is synchronized with the video is helpful, while the same comment in
isolation is at best confusing, and often not useful at all.

The audio transcript is better than we have any right to expect for most
things except technical terms and proper names. But when someone is
speaking at speed, there have been times when I was checking minutes
against the video, and it was still difficult to parse, so anything I could
dig out of the audio transcript helps!

Please do think about this in more depth. Some of us liked that ...

Best,

Spencer

--00000000000031e4ad05c8b1af36
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Alessandro,=C2=A0</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Aug 3, 2021 =
at 9:37 AM Meetecho IETF support &lt;<a href=3D"mailto:ietf@meetecho.com">i=
etf@meetecho.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">Hi Marc,<br>
<br>
while the TTS suggestion is interesting and worth exploring, in the <br>
short run I think it might be worth revamping the custom recording <br>
player we had in the past, which integrated the YouTube video, the <br>
Jabber logs and also the audio transcripts automatically generated by <br>
YouTube. See for instance:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://play.conf.meetecho.com/Playo=
ut/?session=3DIETF106-DISPATCH-20191118-1000" rel=3D"noreferrer" target=3D"=
_blank">https://play.conf.meetecho.com/Playout/?session=3DIETF106-DISPATCH-=
20191118-1000</a><br></blockquote><div><br></div><div>I&#39;m sending Meete=
cho more email in the past 24 hours than in the previous 24 months. But YES=
 YES YES! The audio transcript was the part that I couldn&#39;t remember!=
=C2=A0</div><div><br></div><div>Having spent a LOT of time wandering throug=
h Jabber conversations for several years, including a couple of working gro=
up sessions where the Jabber scribe was asked to say at the Mic:, &quot;you=
 folks should probably be in Jabber, because that&#39;s where the REAL meet=
ing is going on&quot; (=F0=9F=98=89, and I&#39;m not naming names), I often=
 find the side conversations incredibly helpful, but Context Also Matters, =
so seeing someone make a terse comment in Jabber that is synchronized with =
the video is helpful, while the same comment in isolation is at best confus=
ing, and often not useful at all.=C2=A0</div><div><br></div><div>The audio =
transcript is better than we have any right to expect for most things excep=
t technical terms and proper names. But when someone is speaking at speed, =
there have been times when I was checking minutes against the video, and it=
 was still difficult to parse, so anything I could dig out of the audio tra=
nscript helps!</div><div><br></div><div>Please do think about this in more =
depth. Some of us liked that ...</div><div><br></div><div>Best,</div><div><=
br></div><div>Spencer</div></div></div>

--00000000000031e4ad05c8b1af36--


From nobody Wed Aug  4 08:52:35 2021
Return-Path: <warren@kumari.net>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239863A08B3 for <111attendees@ietfa.amsl.com>; Wed,  4 Aug 2021 08:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
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 TCdVHOUCTAzY for <111attendees@ietfa.amsl.com>; Wed,  4 Aug 2021 08:52:28 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1267B3A08B0 for <111attendees@ietf.org>; Wed,  4 Aug 2021 08:52:27 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id g13so5220415lfj.12 for <111attendees@ietf.org>; Wed, 04 Aug 2021 08:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1evz8PN+pKyvjORvytqOoZcZTYZ/iQblb0gofbbCvfM=; b=fKngccNWifuozR5ukEKicDh25ro2rLvc/PmfjWA13GYT210fFgKzaoe18aj6Bqjem9 AB+T38CK6zkmId4qPz70vXj/vOWbSJ8kygZGl/XTyzFUVQUZiIMD5wWhqXknuOx33JOV KQc7xBKjjdJ33Ac7VPz+uIGabcGKJOEe92fWwsQvjZp3RyZR51LCX3TiNRidWYoaepKz jpQlB/re4ml2WzeMhV5yp0aPrz7RhizHRWqIkj5tCnXz//gZ1C2lktayHSCktQW2LDVX b8dp+cVHs1/uT/mOhJOBu2WNV+BvaBL5cagvhB7urDIIW6qV4ZLkhgE31Dl6Cdkw5X1o CzHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1evz8PN+pKyvjORvytqOoZcZTYZ/iQblb0gofbbCvfM=; b=pm7wZMkWwx14lSzfvUL2ADL64NW3I3iuqZpnhPvhgy7iq990gundBq5Ipg0ECEqlnU eNHqQeBCieRU1RJVYyuYfC58o+0b5pRg6Y3JC5NOwiWdp9hR4BrplNzC6lHz9cgCN2KQ zBLF3rbpJKVdBl8wmvlHMPNgTb22Q4sLtqyWccncZuvKyLZd/tTfEFJJXey02nDXLkq8 hrMaWIybSD3NIyJHvt5lCkMj2OoHXF80DajqnH2xDxxmANk+lydQKy0mpl/8EVIO7xni EwPk9fKzxSvsHM2v9LxOd43CVA9bnR7E3Ci9mcJ70eg3sydk+XBf+hEy5cDMrvyQbTX1 E5+Q==
X-Gm-Message-State: AOAM532Hx6H2cY0Bow+RW+Jyi0+qfBQbYVfEhKsk6Zf2cuCvHZalmf5m kbRd4WjXWxPC1GXUjY3WmW3hQdzUK+V7dYtfF1S/fg==
X-Google-Smtp-Source: ABdhPJzL2cmBqDjvPM/vOF4irjZ4UDmgbyY7jqeoJhutfz5ThbKUWjdAKv3t63KsWhubgH5bEAQWBulMOHx+rX0LeXg=
X-Received: by 2002:a19:ac45:: with SMTP id r5mr20443736lfc.484.1628092344443;  Wed, 04 Aug 2021 08:52:24 -0700 (PDT)
MIME-Version: 1.0
References: <AM8P193MB078821D4A3EBB38216268A10FAEC9@AM8P193MB0788.EURP193.PROD.OUTLOOK.COM>
In-Reply-To: <AM8P193MB078821D4A3EBB38216268A10FAEC9@AM8P193MB0788.EURP193.PROD.OUTLOOK.COM>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 4 Aug 2021 11:51:48 -0400
Message-ID: <CAHw9_iJ_Wg6T6mOXYee6cWxrcsj_18ELdYN1v6py3=SQ+E9YEw@mail.gmail.com>
To: Ulrich Wisser <ulrich.wisser@internetstiftelsen.se>
Cc: "111attendees@ietf.org" <111attendees@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000da36cb05c8bdc95e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/sfx-6xZU1fDsP1e8z6LlER4z-5o>
Subject: Re: [111attendees] Network measurements
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2021 15:52:33 -0000

--000000000000da36cb05c8bdc95e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 30, 2021 at 7:58 PM Ulrich Wisser <
ulrich.wisser@internetstiftelsen.se> wrote:

> Hi,
>
>
>
> Thanks for another great conference.
>
> At the physical meetings the noc team sets out stations which show networ=
k
> statistics.
>
> Is there any documentation on this? I would like to try to recreate some
> of it.
>

The stations which showed network statistics were largely just showing
Grafana ( https://grafana.com/grafana/ ) dashboards.


> Maybe someone has a picture or screen dumps?
>

If you are interested in how the IETF network is put together, etc, here is
a presentation I did at IETF 105 -
https://www.youtube.com/watch?v=3DC_mdk9YIg8Y&t=3D789s
and associated slide deck:
https://datatracker.ietf.org/meeting/105/materials/slides-105-netrqmts-the-=
ietf-network-an-overview-00
Slide 3 has a picture of the dashboard.
For more information, here is a NOC report from IETF 101 -
https://datatracker.ietf.org/meeting/101/materials/slides-101-ietf-sessb-no=
c-report-for-ietf-101-00

W


>
> Kind regards from Stockholm
>
>
>
> /Ulrich
>
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>


--=20
The computing scientist=E2=80=99s main challenge is not to get confused by =
the
complexities of his own making.
  -- E. W. Dijkstra

--000000000000da36cb05c8bdc95e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:verdana,sans-serif"><br></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 30, 2021 at 7:58 PM Ulri=
ch Wisser &lt;<a href=3D"mailto:ulrich.wisser@internetstiftelsen.se">ulrich=
.wisser@internetstiftelsen.se</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">





<div lang=3D"en-SE" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-3420883416275164519WordSection1">
<p class=3D"MsoNormal"><span lang=3D"SV">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"SV"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks for another great confer=
ence. <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">At the physical meetings the no=
c team sets out stations which show network statistics.<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Is there any documentation on t=
his? I would like to try to recreate some of it.</span></p></div></div></bl=
ockquote><div><br></div><div><div class=3D"gmail_default" style=3D"font-fam=
ily:verdana,sans-serif">The stations which showed network statistics were l=
argely just showing Grafana ( <a href=3D"https://grafana.com/grafana/">http=
s://grafana.com/grafana/</a> ) dashboards.</div><div class=3D"gmail_default=
" style=3D"font-family:verdana,sans-serif"><span style=3D"font-family:Arial=
,Helvetica,sans-serif">=C2=A0</span><br></div></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"en-SE" style=3D"overflow-wrap: brea=
k-word;"><div class=3D"gmail-m_-3420883416275164519WordSection1"><p class=
=3D"MsoNormal"><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Maybe someone has a picture or =
screen dumps?</span></p></div></div></blockquote><div><br></div><div><div c=
lass=3D"gmail_default" style=3D"font-family:verdana,sans-serif">If you are =
interested in how the IETF network is put together, etc, here is a presenta=
tion I did at IETF 105 -=C2=A0<a href=3D"https://www.youtube.com/watch?v=3D=
C_mdk9YIg8Y&amp;t=3D789s">https://www.youtube.com/watch?v=3DC_mdk9YIg8Y&amp=
;t=3D789s</a></div><div class=3D"gmail_default" style=3D"font-family:verdan=
a,sans-serif">and associated slide deck: <a href=3D"https://datatracker.iet=
f.org/meeting/105/materials/slides-105-netrqmts-the-ietf-network-an-overvie=
w-00">https://datatracker.ietf.org/meeting/105/materials/slides-105-netrqmt=
s-the-ietf-network-an-overview-00</a><br></div><div class=3D"gmail_default"=
 style=3D"font-family:verdana,sans-serif">Slide 3 has a picture of the dash=
board.<br></div><div class=3D"gmail_default" style=3D"font-family:verdana,s=
ans-serif"></div><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">For more information, here is a NOC report from IETF 101 - <a h=
ref=3D"https://datatracker.ietf.org/meeting/101/materials/slides-101-ietf-s=
essb-noc-report-for-ietf-101-00">https://datatracker.ietf.org/meeting/101/m=
aterials/slides-101-ietf-sessb-noc-report-for-ietf-101-00</a></div></div><d=
iv>=C2=A0</div><div><div class=3D"gmail_default" style=3D"font-family:verda=
na,sans-serif">W</div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div lang=3D"en-SE" style=3D"overflow-wrap: break-word;"><div class=
=3D"gmail-m_-3420883416275164519WordSection1"><p class=3D"MsoNormal"><span =
lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Kind regards from Stockholm<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">/Ulrich<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
</div>

-- <br>
111attendees mailing list<br>
<a href=3D"mailto:111attendees@ietf.org" target=3D"_blank">111attendees@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/111attendees" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/111attendees=
</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr">The computing scientist=E2=80=
=99s main challenge is not to get confused by the<br>complexities of his ow=
n making. <br>=C2=A0 -- E. W. Dijkstra</div></div></div>

--000000000000da36cb05c8bdc95e--

