Alternative to defining a bunch of MP-specific frames

quicwg / multipath

In-progress version of draft-ietf-quic-multipath

Other

49 stars 17 forks source link

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

Closed martinthomson closed 3 weeks ago

martinthomson commented 3 months ago

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 commented 3 months ago

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

qdeconinck commented 3 months ago

Actually, this was already discussed a bit as part of #214 (https://github.com/quicwg/multipath/issues/214#issuecomment-1614669787); I believe frames should be fully self-contained, and not doing so would complicate at lot implementations.

mirjak commented 2 months ago

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

mirjak commented 3 weeks ago

Closing this issue now. Please re-open if you think it needs further discussion.