My personal opinion is that reuse is clearly out of scope, especially given the diverging opinions in the working group on this topic.
I'm going to let the chairs step in and let us know what their view of the scope is. David On Sat, Feb 29, 2020 at 4:50 PM Viktor Dukhovni <ietf-d...@dukhovni.org> wrote: > On Sat, Feb 29, 2020 at 04:34:17PM -0800, David Schinazi wrote: > > > I think that what you bring up here has value, but I do not see it in > > scope of draft-ietf-tls-ticket-request. > > I don't see how it can be out of scope. The abstract clearly > puts it in scope: > > TLS session tickets enable stateless connection resumption for > clients without server-side, per-client state. Servers vend an > arbitrary number of session tickets to clients, at their discretion, > upon connection establishment. Clients store and use tickets when > resuming future connections. This document describes a mechanism by > which clients can specify the desired number of tickets needed for > future connections. This extension aims to provide a means for > servers to determine the number of tickets to generate in order to > reduce ticket waste, while simultaneously priming clients for future > connection attempts. > > And even without reuse, the two separate counters aid in producing the > right number of tickets on routine resumption vs. session renegotiation. > > -- > 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
