RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3

This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in…

Read RFC 8446 on the RFC Editor

Outgoing relationships (21 related RFCs)

Updates — RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions
Updates, Normative reference — RFC 5705: Keying Material Exporters for Transport Layer Security (TLS)
Obsoletes, Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Obsoletes, Informative reference — RFC 5077: Transport Layer Security (TLS) Session Resumption without Server-Side State
Obsoletes — RFC 6961: The Transport Layer Security (TLS) Multiple Certificate Status Request Extension
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 8017: PKCS #1: RSA Cryptography Specifications Version 2.2
Normative reference — RFC 7748: Elliptic Curves for Security
Normative reference — RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)
Normative reference — RFC 6960: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
Normative reference — RFC 5756: Updates for RSAES-OAEP and RSASSA-PSS Algorithm Parameters
Informative reference — RFC 6347: Datagram Transport Layer Security Version 1.2
Informative reference — RFC 5764: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)
Informative reference — RFC 5929: Channel Bindings for TLS
Informative reference — RFC 7924: Transport Layer Security (TLS) Cached Information Extension
Informative reference — RFC 6520: Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat Extension
Informative reference — RFC 6176: Prohibiting Secure Sockets Layer (SSL) Version 2.0
Informative reference — RFC 7568: Deprecating Secure Sockets Layer Version 3.0

Incoming relationships (204 related RFCs)

Showing 50 of 204 related RFCs.

Obsoleted by — RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3
Normatively referenced by — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Normatively referenced by — RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Normatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Normatively referenced by — RFC 8783: Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Normatively referenced by — RFC 8915: Network Time Security for the Network Time Protocol
Normatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
Normatively referenced by — RFC 9408: A YANG Network Data Model for Service Attachment Points (SAPs)
Normatively referenced by — RFC 9641: A YANG Data Model for a Truststore
Normatively referenced by — RFC 9642: A YANG Data Model for a Keystore
Normatively referenced by — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Normatively referenced by — RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)
Normatively referenced by — RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
Normatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Normatively referenced by — RFC 8835: Transports for WebRTC
Normatively referenced by — RFC 8879: TLS Certificate Compression
Normatively referenced by — RFC 8960: A YANG Data Model for MPLS Base
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Normatively referenced by — RFC 9230: Oblivious DNS over HTTPS
Normatively referenced by — RFC 9644: YANG Groupings for SSH Clients and SSH Servers
Normatively referenced by — RFC 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 8695: A YANG Data Model for the Routing Information Protocol (RIP)
Normatively referenced by — RFC 8765: DNS Push Notifications
Normatively referenced by — RFC 8844: Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
Normatively referenced by — RFC 8994: An Autonomic Control Plane (ACP)
Normatively referenced by — RFC 9190: EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3
Normatively referenced by — RFC 9209: The Proxy-Status HTTP Response Header Field
Normatively referenced by — RFC 9257: Guidance for External Pre-Shared Key (PSK) Usage in TLS
Normatively referenced by — RFC 9258: Importing External Pre-Shared Keys (PSKs) for TLS 1.3
Normatively referenced by — RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)
Normatively referenced by — RFC 8855: The Binary Floor Control Protocol (BFCP)
Normatively referenced by — RFC 9103: DNS Zone Transfer over TLS
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9155: Deprecating MD5 and SHA-1 Signature Hashes in TLS 1.2 and DTLS 1.2
Normatively referenced by — RFC 9174: Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4
Normatively referenced by — RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
Normatively referenced by — RFC 9633: Deterministic Networking (DetNet) YANG Data Model
Normatively referenced by — RFC 8531: Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols
Normatively referenced by — RFC 8773: TLS 1.3 Extension for Certificate-Based Authentication with an External Pre-Shared Key
Normatively referenced by — RFC 8808: A YANG Data Model for Factory Default Settings
Normatively referenced by — RFC 8862: Best Practices for Securing RTP Media Signaled with SIP
Normatively referenced by — RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar
Normatively referenced by — RFC 9020: YANG Data Model for Segment Routing