RIR vs LIR: Allocation, Assignment and Responsibility
A RIR administers number resources across a region. A local internet registry (LIR) receives resources under that system and manages their use or distribution to customers. An LIR account, a sponsoring-LIR agreement and an address assignment give different rights and responsibilities.
Compare the roles
| Role | What it manages | Your relationship |
|---|---|---|
| RIR | Regional resource registration, policy implementation and registry services | Direct account or service agreement where eligible |
| NIR | National registry services in participating economies | National account and procedures where applicable |
| LIR | Allocations and downstream assignments under regional policy | You may operate the LIR or receive services from one |
| End user | Resources for its own network | Direct assignment, sponsored resources or provider-assigned space |
Terminology differs by region. In RIPE, an LIR is an account operated by a member; one legal organization can operate more than one. ARIN uses organization records and service agreements rather than the same LIR-account model. An APNIC NIR is not simply a commercial sponsor.
For service regions and registry authority, use the RIR overview.
Allocation and assignment are different
An allocation gives a registry or provider a block to manage under policy, including permitted downstream assignments. An assignment identifies space used for a particular end network. It does not automatically allow further distribution to unrelated customers.
RIPE example: the member/LIR manages a PA allocation and assigns space to a user. The PI assignment is registered to its independent holder; the dashed connection shows that holder’s administrative sponsorship through the LIR. These are registration relationships, not packet paths or a promise of available IPv4 supply.
View full diagram
| Situation | Record to inspect | Decision it supports |
|---|---|---|
| A provider offers space from its allocation | Parent block, downstream assignment and service contract | Whether the provider can supply the proposed service |
| An organization holds RIPE PI space | Assignment status, holder and sponsorship agreement | Whether the holder can keep the resource when changing provider |
| A network receives RIPE allocated PA space by transfer | Allocation and receiving member’s account | Whether direct membership is required |
| A customer receives an LOA | Issuer’s authority and underlying resource agreement | Whether announcement is authorized; an LOA does not change the registered holder |
Provider aggregatable (PA) and provider independent (PI) are resource statuses, not promises about global routing. In RIPE, sponsorship can support eligible PI resources and ASNs. It does not turn another organization’s PA allocation into your own allocation.
Direct account or sponsorship
Choose a direct account when the resource type requires it, you need to manage allocations yourself, or you can maintain the registry relationship. Follow the official membership procedure for RIPE membership.
For eligible independent resources, compare sponsorship using concrete responsibilities: who submits registry requests, who controls authentication, who pays renewals, and how the relationship moves to a replacement sponsor. Record the resource holder separately from the company providing administration.
For leased IPv4 space, the registered holder usually remains the lessor. The contract should establish the permitted use, announcement authority, abuse responsibilities and what happens when the lease ends. Leasing does not itself create LIR membership or transfer registration rights.
Verify control before relying on a label
Ask for the exact prefix, resource status, registered legal entity and the account through which changes are authorized. Then identify which party can request reverse DNS changes, manage resource certificates and submit a transfer.
Compare these responsibilities with the contract. A dashboard login or a company describing itself as a “LIR provider” does not answer who is registered for the block. Keep the distinction in your inventory and escalation contacts.