Friday, April 2, 2010

Re: [Geopriv] Deploying authorization policy

>
> One thing that I believe where some misunderstanding starts is that
> users are expected to hand around new URLs all the time (whenever they
> fetch new onces from their LIS). This is in theory possible but in
> practice that might be difficult. Instead, it is more likely that one
> would want to publish location to a server that fulfills already other
> rules (such as a presence server alike concept; you could even call
> Yahoo's FireEagle, Ovi Chat, Google's Latitude). Other uses have a
> long-term contact point to go to for many reasons already.

On a side note: One of the problems with by-possession URLs is that the semantics are not always clear to the user. In other words, by looking at the URL, users can't tell that they are giving away their location, for example. People include URLs in email messages, Twitter posts and web pages all the time, without fully understanding the semantics and the consequences. I suspect people would be upset if

http://www.facebook.com/henning.schulzrinne

just gave public access (as it does today), while

http://www.facebook.com/henning.schulzrinne/293590D256FBEE1F75E816

gave full access to everything, without further authentication.

Henning
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv