[TLS] Re: 【Reply to the comments after the presentation in Montreal】RE: Re: FW: New Version Notification for draft-wang-tls-service-affinity-00.txt

[Aijun Wang <[e-mail]>]

Hi, Usama:

We will refine the draft in the coming days which will try to address your comments.

Aijun Wang
China Telecom


Aijun Wang
China Telecom
> On Jan 30, 2026, at 19:09, Muhammad Usama Sardar <[e-mail]> wrote:
> 
> On 30.01.26 09:50, Aijun Wang wrote:
>> Thanks for your endorsement to implement it at TLS layer.
> Well, I NEVER endorsed it to be done at TLS layer. As I said clearly, you have to defend that yourself. I shared some preliminary working that -- I hope -- will help you move forward. Until I say explicitly that I have evaluated both options, please don't take anything for granted.
>> 
>> As your suggestion, if TLS 1.3 has no explicit session identifier, we can utilize the implicit one, for example, PSK, as the identification of the corresponding session.
>>  
>> The idea of this draft is actually very straightforward:
>> 1)  Notify the client securely another address
>> 2)  Start one new TLS session which can utilize the PSK of the previous session(then skip the negotiation process for the new session).
>> 3)  Keep the application unnoticed, or application agnostic.
> While the idea may be straightforward for you, the draft is unfortunately not straightforward for me. There is no clear description of problem statement, motivation, threat model and desired security goals. I requested you to add authentic references in the draft but I don't see any change. As far as the protocol diagram is concerned, I have requested you at least 3 times to move the protocol to TLS 1.3 but nothing has changed in the draft.
> Without these requested inputs, I am unable to help you any further. Sorry!
> -Usama