forked from I2P_Developers/i2p.www
Clarification on transport caps
This commit is contained in:
@@ -563,6 +563,12 @@ here. Implementers should add defenses where appropriate.
|
||||
|
||||
<h2><a name="capabilities">{% trans %}Peer capabilities{% endtrans %}</a></h2>
|
||||
|
||||
<p>
|
||||
One or more capabilities may be published in the "caps" option.
|
||||
Capabilities may be in any order, but "BC46" is the recommended order, for consistency across implementations.
|
||||
</p>
|
||||
|
||||
|
||||
<dl>
|
||||
<dt>B</dt>
|
||||
<dd>{% trans -%}
|
||||
|
Reference in New Issue
Block a user