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

Feature request: compress away IP and port from each HTTP Datagram #14

Open
DavidSchinazi opened this issue Feb 15, 2023 · 1 comment · May be fixed by #19
Open

Feature request: compress away IP and port from each HTTP Datagram #14

DavidSchinazi opened this issue Feb 15, 2023 · 1 comment · May be fixed by #19
Assignees

Comments

@DavidSchinazi
Copy link
Collaborator

From Ben Schwartz on the list:

In IPv6, the proposed header adds 19 bytes of overhead per packet. For Opus compressed audio, this represents >50% of the media bandwidth for low-bitrate VoIP (20ms frames, 12kbps) or interactive music (2.5ms frames, 112kbps).

The natural benchmark for this draft is TURN. To reduce per-packet overhead, TURN offers a form of "header compression" called Channels (https://datatracker.ietf.org/doc/html/rfc8656#section-3.5). The equivalent thing for this draft would be to define a dynamic context allocation option.

@DavidSchinazi
Copy link
Collaborator Author

This makes sense. I would imagine performing this by using a capsule to register a context ID that maps to a given (IP version, IP address, UDP port) tuple

@asingh-g asingh-g linked a pull request Nov 1, 2023 that will close this issue
@asingh-g asingh-g self-assigned this Nov 2, 2023
@asingh-g asingh-g linked a pull request Nov 2, 2023 that will close this issue
@asingh-g asingh-g linked a pull request Feb 29, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants