yvr is out for me, but i would gladly participate in a workshop.   i'm 
concerned about the blanket use of security/crypto pixie dust
to ensure privacy…   some things, as Ted mentioned in another thread, don't 
need privacy - like time or routing.

/bill


On 10September2013Tuesday, at 11:35, Spencer Dawkins at IETF wrote:

> Hannes, if we have not solved all the problems such a workshop(*) would 
> address by December, I would certainly support a workshop in something like 
> the London IETF timeframe :-)
> 
> Spencer
> 
> (*) and this is not the first time I've said something snarky and then 
> supported a workshop you've proposed, either!
> 
> On Tuesday, September 10, 2013, Hannes Tschofenig wrote:
> I suggested within the IAB to do a workshop* (before the meeting), which 
> would give us an extra day of intense discussion time. Unfortunately, it is a 
> bit close to the next meeting (which  complicates travel planning) and some 
> folks have booked their trip already...
> 
> Despite all the discussions I fear that a BOF slot will make it very 
> difficult to discuss such a broad topic and to make some progress.
> 
> Ciao
> Hannes
> 
> (*): I know that it is not the first time I have suggested a workshop.
> 
> On 10.09.2013 21:03, Scott Brim wrote:
> On Mon, Sep 9, 2013 at 12:39 PM, Peter Saint-Andre<[email protected]>  wrote:
> We'll want to use the high-bandwidth time wisely, and we know that
> security-related discussions (well, all discussions) can easily go off
> track. Staying focused on the core issues, and on problems that might
> have engineering solutions, will be paramount.
> 
> This is a scope question.  How do we decide what to focus on?  I
> suggest that we start by saying it's not security, and it's not
> surveillance, it's privacy, i.e. the ability to control the flow of
> one's personal information (there's your definition, Dave).  Security
> is too large a scope, while surveillance is too small.
> _______________________________________________
> perpass mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/perpass
> 
> _______________________________________________
> perpass mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/perpass
> _______________________________________________
> perpass mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/perpass

_______________________________________________
perpass mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/perpass

Reply via email to