Dear Michele This is a very reasonable question. One of the technical advantages of the "abuse-c:" proposal is that it references an object in which is stored contact information. Currently the discussion is focussing on an "abuse-mailbox:" attribute in that object as the primary contact method. As Tobias said, technically, we could easily add an additional "abuse-url:" attribute if required. Or anything else like "abuse-im:" or "abuse-mobile:". If we have the framework referencing a contact object then whatever the community wants inside that object is possible. You just decide what methods you want and what should be mandatory, required, optional, this or that, etc and the RIPE NCC can build it. From the point of view of the Abuse Finder tool the important step is to have one method of finding the abuse contact from an IP address. Once we can easily find it, you can have as much variation as you like in terms of contact methods. The Abuse Finder tool can just report to the user whatever options you have supplied. Regards Denis Walker Business Analyst RIPE NCC Database Group On 31/07/2012 15:01, "Michele Neylon :: Blacknight" wrote:
Dumb question, but does the abuse field have to be an email address?
Can it be a web address instead?
Regards
Michele
Mr Michele Neylon Blacknight Solutions ♞ Hosting & Colocation, Brand Protection ICANN Accredited Registrar http://www.blacknight.co http://blog.blacknight.com/ http://blacknight.cat http://mneylon.tel Intl. +353 (0) 59 9183072 US: 213-233-1612 Locall: 1850 929 929 Facebook: http://fb.me/blacknight Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845