I count 32 messages like this, relating to the ESNI draft, as github discussion, in the last 24 hours.
Some of those do not need to be reflected to the TLS WG list, but I suspect others do, and before discussion resolves into an unchangeable outcome on github. Note: when I say "suspect" I don't mean anyone's being tricky, I just don't keep open browser tabs for all this stuff because I prefer to handle substantive discussion via email on the list. Are the chairs actively checking that issue-discussion on github is being properly brought to the mailing list as and when needed? Am I alone in being concerned that the efficiency of github for some is leading to others with different workflows being left out of discussion? Ta, S. -------- Forwarded Message -------- Subject: [tlswg/draft-ietf-tls-esni] Fix superfluous padding edge cases. (#258) Date: Tue, 11 Aug 2020 06:54:08 -0700 From: Christopher Wood <notificati...@github.com> Reply-To: tlswg/draft-ietf-tls-esni <reply+abj5qf3jx35u33srzmt3vnv5h2cabevbnhhcqwf...@reply.github.com> To: tlswg/draft-ietf-tls-esni <draft-ietf-tls-e...@noreply.github.com> CC: Subscribed <subscri...@noreply.github.com> Thanks, @bemasc, for raising this! You can view, comment on, or merge this pull request online at: https://github.com/tlswg/draft-ietf-tls-esni/pull/258 -- Commit Summary -- * Fix superfluous padding edge cases. -- File Changes -- M draft-ietf-tls-esni.md (6) -- Patch Links -- https://github.com/tlswg/draft-ietf-tls-esni/pull/258.patch https://github.com/tlswg/draft-ietf-tls-esni/pull/258.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/tlswg/draft-ietf-tls-esni/pull/258
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
