mirror of
https://github.com/opsschool/curriculum.git
synced 2025-12-06 12:19:49 +01:00
Update networking_101.rst (#334)
Replaced the uncommon word "hextet" with an expansion. Changed the example IPv6 address to be in the block reserved in RFC 3849 for documentation. Added a short explanation of zero-replacing in IPv6 addresses.
This commit is contained in:
parent
48d80e8cdb
commit
75ca2bc2bf
|
|
@ -247,10 +247,18 @@ which aims to address the IPv4 address exhaustion problem.
|
||||||
|
|
||||||
Probably the most obvious difference of IPv6 to IPv4 is the representation of addresses.
|
Probably the most obvious difference of IPv6 to IPv4 is the representation of addresses.
|
||||||
Unlike IPV4, IPv6 uses a hexadecimal format to represent a 128-bit address. The format is
|
Unlike IPV4, IPv6 uses a hexadecimal format to represent a 128-bit address. The format is
|
||||||
grouped into 8 hextets separated by a colon.
|
grouped into 8 groups of four hexadecimal digits separated by a colon.
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
3341:1112:AAAA:0001:4321:5876:CBAD:1234
|
2001:0DB8:0000:CBAD:4321:0000:0000:1234
|
||||||
|
|
||||||
|
Leading zeroes may be left off of a group in the address. Whole groups of zeros may be
|
||||||
|
left out entirely, but only once. Generally, the longest run of zeros is dropped, but
|
||||||
|
any run may be. Using these rules, the above address can also be represented in either
|
||||||
|
of these ways:
|
||||||
|
|
||||||
|
2001:DB8::CBAD:4321:0000:0000:1234
|
||||||
|
2001:DB8:0000:CBAD:4321::1234
|
||||||
|
|
||||||
TCP vs UDP
|
TCP vs UDP
|
||||||
==========
|
==========
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user