- Add descriptions to some I2NP messages

- Comment out streaming options added in error (actually hardcoded)

www.i2p2/pages/i2np_spec.html

@@ -2,7 +2,7 @@
 {% block title %}I2NP Specification{% endblock %}
 {% block content %}
 
-Updated June 2013, current as of router version 0.9.6
+Updated July 2013, current as of router version 0.9.7
 
 <h1>I2P Network Protocol (I2NP) Specification</h1>
 <p>
@@ -541,6 +541,12 @@ The key is the "real" hash of the RouterIdentity or Destination, NOT the routing
 
 
 <h3 id="msg_DatabaseLookup">DatabaseLookup</h3>
+<h4>Description</h4>
+<p>
+  A request to look up an item in the network database.
+  The response is either a DatabaseStore or a DatabaseSearchReply.
+</p>
+<h4>Contents</h4>
 <pre>
 {% filter escape %}
 +----+----+----+----+----+----+----+----+
@@ -752,7 +758,7 @@ from:
 </li><li>
 The lookup key, peer hashes, and from hash are "real" hashes, NOT routing keys.
 </li>
-
+</ul>
 
 
 
@@ -899,6 +905,12 @@ Expiration :: Date (8 bytes)
 
 
 <h3 id="msg_TunnelData">TunnelData</h3>
+<h4>Description</h4>
+<p>
+  A message sent from a tunnel's gateway or participant to the next participant or endpoint.
+  The data is of fixed length, containing I2NP messages that are fragmented, batched, padded, and encrypted.
+</p>
+<h4>Contents</h4>
 <pre>
 {% filter escape %}
 +----+----+----+----+----+----+----+----+
@@ -935,6 +947,11 @@ data:
 
 
 <h3 id="msg_TunnelGateway">TunnelGateway</h3>
+<h4>Description</h4>
+<p>
+  Wraps another I2NP message to be sent into a tunnel at the tunnel's inbound gateway.
+</p>
+<h4>Contents</h4>
 <pre>
 {% filter escape %}
 +----+----+----+----+----+----+--\\----+

www.i2p2/pages/streaming.html

@@ -1,7 +1,7 @@
 {% extends "_layout.html" %}
 {% block title %}Streaming Library{% endblock %}
 {% block content %}
-Updated July 2013, current as of router version 0.9.6
+Updated July 2013, current as of router version 0.9.7
 <h2>Overview</h2>
 
 <p>
@@ -124,11 +124,15 @@ See the javadocs for details.
 </td></tr><tr><td>i2cp.enableBlackList</td><td>false
 </td><td>Use the access list as a blacklist for incoming connections
       As of release 0.7.13.
+<!--
 </td></tr><tr><td>i2p.streaming.alpha</td><td>0.125</td><td>
    Ref. RFC 6298. Floating point value. As of release 0.9.8.
+-->
 </td></tr><tr><td>i2p.streaming.answerPings</td><td>true</td><td>Whether to respond to incoming pings
+<!--
 </td></tr><tr><td>i2p.streaming.beta</td><td>0.25</td><td>
    Ref. RFC 6298. Floating point value. As of release 0.9.8.
+-->
 </td></tr><tr><td>i2p.streaming.blacklist</td><td>null</td><td>Comma- or space-separated list of Base64 peer Hashes to be
       blacklisted for incoming connections to ALL destinations in the context.
       This option must be set in the context properties, NOT in the createManager() options argument.
@@ -177,8 +181,10 @@ See the javadocs for details.
    Disabled as of release 0.9.8; uses actual RTT.
 </td></tr><tr><td>i2p.streaming.initialWindowSize</td><td>6</td><td>(if no <a href="#sharing">sharing data</a> available)
    In standard TCP, window sizes are in bytes, while in I2P, window sizes are in messages.
+<!--
 </td></tr><tr><td>i2p.streaming.kappa</td><td>4.0</td><td>
    Ref. RFC 6298 "K". Floating point value. As of release 0.9.8.
+-->
 </td></tr><tr><td>i2p.streaming.maxConcurrentStreams</td><td>-1 </td><td>(0 or negative value means unlimited)
    This is a total limit for incoming and outgoing combined.
 </td></tr><tr><td>i2p.streaming.maxConnsPerMinute</td><td>0 </td><td>Incoming connection limit (per peer; 0 means disabled)