- anti-abuse-wg - mailman.ripe.net

Also seeking input [branching from 'WHOIS (AS204224)']
by Jeffrey Race 03 Nov '15

03 Nov '15

Dear group members, For many years I've silently followed these discussions and now a project is emerging on which I'd like to ask whether any of you knowledgeable members might wish to help. The project starts in a different place but will inform your deliberations. Background: Two years ago I began a research project at the Harvard Kennedy School on "Pathologies of Public- Decision-making," to answer the question: Why do very smart and well-informed persons make decisions with catastrophic consequences, even though warned in advance-- and what can be done to mitigate this pathological behavior? The findings will be based on a series of case studies including the Iraq War and 2007/08 financial crisis (building on my earlier work on the Vietnam War). It turns out that decision-making processes in all these cases share structural similiarities leading to the adverse outcomes. As for us on this group, the decision process leading to the present rules for internet messaging seems to have strong resemblances to the other cases You are all smart and we were adequately warned in advance and all the way along (as this thread illustrates, and over the years I've monitored many dozens of threads like this one). But the result has been catastrophic: most messages are spam, with a heavy economic cost in terms of cleanup and prevention costs and the burden of fraud. So I will include a case study on the spam/abuse phenomenon and why so many smart people (like those on this and related lists I monitor) have produced such adverse outcomes. I am planning to complete my book manuscript next year and hope to be writing up this part of the draft early in '16. I invite anyone interested in commenting (or even working with me in writing this chapter) to send me a note off-list. To understand my approach please see the "Pathologies" page linked on my website noted below. Best to invest 10 minutes in viewing the MP4 file. A quick summary appears in the linked PDF but if you are not read into this type of analysis the elaboration in the spoken version will help a lot. My thanks in advance to any of you who find this of interest and might be able to help make the final result something unusual. Jeffrey Race, President Cambridge Electronics Laboratories Co-organizer, "Buddhism Rejoins the Great Conversation in India" Pune, India, November 22-24, 2014 (Centre for Buddhist Studies University of Oxford) International Center of Excellence --- University of Yangon (2014) "Introduction to Economics and Political Economy" (under auspices of School of Advanced International Studies, The Johns Hopkins University, Washington DC) Ash Center Fellow Harvard University (2012-13) +1 617 629-2805 086 709-7645 (follows me worldwide) (in Thailand) Current projects and forthcoming publications: <http://www.jeffreyrace.com> ****** "The Vietnam War as an Early Warning" <http://www.jeffreyrace.com/document/race_oh.pdf> ****** "Pathologies of Public Decision-making" informal title: "How Not To Be An American Blunderer" <http://www.jeffreyrace.com/tenmin/bonfire.htm> (Presented at Harvard University on 5/26/2015) On Tue, 3 Nov 2015 14:37:10 +0000, Brian Nisbet wrote: >On 03/11/2015 14:14, Gert Doering wrote: >> Hi, >> >> On Tue, Nov 03, 2015 at 01:49:18PM +0000, Sascha Luck [ml] wrote: >>> On Tue, Nov 03, 2015 at 07:13:17PM +0530, Suresh Ramasubramanian wrote: >>>> I would actually prefer any such proposal to come from within >>>> the regular RIPE community, rather than from one of us >>>> outsiders. >>> >>> For once I agree completely. If this goes to an actual proposal, >>> this needs to be in APWG as it would be: >>> >>> a) address policy >>> b) affecting the entire community >>> >>> Any contractual changes will also need membership approval via GM >>> vote anyway. >> >> I'm not so sure about APWG. "Spending resources" is traditionally >> ncc-services-land, "combating abuse" is definitely anti-abuse-wg... so >> discussing the details here, and sending a heads-up over to APWG and >> ncc-services is good enough for me... > >We're getting deep into minutiae at this point, but this is actually >something I had planned to try and bring to the DB-WG and we'd see where >we went from there. That said, I simply haven't had the time over the >summer. > >Suresh, your point is noted, however I was asking more for people to >undertake to help, rather than to lead. > >Ok, I realise I have said this before, but given the proximity of RIPE71 >I will undertake, during that week, to iron out some of the important >minutiae and figure out if DB remains the best place for this and go >from there. > >I would still love if there were more people from this working group who >were willing and able to help with the drafting, of course, because that >would help the whole thing along (and not let me get utterly distracted >by my day job). > >Of course if it is decided that AA-WG is the right place for such a >proposal, I would have to re-evaluate my involvement, but we've >mechanisms in place to deal with that. > >Thanks, > >Brian >

1 0

lart I: we can perfectly spend some time together...
by alessandro maffei 03 Nov '15

03 Nov '15

NETWORK14 (PS) ABUSE TEAM bcc: RIPE Anti Abuse and MSN buseTeam Dear Mr. Muwaffaq Abu-Ghazaleh of Network14, Please, check this abuse (sex unsolited) seems comng from your network, as shown in the header below, and take the following actions: 1) trace the route to spammer and take acton 2) in case report results to RIPE Anti Abuse team and MSN Abuse team Thank you HEADER: Received: from DB4PR08MB0048.eurprd08.prod.outlook.com (10.161.16.22) by DB4PR08MB0048.eurprd08.prod.outlook.com (10.161.16.22) with Microsoft SMTP Server (TLS) id 15.1.312.18 via Mailbox Transport; Tue, 3 Nov 2015 15:23:00 +0000 Received: from AM3PR08CA0069.eurprd08.prod.outlook.com (10.163.23.165) by DB4PR08MB0048.eurprd08.prod.outlook.com (10.161.16.22) with Microsoft SMTP Server (TLS) id 15.1.312.18; Tue, 3 Nov 2015 15:23:00 +0000 Received: from DB5EUR01FT019.eop-EUR01.prod.protection.outlook.com (2a01:111:f400:7e02::202) by AM3PR08CA0069.outlook.office365.com (2a01:111:e400:8854::37) with Microsoft SMTP Server (TLS) id 15.1.318.15 via Frontend Transport; Tue, 3 Nov 2015 15:23:00 +0000 Received: from COL004-MC3F24.hotmail.com (10.152.4.55) by DB5EUR01FT019.mail.protection.outlook.com (10.152.4.249) with Microsoft SMTP Server (TLS) id 15.1.318.9 via Frontend Transport; Tue, 3 Nov 2015 15:22:58 +0000 Received: from icloud.com ([185.86.143.90]) by COL004-MC3F24.hotmail.com with Microsoft SMTPSVC(7.5.7601.23143); Tue, 3 Nov 2015 07:22:57 -0800 X-Originating-Email: [beyjlo(a)icloud.com] X-Sender: Milf Selfies(a)icloud.com From: Hot MILFs <beyjlo(a)icloud.com> To: <cousineddie_ks(a)hotmail.com>, <cude1971(a)hotmail.com>, <dancrook01(a)hotmail.com> Subject: we can perfectly spend some time together... Date: Tue, 3 Nov 2015 16:22:41 +0000 Content-Type: text/plain; format=flowed Message-ID: <ACYXJLKLYRPQHMUADUTOTVX(a)icloud.com> Return-Path: beyjlo(a)icloud.com X-OriginalArrivalTime: 03 Nov 2015 15:22:57.0527 (UTC) FILETIME=[84B50870:01D1164B] X-MS-Exchange-Organization-Network-Message-Id: 3437c431-87c0-406e-9f36-08d2e462a879 X-EOPAttributedMessage: 0 X-MS-Exchange-Organization-MessageDirectionality: Incoming CMM-sender-ip: 185.86.143.90 CMM-sending-ip: 185.86.143.90 CMM-Authentication-Results: hotmail.com; spf=softfail (sender IP is 185.86.143.90; identity alignment result is pass and alignment mode is relaxed) smtp.mailfrom=beyjlo(a)icloud.com; dkim=none (identity alignment result is pass and alignment mode is relaxed) header.d=icloud.com; x-hmca=fail header.id=beyjlo(a)icloud.com CMM-X-SID-PRA: beyjlo(a)icloud.com CMM-X-AUTH-Result: FAIL CMM-X-SID-Result: FAIL CMM-X-Message-Status: n:n CMM-X-Message-Delivery: Vj0xLjE7dXM9MDtsPTA7YT0wO0Q9MjtHRD0yO1NDTD02 CMM-X-Message-Info: fp3V/SmXfVTjWJ53FrjpwD61zXXhYE3ohEYeVAKDCEX8NXD+rdZGTVEvoO6FE6Ap86f2Zw1GMcCTvR8TpQYAHX4UcAiSCDh1WG4UaN9S4GUklUCYJ4l6vR1Ui/3uZE0GPf2Fq8OTlt82gqCbS6bOjS90hQ3sHmmfQ/UvsVeV02v7XiYuyL0t2KolxAcv7u4UP6S94w4k5cs4oH4RZxk5vJ+lNUc6DVOGI1exjAzF57USw724qQBG3Q== X-MS-Exchange-Organization-PCL: 2 X-Forefront-Antispam-Report: CIP:25.152.4.55;CTRY:GB;IPV:NLI;EFV:NLI;SFV:SPM;SFS:(28900001);DIR:INB;SFP:;SCL:5;SRVR:DB4PR08MB0048;H:COL004-MC3F24.hotmail.com;FPR:;SPF:None;LANG:en; X-Microsoft-Exchange-Diagnostics: 1;DB4PR08MB0048;2:+MFPkFWOn84PUNwIiIxeRc3dtMiJ82k5zpT6ksBqOdynRayc+2GQyZ7E6Q1dEctYgR/WEqksQwT438OU55mfyQdLdwrDJHrsyx6zy4y3CGoXMRkfGVKYRJU9c10mBanEcKQRNF+SnpjUsdAw/0ULmzQg4NlxGnpowTmcmSi/oHK00GfwbLrw7tSH+oeh1Ohm;3:PSGVDaJ5Y7CkeKE68fNyIsKPcnCuzyrUCIsi1uDZXukPKivVv8dIo6sOJkEVJODSTdKvD1zjfc2gZOmjqbH6ZnGt/apVDEbDnuAkwm20krEt8/+NGpzZm8+lzO3fNxHcRmOSuUpnE3wUHIbkchSukXh6DnJn9wodE1KInzq9BRg9lHYJxhlffGQ2z4m+m5riGYaN8Y4Zfwff5aJk4mDVyg==;25:u6g5oN5i99Zp6IL1BWF/zFNryvGoqFNG9gBYl7pf9Bxj5Sz18zoABqYqmhqhhzBnzp0Cb6N6lTXqgOgirBJX1raCZpjjvlQyoq8XOp/ihep4B4llgxxCz8e5KebIn1OZSxpOS/8QoH0VkVHb6/AFaIAVj2Wm2f9qv194wWCQIulLkB/LsWf0nO0ywi4KXrnNeddLqJHoUJ3ykBcfpLvMn0QDd6gQPxW2T9wilAkNAOHn/I4jFiK4KDbQnotkFF+y+Npz84KwSOlt2I6Dxb7DCA== X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(8291501001);SRVR:DB4PR08MB0048; X-MS-Exchange-Organization-AVStamp-Service: 1.0 X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(81415001)(82015046);SRVR:DB4PR08MB0048;BCL:0;PCL:0;RULEID:;SRVR:DB4PR08MB0048; X-Microsoft-Exchange-Diagnostics: 1;DB4PR08MB0048;4:hMSI+UjXvjjuG/C4URCA+ROikcOvgihwDEVW5czyaY7nhJIx14VoFI3PeUyetWjPyM+BEvtvxMQzJpN360+kSG9hZfrSSMIydUELDLHlDcSrmgWpoKD8fwYcSN3BPevDqfZV2bd+JrQQG9CU3wnBvjq6P7nv7vC9PVGGQV5PPVRnQg+fDIQCPWpCK2MnNtpA9d9qjicDHMgSQUV6OM9lFrKlLs8kCIp/M73JHd00K234kSdvlPmmFrDZ5yK+AIygHxxpBY2tSYLsbYDmbhWmA3+FzW4HhjgkywtluT2Wdmk=;23:ErObBPQAPy+/6/AhWuJlmcIcspBwEWqmovdfeq9n+WEsH7Awar4MwG/zRuT0sHnoNSHEFRDSM6ueCsua9sWyCcSeEFeLkmrjxTGP34wbk5j1fqx1LSYFGPOPTTqpzDSBm1QOvZqHm9XHa6lnOEbigVK45ZnZ8cpyrGwehsOKhGxX5wn+s/AF5U/Rw7LcaT+n;5:ONT3qFeM1/m/mkBH2XBvoxgaatTeN1phfiWBtlnVL73bFGG6r2xBFAJ5joDPUkAJLP8+6dzbRHB6MrCJdDF7S4+2x6lv5AtLcBxaZuCvtWNCVaqvJ2iOdMkrBBPiqv4PnXdLk6TO/FLdeKRbCSgWdA==;24:vbW3o9MJxI2ng/Bg+INOH2Vtlje12pXBZa1BzVjMKjxNbqcBkuEYx4ecO/38aWu/ob9aAZjAQcV5+g4l/6AkEA==;20:pXuNx3FbZPIBF5Guw+rowjO63EoVrGKG40luyVHccg2g2FbWIJSbW1DAlGprCL3xg0vZ4kMldGRt7nJiJot0Rw== X-MS-Exchange-Organization-SCL: 5 SpamDiagnosticOutput: 1:22 SpamDiagnosticMetadata: 00000000%2D0000%2D0000%2D0000%2D000000000000 X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Nov 2015 15:22:58.5725 (UTC) X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR08MB0048 X-MS-Exchange-Organization-AuthSource: DB5EUR01FT019.eop-EUR01.prod.protection.outlook.com X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Transport-EndToEndLatency: 00:00:02.3709977 MIME-Version: 1.0 NO ABUSE Found (Blocked) fake (IP 185.86.143.90 NO rNS configured) identified as icloud.com Abuse contact info: abuse.ripe(a)superlink.ps RIPE Anti-Abuse anti-abuse-wg(a)ripe.net inetnum: 185.86.142.0 - 185.86.143.255 netname: NETWORK14 descr: SuperLink ADSL Service 14 country: PS admin-c: MA9774-RIPE tech-c: MA9774-RIPE status: ASSIGNED PA mnt-by: MNT-SUPERLINK created: 2015-02-03T12:51:53Z last-modified: 2015-02-03T12:51:53Z source: RIPE # Filtered Update Delete person: Muwaffaq Abu-Ghazaleh address: Nablus phone: + 970 9 2377740 nic-hdl: MA9774-RIPE mnt-by: MNT-SUPERLINK created: 2010-09-29T12:52:07Z last-modified: 2010-10-03T09:16:58Z source: RIPE # Filtered Update Delete RIPEstat route: 185.86.142.0/23 descr: R132 origin: AS51737 mnt-by: MNT-SUPERLINK created: 2015-02-03T12:59:42Z last-modified: 2015-02-03T12:59:42Z source: RIPE # Filtered ________________________________________ Da: Hot MILFs <beyjlo(a)icloud.com> Inviato: martedì 3 novembre 2015 17.22 A: cousineddie_ks(a)hotmail.com; cude1971(a)hotmail.com; dancrook01(a)hotmail.com Oggetto: we can perfectly spend some time together... Could you do us a really big favor and take a minute to say hi to some of = our lonely, but very pretty, ladies? These ladies are very friendly, and just want to talk to a nice man today. They are all married, but super attractive MILFs that want to cheat. And they want to meet a man that they can have an affair with this week. They are not looking for a boyfriend, just a man that they can sleep with. Just say hello to a few of these lonely wives: http://t.cn/RUzO4tT These women are so amazing and so much fun. You will love meeting them. Their husbands take them for granted. But these ladies will not take you = for granted! We really appreciate you taking time out of your day to say hi to these = wonderful ladies! http://t.cn/RUzO4tY ------------- If you would like to not be contacted from us again please visit the page = below: http://t.cn/RUzCWJl

1 0

Re: [anti-abuse-wg] Verifiability (was: WHOIS (AS204224))
by Aftab Siddiqui 03 Nov '15

03 Nov '15

Hi Jeffrey, On Tue, 3 Nov 2015 at 13:21 Jeffrey Race <jrace(a)attglobal.net> wrote: > This is trivially and virtually costlessly done in an automated way, > taking about a day of a good programmer's time. Thereafter > zero/minimal maintenance except for 'exception' followups. > > One informs registrants that CONTINUOUSLY working > contact modes (e-mail, fax, phone, postal, say at least three of four) > are mandatory to avoid suspension/rescission. > > Then one automates a routine to transmit tokenized letters/faxes/ > calls/e-mails on a periodic but random basis, with the covering > message stating that the token must be returned on a website > within x days according to the terms of registration. If sufficient > tokens to not appear, suspension occurs automatically, just as if > you don't pay your credit card bill or pay your phone bill. > > This is easy stuff. > Yes it is easy.. but not scalable, exception rate would be very high.. multiply that with 7000+ (members) -- Best Wishes, Aftab A. Siddiqui

5 7

Re: [anti-abuse-wg] Verifiability (was: WHOIS (AS204224))
by Ronald F. Guilmette 03 Nov '15

03 Nov '15

Jeffrey Race <jrace(a)post.harvard.edu> wrote: >This is easy stuff. I agree that it isn't at all hard, thank you for supporting the point I was attempting to make, anmd complement you for the clever addition of the "continuously working" requirement, and the idea of automated, time-randomized spot checking. Ingeneous! Regards, rfg

1 0

ICANN's "Money Grab"
by Ronald F. Guilmette 31 Oct '15

31 Oct '15

Yet more evidence that ICANN is simply serving their masters, the registrars, while shafting the rest of us: http://www.theregister.co.uk/2015/10/27/verisign_warns_new_gtlds_could_dest… Taken together, the new gTLD program, and ICANN's lame and half-hearted "negotiation" of a new (2013) Registrar Accreditation Agreement... an agreement which fully supports business-as-usual, i.e. -ZERO- requirements for registrars to perform any meaningful validation of WHOIS information, ever... should make it clear to anybody who has any lingering doubts that the unregulated monopoly known as ICANN is basically an organization that... if it did not have a lot of powerful friends... would probably be investigated (in the U.S. at least) under the Racketeer Influenced and Corrupt Organizations (RICO) statute. What has this all got to do with network "abuse"? Simple. ICANN has bent itself to the will of its real constituents (the registrars) and made sure that none of them will ever be contractually obligated to ever do anything other than send an e-mail to the contact e-mail address in a disputed domain WHOIS record... e.g. <Mr.Phony.Baloney(a)hotmail.com>... and then get an affirmative reply back. The registrars are NEVER even required to find fault with even the most ridiculously bogus physical address information (e.g. "123 Planetary Way, Mars, Milky Way, 999999") nor are they ever contractually required to take any action at all if one of their registered domain names has a contact phone number of +9.999999999. Don't believe me? Look it up. It's in the contract (2013 RAA)... plain as day. Why is there so much crime, phishing, hacking, and spamming on the net? Well, you can't catch the criminals and the spammers if you can't find them. And ICANN... or rather the registrars who make ICANN policy on these things... have made sure that NOBODY will ever be able to find any spammer or criminal who doesn't want to be found. OF COURSE they will all swear up and down that they have done this for the benefit of, or at the request of "privacy advocates". It's just a complete coincidence that it also helps them to line their own pockets. And if you believe that, then I have a bridge that I'd like to have you take a look at. Regards, rfg

2 4

spamcop Email sent to spam by Google
by Lu Heng 31 Oct '15

31 Oct '15

Hi As a small business, some part of our business uses google app. Accidentally I discover there are dozens of spamcop mail about our IP address for past week laying in the spam mail box, and my abuse team in the company seems knowing little about this spammer are abusing our service, then with future investigation, I found google actually send spamcop mail to spam folder in which causes the problem. Now we kicked out the customer and this message just a little reminder to my fellow colleagues who are also using google app and do want to receive abuse report in their abuse mailbox, please whitelist spamcop(or any other similar service) in your list to have best delivery. Better practice in this issue--if anyone has idea, would be very welcome(because I fear spamcop is not the only one get sent to spam box). -- -- Kind regards. Lu

1 0

AS200439 (LLC Stadis) hijacking IP space
by furio ercolessi 30 Oct '15

30 Oct '15

Just in case someone is not aware of this and is interested, AS200439 is actively engaged in announcing unallocated APNIC IP ranges and using them to pump out spam. Excerpt from http://bgp.he.net/AS200439#_bogons : Bogon Prefixes # Prefix Type 1 103.9.132.0/22 unallocated 2 103.10.44.0/22 unallocated 3 103.10.172.0/22 unallocated 4 103.10.236.0/22 unallocated 5 103.11.0.0/22 unallocated 6 103.20.68.0/22 unallocated 7 103.21.8.0/22 unallocated 8 103.21.236.0/22 unallocated 9 103.22.140.0/22 unallocated 10 103.22.204.0/22 unallocated 11 103.22.244.0/22 unallocated 12 103.23.204.0/22 unallocated 13 103.25.120.0/22 unallocated 14 103.26.76.0/22 unallocated 15 160.19.228.0/22 unallocated 16 160.20.16.0/22 unallocated 17 160.20.36.0/22 unallocated 18 160.20.76.0/22 unallocated 19 160.20.104.0/22 unallocated 20 163.227.216.0/22 unallocated 21 203.148.88.0/22 unallocated 22 203.160.132.0/22 unallocated 23 203.176.124.0/22 unallocated 24 203.189.248.0/22 unallocated 25 203.189.252.0/22 unallocated 26 203.190.32.0/22 unallocated 27 203.212.28.0/22 unallocated 28 203.217.164.0/22 unallocated 29 220.247.132.0/22 unallocated 30 223.25.252.0/22 unallocated These gentlemen appear to be a relatively new LIR, less than 4 months old. Without doubt the activity is some terrible mistake caused by a young sysop that will be fired on the spot, but the possibility that their BGP equipment has been hacked or had a virus inside should obviously also considered. aut-num: AS200439 as-name: STADIS-LLC-AS descr: LLC Stadis org: ORG-LS213-RIPE sponsoring-org: ORG-TL122-RIPE import: from AS35297 accept ANY export: to AS35297 announce AS200439 import: from AS12695 accept ANY export: to AS12695 announce AS200439 admin-c: SO3128-RIPE import: from AS58271 accept ANY export: to AS58271 announce AS200439 tech-c: SO3128-RIPE remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: STADIS-MNT mnt-routes: STADIS-MNT created: 2015-07-03T08:34:46Z last-modified: 2015-07-20T17:23:57Z source: RIPE # Filtered organisation: ORG-LS213-RIPE org-name: LLC Stadis org-type: OTHER address: Russia, Ekaterinburg, str. A.Valeka 13, office 401 mnt-ref: STADIS-MNT mnt-by: STADIS-MNT created: 2015-07-01T11:18:09Z last-modified: 2015-07-01T11:18:09Z source: RIPE # Filtered furio

5 6

Timing Change AA-WG @ RIPE71
by Brian Nisbet 23 Oct '15

23 Oct '15

Colleagues, While there is no update to the draft agenda, there is a change to when the AA-WG session will be taking place. It will now be on at 11:00 EET (GMT +2) on Thursday 19th November. You will be able to follow the session live and participate remotely. This will all be available via ripe71.ripe.net Brian -- Brian Nisbet, Network Operations Manager HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin 1 Registered in Ireland, no 275301 tel: +35316609040 fax: +35316603666 web: http://www.heanet.ie/

1 0

RIPE 71 Agenda -Second Draft
by Brian Nisbet 19 Oct '15

19 Oct '15

Colleagues, Here is the second draft of the RIPE 71 Anti-Abuse WG session. The session will take place at 14:00 EET (GMT +2) on Thursday 19th November. The session will be live streamed and recorded, along with live stenography. A. Administrative Matters - 5' * Welcome * Scribe, Jabber, Stenography * Microphone Etiquette * Approve Minutes from RIPE 70 * Finalise agenda B. Update - 15' * B1. Recent List Discussion * B2. AA-WG Chair Matters C. Policies - 0' D. Interactions - 20' * D1. Working Groups * D2. RIPE NCC Gov/LEA Interactions Update E. Presentation - 45' * E1. Open Source Abuse Management for Network Operators - Abuse.io * E2. Helping Network Operators to Bring Down DDos Sources - ANSSI X. A.O.B. Z. Agenda for RIPE 72 There is still a very small amount of room on the agenda if anyone has any subjects they wish to bring to the working group. Brian -- Brian Nisbet, Network Operations Manager HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin 1 Registered in Ireland, no 275301 tel: +35316609040 fax: +35316603666 web: http://www.heanet.ie/

1 0

Re: [anti-abuse-wg] anti-abuse-wg Digest, Vol 48, Issue 18
by Marilson 18 Oct '15

18 Oct '15

Hi, Unfortunately Nainsel and according to some members of this group, including the Co-Chair, you should not send to us "spamming single specific incident." We should deal only with "larger issue". Nevertheless, I must inform you that all the larger issues I brought were transformed into spamming single specific incident and were not discussed. Faced with such inconsistency I would not know how to guide you. Unless better guidance, with my regards Marilson -----Mensagem Original----- From: anti-abuse-wg-request(a)ripe.net Sent: Sunday, October 18, 2015 8:00 AM To: anti-abuse-wg(a)ripe.net Subject: anti-abuse-wg Digest, Vol 48, Issue 18 Send anti-abuse-wg mailing list submissions to anti-abuse-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/anti-abuse-wg or, via email, send a message with subject or body 'help' to anti-abuse-wg-request(a)ripe.net You can reach the person managing the list at anti-abuse-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of anti-abuse-wg digest..." Today's Topics: 1. Re: Lottery Master (nainsel705(a)btinternet.com) ---------------------------------------------------------------------- Message: 1 Date: Sat, 17 Oct 2015 17:20:39 +0100 From: <nainsel705(a)btinternet.com> To: <anti-abuse-wg(a)ripe.net> Subject: Re: [anti-abuse-wg] Lottery Master Message-ID: <AAB6345CED83448C94AC3239275AFF91@DESKTOPRAHO0D9> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original I keep adding Lottery Master to the blocked sender list but the emails keep arriving. Has anybody else encountered this problem? Nainsel. -----Original Message----- From: anti-abuse-wg-request(a)ripe.net Sent: Monday, October 12, 2015 11:00 AM To: anti-abuse-wg(a)ripe.net Subject: anti-abuse-wg Digest, Vol 48, Issue 16 Send anti-abuse-wg mailing list submissions to anti-abuse-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/anti-abuse-wg or, via email, send a message with subject or body 'help' to anti-abuse-wg-request(a)ripe.net You can reach the person managing the list at anti-abuse-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of anti-abuse-wg digest..." Today's Topics: 1. Re: anti-abuse-wg Digest, Vol 48, Issue 10 (Brian Nisbet) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Oct 2015 10:38:54 +0100 From: Brian Nisbet <brian.nisbet(a)heanet.ie> To: anti-abuse-wg(a)ripe.net Subject: Re: [anti-abuse-wg] anti-abuse-wg Digest, Vol 48, Issue 10 Message-ID: <561B7FAE.4090704(a)heanet.ie> Content-Type: text/plain; charset=windows-1252; format=flowed Gentlemen, Thank you for the nomination and the answer. So noted. Brian Co-Chair, RIPE AA-WG On 09/10/2015 21:49, Ronald F. Guilmette wrote: > In message <55BB79F4004C439393E855B0BC8065F6@SuperPC>, > "Marilson" <marilson.mapa(a)gmail.com> wrote: > >> I would like to nominate a person for the second chair: meu amigo Ronald >> F. >> Guilmette (friend for one more day). > > While I appreciate this unexpected (and largely unearned) vote of > confidence, unfortunately I find it necessary to quote a man whose > actual accomplishments actually did warrant his consideration for > high office: > > "If nominated I will not run; if elected I will not serve." > -- William Tecumseh Sherman > > (I might actually be tempted to volunteer for the position is question, > but given that I am not physically present anywhere within the RIPE > geographical region, I feel sure that even if relevant bylaws permitted > it, I would be committing a serious disservice to the entire WG if I > were to make any pretense of fulfilling the role in question, e.g. by > merely "phoning it in", so to speak.) > > > Regards, > rfg > > > P.S. Thanks largely to absoluely everybody on this mailing list, I was > compelled to do the research and to find my own answers to the two key > questions that I posted here the other day. The clear implications of > what I found (in the ICANN 2013 RAA) are, I would say, worse than > disturbing, > about which I will have more to say later on. > > What I found does raise one other question however... which I will post > here now in the complete expectation of the exact same level of helpful > responsiveness which you all accorded to my last two questions: > > When the exact wording of the 21013 RAA was being negotiated... by > ICANN, sitting across the table from such other "stakeholders" as the > Registrars Committee... who exactly was the lead negotiator for ICANN's > side of the table? > End of anti-abuse-wg Digest, Vol 48, Issue 16 ********************************************* End of anti-abuse-wg Digest, Vol 48, Issue 18 *********************************************

1 0