Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://dx.doi.org/10.17487/RFC9325 below:

Information on RFC 9325 » RFC Editor

File formats:

Also available: XML file for editing

 

Status:

BEST CURRENT PRACTICE

Obsoletes:

RFC 7525

Updates:

RFC 5288, RFC 6066

Authors:

Y. Sheffer
P. Saint-Andre
T. Fossati

Stream:

IETF

Source:

uta (sec)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9325

Discuss this RFC: Send questions or comments to the mailing list uta@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9325

Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on the most commonly used cipher suites and their modes of operation. This document provides the latest recommendations for ensuring the security of deployed services that use TLS and DTLS. These recommendations are applicable to the majority of use cases.

RFC 7525, an earlier version of the TLS recommendations, was published when the industry was transitioning to TLS 1.2. Years later, this transition is largely complete, and TLS 1.3 is widely available. This document updates the guidance given the new environment and obsoletes RFC 7525. In addition, this document updates RFCs 5288 and 6066 in view of recent attacks.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4