Hi! Based on Tommy Pauly’s suggestion [0], Joe and I believe that the best way for us to get to the place where we can declare rough consensus is to:
* 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. * Consider adoption of an individual draft that describes an extension for hinting ticket reuse. This draft will also discuss the use cases around ticket reuse. Obviously, the rationale here is to progress this relatively simple draft, but allow the reuse discussion to continue. Again, we believe this allows us to declare rough consensus and avoid any deadlocks. Please let us know your thoughts on the PR, which (assuming the PR gets consensus) we plan to ask the authors to merge sometime around 6 March. Thanks, Joe and Sean [0] https://mailarchive.ietf.org/arch/msg/tls/fOmUYve5DLomjx3-Df9xQy0bocg/ [1] https://github.com/tlswg/draft-ietf-tls-ticketrequest/pull/17 _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
