Skip to content
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

Review and improve "Acknowledgement and Lost Packet Handling" section #108

Open
4 tasks
mbakholdina opened this issue Sep 2, 2021 · 0 comments
Open
4 tasks

Comments

@mbakholdina
Copy link
Collaborator

Review and improve "Acknowledgement and Lost Packet Handling" section:

  • Introduce loss-triggered and periodic NAK reports terms.
  • The difference between 2 NAK packets in "NAK (Negative Acknowledgement or Loss Report)" section.
  • The difference between full, small, and light ACKs.
  • The following abstract is now in both "Packet Acknowledgement (ACKs, ACKACKs)" and "Too-Late Packet Drop" sections. It better fits "Too-Late Packet Drop" section, however we should tell about fake ACKs in the first section too.

When a receiver encounters the situation where the next packet to be played was not
successfully received from the sender, it will "skip" this packet (see {{too-late-packet-drop}})
and send a fake ACK. To the sender, this fake ACK is a real ACK, and so it just behaves as if the packet had been received.
This facilitates the synchronization between SRT sender and receiver. The fact that a packet was
skipped remains unknown by the sender. Skipped packets are recorded in the statistics on the
SRT receiver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant