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

I2CP updates for proposal 123

Browse Source
This commit is contained in:
zzz
2019-01-25 14:06:08 +00:00
parent 6f6fbceff5
commit fc93b3e720
3 changed files with 221 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

109
i2p2www/pages/site/docs/protocol/i2cp.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2CP{% endblock %}
{% block lastupdated %}{% trans %}February 2016{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.24{% endblock %}
{% block lastupdated %}{% trans %}January 2019{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.38{% endblock %}
{% block content %}
<p>{% trans -%}
The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
@@ -174,6 +174,75 @@ of sending a MessageStatus and awaiting a ReceiveMessageBegin.
{%- endtrans %}</td>
</tr>
<tr>
<td>i2cp.leaseSetEncType
<td>0.9.38</td>
<td>0
<td>0-65535,...
<td>0
<td>
The encryption type to be used.
Interpreted client-side, but also passed to the router in the
SessionConfig, to declare intent and check support.
May be comma-separated values for multiple types.
See PublicKey in common strutures spec for values.
See proposals 123, 144, and 145.
</td>
</tr>
<tr>
<td>i2cp.leaseSetOfflineExpiration
<td>0.9.38</td>
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>
The expiration of the offline signature, 4 bytes,
seconds since the epoch.
See proposal 123.
</td>
</tr>
<tr>
<td>i2cp.leaseSetOfflineSignature
<td>0.9.38</td>
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>
The base 64 of the offline signature.
See proposal 123.
</td>
</tr>
<tr>
<td>i2cp.leaseSetTransientPublicKey
<td>0.9.38</td>
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>
[type:]b64 The base 64 of the transient private key,
prefixed by an optional sig type number or name,
default DSA_SHA1.
See proposal 123.
</td>
</tr>
<tr>
<td>i2cp.leaseSetType
<td>0.9.38</td>
<td>1,3,5,7
<td>1-255
<td>1
<td>
The type of leaseset to be sent in the CreateLeaseSet2 Message.
Interpreted client-side, but also passed to the router in the
SessionConfig, to declare intent and check support.
See proposal 123.
</td>
</tr>
<tr>
<td>i2cp.messageReliability
<td>&nbsp;</td>
@@ -462,6 +531,12 @@ Since options are encoded in a <a href="{{ commonstructures }}#type_Mapping">Map
all option names and values are limited to 255 bytes (not characters) maximum.
{%- endtrans %}</p>
<h3>{% trans %}Client-side Options{% endtrans %}</h3>
<p>{% trans -%}
The following options are interpreted on the client side,
@@ -531,6 +606,22 @@ of sending a MessageStatus and awaiting a ReceiveMessageBegin.
<td>{% trans %}Gzip outbound data{% endtrans %}</td>
</tr>
<tr>
<td>i2cp.leaseSetEncType
<td>0.9.38</td>
<td>0
<td>0-65535,...
<td>0
<td>
The encryption type to be used.
Interpreted client-side, but also passed to the router in the
SessionConfig, to declare intent and check support.
May be comma-separated values for multiple types.
See PublicKey in common strutures spec for values.
See proposals 123, 144, and 145.
</td>
</tr>
<tr>
<td>i2cp.leaseSetKey
<td>0.7.1
@@ -571,6 +662,20 @@ Use for persistent leaseset keys across restarts.
{%- endtrans %}</td>
</tr>
<tr>
<td>i2cp.leaseSetType
<td>0.9.38</td>
<td>1,3,5,7
<td>1-255
<td>1
<td>
The type of leaseset to be sent in the CreateLeaseSet2 Message.
Interpreted client-side, but also passed to the router in the
SessionConfig, to declare intent and check support.
See proposal 123.
</td>
</tr>
<tr>
<td>i2cp.messageReliability
<td>&nbsp;