Leo Vegoda wrote:
> Hi Denis,
>> On Apr 16, 2012, at 2:32 pm, Denis Walker wrote:
>>> I am not aware of any formal big picture, but I follow the mailing list
>> as closely as I am sure you and many others do. As you will know many of
>> these issues invoke much discussion on the list.
>> I think we only get one opportunity to do this right. Doing it without a strategy that's been agreed by the whole community seems quite scary.
>
Remembering the discussions on various lists and infos I got
from the NCC I would summarize the big picture like this
(but maybe Tobias or Brian could do this much better):
- introduction of the abuse-c
- outlining a time schedule when the abuse-c HAS to be there
(what would lead to an automatic cleanup of other fields
and removal of remarks by the maintainers)
- tools could be introduced for an easier migration
(e.g. a function in the LIR portal, that
could "remove all occurrences of my abuse-mailbox field
with the value foo at bar.com with the abuse-c FOO-RIPE",
another function could be "show me all my objects
that include an email address in the remarks")
- integration of the abuse finder tool into whois and other APIs
(what would make other places unneeded and unused)
- automatic technical validation (syntax, domain checks,
MX and A record checks, check of mailserver availability
either when the abuse-c is updated or repeating or both)
with automatic reminders being sent to the maintainer
- repeating validation via feedback links or similar
- maybe a kind of automatic deletion of other places or fields
Kind regards, Frank
> Regards,
>> Leo
>>>>
--
Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast mailto:frank at powerweb.de
Schinkelstrasse 17 fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921
======================================================================

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacypolicy. You can accept our cookies either by clicking here or by continuing to use the site.