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

evaluate bandwidth requirements for probing multiple paths #8

Open
marten-seemann opened this issue Jul 29, 2023 · 1 comment
Open

Comments

@marten-seemann
Copy link
Owner

When presenting this proposal in AVTCore at IETF 117, some concern was voiced that probing using RFC 9000's path probing mechanism consumes more bandwidth than probing using STUN packets. While that's true, it's not clear if that poses a problem in 2023. We should evaluate and at the very least add these considerations to the draft.

@marten-seemann
Copy link
Owner Author

I'm still not convinced that bandwidth is a major concern here. Especially for video applications, the bandwidth requirements of the application most likely far surpass the bandwidth consumed by path probes.

However, there's a case to be made that any protocol mechanism that creates state on the peer needs to be limited to protect from DoS attacks. This can either be done explicitly (by setting a limit), or implicitly (by rejecting everything that exceeds a peer-defined limit). #11 suggests a way limit the number of concurrent path validations by using the transport parameter.

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