Otoh, ipv6 address assignment tends to be much more contiguous. My (small) residential ISP has one v6 prefix but several v4 prefixes. If you block the whole prefix for services you don't like, it's far less prefixes for v6.
But, it is a new skill, and you can turn off v6 at small cost if you're already ok with heavily restricting v4.
Additionally to the much larger IP space, you also have larger headers and additionally extension headers which make deep packet inspection computationally much more expensive if you consider the scale
>One characteristic of v4 is it's somewhat reasonable to do a straight forward block on a range of addresses to shut down access. This is still somewhat possible with v6, but harder as there's simply a much larger portion of ip addresses that can be all over the place. It's theoretically a lot easier for anyone that wants to bypass a simple filter to grab a new public IP address.
no its not, its easier to block IPv6 ranges than IPv4 ones.
if someone want be block my ISP, they only need a single /32 rule with v6.
n ipv4 /32 is roughly equivalent to an ipv6 /56 or /64
You'd typically block an AS - i.e. every IP originating from AS12345. That's just as easy on v6 as v4.
Only legacy address space is frequently bought and sold, so it moves between AS#s a lot and is also heavily fragmented.
With v6 this is not the case, a given AS# will typically have a single large allocation and can make it larger if they need to, it won't be sold and moved and an entity can't trade it in to get a different allocation.
One characteristic of v4 is it's somewhat reasonable to do a straight forward block on a range of addresses to shut down access. This is still somewhat possible with v6, but harder as there's simply a much larger portion of ip addresses that can be all over the place. It's theoretically a lot easier for anyone that wants to bypass a simple filter to grab a new public IP address.