cnp3-ebook/protocols/ipv6 — English @ Weblate

Exit Zen

124 ../../protocols/ipv6.rst:407

	English 802.15.4 8/10000 · 8
125 ../../protocols/ipv6.rst:407

	English 102 or 81 bytes 15/10000 · 15
126 ../../protocols/ipv6.rst:408

	English Token Ring 10/10000 · 10
127 ../../protocols/ipv6.rst:408

	English 4464 bytes 10/10000 · 10
128 ../../protocols/ipv6.rst:409

	English FDDI 4/10000 · 4
129 ../../protocols/ipv6.rst:409

	English 4352 bytes 10/10000 · 10
130 ../../protocols/ipv6.rst:412

	English Although IPv6 can send 64 KBytes long packets, few datalink layer technologies that are used today are able to send a 64 KBytes packet inside a frame. Furthermore, as illustrated in the figure below, another problem is that a host may send a packet that would be too large for one of the datalink layers used by the intermediate routers. 337/10000 · 337
131 ../../protocols/ipv6.rst:418

	English The need for fragmentation and reassembly 41/10000 · 41
132 ../../protocols/ipv6.rst:422

	English To solve these problems, IPv6 includes a packet fragmentation and reassembly mechanism. In IPv4, fragmentation was performed by both the hosts and the intermediate routers. However, experience with IPv4 has shown that fragmenting packets in routers was costly [KM1995]_. For this reason, the developers of IPv6 have decided that routers would not fragment packets anymore. In IPv6, fragmentation is only performed by the source host. If a source has to send a packet which is larger than the MTU of the outgoing interface, the packet needs to be fragmented before being transmitted. In IPv6, each packet fragment is an IPv6 packet that includes the `Fragmentation` header. This header is included by the source in each packet fragment. The receiver uses them to reassemble the received fragments. 797/10000 · 797
133 ../../protocols/ipv6.rst:427

	English IPv6 fragmentation header 25/10000 · 25
134 ../../protocols/ipv6.rst:429

	English If a router receives a packet that is too long to be forwarded, the packet is dropped and the router returns an ICMPv6 message to inform the sender of the problem. The sender can then either fragment the packet or perform Path MTU discovery. In IPv6, packet fragmentation is performed only by the source by using IPv6 options. 326/10000 · 326
135 ../../protocols/ipv6.rst:433

	English In IPv6, fragmentation is performed exclusively by the source host and relies on the fragmentation header. This 64 bits header is composed of six fields : 154/10000 · 154
136 ../../protocols/ipv6.rst:435

	English a `Next Header` field that indicates the type of the header that follows the fragmentation header 97/10000 · 97
137 ../../protocols/ipv6.rst:436

	English two `Reserved` fields set to `0`. 33/10000 · 33
138 ../../protocols/ipv6.rst:437

	English the `Fragment Offset` is a 13-bit unsigned integer that contains the offset, in 8 bytes units, of the data following this header, relative to the start of the original packet. 175/10000 · 175
139 ../../protocols/ipv6.rst:438

	English the `More` flag, which is set to `0` in the last fragment of a packet and to `1` in all other fragments. 104/10000 · 104
140 ../../protocols/ipv6.rst:439

	English the 32-bit `Identification` field indicates to which original packet a fragment belongs. When a host sends fragmented packets, it should ensure that it does not reuse the same `identification` field for packets sent to the same destination during a period of `MSL` seconds. This is easier with the 32 bits `identification` used in the IPv6 fragmentation header, than with the 16 bits `identification` field of the IPv4 header. 426/10000 · 426
141 ../../protocols/ipv6.rst:445

	English Some IPv6 implementations send the fragments of a packet in increasing fragment offset order, starting from the first fragment. Others send the fragments in reverse order, starting from the last fragment. The latter solution can be advantageous for the host that needs to reassemble the fragments, as it can easily allocate the buffer required to reassemble all fragments of the packet upon reception of the last fragment. When a host receives the first fragment of an IPv6 packet, it cannot know a priori the length of the entire IPv6 packet. 543/10000 · 543
142 ../../protocols/ipv6.rst:447

	English The figure below provides an example of a fragmented IPv6 packet containing a UDP segment. The `Next Header` type reserved for the IPv6 fragmentation option is 44. 163/10000 · 163
143 ../../protocols/ipv6.rst:453

	English IPv6 fragmentation example 26/10000 · 26

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.