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] [db-wg] abuse-c + org / inetnum
- Previous message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org / inetnum
- Next message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org / inetnum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Tue Oct 8 13:29:43 CEST 2013
Hi,
On Mon, Oct 07, 2013 at 11:00:28PM +0200, Gilles Massen wrote:
> Something else in mind: as before: allow abuse-c for inet*num. Prefer
This.
(But I've said this before :-) - I do not see it as a useful excercise
having to create an organization: object for the sole purpose of being
able to have a different abuse-c: for some inet(6)num object)
Gert Doering
-- inetnum maintainer
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: </ripe/mail/archives/anti-abuse-wg/attachments/20131008/30f74aa1/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org / inetnum
- Next message (by thread): [anti-abuse-wg] [db-wg] abuse-c + org / inetnum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]