cnp3-ebook/protocols/ipv6 — English @ Weblate

Exit Zen

14 ../../protocols/ipv6.rst:90

	English PIP proposed in :rfc:`1621` 27/10000 · 27
15 ../../protocols/ipv6.rst:91

	English SIPP proposed in :rfc:`1710` 28/10000 · 28
16 ../../protocols/ipv6.rst:93

	English The IETF decided to pursue the development of IPng based on the SIPP proposal. As IP version `5` was already used by the experimental ST-2 protocol defined in :rfc:`1819`, the successor of IP version 4 is IP version 6. The initial IP version 6 defined in :rfc:`1752` was designed based on the following assumptions : 316/10000 · 316
17 ../../protocols/ipv6.rst:95

	English IPv6 addresses are encoded as a 128 bits field 46/10000 · 46
18 ../../protocols/ipv6.rst:96

	English The IPv6 header has a simple format that can easily be parsed by hardware devices 81/10000 · 81
19 ../../protocols/ipv6.rst:97

	English A host should be able to configure its IPv6 address automatically 65/10000 · 65
20 ../../protocols/ipv6.rst:98

	English Security must be part of IPv6 29/10000 · 29
21 ../../protocols/ipv6.rst:100

	English The IPng address size 21/10000 · 21
22 ../../protocols/ipv6.rst:102

	English When the work on IPng started, it was clear that 32 bits was too small to encode an IPng address and all proposals used longer addresses. However, there were many discussions about the most suitable address length. A first approach, proposed by SIPP in :rfc:`1710`, was to use 64 bit addresses. A 64 bits address space was 4 billion times larger than the IPv4 address space and, furthermore, from an implementation perspective, 64 bit CPUs were being considered and 64 bit addresses would naturally fit inside their registers. Another approach was to use an existing address format. This was the TUBA proposal (:rfc:`1347`) that reuses the ISO CLNP 20 bytes addresses. The 20 bytes addresses provided room for growth, but using ISO CLNP was not favored by the IETF partially due to political reasons, despite the fact that mature CLNP implementations were already available. 128 bits appeared to be a reasonable compromise at that time. 936/10000 · 936
23 ../../protocols/ipv6.rst:105

	English IPv6 addressing architecture 28/10000 · 28
24 ../../protocols/ipv6.rst:107

	English The experience of IPv4 revealed that the scalability of a network layer protocol heavily depends on its addressing architecture. The designers of IPv6 spent a lot of effort defining its addressing architecture :rfc:`3513`. All IPv6 addresses are 128 bits wide. This implies that there are :math:`340,282,366,920,938,463,463,374,607,431,768,211,456 (3.4 \times 10^{38})` different IPv6 addresses. As the surface of the Earth is about 510,072,000 :math:`km^2`, this implies that there are about :math:`6.67 \times 10^{23}` IPv6 addresses per square meter on Earth. Compared to IPv4, which offers only 8 addresses per square kilometer, this is a significant improvement on paper. 676/10000 · 676
25 ../../protocols/ipv6.rst:109

	English Textual representation of IPv6 addresses 40/10000 · 40
26 ../../protocols/ipv6.rst:111

	English It is sometimes necessary to write IPv6 addresses in text format, e.g. when manually configuring addresses or for documentation purposes. The preferred format for writing IPv6 addresses is ``x:x:x:x:x:x:x:x``, where the ``x`` 's are hexadecimal digits representing the eight 16-bit parts of the address. Here are a few examples of IPv6 addresses : 347/10000 · 347
27 ../../protocols/ipv6.rst:113

	English ``abcd:ef01:2345:6789:abcd:ef01:2345:6789`` 43/10000 · 43
28 ../../protocols/ipv6.rst:114

	English ``2001:db8:0:0:8:800:200c:417a`` 32/10000 · 32
29 ../../protocols/ipv6.rst:115

	English ``fe80:0:0:0:219:e3ff:fed7:1204`` 33/10000 · 33
30 ../../protocols/ipv6.rst:117

	English IPv6 addresses often contain a long sequence of bits set to ``0``. In this case, a compact notation has been defined. With this notation, `::` is used to indicate one or more groups of 16 bits blocks containing only bits set to `0`. For example, 245/10000 · 245
31 ../../protocols/ipv6.rst:119

	English ``2001:db8:0:0:8:800:200c:417a`` is represented as ``2001:db8::8:800:200c:417a`` 82/10000 · 82
32 ../../protocols/ipv6.rst:120

	English ``ff01:0:0:0:0:0:0:101`` is represented as ``ff01::101`` 58/10000 · 58
33 ../../protocols/ipv6.rst:121

	English ``0:0:0:0:0:0:0:1`` is represented as ``::1`` 45/10000 · 45

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.