The Security ADs sent the following liaison statement to ETSI on this topic: https://datatracker.ietf.org/liaison/1616/
On Sat, Dec 1, 2018 at 1:11 AM Dmitry Belyavsky <beld...@gmail.com> wrote: > Dear All, > > JFYI. Via Feisti Duck nerwsletter. > > > https://www..etsi.org/news-events/news/1358-2018-11-press-etsi-releases-standards-for-enterprise-security-and-data-centre-management > <https://www.etsi.org/news-events/news/1358-2018-11-press-etsi-releases-standards-for-enterprise-security-and-data-centre-management> > > The eTLS key exchange shall use exactly the same messages and procedures > to establish a set of session keys as a > TLS 1.3 ephemeral Diffie-Hellman key exchange, except for two differences > [2]. > 1) the server shall use a static public/private key pair at Step 2 in > clause 4.3.1; and > 2) the server's certificate at Step 5 shall contain visibility information > as defined in clause 4.3.3 to indicate to the > client that eTLS is in use. > NOTE: Neither the static public key nor the visibility information affects > the operation of a TLS 1.3 compliant > client, so an eTLS server is therefore fully interoperable with TLS 1.3 > compliant clients. > > -- > SY, Dmitry Belyavsky > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
