You are here: Home > Publications > RIPE Document Store > Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

Changes to Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-709: Transfer of Internet Number Resources and Change of a Member’s Official Legal Name ripe-085: Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domai
delete: <h2> Contents delete: </h2>

1.0 delete: <a href="#definitions"> Definitions delete: </a> delete: </p> delete: <p> 2.0 delete: <a href="#introduction"> Introduction delete: </a> delete: </p> delete: <p> 3.0 delete: <a href="#transfer"> Transfer of Internet Number Resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.1 delete: <a href="#transfer31"> Submission of the Request for Transfer delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.2 delete: <a href="#transfer32"> If the Receiving Party is not a Member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.3 delete: <a href="#transfer33"> Financial Consequences delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.4 delete: <a href="#transfer34"> Internet Number Resource Registration and RIPE Database Issues delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.5 delete: <a href="#transfer35"> Transfers Between LIR Accounts Belonging to the Same Member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.6 delete: <a href="#transfer36" data-linktype="anchor" data-val="8"> Transfer of Internet Number Resources under Policy Restrictions due to a Change in the Member's Business Structure delete: </a> delete: </p> delete: <p> 4.0 delete: <a href="#memberchanges"> Member Changes Official Legal Name delete: </a> delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="definitions"> delete: </a> 1.0 Definitions delete: </h3> delete: <p> For the purposes of this document, Internet number resources refer to: delete: </p> delete: <ul> delete: <li> The registered allocation and assignment records of a member delete: </li> delete: <li> In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ". Such a transfer may also be facilitated through the RIPE NCC Listing Service. delete: </li> delete: </ul> delete: <p>   delete: </p> delete: <h3> delete: <a name="introduction"> delete: </a> 2.0 Introduction delete: </h3> delete: <p> In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning: delete: </p> delete: <ul> delete: <li> The natural or legal persons holding the registration of Internet number resources delete: </li> delete: <li> The Internet number resources that are registered to these natural or legal persons delete: </li> delete: </ul> delete: <p> 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. delete: </p> delete: <p> A member must inform the RIPE NCC if delete: <em> one or both delete: </em> of the following changes occurs: delete: </p> delete: <ol> delete: <li> Internet Number Resource are transferred. Such transfers may take place: delete: <ul> delete: <li> Because of a change in the member's business structure (for example in the case of a merger or acquisition of the member's organisation, or if the member is undergoing bankruptcy, liquidation, suspension of payments or insolvency proceedings) that can be proved/supported by official documentation from national authorities. delete: </li> delete: <li> In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ". Transfers of IPv4 Internet number resources may also be facilitated through the delete: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> IPv4 Transfer Listing Service delete: </a> . delete: <br /> delete: <br /> delete: </li> delete: </ul> delete: </li> delete: <li> The member changes its official legal name delete: <strong> . delete: </strong> Such a change may occur, for example, because of a merger or acquisition of the member's organisation. delete: </li> delete: </ol> delete: <p> insert: <br />
insert: <br />
This document describes the procedures for such changes to be properly communicated and the delegation of au- insert: <br />
thority of zones in the 193.in-addr.arpa domain. As of March insert: <br />
16th 1993 the RIPE NCC has been delegated the authority for the insert: <br />
193.in-addr.arpa domain from the root. Due to the fact that in insert: <br />
the 193.x.y address space blocks of 256 class C network numbers insert: <br />
are further delegated to local registries , the possibility ex- insert: <br />
ists to also delegate the zone for these blocks in the 193.in- insert: <br />
addr.arpa domain. This document describes some guidelines and insert: <br />
procedures for this type of delegation and the delegation of re- insert: <br />
verse zones for individual class C networks in 193.x.y. insert: <br />
insert: <br />
insert: <br />
A bit more explained insert: <br />
insert: <br />
With the assignment of class C network numbers following the CIDR insert: <br />
(RFC 1338) model, in which large chunks of the address space are insert: <br />
delegated to one region, and within that region blocks of class C insert: <br />
network numbers are delegated to service providers and non- insert: <br />
provider registries, some hierarchy in the address space is insert: <br />
created, similar to the hierarchy in the domain name space. Due insert: <br />
to this hierarchy the reverse Domain Name System mapping can also insert: <br />
be delegated in a similar model as used for the normal Domain insert: <br />
Name System. For instance, the RIPE NCC has been assigned the insert: <br />
complete class C address space starting with 193. It is there- insert: <br />
fore possible to delegate the 193.in-addr.arpa domain completely insert: <br />
to the RIPE NCC, instead of each and every reverse mapping in the insert: <br />
193.in-addr.arpa domain to be registered with the INTERNIC. This insert: <br />
implies that all 193.in-addr.arpa resistrations will be done by insert: <br />
the RIPE NCC. delete: </p> delete: <p> delete: <strong> Note: delete: <br /> delete: </strong> If a change in a member's official legal name Even better, since service providers receive com- insert: <br />
plete class C network blocks from the RIPE NCC, the RIPE NCC can insert: <br />
delegate the reverse registrations for such complete blocks to insert: <br />
these local registries. This implies that customers of these insert: <br />
service providers no longer have to register their reverse domain insert: <br />
mapping with the root, but the service provider have authority insert: <br />
over that part of the reverse mapping. This decreases the work- insert: <br />
load on the INTERNIC and the RIPE NCC, and at the same time in- insert: <br />
crease the service a provider can offer its customers by improve insert: <br />
response times for reverse mapping changes . However there are insert: <br />
some things that need to be examined a bit more closely to avoid insert: <br />
confusion and inconsistencies. These issues are covered in the insert: <br />
next section. insert: <br />
insert: <br />
insert: <br />
Procedures for the delegation of direct subdomains of 193.in- insert: <br />
addr.arpa insert: <br />
insert: <br />
1. A secondary nameserver at ns.ripe.net is accompanied mandatory for all insert: <br />
blocks of class C network numbers delegated in the 193.in- insert: <br />
addr.arpa domain. insert: <br />
insert: <br />
2. Because of the increasing importance of correct reverse ad- insert: <br />
dress mapping, for all delegated blocks a good set of secondaries insert: <br />
must be defined. There should be at least 2 nameservers for all insert: <br />
blocks delegated, excluding the RIPE NCC secondary. insert: <br />
insert: <br />
3. The delegation of a class C block in the 193.in-addr.arpa insert: <br />
domain can be requested by a transfer of Internet number resources, the member sending in a domain object for the insert: <br />
RIPE database to <hostmaster@ripe.net> with all necessary contact insert: <br />
and nameserver information. The RIPE NCC will then forward all insert: <br />
current reverse zones inside this block to the registry, and insert: <br />
after addition of these by the registry, the NCC will check the insert: <br />
working of the reverse server. Once everything is setup proper- insert: <br />
ly, the NCC will delegate the block, and submit the database ob- insert: <br />
ject for inclusion in the database. An example domain object can insert: <br />
be found at the end of this document. insert: <br />
insert: <br />
4. All reverse servers for blocks must first inform the RIPE NCC of the name change and then of the transfer. delete: </p> delete: <p> If a change in a member's business structure is delete: <em> not delete: </em> accompanied by a transfer of Internet number resources or a change in the member's official legal name, then the RIPE NCC be reachable from the insert: <br />
whole of the Internet. In short, all servers must meet similar insert: <br />
connectivity requirements as top-level domain servers. insert: <br />
insert: <br />
5. Running the reverse server for class C blocks does not need to be informed of imply insert: <br />
that one controls that part of the reverse domain, it only im- insert: <br />
plies that one administers that part of the reverse domain. insert: <br />
insert: <br />
6. Before adding individual nets, the administrator of a reverse insert: <br />
domain must check wether all servers to be added for these nets insert: <br />
are indeed setup properly. insert: <br />
insert: <br />
7. There are some serious implications when a customer of a ser- insert: <br />
vice provider that uses address space out of the service provider insert: <br />
class C blocks, moves to another service provider. The previous insert: <br />
service provider cannot force its ex-customer to change network insert: <br />
addresses, and will have to continue to provide the appropriate insert: <br />
delegation records for reverse mapping of these addresses, even insert: <br />
though it they are no longer belonging to a customer. insert: <br />
insert: <br />
8. The registration of the reverse zones for individual class C insert: <br />
networks will usually be done by the registry administering the insert: <br />
class C block this change. delete: </p> delete: <p> This document network has been assigned from. The registry insert: <br />
will make the necessary changes to the zone, and update the net- insert: <br />
work objects in the RIPE database for these networks, to reflect insert: <br />
the correct "rev-srv" fields. In case the RIPE NCC receives a insert: <br />
request for the reverse zone of an individual class C network out insert: <br />
of a block that has been delegated, the request will be forwarded insert: <br />
to the zone contact for this reverse block. insert: <br />
insert: <br />
9. The NCC advises the following timers and counters for direct insert: <br />
subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), insert: <br />
2 hours retry (7200 seconds), 7 days expire (604800 seconds) and insert: <br />
1 day Time To Live (86400 seconds). The retry counter should be insert: <br />
lowered where connectivity is unstable. insert: <br />
insert: <br />
Above procedures are defined to ensure the necessary high availa- insert: <br />
bility for the 193 reverse domains, and to minimize confusion. insert: <br />
The NCC will ensure fast repsonse times for addition requests, insert: <br />
and will in principle update the 193.in-addr.arpa domain at least insert: <br />
once per working day. insert: <br />
insert: <br />
Example domain object to request a block delegation insert: <br />
insert: <br />
domain: 202.193.in-addr.arpa insert: <br />
descr: Pan European Organisations class C block insert: <br />
admin-c: Daniel Karrenberg insert: <br />
tech-c: Marten Terpstra insert: <br />
zone-c: Marten Terpstra insert: <br />
nserver: ns.eu.net insert: <br />
nserver: sunic.sunet.se insert: <br />
nserver: ns.ripe.net insert: <br />
changed: marten@ripe.net 930319 insert: <br />
source: RIPE insert: <br />
insert: <br />
insert: <br />
insert: <br />
Procedures for the delegation of individual network zones by the insert: <br />
RIPE NCC. insert: <br />
insert: <br />
The registration of the reverse zones for individual class C net- insert: <br />
works will usually be done by the registry administering the insert: <br />
class C block this network has been assigned from. In case the insert: <br />
zone corresponding to the class C block has not been delegated, insert: <br />
the RIPE NCC will automatically add the reverse nameserver as insert: <br />
specified in the "rev-srv" attribute of the RIPE database object insert: <br />
for this network, using the following procedures: insert: <br />
insert: <br />
1. Because of the increasing importance of correct reverse ad- insert: <br />
dress mapping, for all delegated networks a good set of secon- insert: <br />
daries must be defined. There should be at least two nameservers insert: <br />
for all networks delegated. insert: <br />
insert: <br />
2. The "rev-srv" field should ONLY contain one fully qualified insert: <br />
domain name of a nameserver which is authoritative for the re- insert: <br />
verse zone for this network. insert: <br />
insert: <br />
3. If a network has or is going to have any external connectivi- insert: <br />
ty, it is strongly recommended that it has at least one reverse insert: <br />
nameserver that can be reached from all of the Internet. insert: <br />
insert: <br />
4. The checking and addition of the reverse zones for single net- insert: <br />
works is completely automated at the RIPE NCC. Although we do insert: <br />
our best to check the setup of the nameservers, these 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 Users business structure. This procedure is described in the RIPE NCC Procedural Document, " delete: <a href="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-val="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-linktype="external"> Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User delete: </a> ". delete: </p> delete: <p> This document does not describe the procedure to be followed in case of a transfer of Internet number resources from the RIPE NCC service region to the service region of another RIR and vice versa. This procedure is described in the RIPE NCC procedural document, " delete: <a class="external-link" href="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr" data-linktype="external" data-val="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr"> Inter-RIR Transfer of Internet Number Resources delete: </a> ". delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="transfer"> delete: </a> 3.0 Transfer of Internet Number Resources delete: </h3> delete: <p> If a member transfers their Internet number resources to a third party for any reason, this transfer must be declared to the RIPE NCC for approval. delete: </p> delete: <h4> delete: <a name="transfer31"> delete: </a> 3.1 Submission of the Request for Transfer delete: </h4> delete: <p> For the transfer to be processed, a registered contact or an authorised person (e.g., senior manager, legal successor) of the involved parties must submit a request to the RIPE NCC. More specifically: delete: </p> delete: <ul> delete: <li> If the transfer is due to a change in the member's business structure that can be proved/supported by official documentation by national authorities (e.g., merger, acquisition, bankruptcy, liquidation), either of the parties involved must submit the request via the delete: <a href="https://my.ripe.net/#/update-registry"> LIR Portal delete: </a> . If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> delete: </li> delete: <li> If this is a transfer of Internet number resource from one member to another party according to RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ", the transferring party must submit the request via the delete: <a href="https://my.ripe.net/"> LIR Portal delete: </a> . delete: </li> delete: </ul> delete: <p> The RIPE NCC will evaluate the request and process the transfer if it is adequately supported by the submitted information (see below under i-v). delete: </p> delete: <p> The RIPE NCC will ask for the following information: delete: </p> delete: <p> delete: <strong> i. Information regarding the parties involved, including: delete: </strong> delete: </p> delete: <ul> delete: <li> The full official legal names of all parties involved delete: </li> delete: <li> Which party will transfer the Internet number resources and which party will insert: <br />
receive them delete: </li> delete: <li> Recent registration papers issued by the relevant national authorities for all involved parties delete: </li> delete: </ul> delete: <p> If the current official legal names of the involved members are different from those in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in delete: <a href="#memberchanges"> Section 4.0 delete: </a> must be followed prior to the transfer of the Internet number resources. delete: </p> delete: <p> The procedure described under Section 4.0 is not necessary for the transferring member if the RIPE NCC Standard Service Agreement for that member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, " delete: <a href="http://www.ripe.net/publications/docs/closure" data-linktype="external" data-val="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ". delete: </p> delete: <p> delete: <strong> ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of Internet number resources according to the RIPE policies) delete: </strong> delete: </p> delete: <p> If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), a description of the changes among these organisation(s) is necessary. This description must be accompanied by the official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on. delete: </p> delete: <p> If the change in the structure of the organisation(s) involved cannot be proven/supported by official documentation from national authorities describing this change (e.g., a the same level of scrutiny as nameservers for blocks of insert: <br />
class C network acquisition from one member to another), then these cases will fall within the scope of RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ". delete: </p> delete: <p> delete: <strong> iii. A list of the Internet number resources that are requested to be transferred. If delete: <em> all delete: </em> of the transferring member's Internet number resources registered are being transferred, a confirmation of this is requested. delete: </strong> delete: </p> delete: <p> The member must also indicate any End User assignment agreements that are requested to be transferred. delete: </p> delete: <p> If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated upon request of the member or following the member's confirmation (see Section A.1.1. of the RIPE NCC Procedural Document, " delete: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> "). delete: </p> delete: <p> delete: <strong> iv. The correct contact details of all parties involved delete: </strong> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <strong> v. A Transfer Agreement signed by both parties or by their legal successors delete: </strong> delete: </p> delete: <p> The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC. delete: </p> delete: <p> The Transfer Agreement must be signed by authorised persons for both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to act on behalf of this party. The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so. delete: </p> delete: <p> 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 registered contact person or authorised person (e.g., senior manager, legal successor). delete: </p> delete: <p> If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send: delete: </p> delete: <ul> delete: <li> An official document (issued by a national authority) confirming the closure of the transferring party delete: </li> delete: <li> A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object and provide an agreement that proves that the Internet number resource should have been transferred to them. delete: </li> delete: </ul> delete: <p> delete: <strong> vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments delete: </strong> delete: </p> delete: <p> 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. delete: </p> delete: <h4> delete: <a name="transfer32"> delete: </a> 3.2 If the Receiving Party is not a Member delete: </h4> delete: <p> Members may wish to transfer their Internet number resource to another member or to a third party that is not a member. delete: </p> delete: <p> If the Internet number resources are transferred to a non-member, the receiving party must apply to be a member by signing a RIPE NCC Standard Service Agreement before the transfer takes place ( delete: <a href="https://www.ripe.net/../../../become-a-member"> more information on how to become a member is available delete: </a> ). If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources to them. delete: </p> delete: <p> If the Internet number resources to be transferred are Independent Resources (IPv4 PI and AS Numbers), the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on delete: <a href="https://www.ripe.net/../../../participate/resource-management/independent-resources"> Requesting Independent Resources delete: </a> . delete: </p> delete: <p> The request for the transfer can be submitted as described above (Section 3.1). delete: </p> delete: <h4> delete: <a name="transfer33"> delete: </a> 3.3 Financial Consequences delete: </h4> delete: <p> All outstanding invoices and all outstanding financial obligations must be paid in 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. This payment is the responsibility of the receiving member. If the receiving party is not a member, then payment is the responsibility of the transferring member. delete: </p> delete: <p> If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see delete: <a href="http://www.ripe.net/publications/docs/charging"> RIPE NCC Charging Scheme delete: </a> ). delete: </p> delete: <h4> delete: <a name="transfer34"> delete: </a> 3.4 Internet Number Resource Registration and RIPE Database Issues delete: </h4> delete: <p> delete: <strong> The RIPE NCC will review the status of any 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. delete: </strong> delete: </p> delete: <p> The transferring party or (if the transferring party does not exist anymore) the receiving member must deregister from the RIPE Database any invalid or overlapping registrations. delete: </p> delete: <p> 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. delete: </p> delete: <h4> delete: <a name="transfer35"> delete: </a> 3.5 Transfers Between LIR Accounts Belonging to the Same Member delete: </h4> delete: <p> Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> " and will be evaluated in accordance with them. delete: </p> delete: <p> Any time restriction that is applied to Internet number resources when they are received must expire before they can be transferred. However, once this restriction has expired, new time restrictions will not be applied to these resources if they are further transferred between LIR accounts held by the same member. delete: </p> delete: <p> The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v. delete: </p> delete: <p> If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for all LIR accounts must be paid in full. delete: </p> delete: <p> The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the member, in compliance with the RIPE Policies current at the time of the transfer. delete: </p> delete: <p> The member must deregister from the RIPE Database any invalid or overlapping registrations. delete: </p> delete: <p> The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer. delete: </p> delete: <h4> delete: <a id="transfer36"> delete: </a> 3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure delete: </h4> delete: <p> Internet number resources that are subject to transfer restrictions imposed by the RIPE Policy " delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ", and that are transferred due to a change in a member's business structure, must either remain registered with the original LIR account or be registered with a new LIR account. The receiving party will be provided with RIPE NCC services for these Internet number resources via either the original LIR account or the new LIR account until the policy restrictions are lifted. delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="memberchanges"> delete: </a> 4.0 Member Changes Official Legal Name delete: </h3> delete: <p> numbers. It is the obligation of the member to inform the RIPE responsibility of the network insert: <br />
contacts to ensure proper operation. insert: <br />
insert: <br />
5. Any problems regarding the reverse zones in 193.in-addr.arpa insert: <br />
should be directed to <hostmaster@ripe.net>. insert: <br />
insert: <br />
The NCC immediately if any change in the member's official legal name occurs. also suggests that similar procedures are set up for the insert: <br />
delegation of reverse zones for individual class C networks from insert: <br />
the registries to individual organisations.

delete: <p> The member must send a request for name change via the LIR Portal. The request must include: delete: </p> delete: <ul> delete: <li> New registration papers from the national authority; and delete: </li> delete: <li> The official legal documents supporting this change delete: </li> delete: </ul> delete: <p> If the requesting party does not have access to the LIR Portal, the request must be submitted via email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC. delete: </p> delete: <p> The RIPE NCC will send a new delete: <a href="http://www.ripe.net/publications/docs/service-agreement"> RIPE NCC Standard Service Agreement delete: </a> for the 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 are related to this change. The member must update all RIPE Database objects maintained by them that are related to this change. delete: </p> delete: <p> If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement. delete: </p>
Transfer of Internet Number Resources and Change of a Member’s Official Legal Name Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain