CVS update: openprivacy/htdocs/notes/reputations

From: cvs@openprivacy.org
Date: Tue Dec 12 2000 - 18:58:32 PST

Date: Tuesday December 12, 19100 @ 18:58
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/reputations

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

Update of /usr/local/cvsroot/openprivacy/htdocs/notes/reputations
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes/reputations

Modified Files:
        requirements.txt
Log Message:
updated E - communications

*****************************************************************
File: openprivacy/htdocs/notes/reputations/requirements.txt

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

CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?annotate=1.22

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.22&content-type=text/x-cvsweb-markup

CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt.diff?r1=1.22&r2=1.21

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

Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.21 openprivacy/htdocs/notes/reputations/requirements.txt:1.22
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.21 Tue Dec 12 18:49:39 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 18:58:32 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.21 2000/12/13 02:49:39 fen Exp $
+$Id: requirements.txt,v 1.22 2000/12/13 02:58:32 fen Exp $
 
 Reputation Server Requirements: top level feature list
 
@@ -129,21 +129,26 @@
 
 E. === Communications ===
 
-communication encapsulation specification
- contains:
- capability you want to use (e.g., via a URI to a schema or DTD)
- payload (data conformant to the data format spec)
- session key (e.g., a pseudo-random number)
- some sort of TTL-like value (e.g., Freenet's hops-to-live)
+1. Agent discovery (in a distributed, peer-to-peer network)
+ a. local directory maintenance
+ i. initial trusted agents 'built-in'
+ ii. address book maintenence facility
+ b. find an agent pased on:
+ i. reputation
+ ii. capability(s)
+ iii. price, speed, ...
+
+2. Communication encapsulation - what a message may contain:
+ a. capability you want to use (e.g., via a URI to a schema or DTD)
+ b. payload (data conformant to the data format spec)
+ c. session key (e.g., a pseudo-random number, or perhaps the J)
+ d. some sort of TTL-like value (e.g., Freenet's hops-to-live)
 
- (kab) session key will be the J
-
         (kab) I think a lot of this is in 'primary-agent-protocol.txt'... should
         we just migrate this document into requirements...? I think so.
                      
-works with any message-based asynchronous data transport mechanism
- (e.g., UDP, SMTP, ICQ, Carrier Pigeon, etc.)
-
+3. works with any message-based asynchronous data transport mechanism
+ a. e.g. UDP, SMTP, ICQ, Carrier Pigeon, etc.
 
 F. === ontology / meaning ===
 

This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST