MIME-Version: 1.0
References: 
 <177245334761.3494122.16417546920214555219@dt-datatracker-6ff7c68975-7k42g>
In-Reply-To: 
 <177245334761.3494122.16417546920214555219@dt-datatracker-6ff7c68975-7k42g>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 2 Mar 2026 17:48:29 +0530
Message-ID: 
 <CAFpG3gdR3omguE1-A-SFhgq+JukDer3Uk9kk58TvrBa+ZFO6fA@mail.gmail.com>
To: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000da6c04064c0997b9"
Message-ID-Hash: 5EYGZKQ4A2KNTP4RNCXD7TQIW4ROTPAV
Precedence: list
Subject: =?utf-8?q?=5BTLS=5D_Fwd=3A_I-D_Action=3A_draft-ietf-tls-extended-key-update-?=
	=?utf-8?q?10=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tls/KFUD3FPcrUlJmnXSyb3s25UFbdo>

--000000000000da6c04064c0997b9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi ,

The main changes in
https://datatracker.ietf.org/doc/draft-ietf-tls-extended-key-update/ addres=
ses
the session resumption threat identified by the FATT team. The revised
draft also tightens serialization rules between EKU and post-handshake
client authentication to address the comments from Ilari.

Best Regards,
-Tiru

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, 2 Mar 2026 at 17:39
Subject: [TLS] I-D Action: draft-ietf-tls-extended-key-update-10.txt
To: <i-d-announce@ietf.org>
Cc: <tls@ietf.org>


Internet-Draft draft-ietf-tls-extended-key-update-10.txt is now available.
It
is a work item of the Transport Layer Security (TLS) WG of the IETF.

   Title:   Extended Key Update for Transport Layer Security (TLS) 1.3
   Authors: Hannes Tschofenig
            Michael T=C3=BCxen
            Tirumaleswar Reddy
            Steffen Fries
            Yaroslav Rosomakho
   Name:    draft-ietf-tls-extended-key-update-10.txt
   Pages:   41
   Dates:   2026-03-02

Abstract:

   TLS 1.3 ensures forward secrecy by performing an ephemeral Diffie-
   Hellman key exchange during the initial handshake, protecting past
   communications even if a party's long-term keys (typically a private
   key with a corresponding certificate) are later compromised.  While
   the built-in KeyUpdate mechanism allows application traffic keys to
   be refreshed during a session, it does not incorporate fresh entropy
   from a new key exchange and therefore does not provide post-
   compromise security.  This limitation can pose a security risk in
   long-lived sessions, such as those found in industrial IoT or
   telecommunications environments.

   To address this, this specification defines an extended key update
   mechanism that performs a fresh Diffie-Hellman exchange within an
   active session, thereby ensuring post-compromise security.  By
   forcing attackers to exfiltrate new key material repeatedly, this
   approach mitigates the risks associated with static key compromise.
   Regular renewal of session keys helps contain the impact of such
   compromises.  The extension is applicable to both TLS 1.3 and DTLS
   1.3.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tls-extended-key-update/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-tls-extended-key-update-10.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-tls-extended-key-upd=
ate-10

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-leave@ietf.org

--000000000000da6c04064c0997b9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi ,<br><br>The main changes in=C2=A0<a href=3D"https://da=
tatracker.ietf.org/doc/draft-ietf-tls-extended-key-update/" rel=3D"noreferr=
er" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-tls-exten=
ded-key-update/</a>=C2=A0addresses the session resumption threat identified=
 by the FATT team. The revised draft also tightens serialization rules betw=
een EKU and post-handshake client authentication to address the comments fr=
om Ilari.<div><br><div>Best Regards,<br>-Tiru<br><br><div class=3D"gmail_qu=
ote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">----------=
 Forwarded message ---------<br>From: <span dir=3D"auto">&lt;<a href=3D"mai=
lto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Da=
te: Mon, 2 Mar 2026 at 17:39<br>Subject: [TLS] I-D Action: draft-ietf-tls-e=
xtended-key-update-10.txt<br>To:  &lt;<a href=3D"mailto:i-d-announce@ietf.o=
rg">i-d-announce@ietf.org</a>&gt;<br>Cc:  &lt;<a href=3D"mailto:tls@ietf.or=
g">tls@ietf.org</a>&gt;<br></div><br><br>Internet-Draft draft-ietf-tls-exte=
nded-key-update-10.txt is now available. It<br>
is a work item of the Transport Layer Security (TLS) WG of the IETF.<br>
<br>
=C2=A0 =C2=A0Title:=C2=A0 =C2=A0Extended Key Update for Transport Layer Sec=
urity (TLS) 1.3<br>
=C2=A0 =C2=A0Authors: Hannes Tschofenig<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Michael T=C3=BCxen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Tirumaleswar Reddy<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Steffen Fries<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Yaroslav Rosomakho<br>
=C2=A0 =C2=A0Name:=C2=A0 =C2=A0 draft-ietf-tls-extended-key-update-10.txt<b=
r>
=C2=A0 =C2=A0Pages:=C2=A0 =C2=A041<br>
=C2=A0 =C2=A0Dates:=C2=A0 =C2=A02026-03-02<br>
<br>
Abstract:<br>
<br>
=C2=A0 =C2=A0TLS 1.3 ensures forward secrecy by performing an ephemeral Dif=
fie-<br>
=C2=A0 =C2=A0Hellman key exchange during the initial handshake, protecting =
past<br>
=C2=A0 =C2=A0communications even if a party&#39;s long-term keys (typically=
 a private<br>
=C2=A0 =C2=A0key with a corresponding certificate) are later compromised.=
=C2=A0 While<br>
=C2=A0 =C2=A0the built-in KeyUpdate mechanism allows application traffic ke=
ys to<br>
=C2=A0 =C2=A0be refreshed during a session, it does not incorporate fresh e=
ntropy<br>
=C2=A0 =C2=A0from a new key exchange and therefore does not provide post-<b=
r>
=C2=A0 =C2=A0compromise security.=C2=A0 This limitation can pose a security=
 risk in<br>
=C2=A0 =C2=A0long-lived sessions, such as those found in industrial IoT or<=
br>
=C2=A0 =C2=A0telecommunications environments.<br>
<br>
=C2=A0 =C2=A0To address this, this specification defines an extended key up=
date<br>
=C2=A0 =C2=A0mechanism that performs a fresh Diffie-Hellman exchange within=
 an<br>
=C2=A0 =C2=A0active session, thereby ensuring post-compromise security.=C2=
=A0 By<br>
=C2=A0 =C2=A0forcing attackers to exfiltrate new key material repeatedly, t=
his<br>
=C2=A0 =C2=A0approach mitigates the risks associated with static key compro=
mise.<br>
=C2=A0 =C2=A0Regular renewal of session keys helps contain the impact of su=
ch<br>
=C2=A0 =C2=A0compromises.=C2=A0 The extension is applicable to both TLS 1.3=
 and DTLS<br>
=C2=A0 =C2=A01.3.<br>
<br>
The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tls-extended-key-upd=
ate/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc=
/draft-ietf-tls-extended-key-update/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-tls-extended-key-upda=
te-10.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archi=
ve/id/draft-ietf-tls-extended-key-update-10.html</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-tls-exten=
ded-key-update-10" rel=3D"noreferrer" target=3D"_blank">https://author-tool=
s.ietf.org/iddiff?url2=3Ddraft-ietf-tls-extended-key-update-10</a><br>
<br>
Internet-Drafts are also available by rsync at:<br>
rsync.ietf.org::internet-drafts<br>
<br>
<br>
_______________________________________________<br>
TLS mailing list -- <a href=3D"mailto:tls@ietf.org" target=3D"_blank">tls@i=
etf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:tls-leave@ietf.org" targe=
t=3D"_blank">tls-leave@ietf.org</a><br>
</div></div></div></div>

--000000000000da6c04064c0997b9--