Network Engineering Stack Exchange is a question and answer site for network engineers. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In IPv4 we use /30 to conserve addresses. So why do some people recommend using /64 on P2P links instead of /126? I get using a /64 on regular subnets but isn't using a /64 when there will only ever be two addresses in use on P2P links tremendous waste of addresses?

share|improve this question
Hi, please consider the perspectives expressed in RFC 6164 – Mike Pennington Feb 19 '14 at 19:39
Because they haven't read RFC 6164, probably. – Michael Hampton Feb 19 '14 at 20:17

Many of us do use /126's on PTP links. I personally like being able to identify something as a network infrastructure PTP link just based on the first 64 bits of the address, so I reserve a /64 to pull the /126's from. Different people have different opinions on what's important, so...shrug

Incidentally (#1), because IPv6 doesn't have the concept of a broadcast address or a network address on an IP network, you could actually use /127's instead of /126's. Beware that some vendor gear has (wrongly) not allowed this netmask as being an "invalid" netmask, despite the fact that it is perfectly valid, so you may run into some vendor support issues if you decide to try to use /127's...and this is why I use /126's.

Incidentally (#2), if your links are truly defined as PTP links, you should be able to use any IP addresses without them having to be in a common IP network at all.

share|improve this answer
Can you give an example of a vendor that restricts the use of /127s? – Ryan Foley Feb 19 '14 at 20:12
At one point, Brocade in the FastIron line and perhaps in the NetIron line didn't allow it. I haven't checked recent firmware versions, so I don't know if that is still the case or not. – Jeff McAdams Feb 19 '14 at 20:14
Brocade isn't a small company, either. Good insight. – Ryan Foley Feb 19 '14 at 20:17
up vote 1 down vote accepted

Because IPv6 always recommends using /64 for all links.

For the second part of the question, is it a waste?

A /64 has 18,446,744,073,709,551,615, or 18 quintillion addresses.

Most IPv4 subnets are less than 255 hosts. Assume that you have a network with 255 hosts on it and they're given a /64 prefix. That means that 255 hosts are assigned a v6 address, leaving 18,446,744,073,709,551,360 addresses unused. That's over 99.99%. To be more accurate, that's sixteen 9's, or effectively 100% "waste".

Even if you had a subnet with 1,000,000 hosts on it, that's 18,446,744,073,708,551,616 wasted addresses, or still over 99.99%. Only thirteen 9's this time, but still effectively 100% "waste".

So the percentage difference between using one million addresses or two addresses on a single link is negligible.

And just so you can see what these numbers look like.

* Two hosts is 99.9999999999999999891579782751449556599254719913005828857422% unused.
* 255 hosts is 99.9999999999999986176422300809818466404976788908243179321289% unused.
* 1M  hosts is 99.99999999999457898913757247782996273599565029144287109375% unused.
* 4B  hosts is 99.999999976716935634613037109375% unused.

Even the entire IPv4 Internet placed on a single /64 link would leave effectively 100% of the addresses unused. When you look at the numbers like this, using anything other than a /64 on a link is just silly.

share|improve this answer
A lot of ISPs DO use /126 for point to point links. I guess old habits die hard ;-) – Ron Trunk Feb 19 '14 at 19:08
They do, but hopefully realizing that the entire IPv4 Internet is still effectively 0% of a /64 may bring some proper perspective. – bahamat Feb 19 '14 at 19:11
One possible reason (I'm not an ISP) may be that they can take a single /64 subnet and put all of their links into it. It may make management and troubleshooting easier. – Ron Trunk Feb 19 '14 at 20:01
@bahamat I don't think you fully answered your original question. "Because IPv6 always recommends using /64 for all links" does not answer "So why do some people recommend using /64 on P2P links instead of /126?". – Ryan Foley Feb 19 '14 at 20:08
In addition to my full answer, I wanted to comment on this one. The statement that IPv6 always recommends using /64 for all links is no longer valid. – Jeff McAdams Feb 19 '14 at 20:56

There are two parts to the answer.

First, to answer your question directly: the official recommendation on this topic has changed. In the past, RFC 3627 is titled "Use of /127 Prefix Length Between Routers Considered Harmful" The current recommendation is different, though: RFC 6164 recommends using a /127 (not a /126!) on point-to-point links. Both RFCs outline the reasons for the respective recommendations.

The second part of the answer is that generally, outside point-to-point links, IPv6 will break with any prefix longer than /64. It is actually not IPv6 itself, but many of the protocols it uses, such as SLAAC, Neighbor Discovery, etc. Since a point-to-point link does not involve any form of discovery, that consideration is not relevant, and a /127 will work.

share|improve this answer
RFC 6547 clarifies the fact that RFC 3627 has been moved to Historical Status, and that RFC 6164 obsoletes it. – Ron Maupin Nov 8 '15 at 4:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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