I understand that you don't like process. Who does? 

The good thing is that there is very little process (or even no process) for 
you. The additional effort is for those who run the experiment and maybe they 
come to the conclusion that there is no risk for others. 

Ciao
Hannes

-------- Original-Nachricht --------
> Datum: Fri, 9 Jul 2010 08:16:36 -0700
> Von: Joel Jaeggli <joe...@bogus.com>
> An: Hannes Tschofenig <hannes.tschofe...@gmx.net>
> CC: "ietf@ietf.org" <ietf@ietf.org>
> Betreff: Re: Comments on <draft-cooper-privacy-policy-01.txt>

> With all due respect the geopriv held experiment at ietf71 could have been
> done anywhere, and had no impact on participants who were not involved in
> them.
> 
> I have zero interest in building process that might impede the activity of
> people conducting protocol experiments that occur effectively in
> isolation.
> 
> Joel's iPad
> 
> On Jul 9, 2010, at 7:39 AM, "Hannes Tschofenig"
> <hannes.tschofe...@gmx.net> wrote:
> 
> > Randy, 
> > 
> > this privacy policy effort is not a means to put someone in the
> spotlight because a mistake has been made. 
> > 
> > I think it is good that we do all sorts of experiments with the IETF
> network and use it for research purposes. 
> > 
> > Still, if someone wants to do their tests then they should do it in an
> open and transparent fashion and tell people what they do. The writeup
> should then contain information like
> > * what data is collected
> > * what is the purpose
> > * how long is it stored
> > * how is responsible 
> > * how does the opt-in procedure work
> > 
> > It would also be nice to hear the results of the effort afterwards as
> well. 
> > 
> > Without listing other persons efforts I would like to mention the
> location server experiment a few of us did from the GEOPRIV working group. I
> don't recall anymore how we announced it and what we said in our announcement
> (it was a few years ago already) but a document like the one written by
> Alissa would have helped us. Richard Barnes might remember the details.  
> > 
> > Ciao
> > Hannes
> > 
> > -------- Original-Nachricht --------
> >> Datum: Fri, 09 Jul 2010 21:28:43 +0900
> >> Von: Randy Bush <ra...@psg.com>
> >> An: "Hannes Tschofenig" <hannes.tschofe...@gmx.net>
> >> CC: ietf@ietf.org
> >> Betreff: Re: Comments on <draft-cooper-privacy-policy-01.txt>
> > 
> >>>>> And "yes" we have researchers looking into the traffic, people
> storing
> >>>>> all sorts of data, etc.
> >>>> 
> >>>> we do?  about our traffic on the ietf meeting network?  stuff other
> >> than
> >>>> the _ephemeral_ data the noc ops use to manage the network?
> >>> 
> >>> Yes, the IETF meeting network. 
> >> 
> >> cites, please.
> > 
> > Remember the discussion about the RFID experiment, the location server
> experiment, 
> >> 
> >>>>  o there is no plan known by the net ops to do so in maastricht or
> >>>>    beijing at either of those meetings.
> >>> 
> >>> I don't know. There is no central place where I could lookup any of
> >>> this info. 
> >> 
> >> but you suspect the worst?  i am on the noc ops team.  you can trust my
> >> statement or not.
> > 
> > I don't suspect anything. I believe it is good if people use the network
> for all sorts of tests, if they tell us what they do. 
> > 
> > 
> >> 
> >>>>  o aside from issues in the wireless deployment, the data about net
> >> use
> >>>>    at ietf meeings seems pretty boring to me from a research view
> >>> 
> >>> Maybe boring for you. 
> >>> Some consider it a very large WLAN network, some others test their
> >>> favorite tunneling technology with it, etc.
> >> 
> >> that is not gathering data on others' use of the network.
> >> 
> >> randy
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> > 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to