diff --git a/www.i2p2/pages/tunnel_message_spec.html b/www.i2p2/pages/tunnel_message_spec.html index 3dbc8881..93f36db0 100644 --- a/www.i2p2/pages/tunnel_message_spec.html +++ b/www.i2p2/pages/tunnel_message_spec.html @@ -2,7 +2,7 @@ {% block title %}Tunnel Message Specification{% endblock %} {% block content %} -Updated October 2011 for release 0.8.10 +Updated November 2013 for release 0.9.9

Tunnel Message Specification

This document specifies the format of tunnel messages. @@ -204,6 +204,7 @@ flag: bits 6-5: delivery type For tunnel messages: 0x0 = LOCAL, 0x01 = TUNNEL, 0x02 = ROUTER, 0x03 = unused + Note: LOCAL is used for inbound tunnels only, unimplemented for outbound tunnels For garlic cloves: 0x0 = LOCAL, 0x01 = DESTINATION, 0x02 = ROUTER, 0x03 = TUNNEL bit 4: delay included? Unimplemented, always 0 @@ -212,7 +213,7 @@ flag: If 1, the message is fragmented, and the instructions contain a Message ID bit 2: extended options? Unimplemented, always 0 If 1, extended options are included - bits 1-0: reserved + bits 1-0: reserved, set to 0 for compatibility with future uses Tunnel ID: 4 bytes @@ -248,12 +249,15 @@ Extended Options: size: 2 bytes + Required in a tunnel message; never present in a garlic clove. The length of the fragment that follows - Valid values: 1 to approx. 960 in a tunnel message; 1 to 64K - 1 in a garlic clove + Valid values: 1 to approx. 960 in a tunnel message Total length: Typical length is: - 3 bytes for LOCAL delivery (garlic clove); - 35 bytes for ROUTER / DESTINATION delivery or 39 bytes for TUNNEL delivery (unfragmented or garlic clove); + 1 byte for LOCAL delivery (garlic clove); + 3 bytes for LOCAL delivery (tunnel message); + 35 bytes for ROUTER / DESTINATION delivery or 39 bytes for TUNNEL delivery (unfragmented tunnel message); + 33 bytes for ROUTER / DESTINATION delivery or 37 bytes for TUNNEL delivery (garlic clove); 39 bytes for ROUTER delivery or 43 bytes for TUNNEL delivery (first fragment) @@ -280,7 +284,7 @@ frag: Message ID: 4 bytes - The same ID specified in the first fragment + The same ID specified in the first fragment for this message ID size: 2 bytes