On Thu, Apr 8, 2010 at 11:27 PM, Frank Gadegast <phade@www.powerweb.de> wrote:

>
> >
> > Not getting it.
>
> I apologise. Allow me to rephrase:
>
> Any organisation to which net space is allocated or assigned may own zero, one or several Internet domains. It may be difficult to know exactly what to type on the domain side of an abuse@ address. Your proposal avoids this issue. This is an advantage of your proposal as compared with RFC 2142.

No, because the system generates email addresses only related to the IP address
that causes the abuse.

The monitoring system at RIPE NCC than "translates" this IP like email addresses
to either the abuse address, that the member was putting into RIPEs system
or the main member address, the member has to setup, when becoming a
member.

RIPE NCC knows best how to "translate" the IP like abuse email address
to the members address, because RIPE NCC has best knowlegde about
the allocation all member ownes.

BTW: thats the main advantage of my draft ... nobody has to know
the actual abuse address for a IP range or has to look it up
via whois. Anybody that gets attacked knows the right address
just by sending his report to

1.2.3.4@abuse.ripe.net

when the IP 1.2.3.4 caused the abuse.

Kind regards, Frank

>
> --
> Thor Kottelin
> http://www.anta.net/
>
>
>