@BRIAN_____ @tqbf It wasn't us who proposed this "there can be only one" CFRG process.
-
-
Replying to @BRIAN_____
@BRIAN_____@tqbf this captures the "anyone who proposes anything other than 25519 is being unhelpful" argument nicely2 replies 0 retweets 0 likes -
Replying to @marshray
@marshray@BRIAN_____@tqbf Microsoft may have had good intentions but to an outsider it really feels like they were obstructing the CFRG2 replies 0 retweets 2 likes -
Replying to @bascule
@marshray@BRIAN_____@tqbf most of Microsoft's proposals seemed... kind of insane? Who wants to be implementing short Weierstrass in 2014?1 reply 0 retweets 0 likes -
Replying to @bascule
@marshray@BRIAN_____@tqbf after a lot of teeth pulling and backpeddling, we wound up with rigid curve generation that generates Curve255192 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@brian_____@tqbf which kind of raises questions about rigidity in a committee process (not security tho)1 reply 0 retweets 0 likes
@marshray @BRIAN_____ @tqbf I spoke out against rigidity: https://www.ietf.org/mail-archive/web/cfrg/current/msg05767.html …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.