RFC 9293
E292423
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9293 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2724403 — 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.
Target entity: RFC 9293 Context triple: [RFC 793, obsoletedBy, RFC 9293]
-
A.
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.
-
B.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
D.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
E.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 9293 Target entity description: RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
A.
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.
-
B.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
D.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
E.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet Standard
ⓘ
Request for Comments ⓘ |
| abbreviation |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| defines |
TCP connection semantics
ⓘ
TCP reset behavior ⓘ TCP segment format ⓘ TCP state definitions ⓘ TCP timers ⓘ TCP urgent mechanism ⓘ Transmission Control Protocol ⓘ
surface form:
Transmission Control Protocol core specification
|
| documentType |
RFCs
ⓘ
surface form:
Internet Standards Track RFC
|
| excludes |
TCP congestion control algorithms
ⓘ
TCP implementation-specific optimizations ⓘ |
| intendedUse |
reference for TCP implementers
ⓘ
reference for network engineers ⓘ reference for protocol designers ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 2873
ⓘ
RFC 6093 ⓘ RFC 6429 ⓘ RFC 6528 ⓘ RFC 793 ⓘ RFC 879 ⓘ |
| protocolFamily | TCP/IP ⓘ |
| protocolLayer | transport layer ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| replaces | original TCP specification defined in RFC 793 ⓘ |
| replacesTerm | host ⓘ |
| scope | core TCP protocol specification ⓘ |
| series | STD 7 ⓘ |
| specifies |
TCP congestion control hooks
ⓘ
TCP connection establishment ⓘ TCP connection termination ⓘ TCP error handling ⓘ TCP flow control ⓘ TCP header format ⓘ TCP options ⓘ TCP retransmission behavior ⓘ Transmission Control Protocol ⓘ
surface form:
TCP state machine
|
| standardizes |
connection-oriented transport
ⓘ
reliable byte-stream transport ⓘ |
| status | Internet Standard ⓘ |
| title | Transmission Control Protocol ⓘ |
| updates | TCP specification ⓘ |
| usesTerm | endpoint ⓘ |
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.
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.
Subject: RFC 9293 Description of subject: RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.