kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify SSU Peer Test Message handling

Browse Source
This commit is contained in:
zzz
2014-04-07 15:01:14 +00:00
parent 85010240df
commit e86c88dd04
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
i2p2www/pages/site/docs/spec/ssu.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}SSU Protocol Specification{% endblock %}
{% block lastupdated %}February 2014{% endblock %}
{% block accuratefor %}0.9.11{% endblock %}
{% block lastupdated %}April 2014{% endblock %}
{% block accuratefor %}0.9.12{% endblock %}
{% block content %}
<p>
@@ -999,6 +999,12 @@ Only testing of IPv4 addresses is supported.
Therefore, all Alice-Bob and Alice-Charlie communication must be via IPv4.
Bob-Charlie communication, however, may be via IPv4 or IPv6.
Alice's address, when specified in the PeerTest message, must be 4 bytes.
</li><li>
A peer must maintain a table of active test states (nonces).
On reception of a Peer Test message, look up the nonce in the table.
If found, it's an existing test and you know your role (Alice, Bob, or Charlie).
Otherwise, if the IP is not present and the port is 0, this is a new test and you are Bob.
Otherwise, this is a new test and you are Charlie.
</li></ul>
<h3 id="holePunch">HolePunch</h3>