forked from I2P_Developers/i2p.www
Prop. 159 add Relay Response block to Hole Punch message
This commit is contained in:
@@ -4980,6 +4980,7 @@ Payload
|
||||
```````
|
||||
- DateTime block
|
||||
- Address block
|
||||
- Relay Response block
|
||||
- Padding block (optional)
|
||||
|
||||
The minimum payload size is 8 bytes. Since the DateTime and Address blocks
|
||||
@@ -5566,7 +5567,8 @@ RelayResponse
|
||||
``````````````
|
||||
|
||||
Sent in a Data message in-session, from Charlie to Bob
|
||||
or from Bob to Alice.
|
||||
or from Bob to Alice, AND in the Hole Punch message
|
||||
from Charlie to Alice.
|
||||
See Relay Process section below.
|
||||
|
||||
|
||||
@@ -7162,6 +7164,14 @@ IPv4 and IPv6 introductions are supported.
|
||||
A Relay Request may be sent over an IPv4 session for an IPv6 introduction,
|
||||
and a Relay Request may be sent over an IPv6 session for an IPv4 introduction.
|
||||
|
||||
As in SSU 1 (but may not be well-documented in those specifications),
|
||||
Alice should initiate the handshake with Charlie after receiving
|
||||
EITHER the Relay Response from Bob OR the Hole Punch from Charlie,
|
||||
which may be received in either order.
|
||||
SSU2 makes the Hole Punch easier to process by making it a new
|
||||
message with defined connection IDs and contents.
|
||||
The Relay Response (Data message) and Hole Punch message both contain the identical
|
||||
signed Relay Response block.
|
||||
|
||||
|
||||
Published Router Info
|
||||
|
Reference in New Issue
Block a user