forked from I2P_Developers/i2p.www
Protocol stack doc update
This commit is contained in:
@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Protocol Stack{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}August 2010{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.8{% endblock %}
|
||||
{% block lastupdated %}2021-12{% endblock %}
|
||||
{% block accuratefor %}0.9.52{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<p>{% trans docs=site_url('docs') -%}
|
||||
@ -29,10 +29,10 @@ The capabilities are listed below, starting at the bottom of the protocol stack.
|
||||
<li>
|
||||
{% trans -%}
|
||||
<b>I2P Transport Layer:</b> provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.
|
||||
Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP.
|
||||
Two protocols are implemented to provide these capabilities. NTCP2 builds on top of TCP, while SSU uses UDP.
|
||||
{%- endtrans %}
|
||||
<br />
|
||||
<a href="{{ site_url('docs/transport/ntcp') }}">NTCP</a>: {% trans %}NIO-based TCP{% endtrans %}
|
||||
<a href="{{ spec_url('ntcp2') }}">NTCP2</a>: {% trans %}NIO-based TCP{% endtrans %}
|
||||
<br />
|
||||
<a href="{{ site_url('docs/transport/ssu') }}">SSU</a>: {% trans %}Secure Semi-reliable UDP{% endtrans %}
|
||||
</li>
|
||||
@ -102,9 +102,9 @@ We can order this based on the I2P stack layer they use.
|
||||
{%- endtrans %}</p>
|
||||
<ul>
|
||||
<li>{% trans %}<b>Streaming/datagram applications</b>: i2psnark, Syndie, i2phex...{% endtrans %}</li>
|
||||
<li>{% trans %}<b>SAM/BOB applications</b>: IMule, i2p-bt, i2prufus, Robert...{% endtrans %}</li>
|
||||
<li>{% trans %}<b>SAM applications</b>: IMule, i2p-bt...{% endtrans %}</li>
|
||||
<li>{% trans plugins=site_url('docs/plugins') %}<b>Other I2P applications</b>: Syndie, EepGet, <a href="{{ plugins }}">plugins</a>...{% endtrans %}</li>
|
||||
<li>{% trans %}<b>Regular applications</b>: Jetty, Apache, Monotone, CVS, browsers, e-mail...{% endtrans %}</li>
|
||||
<li>{% trans %}<b>Regular applications</b>: Jetty, Apache, Git, browsers, e-mail...{% endtrans %}</li>
|
||||
</ul>
|
||||
|
||||
<div class="box" style="text-align:center;">
|
||||
@ -115,7 +115,7 @@ We can order this based on the I2P stack layer they use.
|
||||
<br/>
|
||||
|
||||
<p>
|
||||
* {% trans %}Note: SAM/SAMv2 can use both the streaming lib and datagrams.{% endtrans %}
|
||||
* {% trans %}Note: SAM can use both the streaming lib and datagrams.{% endtrans %}
|
||||
</p>
|
||||
|
||||
{% endblock %}
|
||||
|
Reference in New Issue
Block a user