Core Networking · Study deck

IPv6 for IoT

IPv4 is the older common plan for network addresses.

Packet Pete is your guide for this deck.

addripv6

Packet Pete, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

Follow this chapter path with evidence at each boundary.

Name the system boundary.
Record the evidence needed there.
Keep the next decision tied to the source.

Shorten and expand an IPv6 address. Read its prefix and base header. Verify discovery, route, constrained-link compression, and any IPv4 transition.

Major section

Begin With One New Device

IPv4 is the older common plan for network addresses.

IPv6 is a newer plan with a far larger address space.
A gateway is a node that joins one network to another.
It needs an address, a local path, and a route to the service.
Also test a device that has only the older address plan.

Major section

Begin With One New Device (continued)

Auto setup can reduce hand work, but bad router data can spread a bad choice.

The large address space removes a shortage, but it does not remove design work.
Two address plans can ease a move, but they add tests and failure paths.
For an IPv6 join, build the prefix and join record; check neighbor discovery, routing, small-link use, and transition limits before accepting the result.

Major section

Overview: IPv6 Removes the Address Bottleneck, Not the Design Work

The header fields expose the routing, lifetime, traffic, and next-protocol evidence that operations must be able to capture.

The fixed sequence separates per-packet forwarding information from optional extension headers.
That distinction connects explicit prefix planning to packet-trace evidence when reachability, policy, or path lifetime fails.

IPv6 fixed base header and its routing and delivery fields

Major section

Practitioner: Build the Prefix and Autoconfiguration Record

Leading zeroes inside a group may be dropped, and one consecutive run of all-zero groups may be replaced by ::; using that shortcut twice would make the number of missing groups ambiguous.

The compressed form is easier to read, but troubleshooting should expand it back to the same 128 bits before comparing prefixes or logs.

IPv6 address compression example showing removal of leading zeros and replacement of one consecutive zero run with double colon notation. — Address notation should be short enough to read and consistent enough to troubleshoot.

Major section

Practitioner: Build the Prefix and Autoconfiguration Record (continued)

If compression reduces the header from 40 bytes to 6 bytes, it saves 34 bytes before transport and application data are counted.

Two strings can look similar while belonging to different subnets, and several spellings can represent one identical address.
Both endpoints must share the same context, and fragmentation can still dominate a small frame.
The record should therefore include compression mode, context lifetime, fallback behaviour, and the complete on-air packet size.

Major section

Under the Hood: Neighbor Discovery, Routing, and Transition Boundaries

Each branch gives routing and operations a summarizable boundary while leaving room for growth.

The hierarchy connects prefix planning to neighbor, route, firewall, and ownership evidence: when a branch fails, responders can narrow both the affected estate and the responsible control plane.

Hierarchical IPv6 prefix plan for a smart-city deployment

Major section

Shorten an IPv6 Address Without Changing It

The full streetlight address and its short form encode the same one hundred twenty-eight bits.

Name the system boundary.
Record the evidence needed there.
Keep the next decision tied to the source.

Full streetlight address: 2001:0db8:0000:0000:0217:5aff:fe3c:0042 → short form: 2001:db8::217:5aff:fe3c:42. One double colon replaces the two all-zero groups. Written-address shortening is different from 6LoWPAN header compression.

Major section

Shorten an IPv6 Address Without Changing It (continued)

Header compression does not shorten the logical IPv6 address space; it avoids repeating fields that both ends can reconstruct on that link.

Hop Limit bounds a routing loop; it does not state how many radio retries occurred on one low-power link.
Two :: marks would make the number of omitted zero groups ambiguous.
The link may depend on 6LoWPAN context and compression to fit its packet budget.

Deck summary

Key takeaways

IPv4 is the older common plan for network addresses.

Auto setup can reduce hand work, but bad router data can spread a bad choice.
The header fields expose the routing, lifetime, traffic, and next-protocol evidence that operations must be able to capture.
Leading zeroes inside a group may be dropped, and one consecutive run of all-zero groups may be replaced by ::; using that shortcut twice would make the number of missing groups ambiguous.
If compression reduces the header from 40 bytes to 6 bytes, it saves 34 bytes before transport and application data are counted.

Retrieval practice

Recall check 1 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q1Which IPv6 design habit is strongest for an IoT deployment?

AAssign every device a global prefix first, then add firewall rules after applications are online.

BPlan scope, prefixes, routing policy, local discovery, and verification evidence before rollout.

CDisable link-local addressing so device traffic always uses a routable site or cloud prefix.

DReuse IPv4-style small subnet sizing so the IPv6 deployment conserves address space.

Show answer

Answer: B IPv6 IoT planning should define address scope, prefixes, routing policy, local discovery, access boundaries, and verification evidence.

Retrieval practice

Recall check 2 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q2A campus IoT team has a large IPv6 allocation and wants addresses that help operations during incidents. What is the best planning move?

APack every device class into the smallest subnet possible so unused address space is minimized.

BUse only link-local addresses because most devices normally talk to a nearby campus gateway.

CUse readable prefixes for site, floor, device class, or trust zone and record route checks.

DUse random prefixes without inventory records because the IPv6 allocation has enough space.

Show answer

Answer: C An IPv6 IoT plan should encode operational meaning in prefixes and record address formation, routing, and verification evidence.

Retrieval practice

Recall check 3 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q3A sensor uses IPv6, but the old reporting service accepts only IPv4. What should the path record name?

AName the dual-stack, translation or tunnel boundary and its operator.

BRecord IPv6 prefix alone while leaving the IPv4-only service boundary unnamed.

CRecord service hostname alone without address-family conversion ownership.

DRecord dashboard color alone as if it explained IPv4-to-IPv6 connectivity.

Show answer

Answer: A The record must show where address families meet and which component owns the conversion.

Retrieval practice

Recall check 4 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q4Why is a clean IPv6 prefix plan not enough by itself?

ABecause IPv6 addresses cannot cross routed networks unless NAT is enabled at each boundary.

BBecause link-local addresses are optional and should usually be disabled on IoT interfaces.

CBecause 6LoWPAN compression removes the need to test constrained low-power links.

DBecause discovery, routing policy, firewalls, constrained links, and transitions must work too.

Show answer

Answer: D IPv6 operations require evidence for local discovery, routing, security policy, constrained-link behavior, and IPv4/IPv6 transition boundaries.

Print reference

Answers

Answer key.

B · IPv6 IoT planning should define address scope, prefixes, routing policy, local discovery, access boundaries, and verification evidence.
C · An IPv6 IoT plan should encode operational meaning in prefixes and record address formation, routing, and verification evidence.
A · The record must show where address families meet and which component owns the conversion.
D · IPv6 operations require evidence for local discovery, routing, security policy, constrained-link behavior, and IPv4/IPv6 transition boundaries.

B · Plan scope and evidence. C · Use meaningful prefixes. A · Name the IPv4 transition owner. D · Verify discovery, routing, policy, and constrained links.