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/).
I have filed an issue with some thoughts at:

  https://github.com/tlswg/draft-ietf-tls-esni/issues/604

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
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to