[ipv6-wg at ripe.net] Re: Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)

• Previous message (by thread): [ipv6-wg at ripe.net] Re: [db-wg] Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)
• Next message (by thread): [ipv6-wg at ripe.net] Re: [db-wg] Re: Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hroi Sigurdsson hroi at asdf.dk
Wed Aug 13 23:28:52 CEST 2003

Pim van Pelt wrote:

> If you'd like to limit the amount of queries an individual/company can
> do, you may want to use the database itself for some sort of 
> constraint.
>
> Let us say that a user from 2001:7b8:3:32:202:b3ff:fe2a:1e2d wants to
> look something up. You can check its most specific inet6num which would
> be NL-BIT1-PN1-POP3 and account queries per timeinterval per inet6num
> and limit that.

That seems a bit complicated. Why not just limit per /64 or /48?
Aside, how important is this for privacy anyway, given the fact that 
the whole
database is also available via FTP?

-- 
Hroi

• Previous message (by thread): [ipv6-wg at ripe.net] Re: [db-wg] Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)
• Next message (by thread): [ipv6-wg at ripe.net] Re: [db-wg] Re: Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]