IPv6 for Embedded Developers used to IPv4
summary
Predictable facts: IPv6 is necessary because RIR pools exhausted (2011 onward) and consumer ISPs commonly give /48 or /64 prefixes; IoT scales to tens of billions of devices so per-device global addresses matter. Practical guidance: use getaddrinfo/getnameinfo, sockaddr_storage and the new IP tools instead of ifconfig, write IPv6 servers (disable IPV6_V6ONLY only when intended), handle multiple rotating addresses per interface, watch duplicate address detection, listen for changes via netlink, and consider 6lowpan/header compression for constrained mesh networks.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 2:40IPv4 exhaustion
- 5:05IPv6 features and benefits
- 11:14Auto-configuration
- 15:44Privacy and security
- 20:16Addressing and prefixes
- 26:39Address management
- 30:10Programming for IPv6
- 36:14Software development best practices
- 43:36IoT and 6LowPAN
- 50:03Q&A and concluding thoughts
related talks
26mIPv6 for Programmers
48mIPv6 for Server Admins and Client Developers
36mIPv6 in 2025: Quo Vadis?
28mHow and Why to Publish Your Site on IPv6
23mAIN: A Blueprint for an All-IP Data Center Network
26mIPv6 First, Not Just Ready: Kubernetes Without IPv4 Using Cilium
31mHow to share IPv4 addresses by partitioning the port space
18mWorld IPv6 Day: What We Learned