RFC 8999
E184130
RFC 8999 is an Internet Engineering Task Force (IETF) standards document produced by the QUIC Working Group that specifies aspects of the QUIC transport protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8999 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1632099 — 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 8999 Context triple: [IETF QUIC Working Group, product, RFC 8999]
-
A.
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.
-
B.
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.
-
C.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
D.
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.
-
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 8999 Target entity description: RFC 8999 is an Internet Engineering Task Force (IETF) standards document produced by the QUIC Working Group that specifies aspects of the QUIC transport protocol.
-
A.
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.
-
B.
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.
-
C.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
D.
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.
-
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 |
Internet standard
ⓘ
RFC ⓘ |
| appliesTo | all versions of QUIC ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| defines |
QUIC connection ID invariants
ⓘ
QUIC invariants ⓘ QUIC long header form invariants ⓘ QUIC packet type invariants ⓘ QUIC short header form invariants ⓘ QUIC spin bit invariants ⓘ QUIC stateless reset invariants ⓘ QUIC version negotiation invariants ⓘ QUIC version-independent wire image ⓘ constraints on middlebox behavior for QUIC ⓘ version-independent properties of QUIC ⓘ |
| documentType | standards-track RFC ⓘ |
| field |
Internet transport protocols
ⓘ
computer networking ⓘ |
| focusesOn | version-independent aspects of QUIC ⓘ |
| intendedFor |
implementers of QUIC
ⓘ
middlebox designers ⓘ network operators ⓘ |
| language | English ⓘ |
| obsoletes | RFC 6437 ⓘ |
| producedBy |
IETF QUIC Working Group
ⓘ
surface form:
QUIC Working Group
|
| protocol | QUIC ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 9000
ⓘ
RFC 9001 ⓘ RFC 9002 ⓘ |
| scope | version-independent aspects of QUIC protocol design ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| shortTitle | Version-Independent Properties of QUIC ⓘ |
| specifies | aspects of the QUIC transport protocol that are invariant across versions ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Proposed Standard ⓘ |
| title | Version-Independent Properties of QUIC ⓘ |
| updates |
RFC 2474
ⓘ
RFC 3168 ⓘ RFC 4301 ⓘ RFC 6040 ⓘ RFC 6790 ⓘ RFC 6864 ⓘ |
| workingGroup |
IETF QUIC Working Group
ⓘ
surface form:
QUIC Working Group
|
| workingGroupDocumentOf |
IETF QUIC Working Group
ⓘ
surface form:
QUIC Working Group
|
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 8999 Description of subject: RFC 8999 is an Internet Engineering Task Force (IETF) standards document produced by the QUIC Working Group that specifies aspects of the QUIC transport protocol.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.