MIME-Version: 1.0
References: <AFAA7D8A-D19F-4942-A404-0764EBBC57EE@tsinghua.org.cn>
In-Reply-To: <AFAA7D8A-D19F-4942-A404-0764EBBC57EE@tsinghua.org.cn>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Sat, 15 Mar 2025 22:09:51 +0100
Message-ID: 
 <CADqLbzKkbPwEMDxZum7sxWaFr9A4YXTHh4JZ=5a1Yiw7Wg_G1A@mail.gmail.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Content-Type: multipart/alternative; boundary="0000000000007d9946063067fa4c"
Message-ID-Hash: 725UN5TVLRI2TXXUVJ5YMBQREZOO5NXX
CC: TLS Mailing List <tls@ietf.org>,
 draft-wang-tcpm-tcp-service-affinity-option@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BTLS=5D_Re=3A_Co-Authors_to_be_invited_for_one_draft_that_requir?=
 =?utf-8?q?es_the_extension_of_TLS_protocol?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tls/s-Rvvraztz7t09E7oqi8tB5IdDY>

--0000000000007d9946063067fa4c
Content-Type: text/plain; charset="UTF-8"

Do I correctly understand that you are proposing the mechanism to save some
traffic and computation when we have a previously happened communication?

On Sat, 15 Mar 2025, 16:39 Aijun Wang, <wangaijun@tsinghua.org.cn> wrote:

> Hi, All TLS experts:
>
> We are seeking the experts from the TLS WG, who is/are familiar with the
> TLS protocol itself and know how to extend it to accommodate new features
> within TLS.
>
> We have provided such extensions within the TCP protocol(
> https://datatracker.ietf.org/doc/html/draft-wang-tcpm-tcp-service-affinity-option-06)
> and now want to extend it to the TLS protocol.
>
> If you have such experiences and interested to cooperate with us, please
> contact me, via mail, or on-site at Bangkok during the IETF 122 meeting.
>
> I can explain the background of such extensions with you and discuss the
> futures cooperation expectations.
>
> Aijun Wang
> China Telecom
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>

--0000000000007d9946063067fa4c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Do I correctly understand that you are proposing the mech=
anism to save some traffic and computation when we have a previously happen=
ed communication?=C2=A0</div><br><div class=3D"gmail_quote gmail_quote_cont=
ainer"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, 15 Mar 2025, 16:39 Aij=
un Wang, &lt;<a href=3D"mailto:wangaijun@tsinghua.org.cn">wangaijun@tsinghu=
a.org.cn</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"auto">Hi, All TLS experts:<div><br></div><div>We are seeking the experts f=
rom the TLS WG, who is/are familiar with the TLS protocol itself and know h=
ow to extend it to accommodate new features within TLS.</div><div><br></div=
><div>We have provided such extensions within the TCP protocol(<a href=3D"h=
ttps://datatracker.ietf.org/doc/html/draft-wang-tcpm-tcp-service-affinity-o=
ption-06" target=3D"_blank" rel=3D"noreferrer">https://datatracker.ietf.org=
/doc/html/draft-wang-tcpm-tcp-service-affinity-option-06</a>) and now want =
to extend it to the TLS protocol.</div><div><br></div><div>If you have such=
 experiences and interested to cooperate with us, please contact me, via ma=
il, or on-site at Bangkok during the IETF 122 meeting.</div><div><br></div>=
<div>I can explain the background of such extensions with you and discuss t=
he futures cooperation expectations.</div><div><br></div><div><div dir=3D"l=
tr">Aijun Wang<div>China Telecom</div></div></div></div>___________________=
____________________________<br>
TLS mailing list -- <a href=3D"mailto:tls@ietf.org" target=3D"_blank" rel=
=3D"noreferrer">tls@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:tls-leave@ietf.org" targe=
t=3D"_blank" rel=3D"noreferrer">tls-leave@ietf.org</a><br>
</blockquote></div>

--0000000000007d9946063067fa4c--