Re: [TLS] Status of draft-ietf-tls-esni

[Arnaud Taddei <[e-mail]>]

Hi Eric, sorry I am late, thank you for all the amount of work, really appreciate.

Unfortunately bad timing for me to work on it at the moment as all your contributions on GitHub came when ITU-T SG17 (1) started last week.

So, to set expectations, I will resurface here next week when SG17 is finished.

PS:


  1.  Being SG17 Vice Chair we are facing now 187 contributions (+30%) including 62 new work items (+100%) and I am in charge of the equivalent of the whole ‘dispatch’ … so have nearly 200+ texts in my head at the moment, let alone a number of other problems to fix. • 18 hours work per day including week end.



From: TLS <[e-mail]> on behalf of Eric Rescorla <[e-mail]>
Date: Saturday, 17 February 2024 at 19:56
To: <[e-mail]>
Subject: [TLS] Status of draft-ietf-tls-esni
Hi folks,

I wanted to provide an update on draft-ietf-tls-esni. I went through
all existing PRs and issues as well as some of the recent list
discussion. This message provides a summary of the status:

PRs
* 594: A first proposal to fix the no-sni section [Arnaud Taddei]
  I think this is fine and will merge on 2/24 unless people object.

* 602: More explanatory text [EKR]
  This is a pretty substantial rewrite of the overview section
  to address some of the clarity issues raised by Arnaud Taddei.
  This is editorial, but needs review.

* 603: Clarify that you can fall back by providing no ECH in EE [EKR]
  This addresses a point made by Elardus Erasmus about what indicated
  you're disabling ECH. Hopefully this is uncontroversial.

Arnaud also provided two editorial PRs with clarifications
(587 and 588). I believe that these are addressed by 602.



ISSUES
* 866: Server retry flow, section 7.1 [Robert Sayre]
  I'm not seeing support for a change here, so I propose to
  close unless someone provides a PR that receives some
  support.

* 591: Can we clarify the Misconfiguration section? [Arnaud Taddei]
  This is addressed in PR #602, so I propose to close it once that
  lands.


Finally, Erlardus Erasmus raised some issues around limiting
retries (https://mailarchive.ietf.org/arch/msg/tls/bvvWbtxJAiMfilfy32EvdaCszQ4/<https://www.google.com/url?q=https://mailarchive.ietf.org/arch/msg/tls/bvvWbtxJAiMfilfy32EvdaCszQ4/&source=gmail-imap&ust=1708801018000000&usg=AOvVaw2BezPIeAsLPGHpU72ZQRrO>).
I have filed an issue with some thoughts at:

  https://github.com/tlswg/draft-ietf-tls-esni/issues/604<https://www.google.com/url?q=https://github.com/tlswg/draft-ietf-tls-esni/issues/604&source=gmail-imap&ust=1708801018000000&usg=AOvVaw0re96sZhE8WbqXmtooET6z>

I think this needs some discussion before we have a PR.


Assuming that there are no strong objections to the resolutions
of the PRs and issues above and we can get consensus on Issue 604,
I should be able to spin a WGLC-ready version of ECH before the
draft deadline.

-Ekr
















-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.