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

bruno.decraene@orange.com Fri, 03 April 2020 10:14 UTC

Return-Path: <bruno.decraene@orange.com>
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 D387E3A16BB for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 3_Elbj6Zl7Lb for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:14:19 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1DE53A16B7 for <lsr@ietf.org>; Fri, 3 Apr 2020 03:14:19 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 48twlG0tNnz7tgK; Fri, 3 Apr 2020 12:14:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1585908858; bh=NltfBdIj5cpAMNscSVyiRdz45wTOBt6sa9PU9fuQx6M=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=j0LMpoBcbFSr/V+zh9VPgZEhqzGrew2kfWvquuNeCOl2mWjOUVpDWRTRsb+DUS2nd ebVl9i1HplEKu+lSWEvKQBkILdgwxiHOMnsj5hNihTJ3qQxvSWpbiU/1ekG0TSI9RE CE4ayUbC2Ms162m7ZQ5tJ0LgyC4MNBfHZ9kclJjdiddKvUTPDXwni77cqLsA7PzYIS xjtRk1wOwiB7f81y0GAJAjxPasZcqHop+KneeVOyXITBP5o0JFWiKPC+0ozkOfsnSn Q7BlIHP5GJMF67l2IAG2jxk5L+AN7Fo4l4E1QerWbcbLRw5BBXB4THpi2d5v489iQD SdGOUsMr+jvHQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.23]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 48twlF69fwzCqkY; Fri, 3 Apr 2020 12:14:17 +0200 (CEST)
From: bruno.decraene@orange.com
To: Christian Hopps <chopps@chopps.org>, Robert Raszuk <robert@raszuk.net>
CC: "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>
Thread-Topic: [Lsr] problem joining interim [Re: A new version of I-D, draft-liu-lsr-isis-ifit-node-capability-02]
Thread-Index: AQHWCTocjQ5490kuCEOn6C2rZSeArahnH9QA
Date: Fri, 03 Apr 2020 10:14:17 +0000
Message-ID: <4764_1585908857_5E870C79_4764_208_1_53C29892C857584299CBF5D05346208A48E0BE48@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
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>
In-Reply-To: <3DFEBF57-427E-425E-B5D2-48F683519D16@chopps.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/DaHQAGBBbBhgLOlUQpp9tQPWb64>
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:14:24 -0000

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.