IETF QUIC Working Group
E35277
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
All labels observed (4)
| Label | Occurrences |
|---|---|
| QUIC Working Group | 8 |
| IETF QUIC Working Group canonical | 3 |
| IETF QUIC | 1 |
| QUIC WG | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T270968 — 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: IETF QUIC Working Group Context triple: [HTTP/3, workingGroup, IETF QUIC Working Group]
-
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.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
-
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.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
E.
IEEE 802.1 Working Group
The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
- 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: IETF QUIC Working Group Target entity description: The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
-
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.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
-
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.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
E.
IEEE 802.1 Working Group
The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards body ⓘ |
| area | Transport Area ⓘ |
| communicationChannel | [email protected] mailing list ⓘ |
| coordinatesWith |
HTTP Working Group
ⓘ
TLS Working Group ⓘ |
| field |
Internet standards
ⓘ
network protocols ⓘ transport protocols ⓘ web protocols ⓘ |
| focusesOn |
congestion control
ⓘ
connection migration ⓘ deployability on the public Internet ⓘ extensibility of the QUIC protocol ⓘ loss recovery ⓘ low-latency transport ⓘ middlebox traversal ⓘ multiplexing of streams ⓘ transport security ⓘ versioning of the QUIC protocol ⓘ |
| hasProcess |
open participation
ⓘ
rough consensus and running code ⓘ |
| meetsAt | IETF meetings ⓘ |
| parentOrganization | Internet Engineering Task Force ⓘ |
| product |
HTTP/3
ⓘ
surface form:
HTTP/3 specification
QUIC TLS usage specification ⓘ QUIC invariants specification ⓘ QUIC recovery specification ⓘ QUIC transport specification ⓘ RFC 8999 ⓘ RFC 9000 ⓘ RFC 9001 ⓘ RFC 9002 ⓘ RFC 9114 ⓘ |
| purpose |
develop related technologies for QUIC
ⓘ
develop the QUIC transport protocol ⓘ maintain the QUIC transport protocol ⓘ standardize QUIC for use on the Internet ⓘ support deployment of HTTP over QUIC ⓘ support deployment of HTTP/3 ⓘ |
| shortName |
IETF QUIC Working Group
self-linksurface differs
ⓘ
surface form:
QUIC WG
|
| standardizes |
HTTP/3
ⓘ
QUIC ⓘ QUIC TLS integration ⓘ QUIC invariants ⓘ QUIC loss detection and congestion control ⓘ QUIC recovery ⓘ QUIC version negotiation mechanisms ⓘ extensions to the QUIC transport protocol ⓘ |
| usesSecurityProtocol |
RFC 8446
ⓘ
surface form:
TLS 1.3
TLS ⓘ
surface form:
Transport Layer Security
|
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: IETF QUIC Working Group Description of subject: The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
Referenced by (13)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
QUIC WG
subject surface form:
DNS over QUIC
this entity surface form:
IETF QUIC
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group
this entity surface form:
QUIC Working Group