There was a lengthy discussion after the last time this was discussed. Can I request that an editor (or a chair) summarize that discussion and the resulting actions (if any)? I was involved in that discussion, but I don't see any changes from that. I'm totally OK with publication as-is, but I want to make sure that nothing got dropped.
p.s., it might make sense to include some advisory text on prioritization of tickets vs. application data. I can see a naive implementation of this seriously degrading application performance. For instance, it doesn't take that many tickets to fill an early TCP congestion window. p.p.s., yes, if you keep issuing last calls, I will keep finding new things. On Wed, Nov 6, 2019, at 03:05, Sean Turner wrote: > All, > > This is the working group last call for the "TLS Ticket Requests" draft > available at > https://datatracker.ietf.org/doc/draft-ietf-tls-ticketrequests/. > Please review the document and send your comments to the list by 2359 > UTC on 19 November 2019. > > Note the the GH repo for this draft can be found at: > https://github.com/tlswg/draft-ietf-tls-ticketrequest > > Thanks - J&S > _______________________________________________ > 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
