You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: