Send information about the current (and the previous) connection.
Both peers MUST initially send this message as part of the handshake. Each peer MUST wait until it has received the message from the other peer before sending any further messages.
If a previous connection is being resumed, this MUST contain information about the previous connection.
When a subsequent connection fails before the new connection ID has been established, the previous connection ID remains for an upcoming connection attempt.
As soon as a new connection ID has been established, the ownership of the cached chunks will be transferred to the newly established connection ID. That way, only one former connection ID exists where cached chunks are assigned to.
| Field | Description | Type | Optional | Nullable |
|---|---|---|---|---|
| id |
The current Connection ID |
Binary | False | False |
| resume |
The previous connection to be resumed. If the Connection ID does not match on both sides, the peers SHALL NOT send cached messages but discard them and treat the connection as a newly established web session. |
Map<Connection> | True | False |
| Field | Description | Type | Optional | Nullable | Default |
|---|---|---|---|---|---|
| id |
The Connection ID of the connection to be resumed |
Binary | False | False | |
| sequenceNumber |
The Sequence Number of the last message received during the connection |
Integer (u32) | False | False |