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

Legend
Added
Deleted

 European Internet Registry:

                   Procedures for DNS Delegation

                     in the IN-ADDR.ARPA Domain



                           David Kessens

                             June 1994

                       Document-ID: ripe-105++
                         Obsoletes: ripe-105




                              ABSTRACT

           1.0 Definitions
For the purposes of this document, Internet number resources refer to:
The registered allocation and assignment records of a member
In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".
2.0 Introduction
In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:
The natural or legal persons holding the registration of Internet number resources
The Internet number resources that are registered to these natural or legal persons
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.
A member must inform the RIPE NCC if one or bothof the following changes occurs:
Internet Number Resource are transferred. Such transfers may take place: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.
In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".
The member changes its official legal name. Such a change may occur, for example, because of a merger or acquisition of the member's organisation.
 This document describes the procedures for the
      delegation of zones in European subdomains of
      IN-ADDR.ARPA.



Introduction


The domain tree below IN-ADDR.ARPA is used to facilitate "reverse"
mapping from IP addresses to domain names [RFC883, RFC1033].  This
document describes the procedures for the delegation of zones in
European subdomains of IN-ADDR.ARPA.


Randomly Assigned Numbers


There are two groups of European network numbers: hierarchically assigned
numbers and randomly assigned ones. The hierarchically assigned numbers
are part of the 193.x.y.0 and 194.x.y.0 network blocks. All other
European network numbers, class A, class B and 192.x.y.0 class Cs are
randomly assigned.


Hierarchically Assigned Numbers

The subdomains of IN-ADDR.ARPA corresponding to the hierarchically
assigned network numbers are administered by the RIPE NCC.  These
numbers are currently:


        193.0.0.0 - 194.255.255.255


The other addresses are administered by the other regional registries
that might have other procedures for requesting a reverse delegation.

For clarity we refer in the procedures and examples as described below to
the 193.x block of addresses, although we could have as well used the
other block(s) that RIPE administers.

With the assignment of class C network numbers following RFC1466,
large chunks of the address space are delegated to regional Internet
Registries. The regional registries delegate blocks of class C net-
work numbers to local Internet Registries. In this way a hierarchy
in the address space is created, which is similar to the hierarchy
in the domain name space. Due to this hierarchy the reverse DNS map-
ping can also be delegated in a similar model as used for the
normal Domain Name System.

For instance, the RIPE NCC has been delegated the complete class  C
address space starting with 193. It is therefore possible to
delegate the 193.IN-ADDR.ARPA domain completely to the RIPE NCC,
instead of each and every reverse mapping in the 193.IN-ADDR.ARPA
domain to be such changes to be properly communicated and registered with the InterNIC. This implies that all
193.IN-ADDR.ARPA delegations in turn will be done by the RIPE NCC.

Even better, since local registries usually receive blocks of 256 class C
networks from the RIPE NCC, the NCC can delegate the reverse
registrations for such complete blocks to these local registries. This
implies that customers of these service providers no longer have to
register their reverse domain mapping with the InterNIC or the NCC, but
the service providers have authority over that part of the reverse
mapping. This decreases the workload on the InterNIC and the RIPE NCC,
and at the same time improves the service a provider can offer its
customers by improving response times for reverse mapping changes.

In order to provide a reliable service some procedures have been agreed
and must be followed in order to avoid confusion and inconsistencies.
These procedures are covered in the procedure section.

The registration of the reverse zones for individual class C net-
works will  usually  be  done  by the registry administering the
class C block this network has been assigned from.

If the subdomain has not yet been delegated to the registry con-
cerned the RIPE NCC will register the individual networks. However
this service is only provided at a "best-effort" level and no ser-
vice guarantees are given.  The local registries should whenever
possible provide this service locally.


Responsibilities for the DNS administrator of a reverse block delegation:


As with all domain name space, running the reverse server for class C
blocks does not imply that one controls that part of the reverse domain.
It only implies that one administers that part of the reverse domain. If
after repeated complaints the delegated name space is still not
administered properly the RIPE NCC has to revoke the delegation.

Before adding individual nets, the administrator of a reverse domain must
check whether all servers to be added for these nets are indeed set up
properly.

There are some serious implications when a customer that uses
address space out of the service provider class C blocks, moves
to another service provider. The  previous service  provider
cannot force its ex-customer to change network addresses, and
will have to continue to provide  the appropriate delegation
records  for reverse mapping of these addresses, even though
they are no longer belonging to a customer.

The registration of the reverse zones for individual  class C
networks  will  usually be done by the registry administering
the class C block this network has been assigned from.  The
registry will make the necessary changes to the zone files.
The registry will also make sure that the network objects in
the RIPE database for these networks are updated with the
correct "rev-srv" attributes.

In case the RIPE NCC receives a request for the reverse zone of
an individual class C network out of a block that has been
delegated, the request will be forwarded to the mailbox speci-
field in the SOA RR for the zone concerned and to the zone-
contact registered in the RIPE database for that zone.

The NCC also suggests that similar procedures are set up for  the
delegation  of reverse zones for individual class C networks from
the registries to individual organisations.









Procedures


The procedure for asking the reverse delegation of a block (256 C's) of
addresses or network (1 or more C's) addresses is quite similar but there
are some differences. Therefor they are described as one procedure with
clear remarks when something only applies for block or network delegations.
Note that we will be a little bit more stringent on the rules for block
delegations since we need to be sure that other people can rely on you
for proper operation of the DNS system.

Above procedures are defined to ensure the necessary high availabil- ity
for the reverse domains, and to minimise confusion.  The NCC will ensure
fast response times for addition requests, and will in principle update
the 193.IN-ADDR.ARPA domain at least once per working day, if needed. Any
problems regarding the reverse zones in 193.IN-ADDR.ARPA should be
reported to <[email protected]>.



 1.  We only reverse delegate when all addresses are assigned to you.

 2.  Your nameservers should be configured and running and should have
     good reachability on the internet. Nameservers for block delegations
     must meet similar connectivity requirements as top-level domain
     servers.

     The NCC recommends to use the following timers and counters (as
     advised by RFC1537):

	 28800	;refresh period (8 hours)
	 7200	;retry interval (2 hours)
	 604800	;expire time    (1 week)
	 86400	;default ttl    (1 day)

     It is mandatory for network (C) reverse delegations:

     - ns.ripe.net is NOT one of the secondary/primary nameservers

     - at least two nameservers should be used

     - We need a RIPE database 'inetnum' object with 'rev-srv:'
       attributes for the name (not IP address) of each nameserver.


     It is mandatory for block reverse delegations:

     - ns.ripe.net is one the secondary (never primary) nameservers

     - at least two other nameservers that don't reside on the same
       ethernet are required

     - Operators of the primary nameservers should be familiar with
       RFC1537 and this document

     - We need a RIPE database 'domain' object for each delegation
       with 'nserver:' attributes for the name (not IP address) of each
       nameserver


 3.  Send an E-mail request to <[email protected]> with:

     - In the header (or body if not possible) of your E-mail message:

       X-NCC-RegID: Country.RegistryName

       This is not required, though easy for keeping track of the
       requests. Of course, we don't need your local registry ID if you
       are not from a RIPE local registry.

     For network (C) reverse delegations:

     - We need a RIPE database 'inetnum' object with 'rev-srv:'
       attributes for the name (not IP address) of each nameserver

     For block reverse delegations:

     - State in your request that you know about RFC1537 & this document

     - A RIPE database 'domain' object for each delegation
       with 'nserver:' attributes for the name (not IP address) of each
       nameserver

 4.  Your request will first go through to an automatic checking program.
     The program will check your zone files and report you about errors
     (that should be fixed), warnings (that you might want to change), or
     that no errors have been found. If errors are found, you will be
     asked to fix them and resubmit your request and the automatic checks
     will be done again.

     If no errors (warnings are allowed, but we strongly suggest that you
     at least take a look at them) are found your request will be
     acknowledged and your request will be forwarded to the person in
     charge of the reverse delegation requests. He/she processes the
     request further. If no additional problems are found the object will
     included in the database and the block/network reverse delegated.
     You will always receive an acknowledgment when the delegation has
     been done or an explanation why not.


Example of a network delegation request:


From: "Anne X. Ample" <[email protected]>
To: RIPE Hostmaster <[email protected]>
Subject: LONGACK 2.1.193.in-addr.arpa delegation please

Please delegate 2.1.193.in-addr.arpa as specified below.

Thank you!

For the AMPLE Corporation

Anne X. Ample


inetnum:   193.1.2.0 - 193.1.3.255
netname:   AMPLE
descr:     AMPLE Corporation
descr:     Amsterdam, Netherlands
country:   NL
admin-c:   Anne X. Ample
tech-c:    G. E. K. Ample
aut-sys:   4711
rev-srv:   ns.ample.nl
rev-srv:   ns.elpma.ln
changed:   [email protected] 930101
source:    RIPE



Example of a block (256 C's) reverse delegation:


From: Marten Terpstra <[email protected]>
To: RIPE Hostmaster <[email protected]>
Subject: LONGACK 202.193.in-addr.arpa delegation please


Dear NCC people,

I have read and understood ripe-105++ and RFC1537.
Could you please delegate 202.193.in-addr.arpa as specified below.

Thank you!

Marten Terpstra


domain:  202.193.in-addr.arpa
descr:   Pan European Organisations class C block
admin-c: Daniel Karrenberg
tech-c:  Marten Terpstra
zone-c:  Marten Terpstra
nserver: ns.eu.net
nserver: sunic.sunet.se
nserver: ns.ripe.net
changed: [email protected] 930319
source:  RIPE



Some notes on the automatic checking program:

You can use some keywords in the 'Subject:' line of your E-mail to
control the checking process. The use of the LONGACK keyword is very
recommended. For changing an existing delegation put the keyword CHANGE
in the 'Subject:' line of your E-mail message.

HELP    - will send you this document
CHANGE  - is needed if you want to change an existing reverse delegation
LONGACK - will give you the most verbose output as possible
TEST    - will only test your zone files without actually doing
          the request


When you want to to a request for a block delegation and you want to know
if there are already reverse zones registered within the zone of the
requested block delegation, just send in your request and you will
receive an error report that includes a copy of our zone file regarding
this zone!

~~RIPE NCC.~~

Additionally, this document describes the procedure for requesting a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.

Note:
If a change in a member's official legal name is accompanied by a transfer of Internet number resources, the member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in a member's business structure is notaccompanied by a transfer of Internet number resources or a change in the member's official legal name, then the RIPE NCC does not need to be informed of this change.

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 Users business structure. This procedure is described in the RIPE NCC Procedural Document, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

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, "Inter-RIR Transfer of Internet Number Resources Link: http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr ".

3.0 Transfer of Internet Number Resources

~~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.~~

3.1 Submission of the Request for Transfer

~~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:~~

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 LIR Portal Link: https://my.ripe.net/#/update-registry . If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to [email protected] Link: mailto:[email protected]
If this is a transfer of Internet number resource from one member to another party according to RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ", the transferring party must submit the request via the LIR Portal Link: https://my.ripe.net/ .

~~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).~~

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

i. Information regarding the parties involved, including:

~~The full official legal names of all parties involved~~
~~Which party will transfer the Internet number resources and which party will receive them~~
~~Recent registration papers issued by the relevant national authorities for all involved parties~~

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 Section 4.0 Link: #memberchanges must be followed prior to the transfer of the Internet number resources.

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, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ".

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)

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.

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 network acquisition from one member to another), then these cases will fall within the scope of RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".

iii. A list of the Internet number resources that are requested to be transferred.

~~If allof the transferring member's Internet number resources registered are being transferred, a confirmation of this is requested.~~

~~The member must also indicate any End User assignment agreements that are requested to be transferred.~~

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, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ").

iv. The correct contact details of all parties involved

~~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.~~

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

~~The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC.~~

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.

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).

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

~~An official document (issued by a national authority) confirming the closure of the transferring party~~
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.

vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments

~~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.~~

3.2 If the Receiving Party is not a Member

~~Members may wish to transfer their Internet number resource to another member or to a third party that is not a member.~~

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 (more information on how to become a member is available Link: ../../../../../../../../../../../../../../../become-a-member ). If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources to them.

If the Internet number resources to be transferred are Independent Resources (IPv4 PI, IPv6 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 Requesting Independent Resources Link: ../../../../../../../../../../../../../../../participate/resource-management/independent-resources .

~~The request for the transfer can be submitted as described above (Section 3.1).~~

3.3 Financial Consequences

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.

~~If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see RIPE NCC Charging Scheme Link: http://www.ripe.net/publications/docs/charging ).~~

3.4 Internet Number Resource Registration and RIPE Database Issues

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.

~~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.~~

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.

3.5 Transfers Between LIR Accounts Belonging to the Same Member

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies " and will be evaluated in accordance with them.

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.

~~The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v.~~

~~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.~~

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.

~~The member must deregister from the RIPE Database any invalid or overlapping registrations.~~

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.

3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure

Internet number resources that are subject to transfer restrictions imposed by the RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ", 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.

3.7 Transfers due to Seizure

If the RIPE NCC is delivered a court order for the seizure of the right to registration of Internet number resources for the recovery of money, in accordance with Dutch legal procedures, the RIPE NCC will comply with its obligations. This order may create obligations for the RIPE NCC, such as the restriction of the transfer of Internet number resources from the member’s account, the issuance of a statement outlining the Internet number resources registered to a member’s account, and the transfer of the Internet number resources away from the member’s account.

~~The RIPE NCC will comply on the condition that the court order:~~

~~Has entered into force and is recognised by the Dutch courts.~~
~~Is served by a bailiff in advance to the RIPE NCC in the form of an authentic enforceable document (e.g., a court order).~~
Specifically mentions the RIPE NCC and creates an obligation for the RIPE NCC to perform the transfer. (i.e., the enforceable title must apply specifically to the RIPE NCC). This does not mean the RIPE NCC needs to be named as a defendant.
~~States the specific Internet number resources at issue.~~

Each order will be reviewed on a case-by-case basis. If the RIPE NCC believes that an order or the third party seeking to enforce the order does not comply with RIPE policies or RIPE NCC procedures, the RIPE NCC reserves the right to dispute it.

4.0 Member Changes Official Legal Name

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

~~The member must send a request for name change via the LIR Portal. The request must include:~~

~~New registration papers from the national authority; and~~
~~The official legal documents supporting this change~~

If the requesting party does not have access to the LIR Portal, the request must be submitted via email to [email protected] Link: mailto:[email protected] and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC.

The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/publications/docs/service-agreement 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.

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.

5.0 Voluntary Transfer Lock of Internet Number Resources

5.1 The Scope of The Voluntary Transfer Lock

~~The RIPE NCC may approve a request for a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.~~

~~If the RIPE NCC deems that a voluntary transfer lock request is not in line with RIPE policies, RIPE NCC procedural documents, or applicable law, the RIPE NCC reserves the right to reject the request.~~

The RIPE NCC reserves the right not to enforce a voluntary transfer lock even if the relevant request has been approved by the RIPE NCC. The RIPE NCC may not enforce a voluntary transfer lock, for example, in case of Transfers of Internet Number Resources Due to a Change in the Member's Business Structure (see above Section 3.6) or Transfers Due to Seizure (see above Section 3.7).

This document does not describe the procedure to be followed in the case of voluntary transfer locks for independent Internet number resources assigned to End Users. This procedure is described in the RIPE NCC Procedural Document, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

5.2 Submission of the Request for Voluntary Transfer Lock

For the voluntary transfer lock to be approved, a registered contact or an authorised person (for e.g., a senior manager, the legal successor) of the requesting party must submit a request to the RIPE NCC.

~~The RIPE NCC will evaluate the request and approve the voluntary transfer lock if it is adequately supported by the information submitted and documentation as described below.~~

~~The RIPE NCC will ask for the following:~~

~~The Voluntary Transfer Lock Request Form~~

~~The requesting party must complete the Voluntary Transfer Lock Request Form. The template of the Voluntary Transfer Lock Request Form is provided by the RIPE NCC.~~

~~The Voluntary Transfer Lock Request Form must be submitted to the RIPE NCC via the LIR Portal by a registered contact or an authorised person of the requesting party.~~

~~The Voluntary Transfer Lock Request Form must be signed by the authorised person for the requesting party 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 the requesting party is authorised to do so.~~

~~To complete the Voluntary Transfer Lock Request Form, the requesting party will have to provide:~~

~~The full official legal name~~
~~Recent registration papers issued by the relevant national authority~~

If the current official legal name of the requesting party is different from the one in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in Section 4.0 Link: #memberchanges must be followed prior to requesting voluntary transfer lock.

~~The RIPE NCC may ask the requesting party 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.~~

In the Voluntary Transfer Lock Request Form the requesting party is required to indicate the duration of the voluntary transfer lock, which can be 6, 12 or 24 months. The voluntary transfer lock will be applied from the date on which the RIPE NCC approves the voluntary transfer lock request.

~~The voluntary transfer lock will expire after 6, 12 or 24 months, depending on the duration requested.~~

~~To continue with the voluntary transfer lock after the expiration of the requested lock duration, a member will have to submit a new voluntary transfer lock request to the RIPE NCC for approval.~~

~~Members cannot request the cancellation of the voluntary transfer lock once the lock has been applied until the voluntary transfer lock expires.~~

5.3 The Publication of Internet Number Resources under the Voluntary Transfer Lock

~~The RIPE NCC will publish a list of Internet number resources under voluntary transfer lock on its website.~~

6.0 Temporary Transfers

As per Section 2.1 of RIPE Resource Transfer Policies Link: https://www.ripe.net/publications/docs/transfer-policies , transfers of Internet Number Resources in the RIPE NCC region are allowed on a permanent or temporary basis (“Temporary Transfers”). Temporary Transfers must be declared to the RIPE NCC for approval according to the procedure described in Section 3.0.

6.1 Term of a Temporary Transfer

In case of a Temporary Transfer, the Internet Number Resources are registered with the Receiving Party until a set date (as mutually agreed by the involved parties and specified in Article 1 of Transfer Agreement Link: https://www.ripe.net/media/documents/Transfer_Agreement_Template_v6.0_FINAL.pdf ) and on such date, the Internet Number Resources automatically return to the Offering Party. The Receiving Party may not further transfer these Internet Number Resources to a third party.

6.2 Earlier Termination of a Temporary Transfer

6.2.1 Standard Service Agreement termination

If the Offering Party is a member and its Standard Service Agreement is terminated (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were temporarily transferred to the Receiving Party, shall not be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement. Instead, the RIPE NCC shall deregister the relevant Internet Number Resources per such date.

If the Receiving Party is a member and its Standard Service Agreement is terminated (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were temporarily transferred to the Receiving Party, shall be returned to the Offering Party as per the date that the Standard Service Agreement was terminated.

6.2.2 End User Assignment Agreement termination

As per Section 2 of Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , an End User of independent Internet number resources must have a contractual relationship with a sponsoring LIR at all times. If the contractual relationship between the End User and the sponsoring LIR is terminated for any reason, the RIPE NCC must be notified. The End User must at this point enter into a contractual relationship with a different sponsoring LIR or with the RIPE NCC directly.

If the Offering Party is an End User and its contractual relationship with its sponsoring LIR is terminated before the date indicated in Article 1 of the Transfer Agreement, and the Offering Party does not enter into a contractual relationship with a sponsoring LIR within the timeframe set by section 2 of the Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , the RIPE NCC shall deregister the relevant Internet Number Resources.

If the Receiving Party is an End User and its contractual relationship with its sponsoring LIR is terminated before the date indicated in Article 1 of the Transfer Agreement, and the Receiving Party does not enter into a contractual relationship with a sponsoring LIR within the timeframe set by section 2 of the Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://ripe.net/publications/docs/lir-end-user-contractual-changes#2--termination-of-contractual-relationship , the Internet Number Resources shall be returned to the Offering Party.

6.2.3 Reasons for Deregistration of the temporarily transferred Internet Number Resources

If there is a reason to deregister temporarily transferred Internet Number Resources (for any reason outlined in the Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure/ ) before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources shall be returned to the Offering Party upon request by the RIPE NCC.

6.3 Sanctions on either party involved in the Temporary Transfer

As per Section 3.1 of the Due Diligence for the Quality of the RIPE NCC Registration Data Link: https://www.ripe.net/publications/docs/due-diligence , the RIPE NCC, as an association under Dutch Law, has to comply with sanctions imposed by the Netherlands and the EU.

In case the Offering Party becomes subject to sanctions, with which the RIPE NCC has to comply, before or on the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources it transferred to the Receiving Party, shall not be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement, but shall be placed on such date under the RIPE NCC’s control. The Internet Number Resources will be returned to the Offering Party, when the Offering party ceases to be subject to sanctions applicable to the RIPE NCC.

In case the Receiving Party becomes subject to sanctions, with which the RIPE NCC has to comply, before the date indicated in Article 1 of the Transfer Agreement, the Internet Number Resources that were transferred to the Receiving Party, will be returned to the Offering Party on the date indicated in Article 1 of the Transfer Agreement.