You are here: Home > Publications > RIPE Document Store > RIPE NCC Internet Numbers Registration Procedures

Changes to RIPE NCC Internet Numbers Registration Procedures

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-072: RIPE NCC ripe-628: Transfer of Internet Numbers Registration Procedures Number Resource Records and Change of a Member’s Official Legal Name

delete:  insert: <h2 class="western">

Contents insert: `</h2>`

insert: 

insert:  1.0 insert: <a href="#1"> Definitions insert: </a> insert:  insert: 

insert: 

insert:  2.0 insert: <a href="#2"> Introduction insert: </a> insert:  insert: 

insert: 

insert:  3.0 insert: <a href="#3"> Transfer of Internet Number Resource Records insert: </a> insert:  insert: 

insert: 

insert:  3.1 insert: <a href="#31"> Submission of the Request for Transfer insert: </a> insert:  insert: 

insert: 

insert:  3.2 insert: <a href="#32"> If the Receiving insert: </a> insert: <a href="#32"> Party insert: </a> insert: <a href="#32"> insert: </a> insert: <a href="#32"> is insert: </a> insert: <a href="#32"> not insert: </a> insert: <a href="#32"> a insert: </a> insert:  insert: <a href="#32"> Member insert: </a> insert:  insert:  insert: 

insert: 

insert:  3.3 insert: <a href="#33"> Financial Consequences insert: </a> insert:  insert: 

insert: 

insert:  3.4 insert: <a href="#34"> Internet Number Resource Registration and RIPE Database Issues insert: </a> insert:  insert: 

insert: 

insert:  4.0 insert: <a href="#4"> The insert:  Member insert:  Changes its Official Legal Name insert: </a> insert:  insert: 

insert: <h3 class="western">

insert: `<a name="1">` insert: `</a>` insert: `` insert: `` 1.0 Definitions insert: `` insert: `` insert: `</h3>`

insert: 

insert:  For the purposes of this document: insert:  insert: 

insert: 

insert:  Internet number resource records refer to insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  The registered insert:  allocations and assignments of a Member insert:  insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  The independent Internet number resources assigned through the Member as a “sponsoring LIR” to an End User insert:  insert: 
insert: </li>

insert: </ul>

insert: <h3 class="western">

insert: `<a name="2">` insert: `</a>` insert: `` insert: `` 2.0 Introduction insert: `` insert: `` insert: `</h3>`

insert: 

insert:  In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning: insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  The natural or legal persons holding the registration of Internet number resources insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  The Internet number resource records that are registered to the natural and legal persons insert:  insert: 
insert: </li>

insert: </ul>

insert: 

insert:  This means that any transfer of Internet number resources from one party to another, or any change to the legal status of a party holding the registration of Internet number resources, must be communicated to the RIPE NCC. insert:  insert: 

insert: 

insert:  The Member must inform the RIPE NCC if insert:  one or both insert:  of the following changes occurs: insert:  insert: 

insert: <ol>

insert: <li>

insert: 
insert:  Internet Number Resource records are transferred. Such transfers may take place: insert:  insert: 
insert: <ul>
- insert: 
 insert:  Because of a change in the business structure of the Member, for example in the case of a merger or acquisition of the Member's organisation; or insert:  insert: 
 insert: </li>
- insert: 
 insert:  I insert:  insert:  insert:  n the case of a pure transfer of IPv4 address records from a Member to another party according to RIPE Policies ( insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Sections 5.5 and 6.4 , "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”). Such a transfer may also be facilitated through the insert: <a data-val="8768823a7d79496c8bff938729212474" href="./resolveuid/8768823a7d79496c8bff938729212474" data-linktype="internal"> RIPE NCC Listing Service. insert: </a> insert:  insert:  insert: 
 insert: </li>
insert: </li>

insert: <li>

insert: 
insert:  The Member changes its official legal name This documents obsoletes ripe-65, version 0.6 of this document . delete:   delete:   Abstract delete:   delete:   delete:   Such a change may occur, for example, because of a merger or acquisition of the Member's organisation. insert:  insert: 
insert: </li>

insert: </ol>

insert: 

insert:  This document describes the procedures to be followed for the reassignment of IP such changes to be properly communicated to, and registered with, the RIPE NCC. insert:  insert: 

insert: 

insert: 

insert: 

insert:  insert:  Note: insert:  insert:  insert: 

insert: 

insert:  If a change in the Member's official legal name is accompanied by a transfer of Internet number resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer. insert:  insert: 

insert: 

insert:  If a change in the Member's business structure is insert:  not insert:  accompanied by a transfer of Internet number resource records or a change in the Member's official legal name, then the RIPE NCC does not need to be informed of this change. insert:  insert: 

insert: 

insert:  This document does not describe the procedure to be followed in the case of changes with regards to independent Internet number resources assigned to End Users or any changes to the End User's business structure. This procedure is described in the RIPE NCC Procedural Document, “ insert: <a href="https://www.ripe.net/publications/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User insert: </a> ”. insert:  insert: 

insert: <h3 class="western">

insert: `<a name="3">` insert: `</a>` insert: `` insert: `` 3.0 Transfer of Internet Number Resource Records insert: `` insert: `` insert: `</h3>`

insert: 

insert:  If a Member transfers their Internet number resource records to a third party for any reason, this transfer must be declared to, and approved by, the RIPE NCC. insert:  insert: 

insert: <h4>

insert: `<a name="31">` insert: `</a>` 3.1 Submission of the Request for Transfer insert: `</h4>`

insert: 

insert:  One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed: insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  If the transfer is due to a change in the business structure of the Member (e.g., merger or acquisition), the request must be submitted to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  insert:  If the transfer is a transfer of IPv4 address records from one Member to another insert:  insert:  insert:  insert:  party ac insert:  insert:  insert:  insert:  cording to RIPE Policies ( insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Sections 5.5 and 6.4, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ”), the request must be submitted to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert:  insert:  insert: 
insert: </li>

insert: </ul>

insert: 

insert:  A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request. insert:  insert: 

insert: 

insert: 

insert: 

insert:  The RIPE NCC will ask for the following information: insert:  insert: 

insert: 

insert:  insert:  i. Information regarding the parties involved, including: insert:  insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  The full official legal names of all parties involved insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  Which party will transfer the Internet number resource records and which party will receive them insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  Recent registration papers issued by the relevant national authorities for all involved parties insert:  insert: 
insert: </li>

insert: </ul>

insert: 

insert:  I insert:  insert:  insert:  f the current official legal names of the involved Members are different from the ones in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under insert: <a href="#4"> Section insert: </a> insert: <a href="#4"> 4.0 insert: </a> must be followed prior to the transfer of the Internet number resource records. insert:  insert:  insert: 

insert: 

insert:  insert:  The procedure described under Section 4.0 is not necessary for the transferring Member if the RIPE NCC Standard Service Agreement of the transferring Member is terminated (see Closure of LIR and Deregistration of Internet number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. insert: </a> and insert: <a title="" href="https://www.ripe.net/publications/docs/closure#12" class="external-link" target="_self"> Section A.1.2. insert: </a> ). insert:  insert:  insert:  insert:  insert:  insert:  insert: 

insert: 

insert:  insert:  insert: 
network numbers from blocks obtained from the RIPE Network Coordination delete:   Centre. It deals with items as providing information insert:  insert:  insert:  insert: 

insert: 

insert:  insert:  insert:  ii. A description of the reason for the RIPE delete:   database, as well as reassignment of IP addresses transfer (for exa insert:  mple, due to merger, acquisition, transfer of allocation according to the RIPE policies) insert:  insert:  insert: 

insert: 

insert:  If the transfer is taking place due to a change in light of delete:   the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller delete:   et al. delete:   delete:   delete:   Introduction delete:   delete:   delete:   Since May 1st 1992, the RIPE Network Coordination Centre (NCC) the structure of the organisation(s) involved, a description of the changes among the organisation(s) is delete:   acting as a delegated registry for IP networks numbers to NICs and NOCs delete:   in Europe. It is RIPE NCC policy not to give out network numbers to delete:   individual organisations, who should refer in turn, to their IP network delete:   service provider. delete:   delete:   The mission of the RIPE NCC is to give network numbers to the various delete:   service providers and NICs. The NICs and NOCs can then reassign the delete:   actual IP network numbers to organisations requesting IP network delete:   numbers. delete:   delete:   delete:   Class B Network Number Allocation Procedure delete:   delete:   Service providers can request Class B network numbers on a one-by-one delete:   basis from the RIPE NCC. Because class B address space is a critical delete:   resource, a request for a class B network number necessary. The description must be accompanied by all official legal documents proving/supporting the changes the request is based on. insert:  insert: 

insert: 

insert:  insert: 
a justification insert:  insert:  insert: 

insert: 

insert:  insert:  iii. A list of the Internet number resource records that are requested to be transferred. If insert:  insert:  insert:  all insert:  insert:  insert:  of the transferring Member's Internet number resource records registered are being transferred, a confirmation of this is requested. insert:  insert:  insert: 

insert: 

insert:  The Member must also indicate any End User assignment agreements that are requested to be transferred. insert:  insert: 

insert: 

insert:  If a Member transfers all of their Internet number resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (see Closure of LIR and Deregistration of Internet number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. insert: </a> ). insert:  insert: 

insert: 

insert:  insert:  insert:  
insert:  insert:  insert: 

insert: 

insert:  insert:  iv. The correct contact details of all parties involved insert:  insert:  insert: 

insert: 

insert:  The RIPE NCC may ask the parties involved to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details. insert:  insert: 

insert: 

insert:  insert:  insert:  
insert:  insert:  insert: 

insert: 

insert:  insert:  v. A Transfer Agreement signed by both parties or by their legal successors insert:  insert:  insert: 

insert: 

insert:  The RIPE NCC will make a template of the Transfer Agreement available. Either party may submit the Transfer Agreement to the RIPE NCC, signed by authorised persons for both parties. The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a contact person or authorised person (e.g., senior manager, legal successor). insert:  insert: 

insert: 

insert:  If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send: insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  an official document (issued by a national authority) confirming the closure of the transferring party; and insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  a copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resource records. If such an agreement is not available, the receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor). The RIPE NCC reserves the right to reverse the transfer should another party object to this transfer and provide an agreement that proves that the Internet number resource records should have been transferred to them. insert:  insert: 
insert: </li>

insert: </ul>

insert: 

insert:  insert:  insert:  insert:  insert:  
insert:  insert:  insert:  insert:  insert: 

insert: 

insert:  insert:  insert:  insert:  v insert:  insert:  insert:  i. insert:  insert:  insert:  insert:  An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments insert:  insert:  insert:  insert:  insert:  insert: 

insert: 

insert:  insert:  The RIPE NCC may ask for an overview of the utilisation of all Internet number resources registered to the Member and of all End User assignment agreements signed by the Member. insert:  insert:  insert: 

insert: <h4>

insert: `<a name="32">` insert: `</a>` 3.2 If the Receiving Party is not a Member insert: `</h4>`

insert: 

insert:  insert:  Members may wish to transfer their Internet number resource records to another Member or to a third party that is not a Member. insert:  insert:  insert: 

insert: 

insert:  insert:  If the Internet number resource records are transferred to a non-Member, the receiving party must apply to be a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place ( insert: <a href="https://www.ripe.net/lir-services/member-support/become-a-member"> more information on how to become a Member is available insert: </a> ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resource records to them. insert:  insert:  insert: 

insert: 

insert:  insert:  If the Internet number resource records to be transferred are Provider Independent (PI) addresses , the receiving party may either apply to be a Member by signing the RIPE NCC Standard Service Agreement or enter into a contractual relationship with a sponsoring LIR. insert:  insert:  insert:  For more information, please see: insert:  insert:  insert:  insert: 

insert: 

insert: <a href="https://www.ripe.net/lir-services/resource-management/independent-resources/"> insert:  insert:  insert:  insert:  https://www.ripe.net/lir-services/resource-management/independent-resources/ insert:  insert:  insert:  insert:  insert: </a> insert: 

insert: 

insert:  insert:  The request for the transfer can be submitted as described above (Section 1). insert:  insert:  insert: 

insert: <h4>

insert: `<a name="33">` insert: `</a>` 3.3 Financial Consequences insert: `</h4>`

insert: 

insert:  insert:  All outstanding invoices and all outstanding financial obligations must be paid in terms of the requesting organisation's size, current delete:   network full. If the RIPE NCC Standard Service Agreement is terminated in the course of the RIPE NCC financial year, the service fee for this Member must be paid for the full year. The payment is the responsibility of the receiving Member.If the receiving party is not a Member, then the payment is the responsibility of the transferring Member. insert:  insert:  insert: 

insert: 

insert:  insert:  If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see insert: <a href="http://www.ripe.net/ripe/docs/charging"> RIPE NCC Charging Scheme insert: </a> ). insert:  insert:  insert: 

insert: <h4>

insert: `<a name="34">` insert: `</a>` 3.4 Internet Number Resource Registration and expected network growth. The requestor should also make delete: ` ` clear why they cannot use a block of class C network numbers to achieve delete: ` ` their goals. RIPE Database Issues insert: `</h4>`

insert: 

insert:  insert:  insert:  The RIPE NCC will review requests using the same standards delete:   as the status of any other Internet Registry, particularly the US NIC. IP address allocation or independent Internet Number Resource assignment maintained by the party involved, in compliance with the RIPE Policies current at the time of the transfer. insert:  insert:  insert:  insert: 

insert: 

insert:  The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. insert:  insert: 

insert: 

insert:  The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The transferring Member must update all RIPE Database objects maintained by them that are related to this transfer. insert:  insert: 

insert: <h3 class="western">

insert: `<a name="4">` insert: `</a>` insert: `` insert: `` 4.0 The Member Changes its Official Legal Name insert: `` insert: `` insert: `</h3>`

insert: 

insert:  It is the obligation of the Member to inform the RIPE NCC immediately if any change in the Member's official legal name occurs. insert:  insert: 

insert: 

insert:  The Member must send an email to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> informing the RIPE NCC of the name change. This email must include: insert:  insert: 

insert: <ul>

insert: <li>

insert: 
insert:  New registration papers from the national authority; and insert:  insert: 
insert: </li>

insert: <li>

insert: 
insert:  The official legal documents supporting this change insert: 

delete:   Class C Allocation Procedures delete:   delete:   NICs and NOCs accepting a block of class C numbers agree to adhere to delete:   the following procedures: delete:   delete:   A) The insert: 
insert: </li>

insert: </ul>

insert: 

insert:  insert:  T insert:  insert:  insert:  insert:  insert:  he RIPE NCC will assign complete class C blocks to individual NICs delete:   and NOCs. They can be requested from <[email protected]>. delete:   delete:   B) In order to prevent implementation problems, network numbers ending delete:   with 0 or 255 should NOT be reassigned. delete:   delete:   C) Full information about reassigned network numbers must be reported delete:   back to the RIPE NCC in full RIPE database format (ref ripe-13). delete:   The complete entries should be sent immediately after reassignment to delete:   <[email protected]>. delete:   The RIPE NCC is ready to accept block entries send a new insert: <a title="" href="https://www.ripe.net/publications/docs/service-agreement" class="external-link" target="_self"> RIPE NCC Standard Service Agreement insert: </a> for the RIPE database. delete:   For block syntax, please contact the RIPE NCC. delete:   delete:   D) Reassignment of class C network numbers should be done in a manner delete:   Member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the Member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that facilitates Supernetting (see next section). delete:   delete:   E) Requests for network numbers should be reasonable. All NICs and NOCs delete:   should prevent stockpiling of network numbers. delete:   delete:   F) On first request from the RIPE NCC, the class C network numbers not delete:   yet reassigned, must be returned to the RIPE NCC. delete:   delete:   delete:   Supernetting delete:   delete:   NICs and NOCs reassigning IP network numbers are urgently requested to delete:   read the Supernetting proposal related to this change. The Member must update all RIPE Database objects maintained by Vince Fuller et al. This document can delete:   be obtained from the rfc section of the RIPE document store or other RFC delete:   servers. It is called rfc1338.txt. delete:   The Supernetting proposal was made to reduce the increase of routing delete:   table size in the current Internet. It proposes to create a hierarchy delete:   of IP network numbers, which can then be aggregated resulting in less delete:   routing table entries in routing equipment. While them that are related to this proposal has not delete:   been formally adopted we expect that something at least along the same delete:   principle will be implemented in the near future. delete:   delete:   Here is how it works: delete:   delete:   If an organisation A needs 8 class C network numbers, the numbers should delete:   be given out in such a way that the routing information for each of delete:   these 8 networks could appear as one entry with the correct mask in delete:   routers. delete:   delete:   More concretely: delete:   delete:   Service provider S hands out networks 192.24.8 through 192.24.15 to delete:   organisation A. These networks can then appear in routing equipment as a delete:   supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C delete:   network numbers appear as one routing table entry. delete:   delete:   The guidelines that can be derived from the Supernetting proposal are: delete:   delete:   A) Service providers should reserve blocks of class C network numbers from delete:   their allocation for each organisations requesting class C network numbers. delete:   delete:   B) The size of these blocks should always be a power of 2. delete:   delete:   C) The numbers in these blocks should be contiguous. delete:   delete:   D) The blocks should start on bit boundaries. delete:   (ie powers of 2, AND multiples of the block size) delete:   delete:   E) The blocks reserved for an organisation should be sufficient for a delete:   reasonable expected growth over the next few years. delete:   delete:   F) Multi-homed organizations may obtain address space from one of their delete:   providers, the RIPE NCC, or the global NIC, as is appropriate to their delete:   network configuration. These organisations are strongly encouraged to delete:   contact the RIPE NCC for guidance. delete:   delete:   delete:   delete:   If you have any questions concerning this, please do not hesitate to delete:   call or mail us at [email protected] delete:  change. insert:  insert:  insert:  insert: 

RIPE NCC Transfer of Internet Numbers Registration Procedures Number Resource Records and Change of a Member’s Official Legal Name

RIPE Documents Search

ripe-072

State:

Obsoleted

Updated by:

ripe-104 , ripe-136 , ripe-140 , ripe-159 , ripe-185 , ripe-234 , ripe-245 , ripe-263 , ripe-288 , ripe-301 , ripe-302 , ripe-324 , ripe-368 , ripe-387 , ripe-389 , ripe-405 , ripe-411 , ripe-424 , ripe-441 , ripe-448 , ripe-449 , ripe-463 , ripe-471 , ripe-484 , ripe-492 , ripe-496 , ripe-498 , ripe-509 , ripe-515 , ripe-524 , ripe-525 , ripe-527 , ripe-528 , ripe-530 , ripe-553 , ripe-577 , ripe-579 , ripe-581 , ripe-582 , ripe-592 , ripe-595 , ripe-599 , ripe-604 , ripe-606 , ripe-621 , ripe-622 , ripe-623 , ripe-628 , ripe-632 , ripe-634 , ripe-638 , ripe-643 , ripe-648 , ripe-649 , ripe-654 , ripe-667 , ripe-679 , ripe-680 , ripe-689 , ripe-695 , ripe-708 , ripe-709 , ripe-720 , ripe-725 , ripe-730 , ripe-733 , ripe-758

Updates:

ripe-065

Authors:

M.Terpstra

Date:

October 1992

Download

File:
ASCII | 5.0KB

Changes to RIPE NCC Internet Numbers Registration Procedures

Contents insert: `</h2>`

insert: `<a name="1">` insert: `</a>` insert: `<span>` insert: `<span>` 1.0 Definitions insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="2">` insert: `</a>` insert: `<span>` insert: `<span>` 2.0 Introduction insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="3">` insert: `</a>` insert: `<span>` insert: `<span>` 3.0 Transfer of Internet Number Resource Records insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="31">` insert: `</a>` 3.1 Submission of the Request for Transfer insert: `</h4>`

insert: `<a name="32">` insert: `</a>` 3.2 If the Receiving Party is not a Member insert: `</h4>`

insert: `<a name="33">` insert: `</a>` 3.3 Financial Consequences insert: `</h4>`

insert: `<a name="34">` insert: `</a>` 3.4 Internet Number Resource Registration and expected network growth. The requestor should also make delete: `<br />` clear why they cannot use a block of class C network numbers to achieve delete: `<br />` their goals. RIPE Database Issues insert: `</h4>`

insert: `<a name="4">` insert: `</a>` insert: `<span>` insert: `<span>` 4.0 The Member Changes its Official Legal Name insert: `</span>` insert: `</span>` insert: `</h3>`

RIPE Documents Search

ripe-072

Changes to RIPE NCC Internet Numbers Registration Procedures

Contents insert: </h2>

insert: <a name="1"> insert: </a> insert: <span> insert: <span> 1.0 Definitions insert: </span> insert: </span> insert: </h3>

insert: <a name="2"> insert: </a> insert: <span> insert: <span> 2.0 Introduction insert: </span> insert: </span> insert: </h3>

insert: <a name="3"> insert: </a> insert: <span> insert: <span> 3.0 Transfer of Internet Number Resource Records insert: </span> insert: </span> insert: </h3>

insert: <a name="31"> insert: </a> 3.1 Submission of the Request for Transfer insert: </h4>

insert: <a name="32"> insert: </a> 3.2 If the Receiving Party is not a Member insert: </h4>

insert: <a name="33"> insert: </a> 3.3 Financial Consequences insert: </h4>

insert: <a name="34"> insert: </a> 3.4 Internet Number Resource Registration and expected network growth. The requestor should also make delete: <br /> clear why they cannot use a block of class C network numbers to achieve delete: <br /> their goals. RIPE Database Issues insert: </h4>

insert: <a name="4"> insert: </a> insert: <span> insert: <span> 4.0 The Member Changes its Official Legal Name insert: </span> insert: </span> insert: </h3>

RIPE Documents Search

ripe-072

Contents insert: `</h2>`

insert: `<a name="1">` insert: `</a>` insert: `<span>` insert: `<span>` 1.0 Definitions insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="2">` insert: `</a>` insert: `<span>` insert: `<span>` 2.0 Introduction insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="3">` insert: `</a>` insert: `<span>` insert: `<span>` 3.0 Transfer of Internet Number Resource Records insert: `</span>` insert: `</span>` insert: `</h3>`

insert: `<a name="31">` insert: `</a>` 3.1 Submission of the Request for Transfer insert: `</h4>`

insert: `<a name="32">` insert: `</a>` 3.2 If the Receiving Party is not a Member insert: `</h4>`

insert: `<a name="33">` insert: `</a>` 3.3 Financial Consequences insert: `</h4>`

insert: `<a name="34">` insert: `</a>` 3.4 Internet Number Resource Registration and expected network growth. The requestor should also make delete: `<br />` clear why they cannot use a block of class C network numbers to achieve delete: `<br />` their goals. RIPE Database Issues insert: `</h4>`

insert: `<a name="4">` insert: `</a>` insert: `<span>` insert: `<span>` 4.0 The Member Changes its Official Legal Name insert: `</span>` insert: `</span>` insert: `</h3>`