[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[freehaven-cvs] remove extraneous notes



Update of /home/freehaven/cvsroot/doc/pynchon-gate
In directory moria.mit.edu:/tmp/cvs-serv3284

Modified Files:
	pynchon-spec.txt 
Log Message:
remove extraneous notes

Index: pynchon-spec.txt
===================================================================
RCS file: /home/freehaven/cvsroot/doc/pynchon-gate/pynchon-spec.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- pynchon-spec.txt	7 May 2004 06:13:12 -0000	1.1
+++ pynchon-spec.txt	7 May 2004 06:14:06 -0000	1.2
@@ -561,183 +561,3 @@
 
    {XXXX Write me.}
 
-Performance analysis:
-
-   N -- number of users
-   S -- number of distributors
-   K -- security parameter for PIR.
-   B -- bucket size
-   Vol[i] -- Volume of message received on a given "day" by user i.
-   CVol -- Volume of messages received on a given "day" by user i,
-       after compression.
-   MCVol[i] -- Maximum compressed volume that user i can receive in
-        one "day".
-   W -- Window in which users must retrieve their messages (in "days").
-
-   ME -- metaindex entry size (36 bytes)
-   IE -- index entry size (40 bytes)
-   SS -- stream seed size (32 bytes)
-
-   Number of message buckets needed (m):
-     SUM( CEIL( CVol[i] / B ) )
-
-   Number of index buckets needed (I):
-
-     CEIL( (N * IE) / (B-IE) )
-
-   Size of metaindex (MS):
-
-     ME * I
-
-   Total storage needed per pool (PS):
-
-     B * (m+I) + MS
-
-   Storage needed at each distributer:
-
-     PS * W
-
-   Bandwidth of nymserver/collator per "day" (assuming idealized
-      Bittorrent):
-
-     SUM(Vol[i]) + PS
-
-     (I'm assuming an idealized Bittorrent where every participant has
-     equal bandwidth; where everybody but the original seed downloads
-     the entire file once; where everybody uploads the entire file
-     once; and where tracker bandwidth is negligible.)
-
-   Client bandwidth per "day":
-
-     User i needs to fetch
-         CEIL( MCVol[i] / B ) + 1
-     buckets per day.  Call this Buckets[i].  Retrieving each bucket
-     takes K-1 requests of SS bytes each, and one request of (m+I)
-     bits.  Each such request yields B bytes.  So for PIR, User i uses
-     bandwidth of:
-
-         Buckets[i] * [ (K-1)*SS + (m+I)/8 + B ]
-
-     Call the above volume ClientPIRVol[i].
-
-     Additionally, each user needs to fetch the metaindex via
-     bittorrent.  This should take (assuming the idealized bittorrent
-     characteristics above), an additional (2*MS) bytes per "day".
-
-   Distributer bandwidth per "day", assuming idealized Bittorrent:
-
-     PS + SUM( ClientB[i]) ) / S
-
-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-Comparison: Type I nymservers
-
-   (Ignoring Type I overhead.)
-
-   r -- reply block size
-   L -- reply block path length
-   S -- number of mixes on mix net.
-
-   Storage needed at nymserver:
-
-      r * N
-
-   Bandwidth needed at nymserver, per "day":
-
-      SUM(Vol[i]) + SUM(CVol[i])
-
-   Bandwidth needed by user i, per "day":
-
-      CVol[i]
-
-   Bandwidth needed across entire mix net, per day:
-
-      2*L*SUM(CVol[i])
-
-      (every node in each reply block must receive and send every
-      message.)
-
-   Bandwidth used by mix node, per "day":
-
-      2*L*SUM(CVol[i])/S
-
-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-Comparison: alt.anonymous.messages, used securely.
-
-   S -- number of news servers
-
-   Storage needed at each news server:
-
-      W * SUM( CVol[i] )
-
-   Bandwidth needed at news server, per day:
-
-      SUM( CVol[i] ) * (N/S + 1)
-
-      (Each server retrieves each message once, and relays all posts
-      to N/S users.)
-
-   Client bandwidth per "day":
-
-      SUM( CVol[i] )
-
-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-Comparison: Type III nymserver design (Underhill)
-
-   r -- reply block size (2K)
-   P -- payload size (28K)
-   M -- packet size (32K)
-   W -- maximum interval at which users must replenish reply blocks,
-        in "days".
-   S -- number of mixes on mix net.
-
-   All of this stuff is *very* approximate.
-
-   Storage needed at nymserver:
-
-      (best case -- holding only reply blocks.)
-      >=3D r * SUM( CEIL(CVol[i]/P) * W )
-
-      (worst case -- out of reply blocks for everybody.)
-      < SUM( CEIL(CVol[i]/P) * W)
-
-   Bandwidth needed at nymserver, per day:
-
-      (Nymserver receives messages, sends compressed messages in
-      packets, and receives SURBs.)
-
-      SUM(Vol[i]) + SUM( CEIL(CVol[i]/P) * M) + SUM(CEIL(CVol[i]/P)*r)
-      =3D=3D SUM(Vol[i]) + (M+r)*SUM(CEIL(CVol[i]/P))
-
-   User i bandwidth, per "day":
-
-      CVol[i]*CEIL(CVol[i]/P)
-
-   Bandwidth per mix on mix net, per "day"
-
-      [2 * L * (M+r) * SUM(CEIL(CVol[i]/P)) ] / S
-
-===============================================================================
-
-
-On Sun, Apr 18, 2004 at 10:34:31PM -0700, Len Sassaman wrote:
- [...]
-> 
-> Reviewing the rest of your comments now...
-
-FYI, I'm currently msging with bram about this stuff on #p2p-hackers.
-
-We've currently made the following changes in my proposal (correct me
-if I'm wrong, Bram):
-
-   1.  The client doesn't use bittorrent to get the metaindex;
-       instead, she just fetches it from any distributor.
-
-   2.  Instead of containing a hash of *all* of a user's buckets, the
-       index entry for the user just contains a hash of the user's
-       first bucket.  The hash of the user's first bucket starts with
-       a hash of each of the user's remaining buckets.  This way, if a
-       bucket is corrupted, the user can tell which one.
-
-Did I miss anything?
-
-

***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs       in the body. http://freehaven.net/