Talk:Requests for comment/IPv6 contributions and talk pages

This is true only for residential ISP's. Business networks often have many users on a single /64 and those users are often unrelated to each other. The same goes for mobile networks. To preserve the collateral damage-limiting benefits of IPv6, it is necessary to keep addresses separate. I would, however, support sharing Echo or talk page notifications for all addresses in the same /64. It is already possible to create a talk page in the form of [address]/64 so this could just be implemented as sending notifications on editing of that talk page.

A better proposal than consolidating the contributions pages would be to add built-in support for range contributions, a feature long desired even for IPv4. Even for home networks, putting everyone under one /64 is a poor design decision which basically negates the collateral damage benefits of IPv6.

I should also add that except for cellular networks, addresses are seldom dynamic enough such that a vandal can't be warned on the address they're currently on; if the vandal is determined to IP-hop then this cannot be any better than IPv4, since many ISP's do not statically assign the /64 prefix. Some Asian ISP's also do not follow standard practice and use DHCPv6 to assign addresses from much larger ranges.

It is already possible to create a talk page in the form of [address]/64 so this could just be implemented as sending notifications on editing of that talk page.

A better proposal than consolidating the contributions pages would be to add built-in support for range contributions, a feature long desired even for IPv4.

That sounds like it would work too. I'm not too fussed about the implementation details, so long as regular users are able to view the contributions of a /64 and send messages to them.