Re: [107all] Update on IETF 107 Vancouver and COVID-19
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 05 March 2020 10:58 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFF63A1265 for <ietf@ietfa.amsl.com>; Thu, 5 Mar 2020 02:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Level:
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 iDqfbH7YPzh6 for <ietf@ietfa.amsl.com>; Thu, 5 Mar 2020 02:58:21 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 02A763A126A for <ietf@ietf.org>; Thu, 5 Mar 2020 02:58:20 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 025AwIGX024162 for <ietf@ietf.org>; Thu, 5 Mar 2020 11:58:18 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D1F45203AE2 for <ietf@ietf.org>; Thu, 5 Mar 2020 11:58:18 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C7D2C2039E9 for <ietf@ietf.org>; Thu, 5 Mar 2020 11:58:18 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 025AwIOl017622 for <ietf@ietf.org>; Thu, 5 Mar 2020 11:58:18 +0100
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
To: ietf@ietf.org
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com> <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com> <CAOj+MMG+OhM9_G3+ikfGxXSqi6PMO0EJeZ=vCC3Wne=YWHLLhg@mail.gmail.com> <CAHw9_i+yuojs6gkX+GmP8xCxPZn_MBvZH66YHf42bM6Xsip4-Q@mail.gmail.com> <653F4F12-E11B-4843-90AD-EBD35D19E21D@nohats.ca> <CAKKJt-dzUPvBAxo7RP_QCMwX=DgS2NJrzK1r9ucdjgUji8+nhw@mail.gmail.com> <c52ec6f1-dd2d-78a5-faa9-6a506a0f3da7@gmail.com> <14AF65D4-8ACA-42E0-97D2-29B1733D6113@consulintel.es> <7c0a3571-3334-2bc9-a8f9-a60131ce7e2e@meetecho.com> <FE0DB611-4915-413B-A9A1-5734CA273E89@consulintel.es> <CF8C876F-B494-42AB-AB6B-C6E022F2020E@consulintel.es> <8b392292-69b0-0de3-1605-2556cb0ce4e7@meetecho.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ae54e200-d0e3-7cb0-ca63-2c7952500504@gmail.com>
Date: Thu, 05 Mar 2020 11:58:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <8b392292-69b0-0de3-1605-2556cb0ce4e7@meetecho.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rsHSQlgsOJ8Hj1VYeg8yhlr6ICE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2020 10:58:23 -0000
Le 05/03/2020 à 11:49, Meetecho IETF support a écrit : > Il 05/03/20 11:39, JORDI PALET MARTINEZ ha scritto: >> Is not the same for the microphones that we usually have in the rooms? > > Those mics are connected to an audio mixer board which provides hardware > echo suppression. And those mics are directional ones designed for > professional use. They are directional ok, but why do I have to speak close on it? That is the problem: the need to speak close on it. They are professional yes. They are Senheiser I believe. The pop screen made of foam for a handheld senheiser is MZW1. It costs 17Eur. One needs something like that for personal use, and throwable, like paper handkerchief. Alex PS: fyi, there are microphones that pick sound without speaker having to produce sound as virbations of air (so no risk of positive loop). I think of those for the Scientist. But they are more expensive. > >> Even if those microphones need to be muted, and we should go next to >> them, but use our one phone, I guess it should work. > > Again, it's a matter of phone mic + room speakers. The room mics don't > play any role. The phone speaker doesn't play any role as well. > > I'm 100% sure this won't work. > > Alessandro > >> Regards, >> Jordi >> @jordipalet >> >> El 5/3/20 11:36, "ietf en nombre de Alessandro Amirante" >> <ietf-bounces@ietf.org en nombre de alex@meetecho.com> escribió: >> >> No. It's not a matter of phone speaker. It's a matter of phone *mic* >> capturing whatever comes out of the *room* speakers. >> Alessandro >> Il 05/03/20 11:27, JORDI PALET MARTINEZ ha scritto: >> > Unless you mute your phone speaker? >> > >> > Regards, >> > Jordi >> > @jordipalet >> > >> > >> > >> > El 5/3/20 10:58, "ietf en nombre de Alessandro Amirante" >> <ietf-bounces@ietf.org en nombre de alex@meetecho.com> escribió: >> > >> > This is a *very* bad idea. It would generate a lot of echo >> as your voice >> > will be captured again from your phone's mic when it comes >> out from the >> > room's loudspeakers. >> > >> > Alessandro >> > >> > Il 05/03/20 10:49, JORDI PALET MARTINEZ ha scritto: >> > > We don't need that! >> > > >> > > Everybody has a phone with microphones. >> > > >> > > We just need a small app that works in iPhone and >> Android, that connects to the Meetecho, because this is already >> connected to the audio! >> > > >> > > Maybe even this app is not needed if you can use the >> standard remote participation from the cellular device (I never tried). >> > > >> > > We don't need even to queue in the Mic, the chairs can >> give the voice to each one in sequence ( >> > > >> > > Regards, >> > > Jordi >> > > @jordipalet >> > > >> > > >> > > >> > > El 5/3/20 10:31, "ietf en nombre de Alexandre Petrescu" >> <ietf-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> >> escribió: >> > > >> > > >> > > >> > > Le 05/03/2020 à 04:45, Spencer Dawkins at IETF a >> écrit : >> > > > Warren, >> > > > >> > > > I'm seeing "I can help" messages on this list, >> which is admirable but >> > > > may not be the best way to meet this need. Could >> you chat with our >> > > > friends on the IESG and ask how they want to >> handle chairs who >> > > > (potentially suddenly) need onsite help? >> > > > >> > > > It seems like we need something where everyone >> can keep track of who is >> > > > helping who, and something we can keep up to date >> throughout the week.. >> > > > Even a wiki page would be an improvement over >> mail messages with an >> > > > off-topic subject line. >> > > >> > > If there were a wiki page, then I would like to put >> something in there: >> > > if there is a f2f meeting, with the usual >> microphones, then use >> > > microphone screens ('anti-pop') that are >> individual, and probably one use. >> > > >> > > This could help as much as the other measures with >> hands, sanitizers, etc. >> > > >> > > Alex >> > > >> > > > >> > > > Best, >> > > > >> > > > Spencer >> > > > >> > > > On Wed, Mar 4, 2020 at 9:17 PM Paul Wouters >> <paul@nohats.ca >> > > > <mailto:paul@nohats.ca>> wrote: >> > > > >> > > > L >> > > > On Mar 4, 2020, at 19:33, Warren Kumari >> <warren@kumari.net >> > > > <mailto:warren@kumari.net>> wrote: >> > > > >> > > >> >> > > >> >> > > >> >> > > >> Simply because the chairs cannot make it >> does not automatically >> > > >> mean that the WG meeting is cancelled -- WGs >> chairs can ask the WG >> > > >> secretary, or appoint a temporary secretary >> or just ask an >> > > >> in-person participant to do the physical >> onsite things, like >> > > >> bluesheets, pushing the big red button, etc.. >> > > > >> > > > I agree and I will happily volunteer to chair >> a meeting where needed. >> > > > >> > > > Paul >> > > > >> > > >> > > >> > > >> > > >> > > >> > > ********************************************** >> > > IPv4 is over >> > > Are you ready for the new Internet ? >> > > http://www.theipv6company.com >> > > The IPv6 Company >> > > >> > > This electronic message contains information which may >> be privileged or confidential. The information is intended to be for >> the exclusive use of the individual(s) named above and further >> non-explicilty authorized disclosure, copying, distribution or use of >> the contents of this information, even if partially, including >> attached files, is strictly prohibited and will be considered a >> criminal offense. If you are not the intended recipient be aware that >> any disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited, will be considered a criminal offense, so you must reply >> to the original sender to inform about this communication and delete it. >> > > >> > > >> > > >> > >> > -- >> > Ing. Alessandro Amirante, Ph.D. >> > >> > Meetecho S.r.l. >> > www.meetecho.com >> > >> > Via Riviera di Chiaia 124 >> > 80122 Napoli, Italy >> > >> > Mobile: +39 329 6178743 >> > E-mail: alex@meetecho.com >> > >> > >> > >> > >> > >> > ********************************************** >> > IPv4 is over >> > Are you ready for the new Internet ? >> > http://www.theipv6company.com >> > The IPv6 Company >> > >> > This electronic message contains information which may be >> privileged or confidential. The information is intended to be for the >> exclusive use of the individual(s) named above and further >> non-explicilty authorized disclosure, copying, distribution or use of >> the contents of this information, even if partially, including >> attached files, is strictly prohibited and will be considered a >> criminal offense. If you are not the intended recipient be aware that >> any disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited, will be considered a criminal offense, so you must reply >> to the original sender to inform about this communication and delete it. >> > >> > >> > >> -- >> Ing. Alessandro Amirante, Ph.D. >> Meetecho S.r.l. >> www.meetecho.com >> Via Riviera di Chiaia 124 >> 80122 Napoli, Italy >> Mobile: +39 329 6178743 >> E-mail: alex@meetecho.com >> >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged >> or confidential. The information is intended to be for the exclusive >> use of the individual(s) named above and further non-explicilty >> authorized disclosure, copying, distribution or use of the contents of >> this information, even if partially, including attached files, is >> strictly prohibited and will be considered a criminal offense. If you >> are not the intended recipient be aware that any disclosure, copying, >> distribution or use of the contents of this information, even if >> partially, including attached files, is strictly prohibited, will be >> considered a criminal offense, so you must reply to the original >> sender to inform about this communication and delete it. >> >> >> >
- Re: [107all] Update on IETF 107 Vancouver and COV… Ramesh Sivakolundu (sramesh)
- Re: [107all] Update on IETF 107 Vancouver and COV… Jay Daley
- Re: [107all] Update on IETF 107 Vancouver and COV… Robert Raszuk
- Re: [107all] Update on IETF 107 Vancouver and COV… Warren Kumari
- Re: [107all] Update on IETF 107 Vancouver and COV… Marc Petit-Huguenin
- Re: [107all] Update on IETF 107 Vancouver and COV… Carlos M. Martinez
- Re: [107all] Update on IETF 107 Vancouver and COV… Paul Wouters
- Re: [107all] Update on IETF 107 Vancouver and COV… Spencer Dawkins at IETF
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Alessandro Amirante
- Re: [107all] Update on IETF 107 Vancouver and COV… Stewart Bryant
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Alessandro Amirante
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Meetecho IETF support
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… Alvaro Retana
- Re: [107all] Update on IETF 107 Vancouver and COV… Carsten Bormann
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Jared Mauch
- Re: [107all] Update on IETF 107 Vancouver and COV… Vittorio Bertola
- Re: [107all] Update on IETF 107 Vancouver and COV… Jared Mauch
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Christer Holmberg
- Re: [107all] Update on IETF 107 Vancouver and COV… Carsten Bormann
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- RE: [107all] Update on IETF 107 Vancouver and COV… Ron Bonica
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- RE: [107all] Update on IETF 107 Vancouver and COV… Ackermann, Michael
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexa Morris
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [Manycouches] [107all] Update on IETF 107 Van… Phillip Hallam-Baker
- Re: [Manycouches] [107all] Update on IETF 107 Van… Mary B
- Re: [107all] Update on IETF 107 Vancouver and COV… Eliot Lear
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Phillip Hallam-Baker
- Re: [107all] Update on IETF 107 Vancouver and COV… Christian
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Touch
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexander Mayrhofer
- Re: [107all] Update on IETF 107 Vancouver and COV… Stephen Farrell
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Eliot Lear
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Toerless Eckert