propagate from branch 'i2p.www' (head 58b6b0589b4b5e4a45b1be2ac97bba8d253e9368)

to branch 'i2p.www.str4d' (head 2ab3bce2634e8d1dcbf7f2bf89c310c5ae3a7eb6)
This commit is contained in:
str4d
2016-03-05 17:38:12 +00:00
76 changed files with 5321 additions and 696 deletions

View File

@@ -2,8 +2,8 @@
I2NP Specification
==================
.. meta::
:lastupdated: January 2015
:accuratefor: 0.9.17
:lastupdated: January 2016
:accuratefor: 0.9.24
Overview
@@ -172,6 +172,9 @@ Notes
research to determine points in the protocol stack where the far-end router's
version is known and checksum generation can be disabled.
* The short expiration is unsigned and will wrap around on Feb. 7, 2106. As of
that date, an offset must be added to get the correct time.
.. _struct-BuildRequestRecord:
BuildRequestRecord
@@ -532,22 +535,24 @@ Delivery Instructions!
Messages
========
========================= ====
Message Type
========================= ====
DatabaseStore_ 1
DatabaseLookup_ 2
DatabaseSearchReply_ 3
DeliveryStatus_ 10
Garlic_ 11
TunnelData_ 18
TunnelGateway_ 19
Data_ 20
TunnelBuild_ 21
TunnelBuildReply_ 22
VariableTunnelBuild_ 23
VariableTunnelBuildReply_ 24
========================= ====
================================== =======
Message Type
================================== =======
DatabaseStore_ 1
DatabaseLookup_ 2
DatabaseSearchReply_ 3
DeliveryStatus_ 10
Garlic_ 11
TunnelData_ 18
TunnelGateway_ 19
Data_ 20
TunnelBuild_ 21
TunnelBuildReply_ 22
VariableTunnelBuild_ 23
VariableTunnelBuildReply_ 24
Reserved for experimental messages 224-254
Reserved for future expansion 255
================================== =======
.. _msg-DatabaseStore:
@@ -1124,6 +1129,11 @@ A length Integer, followed by opaque data.
actual payload of this message
{% endhighlight %}
Notes
`````
* This message contains no routing information and will never be sent
"unwrapped". It is only used inside `Garlic` messages.
.. _msg-TunnelBuild:
TunnelBuild
@@ -1159,6 +1169,10 @@ Notes
* The I2NP message ID for this message must be set according to the tunnel
creation specification.
* While this message is rarely seen in today's network, having been replaced by
the `VariableTunnelBuild` message, it may still be used for very long tunnels,
and has not been deprecated. Routers must implement.
.. _msg-TunnelBuildReply:
TunnelBuildReply
@@ -1177,6 +1191,10 @@ Notes
* The I2NP message ID for this message must be set according to the tunnel
creation specification.
* While this message is rarely seen in today's network, having been replaced by
the `VariableTunnelBuildReply` message, it may still be used for very long
tunnels, and has not been deprecated. Routers must implement.
.. _msg-VariableTunnelBuild:
VariableTunnelBuild
@@ -1210,6 +1228,8 @@ Notes
* The I2NP message ID for this message must be set according to the tunnel
creation specification.
* Typical number of records in today's network is 5.
.. _msg-VariableTunnelBuildReply:
VariableTunnelBuildReply
@@ -1235,6 +1255,8 @@ Notes
* The I2NP message ID for this message must be set according to the tunnel
creation specification.
* Typical number of records in today's network is 5.
References
==========