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] New "status" tag of REVOKED requested
- Previous message (by thread): [db-wg] New "status" tag of REVOKED requested
- Next message (by thread): [db-wg] X-NCC-RegID : cm.intelcam deleting objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aleksi Suhonen
ripe-ml-2003 at ssd.axu.tm
Wed Jun 25 01:47:23 CEST 2003
Hello, Quote from Hank Nussbacher: } >I think 90-120 days is too little before removing the inetnum object. I } >also think that a better a tactic would be to add a "remarks" to the } >inetnum or perhaps create a new "status" tag such as REVOKED. I also think } >such a policy should be uniform between RIRs. } >Comments? Status: REVOKED sounds like the most sensible thing to do. I don't believe in lengthening the period before reallocation, but some sort of a more proactive revocation procedure might get the address space back into production faster and the new status value could be part of that. -- Aleksi Suhonen / Axu TM Oy Internetworking Consulting
- Previous message (by thread): [db-wg] New "status" tag of REVOKED requested
- Next message (by thread): [db-wg] X-NCC-RegID : cm.intelcam deleting objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]