webrtc: support `FIN_ACK`
Open
difficulty:moderate
getting-started
help wanted
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
Implement webrtc FIN_ACK specification.
https://github.com/libp2p/specs/pull/582
Motivation
Closing data channels without data loss.
Current Implementation
Are you planning to do it yourself in a pull request?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked FIN_ACK specification and inspect open pull request #5687, which is already addressing this issue. Trace the existing WebRTC data-channel closing path from the implementation and its tests, if present. Done means FIN_ACK is implemented according to the specification and closing data channels does not lose data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- audio-video-rtc, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100