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] abuse-c
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Abt
sabt at sabt.net
Mon Jan 12 17:37:36 CET 2004
Hi, * "Christian Rasmussen" <chr at jay.net> wrote: > Im not sure if you have seen my previous mail, but I suggested to add > a field called "abuse-address" in the maintainer object and make a > rule saying Ripe NCC MUST check that the email address is correct by > sending a mail to it and not create the maintainer object until the > mail has been responded. I don't think that this is useful, because I'd maybe like to set different abuse contacts for different inet[6]num objects, but want to be able to protect all those objects with one and the same maintainer object. Besides, I don't think that we really need to validate the existence of the email address supplied. I'd also like to see a mandatory/multiple abuse-c field containing a rfc-valid email address. regards, sebastian -- whois: sabt-ripe - phone: +49 (0)160 90759764 email: sabt at sabt.net - pgp-pubkey: 0xD008DA9C
- Previous message (by thread): [db-wg] abuse-c
- Next message (by thread): [db-wg] abuse-c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]