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] 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
Sat Nov 7 03:40:58 CET 2015
As sascha says and for once I agree with him, It can be argued that the LIR is a mere intermediary in this transaction, and executing contracts with the end user while standing in for ripe ncc. Like, say, a VW car dealer - who sells you a Passat TDI diesel car and their name is on all the paperwork, and they are responsible for support such as fitting accessories, servicing and repairs. But if its ECU is tampered with to game emission testing, it is still VW on the hook and not the dealer. --srs > On 07-Nov-2015, at 4:14 AM, Sascha Luck [ml] <aawg at c4inet.net> wrote: > >> On Fri, Nov 06, 2015 at 11:38:52PM +0100, Sander Steffann wrote: >> >> But the RIPE NCC isn't an official party in that contract. The >> contract is between end user and LIR. > > Well... Considering that such a contract must be submitted to, > and approved by, the RIPE NCC (or it will not result in the > assignment of resources); I'm of the opinion that a court might > well see the NCC as a party. It has never been tested though (and > neither has the NCC data protection policy) and > my view doesn't seem to be shared by many... > > rgds, > Sascha Luck > >
- 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 ]