John C Klensin <john-ietf@xxxxxxx> 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@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
