RFC 791:INTERNET PROTOCOL
RFC-Ref

fragmentation


Click on the red underlined text to get to the source

... addresses. The internet protocol also provides for fragmentation and reassembly of long datagrams, if necessary, for transmission through "small packet" networks ...
... internet protocol implements two basic functions: addressing and fragmentation. ...


... smaller than the size of the datagram. To overcome this difficulty, a fragmentation mechanism is provided in the internet protocol. ...
... Fragmentation ...
... Fragmentation of an internet datagram is necessary when it ...
... Fragmentation, transmission and reassembly across a local network which is invisible to the internet protocol ...
... internet protocol module is called intranet fragmentation and may be used [6]. ...
... The internet fragmentation and reassembly procedure needs to be able to break a datagram into an almost arbitrary number of pieces that ...


... The copied flag indicates that this option is copied into all fragments on fragmentation. 0 = not copied ...
... May be copied, introduced, or deleted on fragmentation, or for any other reason. ...
... May be copied, introduced, or deleted on fragmentation, or for any other reason. ...
... trigraphs, and are available from HQ DCA Code 530. Must be copied on fragmentation. This option appears at most once in a datagram. ...
... route. Must be copied on fragmentation. Appears at most once in a datagram. ...
... route. Must be copied on fragmentation. Appears at most once in a datagram. ...
... 3]. Not copied on fragmentation, goes in first fragment only. Appears at most once in a datagram ...
... stream concept. Must be copied on fragmentation. Appears at most once in a datagram. ...
... The timestamp option is not copied upon fragmentation. It is carried in the first fragment. Appears at most once in a ...
... internet service is datagram oriented and provides for the fragmentation of datagrams at gateways, with reassembly taking place ...
... internet protocol module in the destination host. Of course, fragmentation and reassembly of datagrams within a network ...
... allowed since this is transparent to the internet protocols and the higher-level protocols. This transparent type of fragmentation and reassembly is termed "network-dependent" (or intranet ...
... reassembly is termed "network-dependent" (or intranet) fragmentation and is not discussed further here. ...
... Fragmentation and Reassembly. ...
... Fragments are counted in units of 8 octets. The fragmentation strategy is designed so than an unfragmented datagram has all zero fragmentation ...
... fragmentation strategy is designed so than an unfragmented datagram has all zero fragmentation information (MF = 0, fragment offset = ...
... When fragmentation occurs, some options are copied, but others remain with the first fragment only. ...
... internet module must be able to forward a datagram of 68 octets without further fragmentation. This is because an internet header ...
... The fields which may be affected by fragmentation include: ...
... bit is set, then internet fragmentation of this datagram is NOT permitted, although it may be discarded. This can be used to prohibit fragmentation ...
... fragmentation of this datagram is NOT permitted, although it may be discarded. This can be used to prohibit fragmentation in cases where the receiving host ...
... The fragmentation and reassembly procedures are most easily described by examples. The following procedures are example implementations. ...
... An Example Fragmentation Procedure ...
... Checksum; (10) Submit this fragment to the fragmentation test; DONE. ...
... than the maximum size datagrams. For example, one could implement a fragmentation procedure that repeatly divided large datagrams in half until the resulting fragments ...
... time to live, additions or changes to internet options, or due to fragmentation. This checksum at the internet ...


... internet fragments that might result from the fragmentation of this datagram if the maximum sized transmission allowed were 280 octets. ...


... Shoch, J., "Packet Fragmentation in Inter-Network Protocols," Computer Networks, v. 3, n. 1, February 1979. ...



Google
Web
RFC-Ref