search

martinduke / draft-duke-quic-load-balancers

An internet draft to standardize the way that QUIC servers and load balancers can support routable, unlinkable connection IDs
Other
2 stars 4 forks source link

added retry services #49

Closed martinduke closed 5 years ago

martinduke commented 5 years ago

At long last, this is a writeup of what @nibanks proposed back in NYC. There's a bit further thought in this design over and above what he presented then.

martinduke commented 5 years ago

Addresses #29, obviously.

martinduke commented 5 years ago

I rewrote the shared-state section completely. I believe this addresses all of @nibanks's review that I didn't push back on.

Thanks for your comments!

martinduke commented 5 years ago

Do you have concrete suggestion the VN/Retry thing? If not, let's continue with the review and file a separate issue about this. The WG is not going to rule on this in the timescale of this PR.

nibanks commented 5 years ago

For the VN/Retry thing, I was thinking that the server will need to report it's supported versions when initially setting up. That info would be passed to the retry service. The problem (besides the extra state exchange) is if the same retry service sits in front of several different servers that all support different versions. It could definitely complicate things.