Reject TLS 1.1 negotiation
03TLS 1.1 improved some TLS 1.0 behavior, but it still does not meet the newer protocol baseline.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5 ↗
RFC 8996 · § 5EXAMPLE
3 / 3
03
Upgrade the peer before reconnecting.
Use a protocol permitted by the current deployment policy.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 7525 § 3.1.1: SHOULD NOTRFC 8996 §§ 5, 6: MUST NOT
Negotiating TLS 1.1 changes from discouraged to prohibited.
Read the updated RFC section ↗TLS 1.1 MUST NOT be used.
- Implementations MUST NOT negotiate TLS 1.1.
- The Hello versions described in this RFC must not select {03,02}; an incompatible peer receives an alert and the connection closes.
- Legacy ClientHello record-layer values remain distinct from the version ultimately negotiated.
Deprecation does not claim every newer configuration is automatically secure. Cipher suites, keys, and endpoint configuration still matter.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy