Hi - trying to understand the intent of this: “Don’t stick out” approach to eSNI, now being called ECHO apparently.
About a year ago, the understanding was that eSNI would be identifiable and that enterprises wouldn’t need to use it internally and that it would only be used on the Internet. Is that not the case anymore? On Sun, Apr 12, 2020 at 2:33 AM Repository Activity Summary Bot < do_not_re...@mnot.net> wrote: > Sunday April 12, 2020 Issues tlswg/draft-ietf-tls-esni (+2/-0/💬1) > > 2 issues created: > > - #215 Limit "Don't stick out" to explicit signals > <https://github.com/tlswg/draft-ietf-tls-esni/issues/215> (by > chris-wood) > - #214 Clarify whether ClientHelloInner can support TLS 1.2. > <https://github.com/tlswg/draft-ietf-tls-esni/issues/214> (by > chris-wood) > > 1 issues received 1 new comments: > > - #204 Anonymity sets > <https://github.com/tlswg/draft-ietf-tls-esni/issues/204> (1 by > ret394) > > tlswg/draft-ietf-tls-external-psk-importer (+0/-1/💬1) > > 1 issues received 1 new comments: > > - #26 Clarify MUSTs > <https://github.com/tlswg/draft-ietf-tls-external-psk-importer/issues/26> > (1 by chris-wood) > > 1 issues closed: > > - #26 Clarify MUSTs > <https://github.com/tlswg/draft-ietf-tls-external-psk-importer/issues/26> > > tlswg/tls-exported-authenticator (+1/-0/💬1) > > 1 issues created: > > - #56 Generalize authentication terminology > <https://github.com/tlswg/tls-exported-authenticator/issues/56> (by > chris-wood) > > 1 issues received 1 new comments: > > - #56 Generalize authentication terminology > <https://github.com/tlswg/tls-exported-authenticator/issues/56> (1 by > chris-wood) > > Pull requests tlswg/draft-ietf-tls-esni (+1/-0/💬4) > > 1 pull requests submitted: > > - #213 README: fix links to WG docs > <https://github.com/tlswg/draft-ietf-tls-esni/pull/213> (by > Lekensteyn) > > 1 pull requests received 4 new comments: > > - #209 padding scheme text > <https://github.com/tlswg/draft-ietf-tls-esni/pull/209> (4 by > chris-wood, sayrer, sftcd) > > tlswg/draft-ietf-tls-external-psk-importer (+1/-1/💬0) > > 1 pull requests submitted: > > - #29 Tighten up IANA considerations > <https://github.com/tlswg/draft-ietf-tls-external-psk-importer/pull/29> > (by jsalowey) > > 1 pull requests merged: > > - #28 Editorial pass to simplify text and unify terminology. > <https://github.com/tlswg/draft-ietf-tls-external-psk-importer/pull/28> > > tlswg/draft-ietf-tls-ticketrequest (+1/-0/💬4) > > 1 pull requests submitted: > > - #19 Use two counters for fresh and resumed connections > <https://github.com/tlswg/draft-ietf-tls-ticketrequest/pull/19> (by > chris-wood) > > 1 pull requests received 4 new comments: > > - #19 Use two counters for fresh and resumed connections > <https://github.com/tlswg/draft-ietf-tls-ticketrequest/pull/19> (4 by > chris-wood, martinthomson, tfpauly) > > tlswg/dtls13-spec (+0/-0/💬1) > > 1 pull requests received 1 new comments: > > - #129 Removed term "deprotection" > <https://github.com/tlswg/dtls13-spec/pull/129> (1 by ekr) > > Repositories tracked by this digest: > > - https://github.com/tlswg/draft-ietf-tls-semistatic-dh > - https://github.com/tlswg/draft-ietf-tls-md5-sha1-deprecate > - https://github.com/tlswg/draft-ietf-tls-esni > - https://github.com/tlswg/certificate-compression > - https://github.com/tlswg/draft-ietf-tls-external-psk-importer > - https://github.com/tlswg/draft-ietf-tls-ticketrequest > - https://github.com/tlswg/tls-flags > - https://github.com/tlswg/dtls13-spec > - https://github.com/tlswg/dtls-conn-id > - https://github.com/tlswg/tls-subcerts > - https://github.com/tlswg/oldversions-deprecate > - https://github.com/tlswg/sniencryption > - https://github.com/tlswg/tls-exported-authenticator > - https://github.com/tlswg/draft-ietf-tls-grease > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
