Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3

Meiling Chen <> Sat, 08 May 2021 08:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C53903A438F for <>; Sat, 8 May 2021 01:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.868
X-Spam-Status: No, score=-1.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cBn0E9AbUrkT for <>; Sat, 8 May 2021 01:24:45 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8652E3A438C for <>; Sat, 8 May 2021 01:24:38 -0700 (PDT)
Received: from (unknown[]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee260964ab0c36-ca088; Sat, 08 May 2021 16:24:16 +0800 (CST)
X-RM-TRANSID: 2ee260964ab0c36-ca088
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[]) by rmsmtp-syy-appsvr07-12007 (RichMail) with SMTP id 2ee760964aae0be-b65a6; Sat, 08 May 2021 16:24:16 +0800 (CST)
X-RM-TRANSID: 2ee760964aae0be-b65a6
Date: Sat, 8 May 2021 16:24:38 +0800
From: "Meiling Chen" <>
To: "Joseph Salowey" <>, emu <>
References: <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart570423715543_=----"
Archived-At: <>
Subject: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 08 May 2021 08:24:55 -0000

I have noticed that there is one modification in the Figure 1 flow diagram of edition 15.
edition 14 has TLS close_notify message, but in edition 15 changed into TLS application Data 0x00.
in the section 2.1.1, it says" TLS application data 0x00 is therefore to
   be interpreted as success after the EAP-Request that contains TLS
   application data 0x00.  After the EAP-TLS server has received an
   empty EAP-Response to the EAP-Request containing the TLS application 
   data 0x00, the EAP-TLS server sends EAP-Success."
is the data 0x00 that mean not send any more handshake messages?
another question: what's the format of the EAP-success measge, plaintext ot ciphertext?

Best Regards,
From: Joseph Salowey
Date: 2021-05-05 23:33
Subject: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
This is the working group last-call for draft-ietf-emu-eap-tls13.  Please review the draft, focus on the recent changes and submit your comments to the list by May 20, 2021.   



The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at: