I understand that IPv6 reserves the fe80::/10 prefix for link local addresses, and that hosts select an address with a /64 prefix.

Why is the reserved space so much larger than what is actually used for link local?

4 Answers 4


I think the link-local scope was set to /10 simply to "fit in" better with the other scopes, e.g. site-local (before it was replaced with unique local).

Initially I had thought maybe it was to allow the use of many link-local networks on the same link, but RFC 4291 explicitly states that only fe80::/64 may be used.

  • Is there any significance regarding SLAAC implementation? ...is SLAAC "prefix agnostic"? Commented May 8, 2013 at 14:50
  • 1
    SLAAC requires a /64, but it is not really relevant here, because link-local addresses aren't assigned by SLAAC - in fact, SLAAC relies on already having a link-local address. Commented Nov 8, 2015 at 5:34

You know, I've never considered this.

I would presume that fe80::/64 is used because systems then run stateless address autoconfiguration (SLAAC) in that /64. Leaving the rest of the /10 available for statically assigned link-local addresses and netblocks. I'm having a tough time coming up with significant use cases for static link-local assignments, but I suppose there are reasons that people might end up wanting to do so.

  • What's the significant of SLAAC and /64? ...is there something inherent to SLAAC about the /64 prefix? Commented May 8, 2013 at 14:39
  • sometimes statically assigned link local addresses makes it easy to know which node is the next hop when routing dynamically, i.e. R1 is fe80::1/64, R2 is fe80::2/64, etc. Works well in the lab, maybe less so in practice.
    – hrtednrup
    Commented May 8, 2013 at 15:24
  • @CraigConstantine - yes, SLAAC has the /64 boundary hardcoded into the protocol. That is the reason you cannot create subnets smaller than a /64 in IPv6, with the exception of subnets used for routing links (i.e., for a point-to-point link you should use a /127). There are actually other protocols that also have the /64 boundary baked into it. Commented Nov 28, 2015 at 6:21
  • We have a use-case. A process isolation system that needs to bring up the isolation environment with a known link-local address for IPv6 based identification. And we can't wait for DAD, because the environment needs to be ready in microseconds or milliseconds. Commented Feb 10, 2018 at 20:15

The design philosophy behind IPv6 is that having a reasonably-structured address space is more important than conserving addresses. Incidentally, IPv4 was conceived with the same idea (which is why each device has 16 million loopback addresses, but only ever uses the address, and most of the class D and E addresses are unused).

Link-local addresses theoretically do waste gazillions of IP addresses, but it's not considered a problem. Similarly, giving each customer a full /56 or even /48 is technically very wasteful, but not a real problem.

There is a dark side to this approach: the claim that IPv6 can give an IP address to each grain of sand in the world (or some such) is nonsense, just as the claim that IPv4 can support 4 billion devices. In reality, by the time you add up all the waste in IPv6, you'll find that the limits are much narrower (still bigger than IPv4).


I think that it comes down to 2 things. First, a link-local cannot be routed, so no subnet ID is needed. It is assumed that since it cannot be routed that anything following the prefix up until the last 64-bits will be zero's. Second, like other similar IPv6 prefixes, the prefix is everything up until the last '1' bit. This keeps consistency.

  • 1
    If that was how it worked, it would have been a /9 not a /10.
    – kasperd
    Commented Jun 30, 2015 at 22:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.