Hi Viktor, I like the editorial changes in your PR #18, as they do a good job of explaining things. However, I don't think we should add a second count in this extension. Allowing ticket reuse is not something we have consensus for in the WG, and I would like to see this discussion happen in the TLS WG, but not preventing this draft from moving forward.
Thanks, David On Sat, Feb 29, 2020 at 1:18 AM Viktor Dukhovni <ietf-d...@dukhovni.org> wrote: > On Fri, Feb 28, 2020 at 11:23:48AM -0500, Sean Turner wrote: > > > * Consider the PR: [1]. This PR explains that when racing connections, > the client will not necessarily know the number of tickets it will > “consume”, so it should either have enough tickets for two subsequent > handshake resumptions; or else use fewer tickets but potentially run out. > > > > My sincere and deep apologies about tardiness in drafting my PR, it is > now done. This builds on the above PR, but also addresses more fully > happy eyeballs, etc. by observing that even clients that never reuse > ticket can benefit from separate counts for resumption vs. full > handshakes, and can't generally predict which they'll get. > > https://github.com/tlswg/draft-ietf-tls-ticketrequest/pull/18 > > -- > Viktor. > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
