QUIC TLS usage specification
E184131
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
All labels observed (3)
| Label | Occurrences |
|---|---|
| QUIC TLS usage specification canonical | 1 |
| Using TLS to Secure QUIC | 1 |
| draft-ietf-quic-transport | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1632104 — 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: QUIC TLS usage specification Context triple: [IETF QUIC Working Group, product, QUIC TLS usage specification]
-
A.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
B.
DNS over QUIC (DoQ)
DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
-
C.
RFC 8446
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.
-
D.
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.
-
E.
DTLS
DTLS (Datagram Transport Layer Security) is a protocol that provides TLS-like encryption, integrity, and authentication for datagram-based communications such as UDP.
- 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: QUIC TLS usage specification Target entity description: The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
A.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
B.
DNS over QUIC (DoQ)
DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
-
C.
RFC 8446
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.
-
D.
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.
-
E.
DTLS
DTLS (Datagram Transport Layer Security) is a protocol that provides TLS-like encryption, integrity, and authentication for datagram-based communications such as UDP.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
IETF specification
ⓘ
Internet-Draft or RFC ⓘ |
| addresses |
TLS version requirements for QUIC
ⓘ
encrypted internet communication ⓘ error handling for TLS failures in QUIC ⓘ protection of QUIC control information ⓘ secure key exchange for QUIC ⓘ use of TLS ciphersuites with QUIC ⓘ |
| appliesTo | internet communication ⓘ |
| category |
network security specification
ⓘ
transport layer protocol specification ⓘ |
| defines |
how QUIC derives traffic keys from TLS
ⓘ
how QUIC uses TLS for 0-RTT data ⓘ how QUIC uses TLS for forward secrecy ⓘ how QUIC uses TLS session resumption ⓘ how TLS handshake messages are carried in QUIC ⓘ mapping between TLS handshake and QUIC packets ⓘ |
| definesUsageOf |
QUIC transport protocol
ⓘ
TLS ⓘ
surface form:
Transport Layer Security
|
| ensures |
that QUIC encryption is tied to TLS handshake state
ⓘ
that QUIC packets are protected using TLS-derived keys ⓘ |
| focusesOn | integration of QUIC and TLS ⓘ |
| governs | secure use of TLS in QUIC ⓘ |
| hasGoal |
ensure authentication of QUIC endpoints
ⓘ
ensure confidentiality of QUIC traffic ⓘ ensure integrity of QUIC traffic ⓘ provide secure encrypted transport for QUIC ⓘ |
| intendedFor |
implementers of QUIC
ⓘ
protocol designers ⓘ security engineers working with QUIC ⓘ |
| partOf |
QUIC
ⓘ
surface form:
QUIC protocol suite
|
| publishedBy | Internet Engineering Task Force ⓘ |
| relatesTo |
QUIC transport specification
ⓘ
TLS protocol specification ⓘ |
| specifies |
how QUIC uses TLS for authentication
ⓘ
how QUIC uses TLS for encryption ⓘ how QUIC uses TLS for key establishment ⓘ |
| usedBy |
QUIC implementations
ⓘ
servers implementing QUIC ⓘ web browsers implementing QUIC ⓘ |
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: QUIC TLS usage specification Description of subject: The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.