Re: [quicwg/base-drafts] Describe a new version negotiation mechanism which allows for (#1755)

[Kazuho Oku <[e-mail]>]

@ianswett 
> nit: Above, you meant the middlebox injects a VN, not Retry, correct?

Yes. Thank you for noticing that.

> My thinking was the client would only list other versions it likes as well or better than the version it initially tried. ie: it'd try 1, but also list 2.

That's certainly an option, but then you cannot detect downgrade attacks that happen between the wire-compatible versions too.

IMO, it is beneficial to define two version negotiation mechanisms (i.e. one uses VN and one uses the proposed method) as independent as possible, and that leads me to think that the client should include all the versions it can use in the TP, regardless of what the interaction using VN was.

> In my mind, the question of timing comes down to whether we think this will be helpful to upgrade from draft IETF versions to the 'final' v1 . I'd like to think the frames are not likely to change prior to v1 so that feature won't need to be exercised, but that's probably wishful thinking.

That makes sense. Thank you for pointing that out.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1755#issuecomment-425561377