IETF Logo Mail Archive

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

Lou Berger <lberger@labn.net> Fri, 03 April 2020 10:38 UTC

Return-Path: <lberger@labn.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 E19AB3A0EC9 for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:38:55 -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, DKIM_SIGNED=0.1, DKIM_VALID=-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 (768-bit key) header.d=labn.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 NOUudaI0hOfv for <lsr@ietfa.amsl.com>; Fri, 3 Apr 2020 03:38:50 -0700 (PDT)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) (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 302D03A0EDB for <lsr@ietf.org>; Fri, 3 Apr 2020 03:38:49 -0700 (PDT)
Received: from CMGW (unknown [10.9.0.13]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 3B1C81E0981 for <lsr@ietf.org>; Fri, 3 Apr 2020 04:38:43 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id KJiljfnbptoKZKJiljL8MN; Fri, 03 Apr 2020 04:38:43 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.2 cv=fZrd8wYF c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=cl8xLZFz6L8A:10 a=Vy_oeq2dmq0A:10 a=r77TgQKjGQsHNAKrUKIA:9 a=2clOPd4PAAAA:8 a=ek1ZzK3JAAAA:8 a=48vgC7mUAAAA:8 a=vsKwVBCnwYRCdrt4bmgA:9 a=QEXdDO2ut3YA:10 a=6iOBHJr3kTuBEBdewuIA:9 a=T3ESAB07P4_svarW:21 a=_W_S_7VecoQA:10 a=M-nCPFs8X6IGXaTG_0vh:22 a=xQ-UgBqouqXb-DtQvhst:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=D17caXingsoXGEQGlvbC+WO8ODrIXBx8B6e/XIYohIU=; b=rgLu89SkMPJ5Q526ES8fzSiDx2 i5MT6DTE3IQxIzdoD8LV53ztj6MIMGTIkzYRL9I7n0O2/0lx1iMjiKdTMOjt22hJZiTUZNUz1rH13 yMsZUvygnP8ycL/AGlSiRgGsy;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:53582 helo=[11.5.0.140]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <lberger@labn.net>) id 1jKJik-001unm-Og; Fri, 03 Apr 2020 04:38:42 -0600
From: Lou Berger <lberger@labn.net>
To: Robert Raszuk <robert@raszuk.net>, Christian Hopps <chopps@chopps.org>
CC: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, lsr@ietf.org, Jeff Tantsura <jefftant.ietf@gmail.com>, Tianran Zhou <zhoutianran@huawei.com>, "Acee Lindem (acee)" <acee@cisco.com>, wangyali <wangyali11@huawei.com>
Date: Fri, 03 Apr 2020 06:38:41 -0400
Message-ID: <1713f9f0f68.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <CAOj+MMFqoVrWY2K4DJ6_1Kmdu4gv6jwm6c3q_HOTTSCSY7U_3A@mail.gmail.com>
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>
User-Agent: AquaMail/1.23.0-1556 (build: 102300002)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------1713f9f12ac798b277b8677cbf"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1jKJik-001unm-Og
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([11.5.0.140]) [72.66.11.201]:53582
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/yDrFuIrU_OxP7BZ_LZ_AIdNiyPE>
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:38:56 -0000

Fwiw I used the link in the agenda without issue.  I did the same for RAW 
last week.  Also, as host of a different wg interim right before lsr, I 
didn't have to do anything to let people in to the session - they just 
showed up....

Lou


----------
On April 2, 2020 6:10:43 PM Robert Raszuk <robert@raszuk.net> wrote:

> 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
>>
>
>
>
> ----------
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>

v2.23.0 | Report a Bug | By Email