LIR-PARTITIONED: The New "Status:" Attribute
Value FAQs
- What is "LIR-PARTITIONED"?
- When would the LIR-PARTITIONED "status:"
value be used?
- How is such an object created in the RIPE Whois Database?
- How can I protect an LIR-PARTITIONED object?
- Do I have to seek approval from the RIPE NCC
before entering an LIR-PARTITIONED object into the RIPE Whois Database?
- Can I request reverse delegation for an LIR-PARTITIONED
inetnum object?
- Can I use the LIR-PARTITIONED "status:"
value in an inet6num object?
What is "LIR-PARTITIONED"?
LIR-PARTITIONED is a new value which can now be put into the "status:"
attribute of an inetnum object. Prior to this new "status:"
value, inetnum objects could only have the "status:"
attribute "ASSIGNED PA" , ASSIGNED PI", "ALLOCATED
PA or "ALLOCATED PI".
This new value allows RIPE Whois Database users to identify an IP range from an
LIR allocation that has been delegated to a subsidiary of their organisation.
This range can then be assigned to a particular network at a later date.
The new value is strictly a RIPE Whois Database feature, allowing LIRs to delegate
maintenance within their allocations in the RIPE Whois Database. Overall responsibility
for the address space remains with the LIR.
When would the LIR-PARTITIONED "status:"
value be used?
Sometimes LIRs need to distribute part of their allocation to a particular
location and allow maintenance of that range by their subsidiary. The
new "status:" value allows the LIR to create a more specific
level object with the subsidiary's maintainer in it. By doing this, it
allows the subsidiary to administer the assigned inetnum
objects, without giving the subsidiary control over the whole LIR allocation.
It is not a sub-allocation.
How is such an object created in the RIPE
Whois Database?
In the same way as an assigned inetnum object is created,
except the "status:" value, LIR-PARTITIONED PA or LIR-PARTITIONED
PI is used instead of ASSIGNED PA or ASSIGNED PI.
How can I protect an LIR-PARTITIONED object?
Inetnum objects with the LIR-PARTITIONED "status:"
uses the same attributes as inetnums, thus they must
be protected by a valid maintainer, i.e. mnt-by. Hierarchical authority
for LIR-PARTITIONED address space can also be specified in the "mnt-lower"
and "mnt-routes" attributes.
As the LIR is responsible for all objects within its allocated range,
it is important they take appropriate steps to ensure they retain access
to the authorisation of maintainers used in the eventual creation of more
specific objects.
When creating a more-specific object (a route object
for example) the hierarchical structure of authorisation will apply to
the maintainer(s) of the LIR-PARTITIONED object before checking with the
maintainer(s) of the ALLOCATED object.
Do I have to seek approval from the RIPE
NCC before entering an LIR-PARTITIONED object into the RIPE Whois Database?
No, this is strictly a RIPE Whois Database feature and RIPE NCC will keep no record
of these LIR-PARTITIONED objects. Responsibility for errors and problems
arising from the use of LIR-PARTITIONED remains entirely with the LIR
concerned. In addition, LIR-PARTITIONED objects are disregarded when evaluating
requests for an additional allocation. Only ASSIGNED "status:"
objects are counted towards the 80% usage requirement.
Can I request reverse delegation for an
LIR-PARTITIONED inetnum object?
No, the RIPE NCC's reverse delegation check will not consider LIR-PARTITIONED
objects when evaluating a reverse delegation request. The criteria for
receiving reverse delegation for a zone remains the same as before and
can be viewed at http://www.ripe.net/reverse
Can I use the LIR-PARTITIONED "status:"
value in an inet6num object?
No, LIR-PARTITIONED status is only for IPv4 inetnum objects.
The status values for inet6num objects are:
"ALLOCATED-BY-RIR" - For allocations made
by an RIR to an LIR.
"ALLOCATED-BY-LIR" - For allocations made
by an LIR or an LIR's downstream customer to another downstream organisation.
"ASSIGNED" - For assignments made to End User
sites.
For more on this topic, please see:
http://www.ripe.net/ripe/docs/new-value-status.html
|
you are here: home -> Info, Stats and FAQs -> FAQs
