Description TODOS for us
feedback stephen
change title
add context: the protocols are what they are, the browser vendors want speed, etc... that's why we ended up where we are...
too many "mights"....
if you publish the priv. key then ... your own problem. Rather say "this is a known risk"
look at rfc 8744 considered the requiremetns for TLS and possible solutions
the browser implementers want faster times...
DNSSEC -> don't insist on it.
ECH does not cause correlation , but rather centralization lends to ...
Split mode does not match any biz model. But centralization already is a biz model :)
GREASE is missing!!!
NIS --> leave it out.
7.2. ... but this is an incremental deployment, don't assume it all goes at once. But what about correlation then?
7.3.1: not sure clock sync is a real threat there --> don't keep priv. keys around for very long
7.3.1: I think wkech is probably correct to depend on HTTPS working --> fix it.
in the summary - highlight new things. Or mention that all issues were known, but we collect them.
convert to LaTeX from markdown (see the interop report: https://defo.ie/ech-interop-report.pdf )
You can’t perform that action at this time.
