Changes to
IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region

Legend

(+) Added

(-) Deleted

Changed

Tag Added

Tag Deleted

ripe-643: IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ripe-105: Procedures For DNS Delegation In The IN-ADDR.ARPA Domain

delete: <h2>Abstract delete: </h2>

This document describes the RIPE community's current IPv4 address allocation and assignment policies. They were developed through a bottom-up, consensus driven, open policy development process in the RIPE Address Policy Working Group (AP WG). The RIPE Network Coordination Centre (RIPE NCC) facilitates and supports this process. These policies apply to the RIPE NCC and the Local Internet Registries (LIRs) within the RIPE NCC service region. delete: </p>delete: <p>Information on the Address Policy WG Document is available at: in ASCII

delete: <p>delete: <a data-linktype="internal" target="_self" title="" href="resolveuid/6a73933dbb6a4d9655588d6896c4c379" data-val="6a73933dbb6a4d9655588d6896c4c379" class="internal-link">http://www.ripe.net/ripe/groups/wg/ap delete: </a>delete: </p>delete: <h2>Contents delete: </h2>delete: <p>1.0 delete: <a class="anchor-link" href="#1" target="_self" title="">Introduction delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">1.1 delete: <a class="anchor-link" href="#11" target="_self" title="">Scope delete: </a>delete: </p>delete: <p>2.0 delete: <a class="anchor-link" href="#2" target="_self" title="">IPv4 Address Space delete: </a>delete: </p>delete: <p>3.0 delete: <a class="anchor-link" href="#3" target="_self" title="">Goals of the Internet Registry System delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">3.1 delete: <a class="anchor-link" href="#31" target="_self" title="">Confidentiality delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">3.2 delete: <a class="anchor-link" href="#32" target="_self" title="">Language delete: </a>delete: </p>delete: <p>4.0 delete: <a class="anchor-link" href="#4" target="_self" title="">Registration Requirements delete: </a>delete: </p>delete: <p>5.0 delete: <a class="anchor-link" href="#5" target="_self" title="">Policies and Guidelines for Allocations delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">5.1 delete: <a class="anchor-link" href="#51" target="_self" title="">Allocations made by the RIPE NCC to LIRs delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">5.2 delete: <a class="anchor-link" href="#52" target="_self" title="">Unforeseen circumstances delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">5.3 delete: <a class="anchor-link" href="#53" target="_self" title="">Address Recycling delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">5.4 delete: <a class="anchor-link" href="#54" target="_self" title="">Sub-allocations delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">5.5 delete: <a class="anchor-link" href="#55" target="_self" title="">Transfers of Allocations delete: </a>delete: </p>delete: <p>6.0 delete: <a class="anchor-link" href="#6" target="_self" title="">Policies and Guidelines for Assignments delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">6.1 delete: <a class="anchor-link" href="#61" target="_self" title="">Assignments to Internet Exchange Points delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">6.2 delete: <a class="anchor-link" href="#62" target="_self" title="">Network Infrastructure and End User Networks delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">6.3 delete: <a class="anchor-link" href="#63" target="_self" title="">Validity of an Assignment delete: </a>delete: </p>delete: <p style="padding-left: 30px; ">6.4 delete: <a class="anchor-link" href="#64" target="_self" title="">Transfers of PI space delete: </a>delete: </p>delete: <p>7.0 delete: <a class="anchor-link" href="#7" target="_self" title="">Types of Address Space delete: </a>delete: </p>delete: <p>8.0 delete: <a class="anchor-link" href="#8" target="_self" title="">LIR Audit delete: </a>delete: </p>delete: <p>9.0 delete: <a class="anchor-link" href="#9" target="_self" title="">Closing an LIR by the RIPE NCC delete: </a>delete: </p>delete: <h2>delete: <a name="1">delete: </a>1.0 Introduction delete: </h2>delete: <p>The RIPE NCC is an independent association and serves as one of five Regional Internet Registries (RIRs). Its service region incorporates Europe, the Middle East, and Central Asia. The RIPE NCC is responsible for the allocation and assignment of Internet Protocol (IP) address space, Autonomous System Numbers (ASNs) and the management of reverse domain names within this region. The distribution of IP space follows the hierarchical scheme described in the document " delete: <a data-linktype="internal" target="_self" title="" href="resolveuid/24c9d290050ce09f71440263ed95a927" data-val="24c9d290050ce09f71440263ed95a927" class="internal-link">Internet Registry System delete: </a>". delete: </p>delete: <h3 class="western">delete: <a name="11">delete: </a>1.1 Scope delete: </h3>delete: <p>This document describes the policies for the responsible management of globally unique IPv4 Internet address space in the RIPE NCC service region. The policies documented here apply to all IPv4 address space allocated and assigned by the RIPE NCC. These policies must be implemented by all RIPE NCC member LIRs. delete: </p>delete: <p>This document does not describe policies related to AS Numbers, IPv6, Multicast, or private address space. Nor does it describe address distribution policies used by other RIRs. The RIPE community's policies for ASN assignment and IPv6 are published in the RIPE Document Store at: delete: <br />delete: <a href="http://www.ripe.net/ripe/docs/policy">http://www.ripe.net/ripe/docs/policy delete: </a>delete: </p>delete: <h2>delete: <a name="2">delete: </a>2.0 IPv4 Address Space delete: </h2>delete: <p>For the purposes of this document, IP addresses are 32-bit binary numbers used as addresses in the IPv4 protocol. There are three main types of IPv4 addresses: delete: </p>delete: <ol>delete: <li>delete: <p>Public IP addresses are distributed to be globally unique according to the goals described in Section 3 of this document. The two types of IPv4 address described in this documents are Provider Aggregatable (PA) and Provider Independent (PI). delete: </p>delete: </li>delete: <li>delete: <p>Some address ranges are set aside for the operation of private IP networks. Anyone may use these addresses in their private networks without registration or co-ordination. Hosts using these addresses cannot directly be reached from the Internet. Such connectivity is enabled by using the technique known as Network Address Translation (NAT). Private addresses restrict a network so that its hosts only have partial Internet connectivity. Where full Internet connectivity is needed, unique, public addresses should be used. delete: <br />For a detailed description of “Address Allocation for Private Internets” and the actual ranges of addresses set aside for that purpose, please refer to RFC 1918 found at: delete: <a href="ftp://ftp.ripe.net/rfc/rfc1918.txt">ftp://ftp.ripe.net/rfc/rfc1918.txt delete: </a>delete: <br />For information on the “Architectural Implications of NAT”, please refer to RFC 2993, found at: delete: <a href="ftp://ftp.ripe.net/rfc/rfc2993.txt">ftp://ftp.ripe.net/rfc/rfc2993.txt delete: </a>delete: </p>delete: </li>delete: <li>delete: <p>Some address ranges are reserved for special use purposes. These are described in RFC 3330 and are beyond the scope of this document. RFC 3330 can be found at: delete: <a href="ftp://ftp.ripe.net/rfc/rfc3330.txt">ftp://ftp.ripe.net/rfc/rfc3330.txt delete: </a>delete: </p>delete: </li>delete: </ol>delete: <h2>delete: <a name="3">delete: </a>3.0 Goals of the Internet Registry System delete: </h2>delete: <p>Public IPv4 address assignments should be made with the following goals in mind: delete: </p>delete: <ol>delete: <li>delete: <p>Uniqueness: Each public IPv4 address worldwide must be unique. This is an absolute requirement guaranteeing that every host on the Internet can be uniquely identified. delete: </p>delete: </li>delete: <li>delete: <p>Aggregation: Distributing IPv4 addresses in an hierarchical manner permits the aggregation of routing information. This helps to ensure proper operation of Internet routing. delete: </p>delete: </li>delete: <li>delete: <p>Fairness: Public IPv4 address space must be fairly distributed to the End Users operating networks. delete: </p>delete: </li>delete: <li>delete: <p>Registration: The provision of a public registry documenting address space allocations and assignments must exist. This is necessary to ensure uniqueness and to provide information for Internet troubleshooting at all levels. delete: </p>delete: </li>delete: </ol>delete: <h3 class="western">delete: <a name="31">delete: </a>3.1 Confidentiality delete: </h3>delete: <p>Internet Registries (IRs) have a duty of confidentiality to their registrants. Information passed to an IR must be securely stored and must not be distributed wider than necessary within the IR. When necessary, the information may be passed to a higher-level IR under the same conditions of confidentiality. delete: </p>delete: <h3 class="western">delete: <a name="32">delete: </a>3.2 Language delete: </h3>delete: <p>Please note that all communication with the RIPE NCC must be in English. delete: </p>delete: <h2>delete: <a name="4">delete: </a>4.0 Registration Requirements delete: </h2>delete: <p>All assignments and allocations must be registered in the RIPE Database. This is necessary to ensure uniqueness and to support network operations. delete: <br />delete: <br />Only allocations and assignments registered in the RIPE Database are considered valid. Registration of objects in the database is the final step in making an allocation or assignment. Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained). delete: </p>delete: <h2>delete: <a name="5">delete: </a>delete: <b>5.0 Policies and Guidelines for Allocations delete: </b>delete: </h2>delete: <p>An allocation is a block of IPv4 addresses from which assignments are taken. delete: </p>delete: <p>All LIRs receiving address space from the RIPE NCC must adopt a set of policies that are consistent with the policies formulated by the RIPE community and described in this document. delete: </p>delete: <h3>delete: <a name="51">delete: </a>delete: <b>5.1 Allocations made by the RIPE NCC to LIRs delete: </b>delete: </h3>delete: <p>Details of how to join the RIPE NCC can be found in the RIPE Document " delete: <a data-val="1debfd86d3d2ea24a7ce6695202c44f0" href="./resolveuid/1debfd86d3d2ea24a7ce6695202c44f0" data-linktype="internal">Procedure for Becoming a Member of the RIPE NCC delete: </a>" delete: </p>delete: <p>On application for IPv4 resources LIRs will receive IPv4 addresses according to the following: delete: </p>delete: <ol>delete: <li>delete: <p>The size of the allocation made will be exactly one /22. delete: </p>delete: </li>delete: <li>delete: <p>The sum of all allocations made to a single LIR by the RIPE NCC after the 14th of September 2012 is limited to a maximum of 1024 IPv4 addresses (a single /22 or the equivalent thereof). delete: </p>delete: </li>delete: <li>delete: <p>The LIR must confirm it will make assignment(s) from the allocation. delete: </p>delete: </li>delete: </ol>delete: <p>In case an allocation of a single /22 as per clause 1 can no longer be made, multiple allocations up to an equivalent of a /22 in address space will be made to fulfill a request. delete: </p>delete: <p>delete: <a name="52">delete: </a>delete: </p>delete: <h3>delete: <b>5.2 Unforeseen circumstances delete: </b>delete: </h3>delete: <p>A /16 will be held in reserve for some future uses, as yet unforeseen. The Internet is a disruptive technology and we cannot predict what might happen. Therefore it is prudent to keep a /16 in reserve, just in case some future requirement makes a demand of it. delete: </p>delete: <p>In the event that this /16 remains unused at the time the remaining addresses covered by this policy have been distributed, it returns to the pool to be distributed as per section 5.1, and this section is to be automatically deleted from the policy document. delete: </p>delete: <h3>delete: <a name="53">delete: </a>delete: <b>5.3 Address Recycling delete: </b>delete: </h3>delete: <p>Any address space that is returned to the RIPE NCC will be covered by the same rules as the address space intended in section 5.1. delete: </p>delete: <p>This section only applies to address space that is returned to the RIPE NCC and that will not be returned to the IANA but re-issued by the RIPE NCC itself. delete: </p>delete: <p>delete: <a name="54">delete: </a>delete: </p>delete: <h3>delete: <b>5.4 Sub-allocations delete: </b>delete: </h3>delete: <p>Sub-allocations are intended to aid the goal of routing aggregation and can only be made from allocations with a status of "ALLOCATED PA". LIRs holding "ALLOCATED PI" or "ALLOCATED UNSPECIFIED" allocations may be able to convert them to PA allocations if there are no ASSIGNED PI networks within it. The meanings of the various "status:" attribute values are described in Section 7.0. delete: </p>delete: <p>LIRs wishing to convert their allocations to PA status must contact the RIPE NCC by email at delete: <a href="mailto:lir-help@ripe.net">lir-help@ripe.net delete: </a>. delete: </p>delete: <p>LIRs may make sub-allocations to multiple downstream network operators. delete: </p>delete: <p>The LIR is contractually responsible for ensuring the address space allocated to it is used in accordance with the RIPE community's policies. It is recommended that LIRs have contracts requiring downstream network operators to follow the RIPE community's policies when those operators have sub-allocations. delete: </p>delete: <p>Sub-allocations form part of an LIR's aggregatable address space. As such, an LIR may want to ensure that the address space is not retained by a downstream network if the downstream network operator ceases to receive connectivity from the LIR's network. LIRs not wishing to lose address space in this way are responsible for ensuring that the status of the sub-allocation is clear in any contracts between the LIR and the downstream network operator. delete: </p>delete: <h3>delete: <a name="55">delete: </a>delete: <b>5.5 Transfers of Allocations delete: </b>delete: </h3>delete: <p class="western">delete: <span>delete: <span>delete: <span>delete: <span>delete: <span>delete: <span>Any delete: </span>delete: </span>delete: </span>delete: </span>delete: </span>delete: </span>resource holder delete: <span>delete: <span>delete: <span>delete: <span>delete: <span>delete: <span>is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by the RIPE NCC or otherwise through the Regional Internet Registry System. delete: </span>delete: </span>delete: </span>delete: </span>delete: </span>delete: </span>delete: </p>delete: <p class="western">delete: <span>Address space may only be re-allocated to another delete: </span>delete: <span>resource holder who is a member of an RIR that allows transfers delete: </span>delete: <span>. delete: </span>delete: </p>delete: <p class="western">Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis. delete: </p>delete: <p class="western">For transfers from RIR regions that require the receiving region to have needs-based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the transferred resources within five years. delete: </p>delete: <p>While the transfer is in process, during the time the internet number resources are registered in RIPE NCC service region, then RIPE policies will apply. delete: </p>delete: <p>LIRs that receive a re-allocation from another LIR cannot re-allocate complete or partial blocks of the same address space to another LIR within 24 months of receiving the re-allocation. delete: </p>delete: <p>The RIPE NCC will record the change of allocation after the transfer. delete: </p>delete: <p>The RIPE NCC will publish a list of all allocations transferred under this section. The publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses. delete: </p>delete: <p>The list will contain information about approved and non-approved transfers. delete: </p>delete: <p>The following information will be published for approved transfers: delete: </p>delete: <ul>delete: <li>delete: <p>the name of the transferring party, delete: </p>delete: </li>delete: <li>delete: <p>the block originally held by the transferring party, delete: </p>delete: </li>delete: <li>delete: <p>the name(s) of the receiving party or parties, delete: </p>delete: </li>delete: <li>delete: <p>each subdivided prefix (each partial block derived from that original block) transferred, delete: </p>delete: </li>delete: <li>delete: <p>the date each prefix was transferred. delete: </p>delete: </li>delete: </ul>delete: <p>Non-approved transfers will be published in an aggregate statistics. In the statistics the following information will be published delete: </p>delete: <ul>delete: <li>delete: <p>the number of requested transfers not approved after the RIPE NCC's evaluation, delete: </p>delete: </li>delete: <li>delete: <p>the sum of the number of addresses included in the requested transfers. delete: </p>delete: </li>delete: <li>delete: <p>Neither the blocks nor the organizations involved will be identified in these statistics. delete: </p>delete: </li>delete: </ul>delete: <p>Please note that the LIR always remains responsible for the entire allocation it receives from the RIPE NCC until the transfer of address space to another LIR is completed or the address space is returned. The LIR must ensure that all policies are applied. delete: </p>delete: <p>Re-allocated blocks are no different from the allocations made directly by the RIPE NCC and so they must be used by the receiving LIR according to the policies described in this document. delete: </p>delete: <h2>delete: <a name="6">delete: </a>delete: </h2>delete: <h2>6.0 Policies and Guidelines for Assignments delete: </h2>delete: <h3>delete: <a name="61">delete: </a>delete: <b>6.1. Assignments to Internet Exchange Points delete: </b>delete: </h3>delete: <p>A /16 will be held in reserve for exclusive use by Internet Exchange Points (IXPs). On application for IPv4 resources, an IXP will receive one number resource (/24 to /22) according to the following: delete: </p>delete: <ul>delete: <li>delete: <p>This space will be used to run an IXP peering LAN; other uses are forbidden. delete: </p>delete: </li>delete: <li>delete: <p>Organisations receiving space under this policy must be IXPs and must meet the definition as described in section two of the RIPE document "IPv6 Address Space for Internet Exchange Points". delete: </p>delete: </li>delete: <li>delete: <p>IXPs holding other PI IPv4 space for their peering LAN (i.e. they are seeking a larger assignment), must return their old peering LAN resources back to this pool within 180 days of assignment. delete: </p>delete: </li>delete: <li>delete: <p>New IXPs will be assigned a /24. Should they require a larger assignment, they must return their current assignment (or existing PI used as an IXP peering LAN) and receive a replacement /23 or /22. After one year the utilisation of the new assignment must be at least 50%, unless special circumstances are defined. delete: </p>delete: </li>delete: <li>delete: <p>IP space returned by IXPs will be added to the reserved pool maintained for IXP use. delete: </p>delete: </li>delete: <li>delete: <p>Assignments will only be made to IXPs who have already applied for, or received an IPv6 assignment for their peering LAN. delete: </p>delete: </li>delete: </ul>delete: <h3>delete: <a name="62">delete: </a>delete: <b>6.2 Network Infrastructure and End User Networks delete: </b>delete: </h3>delete: <p>IP addresses used solely for the connection of an End User to a service provider (e.g. point-to-point links) are considered part of the service provider's infrastructure. These addresses do not have to be registered with the End User's contact details but can be registered as part of the service provider's internal infrastructure. When an End User has a network using public address space this must be registered separately with the contact details of the End User. Where the End User is an individual rather than an organisation, the contact information of the service provider may be substituted for the End Users. delete: </p>delete: <p>An explanation of how to register objects in the database can be found in the "RIPE Database User Manual: Getting Started" found at: delete: </p>delete: <p>delete: <a href="http://www.ripe.net/data-tools/support/documentation/getting-started">http://www.ripe.net/data-tools/support/documentation/getting-started delete: </a>delete: </p>delete: <h3>delete: <a name="63">delete: </a>delete: <b>6.3 Validity of an Assignment delete: </b>delete: </h3>delete: <p class="western">An assignment is valid as long as the original criteria on which it was based remain valid and it is properly registered in the RIPE Database. Changes to the original criteria must be documented in the RIPE Registry, or the assignment will no longer be considered valid. An assignment that was based on information that turns out to be incorrect is no longer valid. delete: </p>delete: <h3 class="western">delete: <a name="64">delete: </a>6.4 Transfers of PI space delete: </h3>delete: <p class="western">Any holder of Provider Independent (PI) address space is allowed to re-assign complete or partial blocks of IPv4 address space that were previously assigned to them by the RIPE NCC. delete: </p>delete: <p class="western">Address space may only be re-assigned in accordance with the RIPE Policy, “ delete: <a class="western" href="http://www.ripe.net/ripe/docs/contract-req" target="_self">Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a>”. delete: </p>delete: <p class="western">Re-assignments must be reflected in the RIPE Database. This re-assignment can either be on a permanent or non-permanent basis. delete: </p>delete: <p class="western">Parties that receive a re-assignment from another party cannot re-assign complete or partial blocks of the same address space to another party within 24 months of receiving the re-assignment. delete: </p>delete: <p class="western">The RIPE NCC will record the change of PI assignment after the transfer. delete: </p>delete: <p class="western">The RIPE NCC will publish a separate list of all PI assignments transferred under this section. The publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses. delete: </p>delete: <p class="western">The list will contain information about approved and non-approved transfers. delete: </p>delete: <p class="western">The following information will be published for approved transfers: delete: </p>delete: <ul>delete: <li>delete: <p class="western">The name of the transferring party delete: </p>delete: </li>delete: <li>delete: <p class="western">The block originally held by the transferring party delete: </p>delete: </li>delete: <li>delete: <p class="western">The name(s) of the receiving party or parties delete: </p>delete: </li>delete: <li>delete: <p class="western">Each subdivided prefix (each partial block derived from that original block) transferred delete: </p>delete: </li>delete: <li>delete: <p class="western">The date each prefix was transferred delete: </p>delete: </li>delete: </ul>delete: <p class="western">Non-approved transfers will be published in aggregate statistics. In the statistics the following information will be published: delete: </p>delete: <ul>delete: <li>delete: <p class="western">The number of requested transfers not approved after the RIPE NCC's evaluation delete: </p>delete: </li>delete: <li>delete: <p class="western">The sum of the number of addresses included in the requested transfers delete: </p>delete: </li>delete: </ul>delete: <p class="western">Neither the blocks nor the organizations involved will be identified in these statistics. delete: </p>delete: <p class="western">Please note that the transferring party always remains responsible for the entire assignment it receives from the RIPE NCC until the transfer of address space to another party is completed or if the address space is returned. delete: </p>delete: <p class="western">Re-assigned blocks are no different from PI assignments made directly by the RIPE NCC and so must be used by the receiving party according to the policies described in this document. delete: </p>delete: <h2>delete: <a name="7">delete: </a>delete: <b>7.0 Types of Address Space delete: </b>delete: </h2>delete: <p>LIRs are allocated Provider Aggregatable (PA) address space. They sub-allocate and assign this to downstream networks. If a downstream network or End User changes its service provider, the address space assigned or sub-allocated by the previous service provider must be returned and the network renumbered. delete: </p>delete: <p>Clear contractual arrangements are mandatory for PA space. End Users requesting PA space must be given this or a similar warning: delete: </p>delete: <p>delete: <i>Assignment of this IP space is valid as long as the criteria for the original assignment are met and only for the duration of the service agreement between yourself and us. We have the right to reassign the address space to another user upon termination of this agreement or an agreed period thereafter. This means that you will have to re-configure the addresses of all equipment using this IP space if you continue to require global uniqueness of those addresses. delete: </i>delete: </p>delete: <p>LIRs will register the type of any assigned address space using the "status:" attribute of the inetnum object in the RIPE Database. The possible values of this attribute are: delete: </p>delete: <ul>delete: <li>delete: <p>ALLOCATED PA: This address space has been allocated to an LIR and no assignments or sub-allocations made from it are portable. Assignments and sub-allocations cannot be kept when moving to another provider. delete: </p>delete: </li>delete: <li>delete: <p>ALLOCATED PI: This address space has been allocated to an LIR or RIR and all assignments made from it are portable. Assignments can be kept as long as the criteria for the original assignment are met. Sub-allocations cannot be made from this type of address space. delete: </p>delete: </li>delete: <li>delete: <p>ALLOCATED UNSPECIFIED: This address space has been allocated to an LIR or RIR. Assignments may be PA or PI. This status is intended to document past allocations where assignments of both types exist. It is avoided for new allocations. Sub-allocations cannot be made from this type of address space. delete: </p>delete: </li>delete: <li>delete: <p>SUB-ALLOCATED PA: This address space has been sub-allocated by an LIR to a downstream network operator that will make assignments from it. All assignments made from it are PA. They cannot be kept when moving to a service provided by another provider. delete: </p>delete: </li>delete: <li>delete: <p>LIR-PARTITIONED PA: This allows an LIR to document distribution and delegate management of allocated space within their organisation. Address space with a status of LIR-PARTITIONED is not considered used. When the addresses are used, a more specific delete: <b>inetnum delete: </b>must be registered. delete: </p>delete: </li>delete: <li>delete: <p>LIR-PARTITIONED PI: This allows an LIR to document distribution and delegate management of allocated space within their organisation. Address space with a status of LIR-PARTITIONED is not considered used. When the addresses are used, a more specific delete: <b>inetnum delete: </b>must be registered. delete: </p>delete: </li>delete: <li>delete: <p>EARLY-REGISTRATION: This is used by the RIPE Database administration when transferring pre-RIR registrations from the ARIN Database. The value can be changed by database users (except for ALLOCATED PA). Only the RIPE Database administrators can create objects with this value. delete: </p>delete: </li>delete: <li>delete: <p>NOT-SET: This indicates that the registration was made before the "status:" attributes became mandatory for inetnum objects. The object has not been updated since then. New objects cannot be created with this value. The value can be changed by database users. delete: </p>delete: </li>delete: <li>delete: <p>ASSIGNED PA: This address space has been assigned to an End User for use with services provided by the issuing LIR. It cannot be kept when terminating services provided by the LIR. delete: </p>delete: </li>delete: <li>delete: <p>ASSIGNED PI: This address space has been assigned to an End User for a specific purpose. It cannot be used to make further assignments to other parties. delete: </p>delete: </li>delete: <li>delete: <p>ASSIGNED ANYCAST: This address space has been assigned for use in TLD anycast networks. It cannot be kept when no longer used for TLD anycast services. delete: </p>delete: </li>delete: </ul>delete: <p>The creation of an inetnum object with a status of "ASSIGNED PA" or "ASSIGNED PI" is only possible if there is no less specific or more specific inetnum object with an "ASSIGNED" status. delete: </p>delete: <p>Address space without an explicit type in the "status:" attribute is assumed to be PI. LIRs must clearly mark all new assignments in the RIPE Database with either "PA" or "PI" as appropriate. delete: </p>delete: <p>In the past, some LIRs assigned address space that was de facto aggregated but not formally PA because there were no clear contractual arrangements for termination of the assignment. LIRs must ask leaving customers to voluntarily release this address space upon termination of service. Where possible, LIRs should work to make contractual arrangements to convert PI addresses into PA addresses. delete: </p>delete: <p>The RIPE NCC no longer allocates or assigns PI address space, except for assignments to Internet Exchange Points as described in section 6.1. delete: </p>delete: <h2>delete: <a name="8">delete: </a>delete: <b>8.0 LIR Audit delete: </b>delete: </h2>delete: <p>The RIPE community asked the RIPE NCC to audit LIR operations and ensure consistent and fair implementation of the community's policies. Details of this activity are described in the RIPE Document "RIPE NCC Audit Activity" found at: delete: <a href="http://www.ripe.net/ripe/docs/audit">http://www.ripe.net/ripe/docs/audit delete: </a>delete: </p>delete: <p>delete: <a name="9">delete: </a>delete: </p>delete: <h2>delete: <b>9.0 Closing an LIR by the RIPE NCC delete: </b>delete: </h2>delete: <p class=" ">The RIPE NCC may close an LIR for any of the following reasons: delete: </p>delete: <ul>delete: <li>delete: <p>the LIR does not pay money owed to the RIPE NCC delete: </p>delete: </li>delete: <li>delete: <p>the LIR cannot be contacted by the RIPE NCC for a significant period of time delete: </p>delete: </li>delete: <li>delete: <p>the LIR consistently violates the RIPE community's policies delete: </p>delete: </li>delete: </ul>delete: <p>The RIPE NCC takes on responsibility for address space held by closing LIRs. delete: </p>

IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Procedures For DNS Delegation In The IN-ADDR.ARPA Domain

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacy policy. You can accept our cookies either by clicking here or by continuing to use the site.