RFC 9001
E49262
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9001 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T311018 — 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 9001 Context triple: [QUIC, definedIn, RFC 9001]
-
A.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
B.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
- 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 9001 Target entity description: RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
A.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
B.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| appliesTo | QUIC version 1 ⓘ |
| area |
Security
ⓘ
Transport ⓘ |
| category | Standards Track ⓘ |
| defines |
QUIC 0-RTT keys
ⓘ
QUIC 1-RTT keys ⓘ QUIC handshake keys ⓘ QUIC header protection using TLS primitives ⓘ QUIC key update procedures ⓘ QUIC packet protection ⓘ QUIC retry integrity protection ⓘ QUIC secrets derivation ⓘ QUIC-TLS interface ⓘ confidentiality and integrity protection for QUIC packets ⓘ cryptographic handshake for QUIC ⓘ key management for QUIC ⓘ mapping between TLS alerts and QUIC errors ⓘ use of TLS 1.3 to secure QUIC ⓘ use of TLS extensions in QUIC ⓘ |
| focusesOn |
cryptographic handshake for QUIC
ⓘ
key management for QUIC ⓘ security properties of QUIC using TLS 1.3 ⓘ |
| language | English ⓘ |
| obsoletes | RFC 8446 usage for QUIC drafts ⓘ |
| organization |
IETF QUIC Working Group
ⓘ
surface form:
QUIC Working Group
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
QUIC transport protocol
ⓘ
RFC 9000 ⓘ RFC 8446 ⓘ
surface form:
TLS 1.3
|
| securesProtocol | QUIC ⓘ |
| specifies |
TLS 1.3 handshake usage for QUIC
ⓘ
error handling for QUIC-TLS interaction ⓘ exported keying material for QUIC ⓘ how TLS 1.3 is integrated with QUIC ⓘ requirements on QUIC implementations using TLS ⓘ requirements on TLS implementations used with QUIC ⓘ |
| standardizes |
use of TLS 1.3 for QUIC connection establishment
ⓘ
use of TLS 1.3 for QUIC key updates ⓘ use of TLS 1.3 for QUIC packet protection ⓘ |
| status | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
QUIC TLS usage specification
ⓘ
surface form:
Using TLS to Secure QUIC
|
| usesProtocol |
RFC 8446
ⓘ
surface form:
TLS 1.3
|
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 9001 Description of subject: RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.