On 16/11/2019 11:04, Viktor Dukhovni wrote: >> We should probably be emphasizing that *all* policy belongs on the server, >> and >> we are just defining a signal for the client to convey some information as >> input >> to the server's decision. In that mindset I'm not sure that the "subtract >> one" >> signal is the most satisfying design (though I concede that it is probably >> the >> most efficient encoding). > > Do you have an alternative suggestion?
The obvious encoding to me would be to reserve the all-bits-set value to mean "client wants no tickets", all-bits-clear to mean "client prefers to reuse tickets", anything else meaning "please serve up to this many fresh tickets". -- Cheers, Jeremy _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
