W3C home > Mailing lists > Public > public-web-security@w3.org > September 2015

Re: A Somewhat Critical View of SOP (Same Origin Policy)

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Fri, 25 Sep 2015 12:08:14 +0200
Message-ID: <CAKaEYhLqpFB+ZHNGBzCTU0SPHj+bu-GNrkd_5e_vSqxTpVEeQg@mail.gmail.com>
To: Dave Raggett <dsr@w3.org>
Cc: Dave Longley <dlongley@digitalbazaar.com>, Martin Paljak <martin.paljak@ria.ee>, public-web-security@w3.org
On 25 September 2015 at 11:38, Dave Raggett <dsr@w3.org> wrote:

>
> On 24 Sep 2015, at 22:02, Dave Longley <dlongley@digitalbazaar.com> wrote:
>
> We also need to be careful about the privacy implications here. To
> explain this I'm going to lay out some quick terminology for a
> user-centric system.
>
> In the Credentials CG work, we have four main parties that are involved
> in a "credentials ecosystem". Here's a brief overview:
>
> 1. Users - entities about which claims are made
> 2. Issuers - services that make claims
> 3. IdPs - services that aggregate claims on behalf of Users
> 4. Consumers - services that request and make use of claims
>
> Now, regarding privacy, it would be ideal if a User could interact with
> Consumers without Issuers or IdPs being made aware of this fact. If
> information is going to be transferred "server-to-server", this property
> should be preserved.
>
>
> A further desirable property would be that the identifiers used between
> the User and Consumer are short lived (i.e. session based), to minimise
> loss of privacy across sessions or across Consumers.
>

There are times when you would certainly wish to use short lived
identifiers, for example, when the user does not want to be tracked.  But
just as in the real world, there are times when the user will have a
relationship with the consumer, so that the experience can be personalized
to an individual's tastes.  If we consider the real world, both cases are
quite common.


>
> —
>    Dave Raggett <dsr@w3.org>
>
>
>
>
Received on Friday, 25 September 2015 10:08:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:09:38 UTC