attachment
<div dir="ltr"><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername"></b> <span dir="ltr"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>Date: Fri, Aug 10, 2018 at 7:54 PM<br>Subject: [TLS] RFC 8446 on The Transport Layer Security (TLS) Protocol Version 1.3<br>To: <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br>Cc: <a href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>, <a href="mailto:tls@ietf.org">tls@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br><br><br>A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 8446<br>
<br>
Title: The Transport Layer Security (TLS) Protocol <br>
Version 1.3 <br>
Author: E. Rescorla<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: August 2018<br>
Mailbox: <a href="mailto:ekr@rtfm.com">ekr@rtfm.com</a><br>
Pages: 160<br>
Characters: 337736<br>
Obsoletes: RFC 5077, RFC 5246, RFC 6961<br>
Updates: RFC 5705, RFC 6066<br>
<br>
I-D Tag: draft-ietf-tls-tls13-28.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc8446" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>info/rfc8446</a><br>
<br>
DOI: 10.17487/RFC8446<br>
<br>
This document specifies version 1.3 of the Transport Layer Security<br>
(TLS) protocol. TLS allows client/server applications to communicate<br>
over the Internet in a way that is designed to prevent eavesdropping,<br>
tampering, and message forgery.<br>
<br>
This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077,<br>
5246, and 6961. This document also specifies new requirements for<br>
TLS 1.2 implementations.<br>
<br>
This document is a product of the Transport Layer Security Working Group of the IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet Standards Track<br>
protocol for the Internet community, and requests discussion and suggestions<br>
for improvements. Please refer to the current edition of the Official<br>
Internet Protocol Standards (<a href="https://www.rfc-editor.org/standards" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>standards</a>) for the <br>
standardization state and status of this protocol. Distribution of this <br>
memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.<wbr>org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href="mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
</div><br></div>