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 ]
Sascha Luck [ml]
aawg at c4inet.net
Fri Nov 6 02:15:23 CET 2015
On Thu, Nov 05, 2015 at 11:41:32PM +0100, denis wrote: >When it comes to getting an ASN the AUT-NUM does require reference to >a PERSON/ROLE object. But you can pick any PERSON or ROLE object in >the database and reference them. Technically there is no cross >checking. The 'owner' of those objects will not get notified. So >unless the RIPE NCC questions your choice of objects all the contact >data in those objects will be perfectly valid. They just have no >relationship with you. To be fair, there is some egregious rubbish in the db. I have a person: object I can't delete because it is: a) not maintained by my mntner b) referenced from an org: object for a company that I once worked for but that hasn't existed in 10 years. I don't even know why this org: is still in there as the company is not on the membership list anymore so nobody is paying any bills. This has nothing to do with vile criminality but I think it makes a point for a database cleanup effort. I doubt it is the only "dead body" that's in the db.
- 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 ]