Hello,
On 5/15/24 1:28 PM, Edward Shryane via db-wg wrote:
But of course you could also switch IP address and continue to query,
it's difficult to prevent this if the queries are anonymous. We account
by /32 prefix for an IPv4 address and by /64 prefix for an IPv6 address.
I think this is bad approach. Why on IPv4 you block only single host,
but on IPv6 whole subnet?
The argument that the source address can be changed is equally valid for
IPv4 and IPv6.
But in the case of IPv6, you're blocking the entire subnet with multiple
stations, even if only one address is problematic.
That's real issue I faced past days - my own script on my workstation
hit due to programming error AUP limits. As I use IPv6, whole /64 subnet
was blocked and not even colleagues in same subnet could use whois at
that time. This would'nt happen with IPv4.
This is even not good for promoting IPv6, treat IPv6 differently than
IPv4 and in a way (rules) that are actually worse for IPv6.
Please review this and treat both IPv4 and IPv6 in the same manner.
- Daniel
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
