On Sat, Feb 1, 2020 at 7:59 PM Viktor Dukhovni <ietf-d...@dukhovni.org> wrote:
> On Sat, Feb 01, 2020 at 07:04:53PM -0800, Watson Ladd wrote: > > > > The benefit of the new value of "0" is *unambiguous* signalling that > the > > > client would like to reuse the ticket if possible, and the new "255" > > > then carries the "We don't need no stinking tickets" signal. > > > > > > > I'd be happier with a magic 0, or a N = valid tickets at the end > > including the one used, then swapping 2 values and making one magic. > > (For those of you who aren't bridge fiends: > > https://en.wikipedia.org/wiki/Brown_sticker) > > Sorry, no idea what that above means. And is it simpler than the > proposal under discussion (which got some fine-tuning in early > feedback)? > So one proposal in above is we treat 0 tickets as "ensure I have a valid ticket, either this one or a new one" and all other numbers are straight asks for that many tickets. The other proposal is N means "ensure I have N valid tickets, including the one I used on this connection". I find both cleaner then the 0 and 255 swap. > -- > Viktor. > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > -- "Man is born free, but everywhere he is in chains". --Rousseau.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
