diff --git a/www.i2p2/pages/i2cp.html b/www.i2p2/pages/i2cp.html
index d408571dd35824aa401bdf371acdc8bc709a897a..32694efc137709e0f169fd9fa1b37746038b7637 100644
--- a/www.i2p2/pages/i2cp.html
+++ b/www.i2p2/pages/i2cp.html
@@ -1,7 +1,7 @@
 {% extends "_layout.html" %}
 {% block title %}I2CP{% endblock %}
 {% block content %}
-Updated May 2012, current as of router version 0.9
+Updated June 2012, current as of router version 0.9
 
 <p>The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
 the router and any client that wishes to communicate over the network.  It enables
@@ -116,6 +116,10 @@ a <a href="i2cp_spec.html#type_SessionConfig">SessionConfig</a> contained in a <
         If the client is running in the same JVM as a router, this option is not required.
 <tr><td>i2cp.password<td>string<td>&nbsp;<td>&nbsp;<td>For authorization, if required by the router (since 0.8.2).
         If the client is running in the same JVM as a router, this option is not required.
+<tr><td>inbound.*<td>&nbsp;<td>&nbsp;<td>&nbsp;<td>Any other options prefixed with "inbound." are stored
+        in the "unknown options" properties of the inbound tunnel pool's settings.
+<tr><td>outbound.*<td>&nbsp;<td>&nbsp;<td>&nbsp;<td>Any other options prefixed with "outbound." are stored
+        in the "unknown options" properties of the outbound tunnel pool's settings.
 </table>
 <p>
 Note: Large quantity, length, or variance settings may cause significant performance or reliability problems.