Many people are familiar with how multicast addresses are used for one-to-many communications.

This is also a topic that we discuss in our IPv6 COE Podcast #3. Please also read Tom Coffeen’s eloquent blogs ( part 1 and part 2) on “3 Ways to Ruin Your Future Network with IPv6 Unique Local Addresses”. You are encouraged to read RFC 4864, Local Network Protection for IPv6, to learn about why you do not need private addresses for your internal networks and why you subsequently do not need NAT for IPv6. However, with IPv6, beginners discover that FD00::/8 Unique Local Addresses (ULAs) exist for private network addressing, although their use is not generally recommended. Regardless of whether your organization’s public IPv4 or global IPv6 addresses are provided by an RIR or your upstream ISP, they are free to be used to source and receive Internet communications. Public IPv4 addresses are familiar to most, so grasping IPv6’s global unicast addresses (GUA) (2000::/3) is straightforward. It is relatively easy to grasp the concept that unicast addresses are used for one-to-one communications. This article builds upon the IPv6 newbie questions theme and covers a couple of the IPv6 addressing nuances that are often surprising to IPv6 neophytes (and sometimes IPv6 veterans, too!).įrequently Unicast, Sometimes Multicast, but Never Broadcast

We then asked the question, “What are the typical questions you get when teaching an IPv6 class?” Frequently, IPv6 instructors field questions from their students about IPv6 link-local addresses and how they work.

In a recent article, I wrote about some of the common questions that IPv6 novices sometimes ask.

Convert mac address to ipv6 calculator