RFC 6176: Prohibiting Secure Sockets Layer (SSL) Version 2.0
In plain English — editorial summary, not part of the RFC
This document requires that when Transport Layer Security (TLS) clients and servers establish connections, they never negotiate the use of Secure Sockets Layer (SSL) version 2.0. This document updates the backward compatibility sections found in the Transport Layer Security (TLS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6176
- Published
- March 2011
- Authors
- S. Turner; T. Polk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 4
- Also known as
- —
- Updated by:
- RFC 8996
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6170Internet X.509 Public Key Infrastructure -- Certificate ImageObsoleted
May 2011
- RFC 6158RADIUS Design GuidelinesUpdated
March 2011
- RFC 6113A Generalized Framework for Kerberos Pre-AuthenticationCurrent
April 2011
- RFC 6112Anonymity Support for KerberosObsoleted
April 2011
- RFC 6111Additional Kerberos Naming ConstraintsCurrent
April 2011
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
- RFC 6277Online Certificate Status Protocol Algorithm AgilityObsoleted
June 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
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?