Week 6 · Lesson 13

IPv6 Addressing and Format

IPv4 was never designed for billions of always-on devices, and NAT only postponed the problem. IPv6 solves it with a 128-bit address written as eight groups of four hexadecimal digits. Read this lesson slowly — the compression rules are pure marks on the exam, and getting them wrong is the fastest way to lose an address question.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

Why IPv6?

IPv4 provides about 4.3 billion addresses (232). That seemed endless in 1981, when networked computers were rare. It is not. The explosion of PCs, smartphones, tablets, servers, sensors, and cloud instances consumed the free pool; IANA handed out its last IPv4 blocks in 2011. The address registries and carriers have been running on reclaimed and recycled space ever since.

The industry stretched IPv4 with two big hacks. NAT (network address translation) lets thousands of private hosts share one public address by rewriting source ports, which is why a whole home can appear as one IP on the Internet. CIDR (classless addressing) made allocation more efficient than the old classful scheme. Both helped, but neither gives the Internet the thing it actually needs: an end-to-end, globally unique address for every interface.

Definition — IPv6. IPv6 (Internet Protocol version 6) is the successor to IPv4. It uses a 128-bit address, written as eight groups of four hexadecimal digits, providing roughly 3.4 × 1038 addresses — enough to address the entire planet many times over.

IPv6 is not just “IPv4 with bigger numbers”. It removes the header checksum, drops in-router fragmentation, adds built-in support for address autoconfiguration (SLAAC, Lesson 16), and makes a link-local address mandatory on every interface. Those changes make routing faster and host configuration simpler. For CCNA you focus on the addressing and the control protocols, but knowing why the format looks the way it does makes both easy to remember.

IPv4

32 bits — about 4.3 billion addresses. Address exhaustion forced NAT and CIDR onto the network.

IPv6

128 bits — about 3.4 × 1038 addresses. End-to-end addressing returns, and NAT becomes unnecessary.

Written as

Eight hextets of four hexadecimal digits, separated by colons: 2001:db8::1.

Part 2

The 128-bit address and hextets

A bit holds one 0 or 1. IPv4 has 32 bits, so it has 232 values. IPv6 has 128 bits, so it has 2128 values. Writing 128 ones and zeros by hand is unusable, so the address is grouped in hextets (also called fields or groups): each hextet is 16 bits shown as four hexadecimal digits. Eight hextets × 16 bits = 128 bits. Hexadecimal uses 0–9 and A–F, where A = 10 and F = 15.

2001 0db8 0000 0000 0000 ff00 0042 8329 network prefix (first 4 hextets here) interface identifier (last 4 hextets) One IPv6 address = 8 hextets × 16 bits = 128 bits. Each hex digit = 4 bits; four digits = 16 bits = one hextet.

The same address written in full is 2001:0db8:0000:0000:0000:ff00:0042:8329. The boundary between the network prefix and the interface identifier is set by the prefix length, not by a fixed split.

A few formatting facts to lock in:

Part 3

The two compression rules

Even four digits per group is a lot to type. RFC 4291 defines two ways to shorten an address. You may apply both at once, but each has a strict limit that the exam loves to test.

Rule 1 — drop leading zeros.
Within any hextet, remove the leading zeros. 0db8 becomes db8, 0042 becomes 42, and 0000 becomes 0. Trailing zeros are never removed: ff00 stays ff00, not ff.
Rule 2 — replace one run of zeros with ::.
A single consecutive run of all-zero hextets may be replaced by a double colon. The double colon may appear only once in an address, because two occurrences would make the address ambiguous — the reader could not tell how many zero hextets belong in each gap.
Compress an address · type any IPv6 address
0 rules used

Work through the example above. Start with the full address:

2001:0db8:0000:0000:0000:ff00:0042:8329
! apply rule 1: strip leading zeros from each hextet
2001:db8:0:0:0:ff00:42:8329
! apply rule 2: replace the run of zero hextets with ::
2001:db8::ff00:42:8329

Notice that ff00 keeps its trailing zeros — only leading zeros vanish. Notice also that the run 0:0:0 became a single ::. This compressed form is what you will see in every show command output.

Exam tip — the two traps. (1) :: may be used once only. An answer containing two double colons is always wrong. (2) Leading zeros are dropped, but trailing zeros are kept: 2001:0db8::0042 must become 2001:db8::42 — and ff00 is never shortened to ff.
Part 4

Expanding an address back

The reverse operation is equally likely to appear: given a compressed address, write the full form. Count the hextets you can see, then pad the :: with enough zero hextets to reach a total of eight. Finally, left-pad each hextet back to four digits.

Expand an address · type a compressed IPv6 address
0 hidden hextets

StepResultWhy
Visible hextets2001, db8, 1Three shown; the :: hides the rest.
Count needed8 − 3 = 5Five zero hextets replace the ::.
Substituted2001:db8:0:0:0:0:0:1Five zeros inserted.
Fully padded2001:0db8:0000:0000:0000:0000:0000:0001Each hextet left-padded to four digits.

If no :: is present, you simply left-pad each hextet and you are done. If there is a ::, the number of hidden hextets is always at least one — a :: that replaces zero hextets is invalid — and you solve for the remainder by subtraction. Practice until this is automatic.

Part 5

Prefix length and the two halves

IPv6 has no dotted-decimal subnet mask. The network portion is expressed as a prefix length — a slash and a number of network bits, exactly like CIDR in IPv4. A /64 means the first 64 bits (the first four hextets) are the network, and the last 64 bits (the last four hextets) are the interface identifier.

Prefix length explorer · select a prefix

PrefixNetwork bitsCommon meaning
/322 hextetsTypical allocation to a large ISP from a registry (see Lesson 15).
/483 hextetsTypical allocation to one customer site or enterprise.
/644 hextetsThe standard LAN prefix; one per subnet. SLAAC requires /64.
/128all 128 bitsA single host address (equivalent to IPv4 /32).

In a /64, an ISP that has a /48 can carve out 65,536 individual LANs, each enormous enough to number every device a site will ever own. This abundance is the whole point of IPv6: there is no reason to be stingy, so hosts get globally unique addresses and NAT disappears from the design.

Part 6

IPv6 compared with IPv4

Two rows in the comparison deserve a second look. First, IPv6 has no broadcast. Where IPv4 used a network broadcast to reach everyone, IPv6 uses well-known multicast groups such as the all-nodes address ff02::1 (Lesson 14). Second, removing the header checksum is not carelessness: the link layer and the transport layer already detect errors, so re-checking every hop wasted cycles. Dropping it lets routers process packets faster.

IPv4 against IPv6 · select a property

PropertyIPv4IPv6
Address size32 bits128 bits
NotationFour dotted-decimal octets, e.g. 192.0.2.1Eight hex hextets, e.g. 2001:db8::1
Header size20 bytes minimum40 bytes fixed
Header checksumYesNo (removed)
Subnet maskDotted decimal or CIDRPrefix length only (e.g. /64)
BroadcastYesNo — uses multicast instead
Address configManual or DHCPManual, SLAAC, or DHCPv6
NATCommonly requiredNot needed for address conservation
Minimum MTU576 bytes1280 bytes
Note — dual stack. IPv4 and IPv6 are not compatible; they are separate protocols. In practice networks run dual stack, meaning a host has both an IPv4 and an IPv6 address and picks the appropriate one. You will keep seeing IPv4 for years, so you must know both.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Hinden, R. & Deering, S. RFC 4291: IP Version 6 Addressing Architecture (2006) — hextet notation, compression rules, address types. rfc-editor.org/rfc/rfc4291.
  2. Deering, S. & Hinden, R. RFC 8200: Internet Protocol, Version 6 (IPv6) Specification (2017) — 128-bit address and fixed 40-byte header. rfc-editor.org/rfc/rfc8200.
  3. Kawamura, S. & Kawashima, M. RFC 5952: A Recommendation for IPv6 Address Text Representation (2010) — canonical lowercase and compression. rfc-editor.org/rfc/rfc5952.
  4. IANA. IPv6 Address Space registry. iana.org.
  5. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals — compare and contrast IPv4 and IPv6 addressing. cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.