RFC 8446
E6783
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
All labels observed (4)
| Label | Occurrences |
|---|---|
| TLS 1.3 | 24 |
| RFC 8446 canonical | 5 |
| TLS 1.3 (RFC 8446) | 1 |
| The Transport Layer Security (TLS) Protocol Version 1.3 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T63811 — 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 8446 Context triple: [TLS, definedIn, RFC 8446]
-
A.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- 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 8446 Target entity description: RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
A.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
B.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ |
| addresses | known weaknesses in earlier TLS versions ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
TLS 1.3 alert protocol
ⓘ
TLS 1.3 cipher suites ⓘ TLS 1.3 extension mechanisms ⓘ TLS 1.3 handshake protocol ⓘ TLS 1.3 key schedule ⓘ TLS 1.3 record protocol ⓘ TLS 1.3 state machine ⓘ |
| eliminates |
TLS compression
ⓘ
many legacy ciphersuites ⓘ non-ephemeral Diffie-Hellman key exchange ⓘ renegotiation ⓘ static RSA key exchange ⓘ |
| focusesOn |
encrypted communications
ⓘ
improved performance ⓘ improved security ⓘ |
| improves |
forward secrecy
ⓘ
latency of TLS handshake ⓘ |
| intendedFor |
VPN and other secure channels
ⓘ
email transport security ⓘ securing application layer protocols ⓘ web traffic security ⓘ |
| mandates |
AEAD cipher suites
ⓘ
perfect forward secrecy for key exchange ⓘ |
| obsoletes |
RFC 5246
ⓘ
TLS 1.2 specification ⓘ |
| partOfProtocolFamily |
Transport Layer Security
ⓘ
linked to:
TLS
|
| publishedBy | Internet Engineering Task Force ⓘ |
| recommends | disabling TLS 1.0 and TLS 1.1 ⓘ |
| reduces | number of round trips in handshake ⓘ |
| specifiesProtocolVersion |
TLS 1.3
ⓘ
linked to:
TLS 1.1
|
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supports |
0-RTT data
ⓘ
1-RTT handshake ⓘ encrypted SNI via extensions (framework) ⓘ post-handshake authentication ⓘ pre-shared keys ⓘ session resumption via PSK ⓘ |
| title |
The Transport Layer Security (TLS) Protocol Version 1.3
ⓘ
linked to:
RFC 8446
|
| uses |
AEAD ciphers
ⓘ
Diffie-Hellman key exchange ⓘ Elliptic Curve Diffie-Hellman key exchange ⓘ HKDF-based key schedule ⓘ |
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 8446 Description of subject: RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
Referenced by (31)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
subject linked to:
ALPN (Application-Layer Protocol Negotiation)
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446
linked to: RFC 8446