RFC 7435: Opportunistic Security: Some Protection Most of the Time
In plain English — editorial summary, not part of the RFC
This document defines the concept "Opportunistic Security" in the context of communications protocols. Protocol designs based on Opportunistic Security use encryption even when authentication is not available, and use authentication when possible, thereby removing barriers to the widespread use of encryption on the Internet.
Document record
- Document ID
- RFC7435
- Published
- December 2014
- Authors
- V. Dukhovni
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 2015
- RFC 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
- RFC 6655AES-CCM Cipher Suites for Transport Layer Security (TLS)Updated
July 2012
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5116An Interface and Algorithms for Authenticated EncryptionCurrent
January 2008
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?