<html><head></head><body>It's been pointed out to me (thanks Leo!), that the WG is called Anti-Spam below. This is a mistake, to clarify, we're still very much the Anti-Abuse WG. Brian <div class="gmail_quote">On 3 June 2014 17:12:49 GMT+01:00, Brian Nisbet <brian.nisbet@heanet.ie> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class="k9mail">Colleagues, Having taken on board a number of points, here is another draft of this. I think we've got the kinks knocked out, so to speak, or at least reached a point where rough consensus may be manageable. I'm going to set a deadline of 15:00 UTC +1 on Friday 6th June to end this round of discussions. Obviously if something needs to be discussed beyond that, it can, but we've been talking about this for a couple of weeks now. Importantly while I'd like some statements of support, silence, at this point, will be taken to indicate consent. Please see the draft below, Brian ********************************** As the Internet has evolved, so has the scope and scale of network abuse. Unsolicited bulk email (spam) is often merely a symptom of deeper abuse such as viruses or botnets. Consequently the Anti-Spam Working Group has a wide scope, to include all relevant kinds of abuse. The technical details of spam and other abuse constantly vary, in terms of application channel and technique. Channel examples include SMTP, SIP, XMPP and HTTP. Examples of techniques range from buffer overrun to social engineering. Within scope are all systems and mechanisms, both technical and non-technical, that are used to create, control, and make money from, such abuse. While areas such as hosting illegal content or copyright infringement are not seen as a central part of the working group's remit, they are unquestionably bound up in other aspects of network abuse and, as such, may be areas of interest. The working group considers both technical and non-technical aspects of abuse, with the following goals: Produce and continue to update a BCP (Best Common Practice) document for ISPs similar in nature to RIPE-409 but covering a wider range of possible abusive behaviours. Provide advice (beyond that of the BCP) to relevant parties within the RIPE region such as ISPs, Governments and Law Enforcement Agencies on strategic and operational matters. Discuss and disseminate information on technical and non-technical methods of preventing or reducing network abuse. </pre></blockquote></div> -- Brian Nisbet Network Operations Manager, HEAnet (Sent from a mobile device, apologies for brevity)</body></html>