From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Saturday September 30, 19100 @ 2:30
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/notes
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
proto.txt
Log Message:
more rigorous communication at bottom
*****************************************************************
File: openprivacy/htdocs/notes/proto.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/proto.txt?annotate=1.9
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/proto.txt?rev=1.9&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/proto.txt.diff?r1=1.9&r2=1.8
-----------------------------------
Index: openprivacy/htdocs/notes/proto.txt
diff -u openprivacy/htdocs/notes/proto.txt:1.8 openprivacy/htdocs/notes/proto.txt:1.9
--- openprivacy/htdocs/notes/proto.txt:1.8 Fri Sep 22 14:40:59 2000
+++ openprivacy/htdocs/notes/proto.txt Sat Sep 30 02:30:50 2000
@@ -1,6 +1,6 @@
Protocol ideas and solutions
-$Id: proto.txt,v 1.8 2000/09/22 21:40:59 fen Exp $
+$Id: proto.txt,v 1.9 2000/09/30 09:30:50 fen Exp $
Contributors:
Fen Labalme <fen@openprivacy.org>
@@ -77,3 +77,24 @@
7.
+---
+
+ 1) User has browser and OP Client (Primary Agent, or PA) locally
+ 2) PA has local profile Dx and primary nym (Nx, e.g., N1, N2, N3) storage
+ (TBD: format of this storage)
+ 3) PA creates J1 from N1 for communicating with the net
+ 4) PA onion-routes to Secondary Agent (SA) sending P1 = J1(D1)
+ (TBD: are PA and SA two halves of one cooperating agent? I think yes)
+ 5) SA has cookie jar for J1 (associated wirh profile data D1)
+ SA creates cookie K | K = {SA, J2} and associates J2 with J1
+ 6) SA communicates with JetSpeed using cookie K
+ 7) JetSpeed stores {K, D1} profile in PSML data cache
+ 8) (TBD) assume some query agent QA gains access to PSML data
+ QA has offer O = {template T, reward $} to match against PSML data cache
+ 9) QA discovers K is a match! (remember K = {SA, J2})
+10) QA sends message to SA: tell owner(J2) that $ available with proof of T
+11)
+
+Q1) Can J1 separate profile into separately publishable chunks? (J2, J3...)
+
+Q2) Given J2 profile data, how is nym N contacted?
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST