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] Action item 47.2: Proposal for Adding Abuse Contact
- Previous message (by thread): [db-wg] Action item 47.2: Proposal for Adding Abuse Contact
- Next message (by thread): [db-wg] Action item 47.2: Proposal for Adding Abuse Contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco d'Itri
md at Linux.IT
Thu Apr 8 11:23:30 CEST 2004
On Apr 08, Jeroen Massar <jeroen at unfix.org> wrote: > And what reasons are there to assume that the new proposal will > be deployed all of a sudden? I think it should be obvious that abuse-c and abuse-mailbox attributes are much harder to deploy, because they require modifying every bottom level inetnum/inetnum6 object (which may even be protected by the mntner object of the customer). I still think that the requirements for handling of abuse contacts have not been discussed enough. -- ciao, | Marco | [5613 diD/o8PEXAukY] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: </ripe/mail/archives/db-wg/attachments/20040408/01621315/attachment.sig>
- Previous message (by thread): [db-wg] Action item 47.2: Proposal for Adding Abuse Contact
- Next message (by thread): [db-wg] Action item 47.2: Proposal for Adding Abuse Contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]