-
What happens if the client receives a `new-responder` message with an id that is already known? Protocol error?
When does the server start re-assigning already used responder ids? Once the old ones a…
dbrgn updated
8 years ago
-
The WebSocket protocol allows us to close a connection with a specific close code. The code range [3000..3999] can be used for libraries and frameworks.
Proposed close codes:
- 1001: _CLOSE_GOING_AWA…
-
This is not directly something related to the protocol, but should be implemented consistently across all clients. Therefore the issue in the meta repo.
How should we design the public API?
Right no…
dbrgn updated
8 years ago
-
This sentence is a bit confusing:
> Both clients SHALL send this message once the wrapped data channel's state for the handed over signalling is open on the signalling channel that has been establish…
dbrgn updated
8 years ago
-
-
The specified chunk size should include the header bytes.
dbrgn updated
8 years ago
-
Is this correct?
---
The following things need to be validated on each incoming message:
## Source byte
_Only applicable to signaling nonces_
- During server handshake:
- Assert that source byte …
dbrgn updated
8 years ago
-
Should we throw an error or just return null?
See: https://github.com/saltyrtc/chunked-dc-js/blob/673ffd4fb259532625bc307bb25ded830e394cd6/chunked-dc.ts#L52:L54
-
The spec only says that the path should be the hex encoded public key of the initiator.
It does not specify whether the letters in the hex string should be upper- or lowercase though.
dbrgn updated
8 years ago
-
The `chunked-dc` chunking should be explained before or at first use in the specification.
dbrgn updated
8 years ago