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

Robert Raszuk <robert@raszuk.net> Thu, 02 April 2020 22:34 UTC

Return-Path: <robert@raszuk.net>
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 8AAEF3A1B58 for <lsr@ietfa.amsl.com>; Thu, 2 Apr 2020 15:34:44 -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, 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=raszuk.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 z888o1hjFJpC for <lsr@ietfa.amsl.com>; Thu, 2 Apr 2020 15:34:42 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 A3EA73A1B56 for <lsr@ietf.org>; Thu, 2 Apr 2020 15:34:42 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id e4so4348426oig.9 for <lsr@ietf.org>; Thu, 02 Apr 2020 15:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1P/D0PasCLWsZGB1aCM02bHIJoR7C2Axhn5bjF9cdMQ=; b=fj+mD1YOeIO2FzSvNocamWilWSsCLyHqwK4U9bjirYxgTCAUxUq+I7IH4cUwgrQ1KZ ul7vaIPS+WwFmHaCFG7Oyuh0ZcsiX3oGg4XsRJS3PIms8+HoyD1O96CF8FFp2P268Lyv AT4/E24LJ1wulehGEFVhhQYSV2bWzqrm1iELRiR9R6+bc6Usa2wEPEzLPVGOra4AeRT2 rYlNrK3P6kQ0NPkwuHpdPDKqQVOvaZqxmkxJx/F5GFy51S651bQriNWSZesFsC1WyBWk 67X308TCqo6E2djilVoEUEThL3npKvHi00kCcThN9qeU3S4kB7qo3SVOzo7tVzDBRwke kjdQ==
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=1P/D0PasCLWsZGB1aCM02bHIJoR7C2Axhn5bjF9cdMQ=; b=skFuguOzcGtwanNTV6qtiTAKN36NX34cetMKXk56PzB4FMBoZa3uSXJmvAr5f2s3kI 5ZcOUgDI429lgWyW2vSuD38M98Z0fLXVdPyyZG4Kn8MrXhDkQvue1ehmw2/ueqxaPGaV q7sY1ogrKcpSIvx4XnW3fIpdGGyXtRcSbHXBQ9jc4vkh3HlzEwlue7FoJFyoxRGYcalz aKFL9+ZwQdeY2uNLeKTnIEmeft+DkJEXJGnYFKEBggykul6OgqyHbfDA6IxwcgvwmnOq j+aWEX/X/0Bvt/hVR7O7MPHpH9bfKeR3aRVPG6sUd7xz+tmToHwEDmye9e5wmof5pyns SYOg==
X-Gm-Message-State: AGi0PuZCq7khFfmfym+5m1AaCmMP+3I6Cx8qV/izEaVxI124YJxyk3sq n1XgD2wnG+UOWoC2POQQXXfwyfm+sk56CKtpnbT2WA==
X-Google-Smtp-Source: APiQypIkvdE61Yg0PuO4MBg/3bgNR3Qsjt4xcB3xGDOFRnnXJlShIJh7hZ38nLCX4wnoOoPnVvZMTjt/LfhHcMA2rrA=
X-Received: by 2002:a05:6808:4e:: with SMTP id v14mr1038447oic.70.1585866881818; Thu, 02 Apr 2020 15:34:41 -0700 (PDT)
MIME-Version: 1.0
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> <CAOj+MMFqoVrWY2K4DJ6_1Kmdu4gv6jwm6c3q_HOTTSCSY7U_3A@mail.gmail.com> <40DA7CC2-5EAA-4539-AEEF-6BD5827C6FBB@cisco.com>
In-Reply-To: <40DA7CC2-5EAA-4539-AEEF-6BD5827C6FBB@cisco.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 03 Apr 2020 00:34:32 +0200
Message-ID: <CAOj+MMExfWg8SBZ9DRAnZdiA=t2XA7kuT==-T-okVS9b8dYbag@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: Christian Hopps <chopps@chopps.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>, Tianran Zhou <zhoutianran@huawei.com>, wangyali <wangyali11@huawei.com>
Content-Type: multipart/alternative; boundary="00000000000027021105a256687d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/7FdgCqIm8ha8XWzPaEW6JliVqNI>
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: Thu, 02 Apr 2020 22:34:45 -0000

Well I did not knock (notify the host and politely ask to join) as I
assumed IETF WG meeting doors should be open. I figured maybe host just
does not like me to join the party :-)

I think my mistake was that I did not expect password to be needed. Learned
something new then !

Cheers,
R.

On Fri, Apr 3, 2020 at 12:22 AM Acee Lindem (acee) <acee@cisco.com> wrote:

> As host of the meeting, I didn’t see any indication that you were waiting
> in the lobby.
>
> Thanks,
>
> Acee
>
>
>
> *From: *Robert Raszuk <robert@raszuk.net>
> *Date: *Thursday, April 2, 2020 at 6:10 PM
> *To: *Christian Hopps <chopps@chopps.org>
> *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@cisco.com>, wangyali <
> wangyali11@huawei.com>
> *Subject: *Re: [Lsr] problem joining interim [Re: A new version of I-D,
> draft-liu-lsr-isis-ifit-node-capability-02]
>
>
>
> Hi Chris,
>
>
>
> I never noticed the password ...
>
>
>
> Just few days back I participated in IDR and no password was needed or
> perhaps webex invite link contained a token relaxing from needing one.
>
>
>
> Cheers,
> R.
>
>
>
> On Fri, Apr 3, 2020 at 12:00 AM Christian Hopps <chopps@chopps.org> wrote:
>
>
>
> > 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. 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
>
>