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/db-wg@ripe.net/
[db-wg] changes to the implementation of "abuse-c:"
- Previous message (by thread): [db-wg] changes to the implementation of "abuse-c:"
- Next message (by thread): [db-wg] changes to the implementation of "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Thu Jan 26 19:59:19 CET 2017
Hi, On Wed, Jan 25, 2017 at 02:11:49PM -0800, Randy Bush wrote: > > We understand the reasoning for wanting to use two different org > > objects. However, we cannot use different org object IDs for the same > > enduser in resources assigned by the RIPE NCC and have to be strict > > about it. > > seems to me that this strong identity binding is a feature, not a bug. So how do you register two different abuse contacts for different abuse departments in house responsible for different parts of a network block, if abuse-c is hard-tied to the org object, and you can have only one? Which nicely emphasizes the problem statement - it needs to be possible to define abuse contacts for more-specific inet(6)num: objects without introducing extra org objects... Gert Doering -- NetMaster -- 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: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: </ripe/mail/archives/db-wg/attachments/20170126/c6acc4b5/attachment.sig>
- Previous message (by thread): [db-wg] changes to the implementation of "abuse-c:"
- Next message (by thread): [db-wg] changes to the implementation of "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]