How can we improve the Microsoft Edge developer experience?

Support TLS 1.3 with 1-RTT

TLS 1.3, the next version of security protocol for private and authenticated communication, is in the final phase of specification.
Cloudflare already supports it, Chrome 56 plans to support it January 2017 and Firefox in March 2017.
Edge should not stay behind and support TLS 1.3 with 1-RTT as well, ideally in the upcoming Creator's Update already.

397 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Martin Suchan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Bernd P commented  ·   ·  Flag as inappropriate

        This becomes more urgently necessary now since TLS 1.3 has been finalised. MS should get rid of all old/weak/broken and obsolete encryption types ASAP. Add Chacha20_poly1305! in Windows 10, and Camellia with 128Bits+
        CGM and CCM modes.
        Also: Implementation of PCIDSS 3.2 Compliance. Getting rid of TLS 1.0 and all older protocols.
        Thank you.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I agree! Support for TLS 1.3 is the most important you can do in Microsoft Edge right now!

        Thanks!

      Feedback and Knowledge Base