Well, admittedly neither user_mapping, nor cert_type is hugely popular. It would not make sense for the TLS 1.3 spec to be on hold until these extensions are reconciled with it.
However, I do think that a TLS 1.3 ClientHello should be able to advertise extensions that are not defined for TLS 1.3, when the client is willing to accept TLS<=1.2. Cheers, Andrei -----Original Message----- From: ilariliusva...@welho.com [mailto:ilariliusva...@welho.com] Sent: Friday, March 10, 2017 10:43 AM To: Andrei Popov <andrei.po...@microsoft.com> Cc: Eric Rescorla <e...@rtfm.com>; tls@ietf.org Subject: Re: [TLS] Updating for non-X.509 certificate types On Fri, Mar 10, 2017 at 06:04:54PM +0000, Andrei Popov wrote: > Ø Does anyone use this? > > Ø I don't think anyone uses it. > > Au contraire: Windows TLS stack supports user_mapping and this > mechanism appears to be somewhat in use. However, I agree that this > falls into the category of extensions that need to be either > deprecated or redefined for TLS 1.3. Oh, sorry, quoting context fail: I meant that nobody uses cert_type, not that nobody uses user_mapping. -Ilari _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
