IPv6 addressing on point-to-point links

IPv6 subnets are normally not smaller than /64. But this seems a bit excessive use of the IPv6 space. In this post I’m trying to show u the possibilities to use alternative subnet sizes. You can decide for yourself what prefix size you prefer. You could consider the following alternatives;

/127:
You could see this as the equivalent of the 31-bit prefixes in IPv4. Previously a /127 prefix was considered harmful and described in RFC 3627, but RFC 6547 describes that guidance provided in RFC 6164 is to be followed when the two documents are in conflict. This is a quote from RFC 6164 where the authors refute the arguments from the old RFC.

[RFC3627] discourages the use of 127-bit prefix lengths due to
conflicts with the Subnet-Router anycast addresses, while stating
that the utility of Subnet-Router anycast for point-to-point links is
questionable.

[RFC5375] also says the usage of 127-bit prefix lengths is not valid
and should be strongly discouraged, but the stated reason for doing
this is to be in compliance with [RFC3627].

Though the analyses in the RFCs are correct, operational experience
with IPv6 has shown that /127 prefixes can be used successfully.

The same RFC explains the following reasons to use more then 64-bits, particularly 127-bits, as prefix length:

  • Ping-Pong Issue
  • Neighbor Cache Exhaustion Issue

/126:
The lowest possible address in every IPv6 subnet is the “all routers anycast address”. Using a /127 prefix when a vendor is not supporting this could cause problems. Using a 126-bit prefix length solves this issue. However, the highest 128 addresses in every IPv6 prefix are also reserved for anycast addresses (RFC 2526).

/120:
Skips all anycast addresses and you should be save to implement this prefix length.

/112:
same as the /120, but might be more readable for the network engineer. The last four-digit hexadecimal value is used for the host part, so the whole part after the last colon.
/120: NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:NNHH
/112: NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:NNNN:HHHH

Sources/Links:

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.