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/[email protected]/

[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 ]

Randy Bush randy at psg.com
Thu Jan 26 20:11:44 CET 2017

>> 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...

fine with that.  just do not want org being orgorgorgorg.  arin has made
a fun mess that way.

randy

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 ]