srt-rfc
srt-rfc copied to clipboard
Haivision
If there is an active Caller -> Listener session, and a rogue caller tries to handshake, it should be made mandatory that the listener responds with a fake socket id....
The RFC talks about how to calculate RTT0 during handshake. But it's impossible for the sender to associate a handshake packet with its response, as on long latency links there...
If in live mode, the sender stops sending for 500ms as the data is VBR. Is the receiver meant to resend ACKs of the same ackseq? It appears libsrt 1.4.3...
"Available Buffer Size" needs to explain that it's something like 8192 - _buffer_size_ and this value is used for congestion control if it gets too low
libsrt doesn't seem to like it too much if you set HS Extension Length = 0 (e.g for stream ID). The spec should clarify this is not allowed.
Define ranges of valid Socket ID values. - Value `0`. Reserved for handshake procedure. If the destination Socket ID is `0` (destination Socket ID unknown) the packet will be sent...
Describe the behavior in the draft. Each side randomly generates the ISN value. In the caller-listener handshake, both sides use the caller's ISN. In the case of rendezvous, each side...
Haivision has the PNP ID 'HAI'. The procedure for how it should be encoded to become `0x2029` is not clear. ``` 0 1 2 3 0 1 2 3 4...
Reading the specification for control packets, I want to ask about some clarification regarding packets without control information field (CIF). For the packet types Keep-Alive, Shutdown, and AckAck, this draft...
The minimum value is chosen during the HS. [m_config.iMSS = std::min(m_config.iMSS, w_hs.m_iMSS);](https://github.com/Haivision/srt/blob/v1.4.4-rc.1/srtcore/core.cpp#L5465)