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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
- Previous message (by thread): [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
- Next message (by thread): [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Mon Aug 8 11:38:37 CEST 2011
On Mon, Aug 8, 2011 at 2:56 PM, Alessandro Vesely <vesely at tana.it> wrote: > On 08.08.2011 10:03, Suresh Ramasubramanian wrote: >> While the abuse contact wg would be good to develop a standard format >> for noting an abuse contact in RIPE whois, it is hardly the place to >> deal with netblocks registered with fake contact information, and >> quite possibly registered with faked justification paperwork. > > I'd hope some practical hints proposition to define a workable acceptation of > the term "faked" is also on-topic. http://en.wikipedia.org/wiki/I_know_it_when_I_see_it HTH HAND :) Please also apply the concept of mens rea. Is this behavior associated with, say, hosting botnets and snowshoe spam, when the paperworks ays "GRE tunnels", or "dialup pool", just for example?
- Previous message (by thread): [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
- Next message (by thread): [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]