Hi Adrian, Im not sure if you have seen my previous mail, but I suggested to add a field called "abuse-address" in the maintainer object and make a rule saying Ripe NCC MUST check that the email address is correct by sending a mail to it and not create the maintainer object until the mail has been responded. MNT-BY is mandatory on inetnum objects so once all maintainer objects have this field added all inetnum objects will be refering to a correct abuse address without having each LIR to go through all inetnums. The problem with person object is that the email field is optional, so I don't see it as an option to refer to this object in abuse matters. Med venlig hilsen/Best regards Christian Rasmussen Hosting manager, jay.net a/s Smedeland 32, 2600 Glostrup, Denmark Email: noc@jay.net Personal email: chr@corp.jay.net Tlf./Phone: +45 3336 6300, Fax: +45 3336 6301 Produkter / Products: http://hosting.jay.net
-----Original Message----- From: db-wg-admin@ripe.net [mailto:db-wg-admin@ripe.net]On Behalf Of Rev Adrian Kennard Sent: 12. januar 2004 13:37 To: db-wg@ripe.net Subject: [db-wg] abuse-c
Following up my own mail...
Also, the "trouble" field is a good thought - maybe we should add "trouble" to inetnum, as there is already a field name defined for the purpose essentially. Just an idea.
"trouble" is not really the answer as it is freeform. It needs to be a syntax checked email address. abuse-c to a person/role object seems sensible.
-- Rev Adrian Kennard Andrews & Arnold Ltd / AAISP www.aaisp.net.uk