September 2013 - anti-abuse-wg

Automatic IP -> abuse email address mapping
by Olaf van der Spek 15 Dec '13

15 Dec '13

Hi, I hope this is the right list for such a question. How does one map an IP address to an abuse email address in an automated way? I assume scripts exist, but I haven't found any. Does everyone roll their own? -- Olaf

13 38

Yahoo Spamcop (spamcop@mailservices.yahoo.com)
by Reza Farzan 05 Sep '13

05 Sep '13

Hello All, Does anyone know what is going on at Yahoo, where Spammers can create e-mails without any impunity, and where all complaints submitted to Yahoo Spamcop (spamcop(a)mailservices.yahoo.com) all end up at Yahoo! Small Business [yahoosmb(a)cc.yahoo-inc.com]? Every Spam report that I send to Yahoo comes back with this automated response: * Thanks for contacting Yahoo!. Unfortunately, this address cannot accept direct reports of spam. If Yahoo Spamcop has become a meaningless source for complaining against Yahoo related Spammers, then where should one go to report such violations? As always, I welcome your comments and suggestions. Thank you, Reza Farzan rezaf(a)mindspring.com

2 1

Draft Agenda, RIPE 67
by Brian Nisbet 04 Sep '13

04 Sep '13

Colleagues, Here is the draft agenda for the WG session at RIPE 67. This will be happening at 14:00 EEST on Thursday 17th October. The agenda is shaping up nicely, but if you have any additional items you'd like to see on there, please let us know. A. Administrative Matters * Welcome * Scribe, Jabber, Stenography * Microphone Etiquette * Approve Minutes from RIPE 66 * Finalise agenda B. Update * B1. Recent List Discussion * B2. AA-WG Charter C. Policies * RIPE Policy 2011-06 Update, RIPE NCC * RIPE Policy Proposal 2013-01 D. Interactions * D1. Working Groups * D3. RIPE NCC Gov/LEA Interactions Update E. Presentation * E1. ACDC Project * E2. Internet Bad Neighborhoods - Giovane Moura * E2. x-arf - Tobias Knecht X. A.O.B. Z. Agenda for RIPE 68

1 0

New on RIPE Labs: All IP Addresses Are Not The Same (by Geoff Huston)
by Mirjam Kuehne 02 Sep '13

02 Sep '13

Dear colleagues, We published a new article by Geoff Huston on RIPE Labs that you might find interesting: All IP Addresses Are Not The Same https://labs.ripe.net/Members/gih/all-ip-addresses-are-not-the-same Kind regards, Mirjam Kuehne RIPE NCC

1 0

Clarification Regarding Needs Assessment and Audits
by Andrew de la Haye 02 Sep '13

02 Sep '13

Dear colleagues, We have been following the recent discussions on the mailing list and would like to offer clarification in relation to a couple of points that were raised. According to "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" [1], address space is distributed based on demonstrated technical need in order to deliver services. This need is evaluated according to addressing requirements, network infrastructure, equipment and number of customers. The exact services for which the resources are being requested are not considered as part of the evaluation process. As an example, if address space is requested for the technical need of a mail server, it is not verified what type of mails are being sent through that server. This practice is in line with the current IPv4 policy [1]. It is important to note that technical need is evaluated for assignments. The need for an additional allocation is considered based on past and future usage, taking into account all assignments that have been made by the LIR previously. The RIPE NCC does not have a mandate to deregister allocations if the expected growth was less or different than expected. Nevertheless, we do see LIRs voluntarily returning allocations in the event that they no longer have a need for the addresses. As above, this practice is based on current RIPE Policies. When a policy is changed through the RIPE Policy Development Process (PDP) [2], we adjust our processes accordingly. When the RIPE NCC conducts an audit of an LIR, it checks that: - RIPE Policies are followed correctly - Assignments are registered properly and being used for the purpose they were requested for (if not, the technical need is re-evaluated) - Contact information is still correct An LIR is either randomly selected for an audit, or selected following a community report against that member [3]. Last year, the RIPE NCC created a report form to facilitate and simplify reporting on policy violations, provision of untruthful information to the RIPE NCC and incorrect RIPE Database data [4]. Once the reported information and evidence is evaluated, the RIPE NCC investigates the claim and proceeds according to RIPE Policies and RIPE NCC procedures. This can result in address space being deregistered. More detailed information on reasons for deregistration of address space is available in "Closure of Member and Deregistration of Internet Number Resources" [5]. Kind regards Andrew de la Haye Chief Operations Officer RIPE NCC [1] "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" http://www.ripe.net/ripe/docs/v4policy [2] "RIPE Policy Development" http://www.ripe.net/ripe/policies [3] "RIPE NCC Audit Activity" http://www.ripe.net/ripe/docs/audit [4] "RIPE NCC Reporting Procedure" http://www.ripe.net/contact/ripe-ncc-complaints-procedure [5] "Closure of Member and Deregistration of Internet Number Resources" http://www.ripe.net/ripe/docs/closure

10 21