Multipath TCP Working Group
E698187
The Multipath TCP Working Group is an IETF body that develops and standardizes extensions to TCP enabling the use of multiple network paths simultaneously for a single connection.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Multipath TCP Working Group canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928764 — 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: Multipath TCP Working Group Context triple: [Transport Area, oversees, Multipath TCP Working Group]
-
A.
The Addition of Explicit Congestion Notification (ECN) to IP
The Addition of Explicit Congestion Notification (ECN) to IP is an IETF standard (RFC 3168) that specifies how IP and TCP can signal and respond to network congestion without relying solely on packet loss.
-
B.
Network-in-Network architecture
Network-in-Network architecture is a convolutional neural network design that replaces traditional linear convolution layers with micro multilayer perceptrons (MLPs) to enhance feature abstraction and model expressiveness.
-
C.
Internet Protocol fragmentation and reassembly
Internet Protocol fragmentation and reassembly is the process by which large IP packets are split into smaller fragments for transmission across networks with limited maximum transmission units and then reassembled back into the original packet at the destination.
-
D.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
-
E.
QUIC Loss Detection and Congestion Control
QUIC Loss Detection and Congestion Control is an IETF specification that defines how the QUIC transport protocol detects packet loss and manages congestion to ensure efficient and reliable data transmission on the internet.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Multipath TCP Working Group Target entity description: The Multipath TCP Working Group is an IETF body that develops and standardizes extensions to TCP enabling the use of multiple network paths simultaneously for a single connection.
-
A.
The Addition of Explicit Congestion Notification (ECN) to IP
The Addition of Explicit Congestion Notification (ECN) to IP is an IETF standard (RFC 3168) that specifies how IP and TCP can signal and respond to network congestion without relying solely on packet loss.
-
B.
Network-in-Network architecture
Network-in-Network architecture is a convolutional neural network design that replaces traditional linear convolution layers with micro multilayer perceptrons (MLPs) to enhance feature abstraction and model expressiveness.
-
C.
Internet Protocol fragmentation and reassembly
Internet Protocol fragmentation and reassembly is the process by which large IP packets are split into smaller fragments for transmission across networks with limited maximum transmission units and then reassembled back into the original packet at the destination.
-
D.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
-
E.
QUIC Loss Detection and Congestion Control
QUIC Loss Detection and Congestion Control is an IETF specification that defines how the QUIC transport protocol detects packet loss and manages congestion to ensure efficient and reliable data transmission on the internet.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards development organization unit ⓘ |
| abbreviation |
MPTCP WG
NERFINISHED
ⓘ
MPTCP Working Group NERFINISHED ⓘ |
| area | Transport Area NERFINISHED ⓘ |
| areaAbbreviation | TSV ⓘ |
| communicationChannel | IETF mailing list ⓘ |
| concerns |
deployment issues for Multipath TCP
ⓘ
interoperability of Multipath TCP implementations ⓘ security considerations for multipath transport ⓘ |
| field |
Transmission Control Protocol
NERFINISHED
ⓘ
computer networking ⓘ multipath transport protocols ⓘ transport layer protocols ⓘ |
| focusesOn |
extensions to TCP
ⓘ
simultaneous use of multiple network paths for a single transport connection ⓘ |
| goal |
to enable robust and efficient use of multiple network interfaces and paths for a single transport connection
ⓘ
to maintain compatibility with existing TCP applications and infrastructure ⓘ |
| governingBody | IETF Transport Area Directors NERFINISHED ⓘ |
| hasDeliverableType |
Best Current Practice RFCs
ⓘ
Informational RFCs ⓘ Proposed Standard RFCs ⓘ |
| hostedOn | IETF Datatracker NERFINISHED ⓘ |
| meetsAt | IETF meetings NERFINISHED ⓘ |
| membershipPolicy | open to any interested participant ⓘ |
| name | Multipath TCP Working Group NERFINISHED ⓘ |
| operatesUnder | IETF standards process ⓘ |
| organizationType | open standards working group ⓘ |
| parentOrganization | Internet Engineering Task Force NERFINISHED ⓘ |
| produces |
Internet-Drafts
NERFINISHED
ⓘ
RFC specifications ⓘ |
| purpose | to develop and standardize extensions to TCP enabling the use of multiple network paths simultaneously for a single connection ⓘ |
| relatedProtocol |
Multipath TCP
NERFINISHED
ⓘ
TCP ⓘ |
| scope | standardization of Multipath TCP mechanisms and extensions ⓘ |
| standardizes | Multipath TCP NERFINISHED ⓘ |
| status | active IETF working group (as of mid-2020s) ⓘ |
| topic |
backward-compatible TCP extensions
ⓘ
congestion control for multipath transport ⓘ connection-level multipath support ⓘ path management for multipath connections ⓘ session management across multiple subflows ⓘ |
| usesDocumentSeries |
Internet-Draft
NERFINISHED
ⓘ
RFC NERFINISHED ⓘ |
| website | https://datatracker.ietf.org/wg/mptcp ⓘ |
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: Multipath TCP Working Group Description of subject: The Multipath TCP Working Group is an IETF body that develops and standardizes extensions to TCP enabling the use of multiple network paths simultaneously for a single connection.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.