forked from I2P_Developers/i2p.www
multiprotocol
This commit is contained in:
@@ -75,6 +75,8 @@ Version 3.2 is not yet implemented, and the changes listed below are preliminary
|
||||
On failure the server will reply with an I2P_ERROR and a message.
|
||||
<li>Multiple concurrent pending STREAM ACCEPTs are allowed on the same session ID (even with the same port).
|
||||
It isn't clear (either in the spec or the code) if these are allowed now.
|
||||
<li>The same session ID may be used for streams, datagrams, and raw simultaneously.
|
||||
Incoming packets and streams will be routed based on I2P protocol and to-port.
|
||||
<li>The server's control socket may optionally offer SSL/TLS support, as configured on the server and client.
|
||||
Implementations may offer other transport layers as well; this is outside the scope of the protocol definition.
|
||||
<li>For STREAM FORWARD, client may add SSL=true to use an SSL socket
|
||||
|
Reference in New Issue
Block a user