Re: [Lsr] problem joining interim [Re: A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02]

Christian Hopps <chopps@chopps.org> Fri, 03 April 2020 10:26 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE0683A1703 for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, 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 YF2rkabr7fq2 for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:26:14 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA683A16FB for <lsr@ietf.org>; Fri, 3 Apr 2020 03:26:14 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id ED32E6085E; Fri, 3 Apr 2020 10:26:12 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <4764_1585908857_5E870C79_4764_208_1_53C29892C857584299CBF5D05346208A48E0BE48@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Date: Fri, 03 Apr 2020 06:26:12 -0400
Cc: Christian Hopps <chopps@chopps.org>, Robert Raszuk <robert@raszuk.net>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>, Tianran Zhou <zhoutianran@huawei.com>, "Acee Lindem (acee)" <acee@cisco.com>, wangyali <wangyali11@huawei.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DCF5A75-6741-4D42-BE66-34BAEEB26685@chopps.org>
References: <1520992FC97B944A9979C2FC1D7DB0F404DB1AD4@dggeml524-mbx.china.huawei.com> <MW3PR11MB4619361A2CA3A402A44914E5C1FE0@MW3PR11MB4619.namprd11.prod.outlook.com> <1520992FC97B944A9979C2FC1D7DB0F404DB2336@dggeml524-mbx.china.huawei.com> <68249E56-5702-4C15-9748-439E43F3EB0E@chopps.org> <1520992FC97B944A9979C2FC1D7DB0F404DEFC14@dggeml524-mbx.china.huawei.com> <A937FECB-2013-403E-89B2-47971514F6CF@chopps.org> <80a8f83c76d447dda48280495b3a80a7@huawei.com> <6F0E8437-5D82-4FAC-A061-69E56E1E161D@chopps.org> <2189e17f36764960bf2dcc554cde9ce0@huawei.com> <MW3PR11MB4619925BEF83B0C4512DD284C1C90@MW3PR11MB4619.namprd11.prod.outlook.com> <06e8443210924ac788c40fa15972cbdd@huawei.com> <C987B657-64D1-4C70-B471-ED9F1266B990@cisco.com> <3948044C-0CC9-4AE8-8541-4D23A5DF396E@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F404DF089E@dggeml524-mbx.china.huawei.com> <MW3PR11MB46197F8C43B3200B07641838C1C60@MW3PR11MB4619.namprd11.prod.outlook.com> <CAOj+MMGsVkws0sTw4RRdb_SdWvsuh+2Dxc-upXqT2_pmpO_+Lg@mail.gmail.com> <6930807B-2FF0-4A5C-AD39-D05345C37A5E@chopps.org> <MW3PR11MB461955420610E933ACC44BC4C1C60@MW3PR11MB4619.namprd11.prod.outlook.com> <CAOj+MMHoTbDzZrA1ttPsdD5Tk7TADaR=ex5WGF=6+X3X1utoHg@mail.gmail.com> <bd193457-956c-47b0-a50b-8d1778e8349a@Spark> <CAOj+MMGuRHVoJ3ez4nQ3O87J4U+-+yabYWeA1AEfj1UGAbPp7w@mail.gmail.com> <3DFEBF57-427E-425E-B5D2-48F683519D16@chopps.org> <4764_1585908857_5E870C79_4764_208_1_53C29892C857584299CBF5D05346208A48E0BE48@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
To: bruno.decraene@orange.com
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/ubUv-c2-usf_MvfuDBXIiyyiC50>
Subject: Re: [Lsr] problem joining interim [Re: A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02]
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 10:26:25 -0000

Hi Bruno,

This is very useful feedback. It looks like that link the secretary posted simply tries to join a standing open room associated with the LSR webex account. This is frustrating b/c I sent an email to the secretary asking if I'd done things correctly. I'm not sure they are aware that the link they send is no good so I will contact them again.

Thanks,
Chris.

> On Apr 3, 2020, at 6:14 AM, bruno.decraene@orange.com wrote:
> 
> Chris, 
> 
> Please see inline.
> 
> 
>> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Christian Hopps
>> Sent: Friday, April 3, 2020 12:00 AM
>> To: Robert Raszuk
>> 
>> 
>> 
>>> On Apr 2, 2020, at 5:17 PM, Robert Raszuk <robert@raszuk.net> wrote:
>>> 
>>> Many thx,
>>> R.
>>> 
>>> PS. As we are talking LSR here it is strange that joining virtual LSR meeting is not for everyone. I was waiting and tried three times today for host approval to join which was not granted. 
>>> 
>> 
>> I am very sorry to hear this! We had 64 participants, at least at one point that I saw. I set the meeting up, and I don't believe there is any way to exclude anyone in particular, I certainly would never have chosen to do that.
>> 
>> However, Webex has a password requirement when setting up meetings (I guess, I tried to not have one, it wouldn't let me) which we included in all the details wherever the details were posted, it was "linkstate".
>> 
>> I did notice an email, from webex, during the meeting about a request from Bruno to join as guest, but he was in the participant list when I then checked.
>> 
> 
> So may be my experience may help for next time(s). See below.
> 
> An email from the IESG secretary was sent on 2020-03-19, saying "Information about remote participation: https://ietf.webex.com/meet/lsr "
> Hence I used that URL.
> On this webex, the meeting did not start on time so I've waited for some time. Then 10-15 minutes past the start, I decided to 'notify the host', but never got accepted on the webex.
> At that point I assumed a technical issue with webex and monitored the mailing list, but no one was complaining, which is not inline with typical IETF reaction ;-) .
> So I assumed the error was only on my side and I searched for more emails and found one from Chris (2020-03-31) saying that the URL was https://ietf.webex.com/ietf/j.php?MTID=mbef20efa9e66c7e97f9d6b18ea84eca8 
> And this one worked fine.
> My guess is that the 'interim' webex did not use the 'lsr' webex. Also the 'official' notification from the IESG secretary with the incorrect webex URL did not helped.
> 
> --Bruno
> 
>> I didn't receive any other emails like that (and FWIW I had 5 windows over 2 monitors going at once trying to manage all this, so noticing the 1 email was lucky).
>> 
>> Did it let you skip entering a password (or did it not offer the option in the first place)?
>> 
>> It would be good to figure this out before the next interim.
>> 
>> Thanks,
>> Chris.
>> 
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org
>> https://www.ietf.org/mailman/listinfo/lsr
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr