[minion-cvs] Revise and extend E2E-spec.txt

[nickm@seul.org (Nick Mathewson)]

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

Modified Files:
	E2E-spec.txt 
Log Message:
Revise and extend E2E-spec.txt

Change E2E-spec from a design note into a specification in the same
style as the others.  Say more about fragmentation, delivery, headers,
and so on.




Index: E2E-spec.txt
===================================================================
RCS file: /home/minion/cvsroot/doc/spec/E2E-spec.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- E2E-spec.txt	20 Jun 2003 07:11:23 -0000	1.2
+++ E2E-spec.txt	26 Jun 2003 03:07:54 -0000	1.3
@@ -37,27 +37,34 @@
    1.1.     Terminology
 
    2.       End-to-end message encoding
-   2.1.     Preliminaries
-   2.1.1.   Preliminaries: Types of messages
-   2.1.1.   Preliminaries: Compression
-   2.1.2.   Preliminaries: K-of-N fragmentation
+   2.1.     Building blocks
+   2.1.1.   Building blocks: Compression
+   2.1.2.   Building blocks: K-of-N fragmentation
+   2.1.3.   Building blocks: Whitening
[...1385 lines suppressed...]
-   [All of these are mentioned in more detail below.]
+   If the server supports message reconstruction, the section MAY
+   include a "Maximum-size" line, containing the maximum permitted
+   message size in KB (before compression). [XXXX is "before"
+   reasonable?]
+
+A.1. Apendix: versioning and alphas
+
+   Today's alpha code does not publish its version as '1.0'; it uses
+   '0.x' instead (currently '0.1' for all versions in this document).
+   Production versions MUST NOT retain backward compatibility
+   with pre-production releases.
+
+X. Open issues
    
    1. Mail gateways. We should specify these.
-      [Should go into appendix]
-      [Agreed.  We should make an actual list of appendices that we
-       need, and start writing them all.-NM]