IETF Logo Mail Archive

Re: Registration details for IETF 108

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 13 June 2020 21:20 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53AFE3A0EC3 for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2020 14:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 fIcEL2Sv2mld for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2020 14:20:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E6943A0EC1 for <ietf@ietf.org>; Sat, 13 Jun 2020 14:20:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2DB5F389E2 for <ietf@ietf.org>; Sat, 13 Jun 2020 17:18:16 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gXqhuE5Gtmh5 for <ietf@ietf.org>; Sat, 13 Jun 2020 17:18:15 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E0929389C9 for <ietf@ietf.org>; Sat, 13 Jun 2020 17:18:14 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C90A34D0 for <ietf@ietf.org>; Sat, 13 Jun 2020 17:20:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 'IETF Rinse Repeat' <ietf@ietf.org>
Subject: Re: Registration details for IETF 108
In-Reply-To: <602817EB7E0004CD1FD5CCC5@PSB>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <01d701d638ca$c096b5e0$41c421a0$@gmail.com> <CABcZeBOLAw_9s-gobFYB=5THu_Q70UmDLn_ZhVXhNRHN_nu_0w@mail.gmail.com> <607b7682-0a75-62b6-fd0e-5e2e1171a68b@cs.tcd.ie> <CA+9kkMBEqhn115ToB0SwOGavmXze4DdJdL941J4LeVMRrPngpQ@mail.gmail.com> <e1b804ae-4c2e-fdf3-8804-47820d35facf@cs.tcd.ie> <CA+9kkMC8ZWHaCBg=WzwtriVf-3bq=egupVgAH-J7dSqspwLoFw@mail.gmail.com> <a19c3066-bfa7-ded2-d98f-b5e367645451@cs.tcd.ie> <E8BE49F8-6FE8-4470-9314-21F8BFE9768A@gmail.com> <1UWAyqDxFn.1IOJoXgqe8i@pc8xp> <m2tuzpz0eg.wl-randy@psg.com> <94fdbedd-358b-7fae-c784-9550311d8aea@gmail.com> <m2h7voztz5.wl-randy@psg.com> <6F3828AD-FFE3-4331-8E76-E212F1357919@gmail.com> <m2ftb1reu1.wl-randy@psg.com> <2E2893AA-2BCC-4EA1-AF31-0B4BA437C46F@csperkins.org> <m2d065rcjt.wl-randy@psg.com> <496648EA-4D97-44CA-B45A-7AAC283A1025@ietf.org> <00b801d640f9$5afe7bf0$10fb73d0$@acm.org> <602817EB7E0004CD1FD5CCC5@PSB>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 13 Jun 2020 17:20:46 -0400
Message-ID: <8281.1592083246@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0raQO5s__YQ__zqUOQVoHBdtsBQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jun 2020 21:20:51 -0000

John C Klensin <john-ietf@jck.com> wrote:
    > Moreover, unless something has changed that you or Jay know
    > about but I don't, prior experience with Meetecho strongly
    > suggests that, if we discover deficiencies that we would like to
    > have corrected before IETF 108 and give them reasonable notice,
    > the chances of getting those changes made are quite good.
    > Having tried, in non-IETF contexts, to work with the providers
    > of three or four of the systems Diplo lists to get bugs or
    > unfortunate features fixed, a year or two might be plausible,
    > but not six weeks... unless , of course, one is a government
    > making demands and/or threats.

And, I think that I need to repeat that I was unable to file a real bug
report when webex stopped working for desktops with public IPv4.
I got no acknowlegement of my bug, and I have no idea what the problem is.
It's been like 6 weeks now.
And it's not like we don't know people who know the webex people.
I'm hardly surprised that zoom ate their lunch.
I am observing many paying customer abandonning gotomeeting; I'm not sure
why exactly, as it had a lot of advantages.

Allusions were made that it's my browsers' fault, but I note that all the
other webrtc based services continue to function fine.  Some even prefer IPv6.

I guess I can try removing my mitigation during the next call I'm involved
in, and see.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email