RFC 7525: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)

Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are widely used to protect data exchanged over application protocols such as HTTP,…

Read RFC 7525 on the RFC Editor

Outgoing relationships (2 related RFCs)

Informative reference — RFC 2026: The Internet Standards Process -- Revision 3
Informative reference — RFC 7507: TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade Attacks

Incoming relationships (58 related RFCs)

Showing 50 of 58 related RFCs.

Updated by, Normatively referenced by — RFC 8996: Deprecating TLS 1.0 and TLS 1.1
Obsoleted by, Informatively referenced by — RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Normatively referenced by — RFC 8094: DNS over Datagram Transport Layer Security (DTLS)
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
Normatively referenced by — RFC 8310: Usage Profiles for DNS over TLS and DNS over DTLS
Normatively referenced by — RFC 7589: Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
Normatively referenced by — RFC 8915: Network Time Security for the Network Time Protocol
Normatively referenced by — RFC 7590: Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)
Normatively referenced by — RFC 7975: Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection
Normatively referenced by — RFC 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 8745: Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
Normatively referenced by — RFC 8994: An Autonomic Control Plane (ACP)
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 9174: Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4
Normatively referenced by — RFC 7653: DHCPv6 Active Leasequery
Normatively referenced by — RFC 7711: PKIX over Secure HTTP (POSH)
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 8689: SMTP Require TLS Option
Normatively referenced by — RFC 9303: Locator/ID Separation Protocol Security (LISP-SEC)
Normatively referenced by — RFC 7724: Active DHCPv4 Lease Query
Normatively referenced by — RFC 8322: Resource-Oriented Lightweight Information Exchange (ROLIE)
Normatively referenced by — RFC 8751: Hierarchical Stateful Path Computation Element (PCE)
Normatively referenced by — RFC 8921: Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8156: DHCPv6 Failover Protocol
Normatively referenced by — RFC 8733: Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCE
Normatively referenced by — RFC 8857: The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)
Normatively referenced by — RFC 8887: A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
Normatively referenced by — RFC 8932: Recommendations for DNS Privacy Service Operators
Normatively referenced by — RFC 9248: Interoperability Profile for Relay User Equipment
Normatively referenced by — RFC 9289: Towards Remote Procedure Call Encryption by Default
Informatively referenced by — RFC 8085: UDP Usage Guidelines
Informatively referenced by — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Informatively referenced by — RFC 8231: Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Informatively referenced by — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Informatively referenced by — RFC 7696: Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
Informatively referenced by — RFC 7788: Home Networking Control Protocol
Informatively referenced by — RFC 8232: Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE
Informatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Informatively referenced by — RFC 8175: Dynamic Link Exchange Protocol (DLEP)
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 7644: System for Cross-domain Identity Management: Protocol
Informatively referenced by — RFC 7830: The EDNS(0) Padding Option
Informatively referenced by — RFC 8306: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Informatively referenced by — RFC 9190: EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3
Informatively referenced by — RFC 7635: Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization
Informatively referenced by — RFC 7866: Session Recording Protocol
Informatively referenced by — RFC 8855: The Binary Floor Control Protocol (BFCP)