![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 10/19/2016 09:28 AM, Per Jessen wrote:
I know of ISPs that even dish out smaller nets, for hosting for instance.
Ah, got it. Yes, definitely SLAAC would be ruled out. TBH, I don't really understanding the reasoning for handing out less than a /64, I just wanted to mention that I've seen it done. I'm also not sure if it's possible to register whois information (RIPE objects) for less than a /64, but maybe.
I've done a lot of work setting up Internet connections to hosts in data centres. There are 2 ways servers can get an internet connection. One, they get their own connection from a carrier or they may share a subnet that's available in the data centre. With IPv4, they'd typically get a /30. With IPv6, they could get a /64 from the carrier. However, I don't think there would be a problem with a /126 or /127, which is supported in IPv6, to get a single address over a point to point link. However, with all the IPv6 addresses available, a /64 for a single host is not an issue. It just rubs some people the wrong way. ;-) Back when I was using a 6in4 tunnel, I was using client software that could be configured for a /56 prefix or a single address. I used the /56 on my home network and single address on my notebook computer, when away from home. IPv6 /127 https://tools.ietf.org/html/rfc6164 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org