Re: [Tools-discuss] updating interim meeting with webex

Bob Hinden <> Fri, 03 April 2020 16:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 313B03A0755 for <>; Fri, 3 Apr 2020 09:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pBnz3bGAd2Vn for <>; Fri, 3 Apr 2020 09:46:51 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0C9083A074E for <>; Fri, 3 Apr 2020 09:46:51 -0700 (PDT)
Received: by with SMTP id f6so8440214wmj.3 for <>; Fri, 03 Apr 2020 09:46:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8Ye4uUmIm+cMPyyu/xE9A2dIIRidDJelWQYd8bpvJ+0=; b=E7wtgPInaftF1+fHlEtLHsYrvSswOaAG/kP4gNaqRCG3xGtxpvGOHWXKx0BsICld+9 yoFGe+LaPol1PcJwK49wNcPC9hFhxXaqG9L2a6fyKOGRDQ2g9sUPVG6Kfr1ZB6hOLkzC 7rj32FuQs/Z8sdQlQIT4dbOSuIQWpmUDh6jLcE9VHDlOkpSOfwNDn6tfce3wyNa2W5Ms 5DJgHrmyWbEEeYo0VD/IaxnbvKjesm1J1oPXZu2Su4hT90oZCRZVI7OD4G47iyyjV8Cg 3L48LIoqD6/zM0F9D/x0f1C9C07XCiz+jzYoJESMzbQNrMECXSol7vUQl67HI1aMoBw+ JD7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=8Ye4uUmIm+cMPyyu/xE9A2dIIRidDJelWQYd8bpvJ+0=; b=AbRMohEcUYmbjFd99tu4COpvO6+vPy1O7VOf1YfzKw+pC+TelVkw64si5Za8WUC72X +MjKgaPreRhSE3zHggjqvzzGpzbfad6zIlCbPWFJaH5yhARB0H2C/aDlzuSx53VGs5IH tNIzFw261ggPBlae5VQg9h1uiR9MAffplwqt6zNBpmS2lQj7AMLeBMRsSiuQzFULU2+S ZGBCPFk1ZpKPy4toyaY+vparRVc14MXj3L0oaWiLa0Ypv7zVJUxTMq3Dx2mCeh4LOTcP WJxlVb4tEWutow35yXodSfQKneNP582qGrMxhnxaQwf0/LSqazrBpdgyJqi7vxXdggOw dspg==
X-Gm-Message-State: AGi0PuZsT7u6aTbDalTEINq9i/Az6wx++4DYCbnPvHLOcfkM3NqZKpPK 8/Y1hqULrk98S6EpYAuA4EhDE8etKjw=
X-Google-Smtp-Source: APiQypKI8Zpf2W/xriViHQkxejL9vdHoKa0nDSc3u8RFcH0oUdIceRLzn/hnVLNBGjWKZkElOQfnmw==
X-Received: by 2002:a1c:2842:: with SMTP id o63mr9542269wmo.73.1585932407921; Fri, 03 Apr 2020 09:46:47 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:b401:f1b5:b3da:f68? ([2601:647:5a00:ef0b:b401:f1b5:b3da:f68]) by with ESMTPSA id w4sm11948038wmc.18.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Apr 2020 09:46:46 -0700 (PDT)
From: Bob Hinden <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_F4E60B1D-04AC-492C-9C65-7606CFCC8013"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Fri, 3 Apr 2020 09:46:41 -0700
In-Reply-To: <>
Cc: Bob Hinden <>, Henrik Levkowetz <>, Christian Hopps <>
To: Tools Team Discussion <>
References: <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <>
Subject: Re: [Tools-discuss] updating interim meeting with webex
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 03 Apr 2020 16:46:53 -0000

To add to this a little, we had a 6MAN interim meeting last Tuesday.   Earlier we submitted a request and the AD approved it.   I think that sent an email to the mailing list.  But it did not create a Webex session.

I contacted the secretariat about that.  They created a 6MAN Webex account and answered a few questions.   I logged into Webex and created a Webex session for the meeting.   I then email the w.g. list with the Webex info and updated our agenda to include it (along with other info like the etherpad page and jabber room).

As far as I could tell, there wasn’t any way to add this information to the page reached from the upcoming interim meeting page when we did this.

I just looked again at:

Now it shows all of the links for Webex, materials, etc.   This is much better.   Thanks for fixing this!


p.s. Minor issue, but perhaps there is a better icon for Webex than a “phone handset” icon….

> On Apr 3, 2020, at 5:16 AM, Christian Hopps <> wrote:
>> On Apr 3, 2020, at 8:00 AM, Henrik Levkowetz <> wrote:
>> Hi Christian,
>> On 2020-04-03 13:13, Christian Hopps wrote:
>>> Hi Henrik,
>>> Also worth mentioning on the experience, not assigning your webex
>>> details get's the scheduled email sent from iesg-secretary with a
>>> link pointing to a webex room for the WG which simply queues folks up
>>> to be ignored while the actual meeting is running.
>> Huh.  Was this because the webex room for the WG didn't function, or
>> because there wasn't a chair there?
> It's not clear to me yet what was happening. The generic link appears to put the user in a waiting room (waiting on being let in by the host), I don't know if that person was somehow "let in" if they would enter the scheduled meeting or not. I did notice a webex created email sent to lsr-chairs during the meeting for one person (Bruno), I then looked at our current participants and saw him there so that was that.
> After the meeting we were informed by another user that they tried 3 times and were placed in the waiting room 3 times and then gave up. We never received any email for this person.
> I'm not even sure that the waiting room they are being stuck is for the scheduled meeting we were running anyway. I think this might just be like a general way to connect with the "lsr" webex user (like a phone call)?
>>> The email auto generate function should probably not include a
>>> generic link the WG webex account as it does the wrong thing.
>> Ok; however that begs the question of why not use the WG webex account
>> for the interim?
> We did, this was a scheduled meeting made by the LSR account. Here's something from the user who eventually got into the running meeting (Bruno):
>> 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: "
>> 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
>> 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
> Aha! so it appears maybe we got the email about Bruno b/c he clicked "Notify the host"? I bet the other user (Robert) never clicked that, so we got no email. It's not clear what would have happened even if we had invited Bruno in, maybe b/c the LSR user was in the scheduled meeting it would have brought him in to that meeting as well, but that's only hoping.
> In any case having the links default behavior be to stick users in a queue with no notification to the WG account means we probably shouldn't advertise that link.
> Thanks,
> Chris.
> ___________________________________________________________
> Tools-discuss mailing list
> Please report and
> bugs at
> or send email to
> Please report bugs at
> or send email to