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] usage of LIR-PARTITIONED status

Previous message (by thread): [db-wg] usage of LIR-PARTITIONED status

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Marco Schmidt mschmidt at ripe.net
Thu Dec 20 15:14:22 CET 2018

Hello Alex,

Allow me to provide some additional clarification.

As Gert has already correctly explained, the status LIR-PARTITIONED is used to partition allocations.

For inetnum objects with the status ALLOCATED PA, you can create more specific objects with the status LIR-PARTITIONED PA.
The same applies for PI. However there are no inetnums with the status ALLOCATED PI in the RIPE Database, and such ranges are no longer provided by the RIPE NCC.

Recently, consensus was reached on a policy change to remove the status ALLOCATED PI and LIR-PARTITIONED PI from the RIPE IPv4 Policy document.
https://www.ripe.net/participate/policies/proposals/2018-03  

Following this policy change, we will also remove this status from the RIPE Database code and documentation shortly.

I hope this clarifies things.

Kind regards,
Marco Schmidt
Policy Officer
RIPE NCC

Previous message (by thread): [db-wg] usage of LIR-PARTITIONED status

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]