This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Wed Jul 14 16:21:50 CEST 2010
Florian Weimer wrote: > * Tobias Knecht: > > >>> Wouldn't it be easier if RIPE created person/role object dumps, >>> containing only the nic-hdl and the abuse-mailbox field? IRT object >>> dumps would make a lot of sense, too. >>> >> I think RIPE shuts down the Bulk Data Service because of Privacy issues. >> So that might not be the right way. >> > > What? Even for the inetnum objects? Can you provide a pointer for > that, please? > > Just to clarify this point, the RIPE NCC has no plans to shut down bulk access to operational data. The only restrictions are regarding personal and security data. There will be no bulk access to PERSON, ROLE, ORGANISATION or MNTNER objects. In other objects types NIC Handle references will also be removed from the bulk access data. Regards Denis Walker Business Analyst RIPE NCC Database Group >> whois -h whois.ripe.net IRT-MCI-NL -b >> > > I would expect that query type to be subject to rate limits as well. > And when every network block needs an IRT object, some people will > likely script the creation of it, so you end up with less caching. > >
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]