Internet Protocol fragmentation and reassembly
E519653
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Internet Protocol fragmentation and reassembly canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5421625 — 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: Internet Protocol fragmentation and reassembly Context triple: [RFC 760, defines, Internet Protocol fragmentation and reassembly]
-
A.
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.
-
B.
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.
-
C.
Classless Inter-Domain Routing
Classless Inter-Domain Routing (CIDR) is an IP addressing and routing scheme that replaces traditional class-based networks to enable more efficient allocation of IP address space and improved route aggregation on the internet.
-
D.
Requirements for Internet Hosts – Communication Layers
"Requirements for Internet Hosts – Communication Layers" is an IETF standards document (RFC 1122) that specifies the protocol and behavior requirements for Internet host communication across the network, transport, and related layers.
-
E.
ARPANET Interface Message Processor platform
The ARPANET Interface Message Processor platform was the specialized packet-switching computer system that formed the backbone of the early ARPANET, handling data routing between host machines in the first large-scale packet-switched network.
- 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: Internet Protocol fragmentation and reassembly Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
Classless Inter-Domain Routing
Classless Inter-Domain Routing (CIDR) is an IP addressing and routing scheme that replaces traditional class-based networks to enable more efficient allocation of IP address space and improved route aggregation on the internet.
-
D.
Requirements for Internet Hosts – Communication Layers
"Requirements for Internet Hosts – Communication Layers" is an IETF standards document (RFC 1122) that specifies the protocol and behavior requirements for Internet host communication across the network, transport, and related layers.
-
E.
ARPANET Interface Message Processor platform
The ARPANET Interface Message Processor platform was the specialized packet-switching computer system that formed the backbone of the early ARPANET, handling data routing between host machines in the first large-scale packet-switched network.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet Protocol feature
ⓘ
networking mechanism ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ |
| canCause |
higher processing overhead on routers and hosts
ⓘ
increased packet loss probability when any fragment is lost ⓘ reduced performance for real-time applications ⓘ |
| characterizedBy |
fragmentation occurring in-network for IPv4
ⓘ
fragmentation only at endpoints for IPv6 ⓘ |
| constrainedBy | MTU of each link along the path ⓘ |
| differsBetween | IPv4 and IPv6 fragmentation behavior ⓘ |
| discouragedIn | modern network design ⓘ |
| governedBy |
RFC 791
NERFINISHED
ⓘ
RFC 8200 NERFINISHED ⓘ |
| handledBy | IP layer ⓘ |
| hasPurpose | to allow transmission of packets across links with smaller Maximum Transmission Units ⓘ |
| involves |
reassembling fragments into the original IP packet
ⓘ
splitting a large IP packet into smaller fragments ⓘ |
| mayResultIn |
discarding all fragments if any fragment is missing
ⓘ
discarding all fragments if reassembly timer expires ⓘ |
| mitigatedBy |
Path MTU Discovery to avoid in-path fragmentation
ⓘ
firewall policies that drop suspicious fragments ⓘ |
| partOf | Internet Protocol NERFINISHED ⓘ |
| performedBy |
routers in IPv4
ⓘ
sending host in IPv6 ⓘ |
| reassembledBy | destination host ⓘ |
| relatedTo |
Don’t Fragment bit used by Path MTU Discovery in IPv4
ⓘ
Path MTU Discovery NERFINISHED ⓘ |
| requires |
all IPv6 fragments of a packet to carry the same Fragment Identification value
ⓘ
all fragments of a packet to have the same Identification value ⓘ all fragments of a packet to have the same destination address ⓘ all fragments of a packet to have the same protocol field value ⓘ all fragments of a packet to have the same source address ⓘ reassembly timeout at the destination ⓘ |
| securityConcern |
fragmentation-based evasion of intrusion detection systems
ⓘ
overlapping fragment attacks ⓘ resource exhaustion via many incomplete fragment sets ⓘ |
| transparentTo | transport layer protocols ⓘ |
| uses | IP header length field to compute fragment data boundaries ⓘ |
| usesConcept |
Maximum Transmission Unit
ⓘ
Path MTU ⓘ |
| usesExtensionHeader | IPv6 Fragment header ⓘ |
| usesField |
Flags field in the IP header
ⓘ
Fragment Offset field in the IP header ⓘ Identification field in the IP header ⓘ |
| usesFlag |
Don’t Fragment flag
ⓘ
More Fragments flag ⓘ |
| usesUnit | 8-byte blocks for Fragment Offset ⓘ |
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: Internet Protocol fragmentation and reassembly Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.