CVS update: openprivacy/htdocs/papers

From: cvs@openprivacy.org
Date: Wed Mar 07 2001 - 08:20:29 PST

  • Next message: cvs@openprivacy.org: "CVS update: sierra/src/sql"

    Date: Wednesday March 7, 19101 @ 8:20
    Author: fen
    CVSWEB Options: -------------------

    Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi

    View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/papers

    -----------------------------------

    Update of /usr/local/cvs/public/openprivacy/htdocs/papers
    In directory giga:/tmp/cvs-serv15236

    Modified Files:
            200103-white.html
    Log Message:
    minor changes prior to publication

    *****************************************************************
    File: openprivacy/htdocs/papers/200103-white.html

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/papers/200103-white.html?annotate=1.52

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/papers/200103-white.html?rev=1.52&content-type=text/x-cvsweb-markup

    CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/papers/200103-white.html.diff?r1=1.52&r2=1.51

    -----------------------------------

    Index: openprivacy/htdocs/papers/200103-white.html
    diff -u openprivacy/htdocs/papers/200103-white.html:1.51 openprivacy/htdocs/papers/200103-white.html:1.52
    --- openprivacy/htdocs/papers/200103-white.html:1.51 Tue Mar 6 20:52:53 2001
    +++ openprivacy/htdocs/papers/200103-white.html Wed Mar 7 08:20:29 2001
    @@ -9,7 +9,7 @@
       </head>
       <body bgcolor="#ffffff">
     
    - <!-- $Id: 200103-white.html,v 1.51 2001/03/07 04:52:53 fen Exp $ -->
    + <!-- $Id: 200103-white.html,v 1.52 2001/03/07 16:20:29 fen Exp $ -->
         
         <center>
         <h1>OpenPrivacy - Enhancing the Internet with Reputations</h1>
    @@ -38,13 +38,13 @@
         <h2>Abstract</h2>
         <blockquote>
           <p>
    - OpenPrivacy.org is building an Internet platform to take us into the
    - next age - the age of personalized information. Basic to this goal
    - is a platform that will provide people with complete control over
    - their personal information and aid them in protecting their privacy
    - while simultaneously enabling more efficient data mining by
    - marketers and the access to highly desirable market segments by
    - advertisers.
    + OpenPrivacy.org is building an Internet platform to take us into
    + the next age - the age of secure personalized information. Basic to
    + this goal is a platform that will provide people with complete
    + control over their personal information and aid them in protecting
    + their privacy while simultaneously enabling more efficient data
    + mining by marketers and the access to highly desirable market
    + segments by advertisers.
           </p>
           <p>
             OpenPrivacy creates a secure marketplace for anonymous demographic
    @@ -129,39 +129,40 @@
           </p>
           <p>
             OpenPrivacy provides a framework for building intercommunicating
    - systems that support the concept of <i>reputation</i>.
    - Reputations, which can be attached to any object such as
    - pseudonyms, purchase histories, physical objects (using an expanded
    - URI namespace), reputation servers, and even reputations
    - themselves, are pervasive and directly affect every aspect of
    - OpenPrivacy-enabled systems. One example of how this framework can
    - be used is as a customizable privacy-enhanced personal portal with
    - reputation-assisted search and publishing features [<a
    - href="#jets">jets</a>]. We are also creating reputation
    - calculation engines that will provide work-alike similarity for the
    - communities created by the likes of Slashdot and Advogato. Once
    - systems such as these are built on the OpenPrivacy platform, not
    - only with their users enjoy enhanced privacy and security from
    - spoof attacks, but they will also be able to publish selected
    - portions of their profiles for access by the members of these and
    - other communities. Likewise, advertisers can avail themselves of
    - targeted, high-quality profile information with the full
    - cooperation and confidence of a pseudonymous user; conversely, the
    - user can benefit from the targeted ads and promotions that will
    - result.
    + systems that supports the concept of <i>reputation</i> through
    + <i>opinion accumulation</i>. Opinions, which can be attached to
    + any object such as pseudonyms, purchase histories, physical objects
    + (using an expanded URI namespace), reputation servers, and even
    + opinions and reputations themselves, are pervasive and directly
    + affect every aspect of OpenPrivacy-enabled systems. One example of
    + how this framework can be used is as a customizable
    + privacy-enhanced personal portal with reputation-assisted search
    + and publishing features [<a href="#jets">jets</a>]. We are also
    + creating reputation calculation engines that will provide
    + work-alike similarity for the communities created by the likes of
    + Slashdot and Advogato. Once systems such as these are built on the
    + OpenPrivacy platform, not only with their users enjoy enhanced
    + privacy and security from spoof attacks, but they will also be able
    + to publish selected portions of their profiles for access by the
    + members of these and other communities. Likewise, advertisers can
    + avail themselves of targeted, high-quality profile information with
    + the full cooperation and confidence of a pseudonymous user;
    + conversely, the user can benefit from the targeted ads and
    + promotions that will result.
           </p>
           <h3><a name="rms">Reputation Services</a></h3>
           <p>
             We introduce a set of <i>Reputation Services</i> that form the
             cornerstone of the OpenPrivacy framework. These services provide a
    - standard reputation framework that can be used by any community,
    - supporting an unlimited number of mechanisms to create, use and
    - calculate results from accumulated reputation. The implementor of
    - these services can nest or reuse existing reputation calculation
    - engines or roll their own. They gain the ability to query remote
    - RCEs, to perform ontological forwarding, and share all or part of
    - their users profile database with other communities without
    - violating user privacy.
    + standard opinion and reputation framework that can be used by any
    + community, supporting an unlimited number of mechanisms to create,
    + use and calculate results from accumulated opinions, bias and
    + reputations. The implementor of these services can nest or reuse
    + an existing <i>Reputation Calculation Engine</i> (RCE) or roll
    + their own. They gain the ability to query remote RCEs, to perform
    + ontological forwarding, and share all or part of their users'
    + profile database with other communities without violating user
    + privacy.
           </p>
           <p>
             A reputation management system, which implements the reputation
    @@ -193,16 +194,17 @@
               platform, as anonymity can too easily be pierced by what is known
               as "data triangulation." For example, knowing only the age and
               zip code of a heretofore anonymous person, plus the make and
    - model of their car, can narrow the population quite a bit.
    - However, if each of these data points were stored under a
    - different nym, then the same data exists but cannot be connected
    - to a single person. Others can make opinions as to what data is
    - connected - and gain or lose reputation according to the value
    - and usefulness of their opinions - but only the owner can prove
    - it. Mechanisms exist that allow for such proof to be tied to a
    - single receiving party, such that further dissemination of the
    - proof without permission would directly - and adversely - affect
    - the reputation of the receiver.
    + model of their car, can narrow the population quite a bit, often
    + to one person. However, if each of these data points were stored
    + under a different nym, then the same data exists but cannot be
    + connected to a single person, nor even to each other. Others can
    + make opinions as to what data is connected - and gain or lose
    + reputation according to the value and usefulness of their
    + opinions - but only the owner can prove it. Mechanisms exist
    + that allow for such proof to be tied to a single receiving party,
    + such that further dissemination of the proof without permission
    + would directly - and adversely - affect the reputation of the
    + receiver.
             </p>
             <h4>Bias Management</h4>
             <p>
    @@ -253,19 +255,19 @@
           <h3>Communications</h3>
           <blockquote>
             <p>
    - We outline a course-grained capability-based framework in which
    - each nexus of reputation services - generally located one to a
    - hardware machine - is considered to be a secure computation
    - environment (or "vat" [<a href="#dist">dist</a>]) with respect to
    - itself. Communications between vats are signed and encrypted,
    - but also asynchronous and may be unreliable. Secure streams can
    - be built, analogous to the way in which SSL is implemented on top
    - of TCP, which is in turn implemented on top of UDP, but are not
    - required for operation. Note that communication channels, as
    - well as the objects they transport and reference, can themselves
    - gain or lose reputation capital according to their security,
    - reliability and speed. While we leave the specifics of the
    - communications implementation as outside the scope of the
    + OpenPrivacy implements a course-grained capability-based
    + framework in which each nexus of reputation services - generally
    + located one to a hardware machine - is considered to be a secure
    + computation environment (or "vat" [<a href="#dist">dist</a>])
    + with respect to itself. Communications between vats are signed
    + and encrypted, but also asynchronous and may be unreliable.
    + Secure streams can be built, analogous to the way in which SSL is
    + implemented on top of TCP, which is in turn implemented on top of
    + UDP, but are not required for operation. Note that communication
    + channels, as well as the objects they transport and reference,
    + can themselves gain or lose reputation capital according to their
    + security, reliability and speed. While we leave the specifics of
    + the communications implementation as outside the scope of the
               OpenPrivacy framework per se, we believe that a secure, anonymous
               and uncensorable mechanism such as those that Freenet, Free Haven
               or Publius [<a href="#free">free</a>] provide would be well



    This archive was generated by hypermail 2b30 : Wed Mar 07 2001 - 08:20:33 PST