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

Alternative to defining a bunch of MP-specific frames #323

Open
martinthomson opened this issue Mar 20, 2024 · 3 comments
Open

Alternative to defining a bunch of MP-specific frames #323

martinthomson opened this issue Mar 20, 2024 · 3 comments

Comments

@martinthomson
Copy link
Member

martinthomson commented Mar 20, 2024

With the new explicit path identifier, maybe I can suggest an improvement.

Look at Victor's https://datatracker.ietf.org/doc/draft-vvv-quic-namespaces/ It strikes me that the trick he is using with the NS frame there might be useful for MP QUIC. Only path-specific frames would be affected. You can even start with a default value of the current path.

@marten-seemann
Copy link
Contributor

Not treating frames as separate entities breaks a ton of assumption I have in my code. I think this massively complicates implementations.

@qdeconinck
Copy link
Contributor

Actually, this was already discussed a bit as part of #214 (#214 (comment)); I believe frames should be fully self-contained, and not doing so would complicate at lot implementations.

@mirjak
Copy link
Collaborator

mirjak commented May 14, 2024

Given this was discussed in #214 already, can we close this issue?

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

No branches or pull requests

4 participants