Disambiguate TMDI and GCDI (for ctags)
This commit is contained in:
@@ -394,7 +394,7 @@ Change from Session Tags to
|
||||
<li>{% trans tunnelmessage=site_url('docs/spec/tunnel-message') -%}
|
||||
Several of these ideas may require a new I2NP message type, or
|
||||
set a flag in the
|
||||
<a href="{{ tunnelmessage }}#delivery">Delivery Instructions</a>,
|
||||
<a href="{{ tunnelmessage }}#struct_TunnelMessageDeliveryInstructions">Delivery Instructions</a>,
|
||||
or set a magic number in the first few bytes of the Session Key field
|
||||
and accept a small risk of the random Session Key matching the magic number.
|
||||
{%- endtrans %}</li>
|
||||
|
@@ -153,8 +153,7 @@ the tunnel encryption is sufficient.
|
||||
<p>{% trans commonstructures=site_url('docs/spec/common-structures'),
|
||||
elgamalaes=site_url('docs/how/elgamal-aes'),
|
||||
i2cp=site_url('docs/protocol/i2cp'),
|
||||
i2npspec=site_url('docs/spec/i2np'),
|
||||
tunnelmessage=site_url('docs/spec/tunnel-message') -%}
|
||||
i2npspec=site_url('docs/spec/i2np') -%}
|
||||
At the layer above tunnels, I2P delivers end-to-end messages between
|
||||
<a href="{{ commonstructures }}#struct_Destination">Destinations</a>.
|
||||
Just as within a single tunnel, we use
|
||||
@@ -163,7 +162,7 @@ Each client message as delivered to the router through the
|
||||
<a href="{{ i2cp }}">I2CP interface</a> becomes a single
|
||||
<a href="{{ i2npspec }}#struct_GarlicClove">Garlic Clove</a>
|
||||
with its own
|
||||
<a href="{{ tunnelmessage }}#delivery">Delivery Instructions</a>,
|
||||
<a href="{{ i2npspec }}#struct_GarlicCloveDeliveryInstructions">Delivery Instructions</a>,
|
||||
inside a
|
||||
<a href="{{ i2npspec }}#msg_Garlic">Garlic Message</a>.
|
||||
Delivery Instructions may specify a Destination, Router, or Tunnel.
|
||||
@@ -177,12 +176,11 @@ cloves in the Garlic Message:
|
||||
<img src="/_static/images/garliccloves.png" alt="{{ _('Garlic Message Cloves') }}" title="{{ _('Garlic Message Cloves') }}" style="text-align:center;"/>
|
||||
|
||||
<ol>
|
||||
<li>{% trans i2npspec=site_url('docs/spec/i2np'),
|
||||
tunnelmessage=site_url('docs/spec/tunnel-message') -%}
|
||||
<li>{% trans i2npspec=site_url('docs/spec/i2np') -%}
|
||||
A
|
||||
<a href="{{ i2npspec }}#msg_DeliveryStatus">Delivery Status Message</a>,
|
||||
with
|
||||
<a href="{{ tunnelmessage }}#delivery">Delivery Instructions</a>
|
||||
<a href="{{ i2npspec }}#struct_GarlicCloveDeliveryInstructions">Delivery Instructions</a>
|
||||
specifying that it be sent back to the originating router as an acknowledgment.
|
||||
This is similar to the "reply block" or "reply onion"
|
||||
described in the references.
|
||||
@@ -193,14 +191,13 @@ or take other actions.
|
||||
{%- endtrans %}</li>
|
||||
<li>{% trans i2npspec=site_url('docs/spec/i2np'),
|
||||
commonstructures=site_url('docs/spec/common-structures'),
|
||||
tunnelmessage=site_url('docs/spec/tunnel-message'),
|
||||
netdb=site_url('docs/how/network-database') -%}
|
||||
A
|
||||
<a href="{{ i2npspec }}#msg_DatabaseStore">Database Store Message</a>,
|
||||
containing a
|
||||
<a href="{{ commonstructures }}#struct_LeaseSet">LeaseSet</a>
|
||||
for the originating Destination, with
|
||||
<a href="{{ tunnelmessage }}#delivery">Delivery Instructions</a>
|
||||
<a href="{{ i2npspec }}#struct_GarlicCloveDeliveryInstructions">Delivery Instructions</a>
|
||||
specifying the far-end destination's router.
|
||||
By periodically bundling a LeaseSet, the router ensures that the far-end will be able
|
||||
to maintain communications.
|
||||
@@ -256,7 +253,7 @@ so it is not visible to the tunnel's outbound gateway.
|
||||
The Garlic Message mechanism is very flexible and provides a structure for
|
||||
implementing many types of mixnet delivery methods.
|
||||
Together with the unused delay option in the
|
||||
<a href="{{ tunnelmessage }}#delivery">tunnel message Delivery Instructions</a>,
|
||||
<a href="{{ tunnelmessage }}#struct_TunnelMessageDeliveryInstructions">tunnel message Delivery Instructions</a>,
|
||||
a wide spectrum of batching, delay, mixing, and routing strategies are possible.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
Reference in New Issue
Block a user