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: proposal
- Previous message (by thread): [db-wg] abuse-c: proposal
- Next message (by thread): [db-wg] abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
MarcoH
marcoh at marcoh.net
Thu Jan 29 15:16:54 CET 2004
On Thu, Jan 29, 2004 at 03:04:43PM +0100, Niall O'Reilly wrote: > >A default network lookup will return all these objects and we still > >have > >to trust (or teach) the person who is writing a reporting tool to pick > >the > >correct e-mail attribute and not something else carrying a space > >delimited > >string containing the '@' character. > > > > That's the 'Document and Publish' part. Perhaps 'Document, Publish and > Promote' > is a better way of putting it. That can be done on the exsting inet*num object also..in short: "look for irt object, if not present look at the remarks and if everything else fails, pick the e-mail: from the tech-c role. AND DON'T USE CHANGED ATTRIBUTES AND NOTIFY" For some reason Shane's proposal via jabber wasn't that bad: "surpress all data which is only usefulll for maintainers from the default output". MarcoH (sorry for shouting)
- Previous message (by thread): [db-wg] abuse-c: proposal
- Next message (by thread): [db-wg] abuse-c: proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]