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] WHOIS (AS204224)
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Wed Nov 4 01:52:16 CET 2015
Thanks - I've hung around apricot and apnic long enough to know how that works (though these past few years I can't travel so I'm simply on the apricot / Sanog fellowship and program committees) I haven't ever attended a ripe meeting though and wasn't aware of this wg - in my circles (security) apwg is the anti phishing wg :) Beyond that - thank you for that detailed post --srs > On 04-Nov-2015, at 5:35 AM, <ripedenis at yahoo.co.uk> <ripedenis at yahoo.co.uk> wrote: > > Accepting the confusion on your definition of APWG, anything agreed by a RIPE working group is implemented by the RIPE NCC. The RIPE NCC may not agree with everything or may argue constructively for other options, but in the end once the community has reached consensus the RIPE NCC WILL implement the decision. The difficulty is sometimes getting the community to reach a
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]