RFC 8996
E200936
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8996 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1798492 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8996 Context triple: [TLS 1.0, deprecatedInRFC, RFC 8996]
-
A.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
B.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
C.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
D.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8996 Target entity description: RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
A.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
B.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
C.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
D.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
TLS client implementations
ⓘ
TLS server implementations ⓘ application protocols using TLS ⓘ |
| area | Security ⓘ |
| BCPNumber | BCP 195 ⓘ |
| category | Best Current Practice ⓘ |
| definesAction |
deprecate TLS 1.0
ⓘ
deprecate TLS 1.1 ⓘ |
| deprecatesProtocolVersion |
TLS 1.0
ⓘ
TLS 1.1 ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOn |
TLS protocol versions
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| hasLanguage | English ⓘ |
| intendedAudience |
application developers
ⓘ
protocol designers ⓘ system administrators ⓘ |
| isPartOfSeries |
Request for Comments series
ⓘ
linked to:
RFCs
|
| motivation |
improve security of TLS deployments
ⓘ
remove support for obsolete TLS versions ⓘ |
| obsoletes | RFC 7525 ⓘ |
| publicationDate | March 2021 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| recommends |
disable TLS 1.0 in all configurations
ⓘ
disable TLS 1.1 in all configurations ⓘ use TLS 1.2 or later ⓘ |
| recommendsProtocolVersion |
TLS 1.2
ⓘ
TLS 1.3 ⓘ
linked to:
RFC 8446
|
| relation | successor to RFC 7525 for TLS version guidance ⓘ |
| securityConsideration |
TLS 1.0 is vulnerable to multiple attacks
ⓘ
linked to:
TLS 1.0
TLS 1.1 is vulnerable to multiple attacks ⓘ |
| shortName | Deprecating TLS 1.0 and TLS 1.1 ⓘ |
| standardizes | deprecation of TLS 1.0 and TLS 1.1 ⓘ |
| status |
Best Current Practice
ⓘ
Internet standard-track document ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| subject |
Internet security
ⓘ
cryptographic protocols ⓘ protocol deprecation ⓘ |
| title | Deprecating TLS 1.0 and TLS 1.1 ⓘ |
| updates |
TLS 1.2 usage guidelines
ⓘ
linked to:
TLS 1.2
|
| workingGroup |
Using TLS in Applications
ⓘ
linked to:
UTA (Using TLS in Applications)
|
| year | 2021 ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 8996 Description of subject: RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.