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

[minion-cvs] Clarify fragmentation behavior



Update of /home/minion/cvsroot/doc/spec
In directory moria.mit.edu:/tmp/cvs-serv15853

Modified Files:
	E2E-spec.txt 
Log Message:
Clarify fragmentation behavior

Index: E2E-spec.txt
===================================================================
RCS file: /home/minion/cvsroot/doc/spec/E2E-spec.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- E2E-spec.txt	24 Jul 2003 03:33:21 -0000	1.6
+++ E2E-spec.txt	9 Aug 2003 02:51:53 -0000	1.7
@@ -216,7 +216,7 @@
    
        Let M_SIZE = CEIL(LEN(M) / PS)
 
-       Let K = Min(16, 2**CEIL(Log2(M_SIZE)))
+       Let K = Min(32, 2**CEIL(Log2(M_SIZE)))
        Let NUM_CHUNKS = CEIL(M_SIZE / K)
    
        Let M = M | PRNG(Len(M) - NUM_CHUNKS*PS*K)
@@ -413,7 +413,8 @@
    We specify a solution to 2 here.  When generating plaintext forward
    fragmented messages, the message generator uses a routing type of
    "FRAGMENT" (0x0103), an empty routing into, and prepends the
-   following fields to the message body before fragmenting it:
+   following fields to the message body before compressing and
+   fragmenting it:
 
          RS Routing size    2 octets
          RT Routing type    2 octets