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] Automatic IP -> abuse email address mapping
- Previous message (by thread): [anti-abuse-wg] Automatic IP -> abuse email address mapping
- Next message (by thread): [anti-abuse-wg] Automatic IP -> abuse email address mapping
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frank Gadegast
ripe-anti-spam-wg at powerweb.de
Thu Jun 20 14:27:49 CEST 2013
Leo Vegoda wrote: > Hi Frank, Hi Leo, >> > Perhaps it would be useful to consider generalizing the > > > referral mechanism described in 2.11 of the RIPE Database > > > Query Reference Manual? >> >> The main problem is, that IANA should be responsible >> for that, but they will not create a technical service >> for the public. > > Can you please expand upon that? Well, I might be uninformed, but when asking iana's whois I simply get: # whois.ripe -h whois.iana.org 85.237.64.1 % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.ripe.net inetnum: 85.0.0.0 - 85.255.255.255 organisation: RIPE NCC status: ALLOCATED whois: whois.ripe.net changed: 2004-04 source: IANA So, it only tells me the reponsible RIR. Now I know its RIPE, then I have to ask RIPE (and when IANA tells me APNIC, I might have to ask APNIC first, wich tells me, its KRNIC ...) There might be more, when using options, but I would like a command like the following wich would return one single line # whois -h abuse.iana.org 85.237.64.1 abuse at powerweb.de So, there should be an interface between IANA and all RIRs to query abuse contacts, IANA knows at least, which RIR to ask. If IANA sees an IP from RIPE, its pretty easy, the whois could connect to whois.ripe.net make the -b and return a standarizes line. If its that simple with other RIRs, I dont really know, f.e. ARIN holds its abuse contacts still in about 4 different places. APNIC could be pretty easy, because of the IRT-object, others are really hard, because even IANA probably does not know, wich RIR delegated wich network to wich sub-RIR (like BRNIC). And the final interface should be presented under https://abuse.iana.org doing excactly the same, one sentence explaining what its for, one field to enter an IP, one button and following, one line as result. Simple, clean and easy to use for everyone. Then we would have ONE single place, where to look up published abuse contact email addresses. We could direct our end users to it, when they like to report abuse and we would have one single source for automatic reporting ... > ICANN currently provide a whois service (whois.iana.org) which provides > the same information as is found in the registries we publish. "Your" information, not the abuse contacts from all RIRs whois service, I guess (or does IANA mirrors all of them ?) ... > If there > is a strong demand for improvements to the service then please let us > know. Yes, please (strong demand, really strong demand, the most important demand ;o) Kind regards, Frank > > Kind regards, > > Leo Vegoda >
- Previous message (by thread): [anti-abuse-wg] Automatic IP -> abuse email address mapping
- Next message (by thread): [anti-abuse-wg] Automatic IP -> abuse email address mapping
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]