-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handshake Extension Message. What it is about? #97
Comments
It's also didn't said which bit endianness is used in the packets encoding. |
What timestamp is used in Listener handshake packets? Until Listener received conclusion packet connection is not established and it's better not to allocate any resources. So the Listener doesn't have connection establishment time that can be used as epoch time to timestamps. Client can use time when connection was initiated as epoch, but Listener can't. |
Are message numbers started from 1? |
Shutdown message doesn't contain information about last sequence number sent. |
Hi @nikandfor
It is both. Initially, it is the library version. However, the library also defines certain known behavior and some known features like bidirectional transmission, so it is also a protocol version.
It didn't intend initially, as SRT was an internal project of Haivision. Now it should be just treated as the protocol version.
To do #56
The time on the HS Induction response from the listener is ignored and can be zero.
Yes.
Can be something to extend in v1.5.0 🤔 |
I'm implementing the protocol and now I'm making handshake part.
I've received Handshake Extension Message from canonical implementation, responded with my 0.0.1 version and got rejected because of too low version.
My questions are:
And one more little note about extension messages.
Constant SRT_CMD_CONGESTION has only one occurrence in the document. And it's not clear what it means from there.
I've found some more info here but I believe it should have it's own paragraph in the RFC. As well as SRT_CMD_FILTER.
The text was updated successfully, but these errors were encountered: