GeoIPv6 clarifications and updates

I2CP note on option lengths

www.i2p2/pages/geoip.html

@@ -1,7 +1,7 @@
 {% extends "_layout.html" %}
 {% block title %}GeoIP File Specification{% endblock %}
 {% block content %}
-Updated May 2013, current as of router version 0.9.6
+Updated December 2013, current as of router version 0.9.9
 
 
 <h2>Overview</h2>
@@ -57,8 +57,8 @@ The file is gzipped. Ungzipped format:
    Bytes 0-9: Magic number "I2PGeoIPv6"
    Bytes 10-11: Version (0x0001)
    Bytes 12-15 Options (0x00000000) (future use)
-   Bytes 16-23: Creation date (Java long)
-   Bytes 24-xx: Optional comment (UTF-8)
+   Bytes 16-23: Creation date (ms since 1970-01-01)
+   Bytes 24-xx: Optional comment (UTF-8) terminated by zero byte
    Bytes xx-255: null padding
    Bytes 256-: 18 byte records:
        8 byte from (/64)
@@ -69,11 +69,11 @@ The file is gzipped. Ungzipped format:
 NOTES:
 <ul>
 <li>Data must be sorted (SIGNED long twos complement), no overlap.
-So the order is 8000:: ... FFFF:: 0000:: ... 7FFF::
+So the order is 80000000 ... FFFFFFFF 00000000 ... 7FFFFFFF.
 <li>
 The GeoIPv6.java class contains a program to generate this format from
 public sources such as the Maxmind GeoLite data.
 <li>
-This specification is preliminary; I2P does not yet support IPv6 GeoIP lookup.
+IPv6 GeoIP lookup is supported as of release 0.9.8.
 </ul>
 {% endblock %}

www.i2p2/pages/i2cp.html

@@ -160,6 +160,8 @@ Note: Large quantity, length, or variance settings may cause significant perform
 Note: As of release 0.7.7, option names and values must use UTF-8 encoding.
 This is primarily useful for nicknames.
 Prior to that release, options with multi-byte characters were corrupted.
+Since options are encoded in a <a href="common_structures_spec.html#type_Mapping">Mapping</a>,
+all option names and values are limited to 255 bytes (not characters) maximum.
 
 <p>
 The following options are interpreted on the client side,