RFC 4086: Randomness Requirements for Security

Security systems are built on strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on…

Read RFC 4086 on the RFC Editor

Outgoing relationships (24 related RFCs)

Obsoletes, Informative reference — RFC 1750: Randomness Recommendations for Security
Informative reference — RFC 2104: HMAC: Keyed-Hashing for Message Authentication
Informative reference — RFC 1321: The MD5 Message-Digest Algorithm
Informative reference — RFC 4033: DNS Security Introduction and Requirements
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 2246: The TLS Protocol Version 1.0
Informative reference — RFC 4034: Resource Records for the DNS Security Extensions
Informative reference — RFC 4035: Protocol Modifications for the DNS Security Extensions
Informative reference — RFC 2634: Enhanced Security Services for S/MIME
Informative reference — RFC 3174: US Secure Hash Algorithm 1 (SHA1)
Informative reference — RFC 2631: Diffie-Hellman Key Agreement Method
Informative reference — RFC 2440: OpenPGP Message Format
Informative reference — RFC 2633: S/MIME Version 3 Message Specification
Informative reference — RFC 1421: Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
Informative reference — RFC 3766: Determining Strengths For Public Keys Used For Exchanging Symmetric Keys
Informative reference — RFC 3156: MIME Security with OpenPGP
Informative reference — RFC 977: Network News Transfer Protocol
Informative reference — RFC 1320: The MD4 Message-Digest Algorithm
Informative reference — RFC 1422: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management
Informative reference — RFC 1423: Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers
Informative reference — RFC 1948: Defending Against Sequence Number Attacks
Informative reference — RFC 1424: Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services
Informative reference — RFC 2632: S/MIME Version 3 Certificate Handling
Informative reference — RFC 2980: Common NNTP Extensions

Incoming relationships (136 related RFCs)

Showing 50 of 136 related RFCs.

Normatively referenced by — RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core
Normatively referenced by — RFC 6733: Diameter Base Protocol
Normatively referenced by — RFC 6887: Port Control Protocol (PCP)
Normatively referenced by — RFC 4880: OpenPGP Message Format
Normatively referenced by — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Normatively referenced by — RFC 7217: A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
Normatively referenced by — RFC 6830: The Locator/ID Separation Protocol (LISP)
Normatively referenced by — RFC 7030: Enrollment over Secure Transport
Normatively referenced by — RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
Normatively referenced by — RFC 7616: HTTP Digest Access Authentication
Normatively referenced by — RFC 4493: The AES-CMAC Algorithm
Normatively referenced by — RFC 4556: Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)
Normatively referenced by — RFC 6528: Defending against Sequence Number Attacks
Normatively referenced by — RFC 7022: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Normatively referenced by — RFC 7357: Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol
Normatively referenced by — RFC 7873: Domain Name System (DNS) Cookies
Normatively referenced by — RFC 9301: Locator/ID Separation Protocol (LISP) Control Plane
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9230: Oblivious DNS over HTTPS
Normatively referenced by — RFC 5018: Connection Establishment in the Binary Floor Control Protocol (BFCP)
Normatively referenced by — RFC 5997: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
Normatively referenced by — RFC 4615: The Advanced Encryption Standard-Cipher-based Message Authentication Code-Pseudo-Random Function-128 (AES-CMAC-PRF-128) Algorithm for the Internet Key Exchange Protocol (IKE)
Normatively referenced by — RFC 6284: Port Mapping between Unicast and Multicast RTP Sessions
Normatively referenced by — RFC 8907: The Terminal Access Controller Access-Control System Plus (TACACS+) Protocol
Normatively referenced by — RFC 8990: GeneRic Autonomic Signaling Protocol (GRASP)
Normatively referenced by — RFC 9580: OpenPGP
Normatively referenced by — RFC 6238: TOTP: Time-Based One-Time Password Algorithm
Normatively referenced by — RFC 8737: Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge Extension
Normatively referenced by — RFC 6218: Cisco Vendor-Specific RADIUS Attributes for the Delivery of Keying Material
Normatively referenced by — RFC 6450: Multicast Ping Protocol
Normatively referenced by — RFC 6560: One-Time Password (OTP) Pre-Authentication
Normatively referenced by — RFC 8921: Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)
Normatively referenced by — RFC 6098: Generic Notification Message for Mobile IPv4
Normatively referenced by — RFC 6287: OCRA: OATH Challenge-Response Algorithm
Normatively referenced by — RFC 6896: SCS: KoanLogic's Secure Cookie Sessions for HTTP
Normatively referenced by — RFC 8291: Message Encryption for Web Push
Normatively referenced by — RFC 8756: Commercial National Security Algorithm (CNSA) Suite Profile of Certificate Management over CMS
Normatively referenced by — RFC 8913: Two-Way Active Measurement Protocol (TWAMP) YANG Data Model
Normatively referenced by — RFC 9154: Extensible Provisioning Protocol (EPP) Secure Authorization Information for Transfer
Normatively referenced by — RFC 9333: Minimal IP Encapsulating Security Payload (ESP)
Normatively referenced by — RFC 9415: On the Generation of Transient Numeric Identifiers
Normatively referenced by — RFC 9428: Transmission of IPv6 Packets over Near Field Communication
Normatively referenced by — RFC 9654: Online Certificate Status Protocol (OCSP) Nonce Extension
Normatively referenced by — RFC 9704: Establishing Local DNS Authority in Validated Split-Horizon Environments
Normatively referenced by — RFC 9807: The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol
Normatively referenced by — RFC 9891: Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension
Normatively referenced by — RFC 9897: Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses
Informatively referenced by — RFC 4960: Stream Control Transmission Protocol
Informatively referenced by — RFC 5652: Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 7252: The Constrained Application Protocol (CoAP)