CVS update: openprivacy/htdocs/notes/reputations

From: cvs@openprivacy.org
Date: Tue Dec 12 2000 - 00:00:42 PST

Date: Tuesday December 12, 19100 @ 0:00
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:
defined agent/reputation server/broker

*****************************************************************
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.18

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.18&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.18&r2=1.17

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

Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.17 openprivacy/htdocs/notes/reputations/requirements.txt:1.18
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.17 Mon Dec 11 17:48:07 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 00:00:42 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.17 2000/12/12 01:48:07 fen Exp $
+$Id: requirements.txt,v 1.18 2000/12/12 08:00:42 fen Exp $
 
 Reputation Server Requirements: top level feature list
 
@@ -8,8 +8,21 @@
 A. === general ===
 
 1. decentralized, peer-to-peer
- e.g., Freenet, perhaps like an extendable DNS
+ a. agent => reputation server [ => broker ]
 
+An agent
+ can receive requests and return responses
+ has an internal state and possibly access to an internal datastore
+ can examine its state
+ can initiate communications when programmed conditions are met
+
+A reputation server is an agent that can
+ respond to reputation requests
+ such as 'putReputation(URI, rep)' and 'rep = getReputation(URI)'
+
+A broker is a reputation server that has added intelligence for some domain
+ (brokers are generally outside the scope of these requirements)
+
 B. === Security, Authentication, Privacy, Validation ===
 
 Key:
@@ -36,7 +49,7 @@
     b. has O (that was grafted to) changed?
         i. again, positive proof may exist, but lack of proof proves nothing
     c. are signatures valid?
- i. signatures may have expiration dates (is this a requirment?)
+ i. signatures may have expiration dates (is this a requirement?)
         ii. check for a hash mis-match
              requires access to the public key, thus:
              a signer's pubkey <KeyInfo> needs to be accessible to verify a signature
@@ -142,4 +155,4 @@
 with the opinion. (Note that this is unreliable, in that the returned set
 of 'opinions' is defined by the local reputation server(s).
 
-Desireable to be censorship-resistant (e.g., Freenet, MojoNation, Publius)
+Desirable to be censorship-resistant (e.g., Freenet, MojoNation, Publius)

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