ietf
[Top] [All Lists]

Re: Registration for remote participation

2017-05-09 17:06:51
In general, this looks fine to me.  I don’t believe any of the questions are 
particularly invasive, and I can see the utility of each of them (except Title, 
but that’s a cultural thing).

A few remarks inline

On 9 May 2017, at 22:01, IETF Chair <chair(_at_)ietf(_dot_)org> wrote:

Remote participants would be required to register (for free) by providing the 
information below (* denotes required fields). Registration would be 
mandatory to access MeetEcho sessions in real time and to join the remote mic 
queue during a session.

Title
First / Given Name*
Last / Family Name*
Company / Organization
ISO 3166 Country of Residence*
Email*
Gender
Have you attended an IETF meeting in person before?
Have you attended an IETF meeting remotely before?

The last two questions seem to be about gathering statistics (as is the country 
of residence). I’m wondering if it wouldn’t make sense to add a question about 
why the participant is remote (too much travel, too much money, avoids going to 
country X for whatever reason).

Upon registering, participants would be issued a registration ID, just as 
they are today.

To join a session, participants would be asked to input the registration ID. 
The same email-based facility that is currently available to retrieve a 
forgotten registration ID would continue to be available. The cookie-based 
“Remember me” option would also still be available. The only difference from 
how login works today is that the option to "Join without registration ID" 
would be removed.

Does this mean that unregistered people would not be able to listen/view?  I’m 
fine with cutting off *participation*, but even before Meetecho we’ve had a 
live (audio) stream from the room. I wouldn’t want to lose that.  Recordings 
are good, but by the time you listen to a recording, the conversation may have 
moved on.

If they are primarily folks in the hotel, who can't be in two rooms at once, 
we have one set of issues; if they are primarily folks at the end of low 
bandwidth, high RTT paths to the venue, we have a very different set of 
issues.  We also don't know reliably whether we have a small coterie of very 
dedicated remote participants or a wide smattering of folks dipping their 
toes in for a session or two.  

I’m not sure you’d be collecting enough data for that. Specifically the country 
of residence is not enough.  It’s not so much that the US is high bandwidth and 
Russia is low bandwidth. It’s more that New York, Moscow, and San Francisco get 
high bandwidth, while Orem, UT and Donetsk might get a lot less.

Yoav