Seems like some overlap there (all about an hour ago). https://github.com/bwesterb/draft-westerbaan-tls-keyshare-recommendations/pull/5/changes
But still: it should be "Updated Recommendations for TLS Key Shares" (not "For") thanks, Rob On Tue, Apr 28, 2026 at 3:14 PM Rob Sayre <[email protected]> wrote: > It's a short document. Just do the copy editing. > > > > Updated recommendations for TLS keyshares > draft-westerbaan-tls-keyshare-recommendations-02 > Abstract > > This document recommends X25519MLKEM768 for use in TLS by updating > its entry in the TLS Supported Groups registry (previously EC Named > Curve Registry) to Recommended in the light of the future arrival of > cryptographically relevant quantum computers. > > [[ NOTE I use key share in the title and here as it's more accurate > than "group" and perhaps more well known in the context TLS than key > agreement or key exchange. ]] > > > > > On Tue, Apr 28, 2026 at 3:05 PM Muhammad Usama Sardar < > [email protected]> wrote: > >> On 28.04.26 23:26, Rob Sayre wrote: >> >> Well, I think you should go through and fix "keyshare" vs "key share" vs >> "keyshares" vs "key shares". >> >> Not a technical concern, but this document is "all over the shop" on this >> point, as they say. :) >> >> I find that a tiny bit exaggerated. ISTM the only problem was in the >> title which is fixed [0]. >> >> - I don't find "keyshare" anywhere except in draft *name* (not the >> title), which cannot have spaces. >> - All instances of "key share" and "key shares" look fine to me >> (singular vs plural). >> >> If you see something wrong, please submit a PR. Thank you. >> >> Best, >> >> -Usama >> >> [0] >> https://github.com/bwesterb/draft-westerbaan-tls-keyshare-recommendations/pull/5 >> >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
