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 ]
Alessandro Vesely
vesely at tana.it
Mon Aug 8 11:26:21 CEST 2011
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. > RIPE's existing policies *should* cover this - but there's a notable > lack of a formalized resolution process on the lines of wdprs for > domains. What is the current policy about the right to anonymity, for Whois Data Problem Reporting System? It is often said that e-commerce sites cannot be anonymous. It should be added that email sites also cannot. In fact, an email site may grant the right to anonymity to its users, but IMHO it needs not be anonymous itself for doing so properly.
- 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 ]