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] 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
Tue Apr 13 17:59:44 CEST 2004

On Apr 13, Niall O'Reilly <niall.oreilly at ucd.ie> wrote:

> Method B:
> Provide every inet[6]num with an appropriately configured IRT object:
This is not a good assumption because not all inet[6]num objects need
to be updated to be protected, only the parent object does.
Look at IRT-SIXXS and at how many objects it protects for a simple
example.

-- 
ciao, |
Marco | [5719 prCHm.K4ZTyVo]

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