I2NP dataspec tweaks

This commit is contained in:
str4d
2015-06-29 12:52:12 +00:00
parent 7aecc4b68a
commit c42c151228

View File

@@ -651,7 +651,7 @@ type ::
reply token ::
4 bytes
If greater than zero, a Delivery Status Message
If greater than zero, a `DeliveryStatusMessage`
is requested with the Message ID set to the value of the Reply Token.
A floodfill router is also expected to flood the data to the closest floodfill peers
if the token is greater than zero.
@@ -664,7 +664,7 @@ reply_tunnelId ::
reply gateway ::
32 bytes
Hash of the routerInfo entry to reach the gateway
Hash of the `RouterInfo` entry to reach the gateway
Only included if reply token > 0
If $reply_tunnelId is nonzero, this is the router hash of the inbound gateway
of the tunnel the response should be sent to.
@@ -773,9 +773,9 @@ flags ::
through release 0.9.5, must be set to 00
as of release 0.9.6, ignored
as of release 0.9.16:
00 => normal lookup, return RI or LS or `DatabaseSearchReplyMessage`
01 => LS lookup, return LS or `DatabaseSearchReplyMessage`
10 => RI lookup, return RI or `DatabaseSearchReplyMessage`
00 => normal lookup, return `RouterInfo` or `LeaseSet` or `DatabaseSearchReplyMessage`
01 => LS lookup, return `LeaseSet` or `DatabaseSearchReplyMessage`
10 => RI lookup, return `RouterInfo` or `DatabaseSearchReplyMessage`
11 => exploration lookup, return `DatabaseSearchReplyMessage` containing non-floodfill routers only
(replaces an excludedPeer of all zeroes)
bits 7-4:
@@ -810,7 +810,7 @@ tags ::
only included if encryptionFlag == 1, only as of release 0.9.7
reply_tags ::
one or more 32 byte `SessionTags` (typically one)
one or more 32 byte `SessionTag`s (typically one)
only included if encryptionFlag == 1, only as of release 0.9.7
{% endhighlight %}