Hi,
We have submitted an updated version of draft-mattsson-eap-tls13. The new
version is a significant update based on the feedback and comments on the EAP
and EMU mailing lists. The new version also fills in all the sections that was
TDB in the -00 version.
- The draft now updates version updates RFC5216 (instead of obsoleting) and all
text have been updated to make sure that the update stays compatible with all
existing implementations of EAP-TLS.
- Added more text on what TLS 1.3 changes and why an update to RFC5216 is
needed.
- As this is now an update, all duplicated text is removed, and the draft only
describe the changes to message flow, messages, key derivation, privacy, etc.
when TLS 1.3 is used. The new draft follows the structure of RFC5216 and lists
updates (if any) to each section.
- Clearly stated that PSK authentication SHALL not be used (except for
resumption).
- Due to the encrypted handshake in TLS 1.3 there is no longer any need for the
EAP client to send and empty certificate list. A privacy section has been added
that explains this.
- A key hierarchy section has been added specifying that when TLS 1.3 is used
then Key_Material, IV, and Session-Id SHALL be derived from the
exporter_master_secret using the TLS exporter interface.
Comments appreciated.
Cheers,
John
On 2018-01-09, 14:16, "internet-dra...@ietf.org" <internet-dra...@ietf.org>
wrote:
A new version of I-D, draft-mattsson-eap-tls13-01.txt
has been successfully submitted by John Mattsson and posted to the
IETF repository.
Name: draft-mattsson-eap-tls13
Revision: 01
Title: Using EAP-TLS with TLS 1.3
Document date: 2018-01-08
Group: Individual Submission
Pages: 15
URL:
https://www.ietf.org/internet-drafts/draft-mattsson-eap-tls13-01.txt
Status: https://datatracker.ietf.org/doc/draft-mattsson-eap-tls13/
Htmlized: https://tools.ietf.org/html/draft-mattsson-eap-tls13-01
Htmlized:
https://datatracker.ietf.org/doc/html/draft-mattsson-eap-tls13-01
Diff:
https://www.ietf.org/rfcdiff?url2=draft-mattsson-eap-tls13-01
Abstract:
This document specifies the use of EAP-TLS with TLS 1.3 while
remaining backwards compatible with existing implementations of EAP-
TLS. TLS 1.3 provides significantly improved security, privacy, and
reduced latency when compared to earlier versions of TLS.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
