On 9/8/10 9:48 AM, Michael Richardson wrote:
>>>>>> "Joel" == Joel Jaeggli <joe...@bogus.com> writes:
>     Michael> I don't think we've got either the database of "people not
>     Michael> attending because of costs" nor a good model for factoring
>     Michael> them in if we did (e.g. N pnac's times some percentage who
> 
>     >>> Do we at least have a list of people who attended remotely?  (I
>     >>> don't think so)
> 
>     Joel> we can tell you that the peak concurrence of remote attendees
>     Joel> on the audio is an order of magnitude smaller than the actual
>     Joel> concurrence (e.g.  typical peak is around 100 conccurent
>     Joel> remote listeners). vs ~1200 attendees and 750-800 simultaneous
>     Joel> radio associations during a busy meeting window.
> 
>     Joel> total remote attendees over the course of the week is probably
>     Joel> higher, but that data is a lot more ambiguous since users
>     Joel> probably have more than one ip address and potentially more
>     Joel> than one user-agent over that time frame.
> 
> I'll bet the number of dynamic IP addresses amoung IETF remote attendees
> is very small :-)

actually I think you'd be wrong, you don't have to be time shifted by
very much to switch from streaming in the office to streaming at home,
and then you get laptops versus desktops. if you sit in one location the
whole time then yeah the external ip address on your nat box is probably
stable.

> One could look at coordinating the voice session with any simultaneous
> login to the datatracker.

It has been our practice to minimize the amount of date we collect, and
not associate it with other datasets that would result in being able to
uniquely identify individuals. 2 months worth of hand-wringing
discussion on the IETF list suggests that we were justified in
exercising our fiduciary responsibility in that fashion.

listener's can't contribute to the discourse except through some other
channel and don't sign the bluesheets. and since there's an archive
however poor it is they may well be timeshifted by days, hours, or years.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to