Re: remote participation

[Alessandro Amirante <[e-mail]>]

Il 13/11/18 02:41, Ted Lemon ha scritto:
> Several people have pointed out that they weren't able to access the
>  Meetecho Jabber, 
There's no Meetecho Jabber room. Meetecho relays the IETF official 
jabber channels (e.g., [e-mail]).
We have not been reported of people having problems accessing Meetecho 
during the last meeting. If you know such people, Ted, can you please 
ask them to get in touch with us so we can see what happened and sort it 
out?

> and also that the way it handles names isn't ideal.

I'm not sure I get what you mean by "handling names", but please address 
any feedback to the Meetecho team. The IETF remote participation 
platform has improved a lot over the years thanks to the precious 
feedback received by the IETF community. All feedback we receive is 
taken into consideration for the upcoming meetings.

>  I wasn't able to access it because I didn't have an access code
> handy and didn't want to register for remote access when not remote.

As I already said in another thread, all information you need is your 
name and your Registration ID, which is also printed on your badge if 
you're on-site.

Alessandro

>  XMPP-over-Websocket?
> 
> On Mon, Nov 12, 2018 at 8:30 PM Spencer Dawkins at IETF 
> <[e-mail]
> <mailto:[e-mail]>> wrote:
> 
> Just to drill down on one point ...
> 
> On Wed, Nov 7, 2018 at 2:40 PM John C Klensin <[e-mail] 
> <mailto:[e-mail]>> wrote:
> 
> 
> 
> --On Wednesday, November 7, 2018 14:46 -0500 Sandra Murphy 
> <[e-mail] <mailto:[e-mail]>> wrote:
> 
>> Are we mandating the use of meetecho for remote participation? Are
>> those who still use jabber+audio just out of luck?
> 
> I hope not.  At the same time, I see a difference between relatively
> passive remote participation in which someone observes, tracks
> documents, participates on the mailing list, makes an occasional
> comment in a WG meeting, etc., and really active participation in
> which someone might be editing WG documents, taking one leadership
> roles such as WG co-chair or secretary, participating in complex
> directorate discussions, and so on.   If we needed to require that
> someone either be f2f or have enough technology and technology
> available to run Meetecho, I, at least, wouldn't be enthused but
> wouldn't lose a lot of sleep over it either.
> 
> 
> For several years, I carried a Chromebook to IETF meetings, and this 
> was long enough ago that I couldn't run an Android client on my 
> Chromebook (which works now), much less something like Pidgin (which 
> should work as soon as I get my Chromebook sorted for Unix, and I 
> don't think that's far in the future)...
> 
> So I was really aware that Meetecho  provides the jabber room in a 
> separate window - that's usually how I accessed the Jabber room.
> 
> Given that, plus Meetecho using HTML5 for video, etc., what kind of 
> use case are we talking about, where someone can use the audio stream
> plus a jabber client, but can't use Meetecho?
> 
> I'm willing to believe this is a real constraint, I'm just trying to 
> understand what problem we're solving, and if the answer is "we've 
> got most or all of the technology we need to solve these real 
> problems for remote participants without retraining humans, which can
> improve things but not to the point of perfection", that would be
> helpful to know.
> 
> Spencer
> 

-- 
Ing. Alessandro Amirante, Ph.D.

Meetecho S.r.l.
www.meetecho.com

Via Riviera di Chiaia 124
80122 Napoli, Italy

Mobile: [phone]
E-mail: [e-mail]