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] Decision on NWI-4 INETNUM status values
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo at vegoda.org
Tue Apr 5 17:51:42 CEST 2022
On Mon, Apr 4, 2022 at 1:43 PM denis walker <ripedenis at gmail.com> wrote: [...] > > What am I missing? > > What you are missing is that many, many, many of these /24 allocations > are not being used by the resource holder';s organisation. They are > assigned to end users. Thanks for stating this clearly. I agree with everyone else that ensuring the published contact data are accurate is most important. Does that require a software solution? Could it be accomplished with a process change? For instance, if an LIR leases a block to a network operator and shares some kind of documentation with the RIPE NCC, could the RIPE NCC delegate control of the contact data to the network operator for the duration of the lease? Kind regards, Leo
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]