Finally! Huge thanks to everyone who worked on this. We're already seeing a lot of deployment in advance of the RFC, too, so great to see everyone's hard work paying off.
-Ekr On Fri, Aug 10, 2018 at 4:54 PM, <rfc-edi...@rfc-editor.org> wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 8446 > > Title: The Transport Layer Security (TLS) Protocol > Version 1.3 > Author: E. Rescorla > Status: Standards Track > Stream: IETF > Date: August 2018 > Mailbox: e...@rtfm.com > Pages: 160 > Characters: 337736 > Obsoletes: RFC 5077, RFC 5246, RFC 6961 > Updates: RFC 5705, RFC 6066 > > I-D Tag: draft-ietf-tls-tls13-28.txt > > URL: https://www.rfc-editor.org/info/rfc8446 > > DOI: 10.17487/RFC8446 > > This document specifies version 1.3 of the Transport Layer Security > (TLS) protocol. TLS allows client/server applications to communicate > over the Internet in a way that is designed to prevent eavesdropping, > tampering, and message forgery. > > This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, > 5246, and 6961. This document also specifies new requirements for > TLS 1.2 implementations. > > This document is a product of the Transport Layer Security Working Group > of the IETF. > > This is now a Proposed Standard. > > STANDARDS TRACK: This document specifies an Internet Standards Track > protocol for the Internet community, and requests discussion and > suggestions > for improvements. Please refer to the current edition of the Official > Internet Protocol Standards (https://www.rfc-editor.org/standards) for > the > standardization state and status of this protocol. Distribution of this > memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://www.ietf.org/mailman/listinfo/ietf-announce > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see https://www.rfc-editor.org/search > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > _______________________________________________ > 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
