Hi Nico, > But also, this WG has tried to accomodate things like SChannel whose API > designs are very different from others and impinge on what is feasible in the > protocol. E.g., reconnects are avoided. Both Session ID-based and session ticket-based TLS resumption options are supported in schannel. It is true that the API design is different from others (GSS-like, an attempt to match Windows APIs used for other security protocols, e.g., Kerberos).
Cheers, Andrei -----Original Message----- From: TLS <[email protected]> On Behalf Of Nico Williams Sent: Wednesday, March 4, 2020 9:17 PM To: Watson Ladd <[email protected]> Cc: TLS List <[email protected]> Subject: [EXTERNAL] Re: [TLS] consensus call: draft-ietf-tls-ticketrequests On Wed, Mar 04, 2020 at 08:32:45PM -0800, Watson Ladd wrote: > On Wed, Mar 4, 2020 at 6:07 PM Stephen Farrell > <[email protected]> wrote: > > On 04/03/2020 16:06, Sean Turner wrote: > > > Must the ticket reuse use case be addresses in > > > draft-ietf-tls-ticketrequests? > > > > Yes. I think Viktor's use case is one to not bugger up (even if one > > doesn't need to support it) and don't see how supporting it breaks > > something. (While also disliking generic ticket reuse.) > > It's not the usecase: it's the program. Postfix made architectural > choices that make storing tickets allegedly expensive. Well, Postfix runs about 40% of the world's email infrastructure outside of gmail and yahoo and such, so excuse me, but your response is just not acceptable. But also, this WG has tried to accomodate things like SChannel whose API designs are very different from others and impinge on what is feasible in the protocol. E.g., reconnects are avoided. Nico -- _______________________________________________ TLS mailing list [email protected] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Ftls&data=02%7C01%7CAndrei.Popov%40microsoft.com%7Cf68655dfdfb74261cbe408d7c0c4787e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637189822393462003&sdata=%2F1yYpQkjpBiS7BTz1ZMcEVO4VzTf7AnYfrrOrQR5blQ%3D&reserved=0 _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
