On 11/17/2016 06:12 PM, Sean Turner wrote:
At IETF 97, the chairs lead a discussion to resolve whether the WG should
rebrand TLS1.3 to something else. Slides can be found @
https://www.ietf.org/proceedings/97/slides/slides-97-tls-rebranding-aka-pr612-01.pdf.
The consensus in the room was to leave it as is, i.e., TLS1.3, and to not
rebrand it to TLS 2.0, TLS 2, or TLS 4. We need to confirm this decision on
the list so please let the list know your top choice between:
- Leave it TLS 1.3
- Rebrand TLS 2.0
- Rebrand TLS 2
- Rebrand TLS 4
by 2 December 2016.
...
TLS 4.
TLS 1.3 introduces major changes to message flow and substantial
redesign of crypto.
I will respectfully remind that earlier this year the WG has made a
decision to break backward compatibility with large number of devices by
rejecting an option to extend allowed in TLS 1.3 RSA PKCS#1.5 signature
padding scheme to all portions of the handshake. The solution was that
these peers must keep using TLS 1.2
https://www.ietf.org/mail-archive/web/tls/current/msg19360.html .
Changes of this magnitude are not typically associated with a "dot"
release.
+ what other said on confusion with SSL. I don't see this one as a big
deal, but I will go with the consensus of "4.0" v.s "2.0". "1.3" is the
worst choice here.
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
