You are here: Home > Publications > RIPE Document Store > Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

Changes to Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

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

ripe-085: Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domai ripe-515: Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR

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

Abstract insert: `</h2>`

insert: 

This document describes the procedures for the delegation of au- delete:   thority of zones provides guidelines to Local Internet Registries (LIRs) on the steps to take when the organisation operating an LIR changes ownership (due to a merger, sale or takeover) or stops serving entirely as an LIR. insert: 

insert: 

_________________________________________________________________ insert: 

insert: <h2 class="western">

Table of Contents insert: `</h2>`

insert: 

insert: 

insert: 

insert: <a class="anchor-link" href="#1.0"> 1.0 Introduction insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.0"> 2.0 LIR Ownership Change insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.1"> 2.1 IP Address Space insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.2"> 2.2 Service Agreement insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.3"> 2.3 Change in the 193.in-addr.arpa domain. As of March delete:   16th 1993 the RIPE NCC has been delegated the authority for the delete:   193.in-addr.arpa domain from the root. Due to the fact that in delete:   the 193.x.y Operating Organisation insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.4"> 2.4 Contact Person(s) insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.5"> 2.5 RegID insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.6"> 2.6 Transfers of Address Allocations insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#2.7"> 2.7 Takeover fee insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#3.0"> 3.0 Closing an LIR insert: </a> insert: 

insert: 

This section is replaced by the RIPE NCC organisational document " insert: <a href="https://www.ripe.net/publications/docs/closure"> Closure of LIR and Deregistration of Internet Number Resources insert: </a> ". insert: 

insert: 

insert: <a class="anchor-link" href="#4.0"> 4.0 When an LIR is Closed by the RIPE NCC insert: </a> insert: 

insert: 

insert: <h2 class="western">

insert: `<a name="1.0">` insert: `</a>` 1.0 Introduction insert: `</h2>`

insert: 

When an organisation or company operating an LIR changes ownership status or stops serving as an LIR there are financial, IP address space blocks of 256 class C network numbers delete:   and RIPE Database issues that need resolving. Therefore, the RIPE NCC must always be contacted when an LIR changes ownership or closes. insert: 

insert: <h2 class="western">

insert: `<a name="2.0">` insert: `</a>` 2.0 LIR Ownership Change insert: `</h2>`

insert: 

In the case of an LIR ownership change, the LIR should contact the RIPE NCC at insert: <a href="mailto:[email protected]"> [email protected] insert: </a> . insert: 

insert: 

Only registered LIR contact person(s) can discuss the change of an LIR ownership with the RIPE NCC. insert: 

insert: 

The following steps are further delegated to local registries , the possibility ex- delete:   ists to also delegate the zone required to change the organisation operating an LIR: insert: 

insert: 

insert: 

insert: 

1. Clarify the type of change: insert: 

insert: <ul>

insert: <li>

insert: 
A takeover of one LIR by another LIR, closing one of the LIRs. insert: 
insert: </li>

insert: <li>

insert: 
A takeover of one LIR by another LIR, both remain open. insert: 
insert: </li>

insert: <li>

insert: 
A takeover of an LIR by a non-LIR. insert: 
insert: </li>

insert: </ul>

insert: 

insert: 

insert: 

2. Outline the details of the change, stating: insert: 

insert: <ul>

insert: <li>

insert: 
The reason for the change of organisation. insert: 
insert: </li>

insert: <li>

insert: 
The name of the company/companies involved. insert: 
insert: </li>

insert: <li>

insert: 
The number of LIRs affected by the change. insert: 
insert: </li>

insert: <li>

insert: 
The RegID(s) of the LIR(s) affected by the change. insert: 
insert: </li>

insert: </ul>

insert: 

insert: 

insert: 

3. Present the following documents to the RIPE NCC: insert: 

insert: <ul>

insert: <li>

insert: 
Confirmation from all parties agreeing to the change (See section 2.3). insert: 
insert: </li>

insert: <li>

insert: 
Updated list of contact person(s) (See section 2.4). insert: 
insert: </li>

insert: <li>

insert: 
Updated billing e-mail contact details, including any changes to VAT number. insert: 
insert: </li>

insert: <li>

insert: 
A new service agreement, if applicable (See section 2.2). insert: 
insert: </li>

insert: <li>

insert: 
Legal documentation supporting the name change, if applicable (See section 2.2). insert: 
insert: </li>

insert: <li>

insert: 
Overview of utilisation in all allocations (See section 2.6). insert: 
insert: </li>

insert: </ul>

insert: <h3 class="western">

insert: `<a name="2.1">` insert: `</a>` 2.1 IP Address Space insert: `</h3>`

insert: 

Following any type of change (such as mergers, acquisitions or takeovers) of an organisation operating an LIR, the RIPE NCC will review the status of any IP address allocations that are held by the new organisation. insert: 

insert: <h3 class="western">

insert: `<a name="2.2">` insert: `</a>` 2.2 Service Agreement insert: `</h3>`

insert: 

When an organisation operating an LIR changes ownership, a new service agreement may need to be signed. The RIPE NCC will need to request a new service agreement from the new owners if: insert: 

insert: <ul>

insert: <li>

insert: 
The organisation operating the LIR changes name, or insert: 
insert: </li>

insert: <li>

insert: 
The LIR wishes to change their RegID. insert: 
insert: </li>

insert: </ul>

insert: 

The registration documentation from the relevant Chamber of Commerce, or its country equivalent, supporting the name change must be submitted to the RIPE NCC. insert: 

insert: 

The Standard RIPE NCC Service Agreement is available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/service-agreement"> http://www.ripe.net/ripe/docs/service-agreement insert: </a> insert: 

insert: 

insert: 

insert: 

If the organisation operating the LIR does not change its name and keeps the original RegID, the LIR can continue operating under the same service agreement. insert: 

insert: <h3 class="western">

insert: `<a name="2.3">` insert: `</a>` 2.3 Change in Operating Organisation insert: `</h3>`

insert: 

In cases where an organisation operating an LIR takes over one or more LIRs, confirmation of the takeover from all parties involved or their legal successors must be included. insert: 

insert: <h3 class="western">

insert: `<a name="2.4">` insert: `</a>` 2.4 Contact Person(s) insert: `</h3>`

insert: 

It is very important to notify the RIPE NCC, if there is a change of contact person(s). This is essential, as only registered contact person(s) can submit Internet resource requests to the RIPE NCC and provide updates to our internal registry files. insert: 

insert: 

insert: 

insert: 

If the contact person(s) of the affected LIR has changed, the RIPE NCC may adjust the Assignment Window of the LIR until the contact person(s) is up-to-date with RIPE NCC procedures and RIPE community policies. insert: 

insert: 

insert: 

insert: 

If there are no current registered contacts remaining with the LIR, a fax signed by the Managing Director of the LIR on organisation letterhead is required to implement these blocks in the 193.in- delete:   addr.arpa domain. This document describes some guidelines insert: 

insert: 

changes. These changes should include the new registered contact person(s) for the LIR. insert: 

insert: <h3 class="western">

insert: `<a name="2.5">` insert: `</a>` 2.5 RegID insert: `</h3>`

insert: 

It is not necessary to obtain a new Registry Identifier (RegID) if the name of the organisation that operates the LIR changes. The RegID is merely an internal identifier used by the RIPE NCC to distinguish the various LIRs. It does not have to correspond to the legal name of the organisation operating the LIR. insert: 

insert: 

insert: 

insert: 

If an LIR insists on changing their RegID, a fee corresponding to the sign-up fee for a new LIR will be charged to cover additional administrative work generated. Please see the current version of the RIPE NCC Charging Scheme available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/charging"> http://www.ripe.net/ripe/docs/charging insert: </a> insert: 

insert: <h3 class="western">

insert: `<a name="2.6">` insert: `</a>` 2.6 Transfers of Address Allocations insert: `</h3>`

insert: 

All transfers of address allocations from one LIR to another LIR (or to a non-LIR) require approval by the RIPE NCC. It is expected that all database objects relating to this allocation be correct and delete:   procedures for this type of delegation and the delegation of re- delete:   verse zones for individual class C networks in 193.x.y. delete:   delete:   delete:   A bit more explained delete:   delete:   With the assignment of class C network numbers following the CIDR delete:   (RFC 1338) model, in which up-to-date before the transfer occurs. Transferred allocations containing a large chunks of the amount of unassigned address space may be set aside and kept by the RIPE NCC until the other allocations held by the LIR are delete:   delegated to considered fully used (about 80%). Once the LIR has reached full utilisation in its other allocations, the reserved allocations will be made available to the LIR. For further details on allocation policy, please refer to the document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" available from the RIPE Document Store at: insert: 

insert: 

insert: <a href="http://www.ripe.net/ripe/docs/ipv4-policies"> http://www.ripe.net/ripe/docs/ipv4-policies insert: </a> insert: 

insert: <h3 class="western">

insert: `<a name="2.7">` insert: `</a>` 2.7 Takeover Fee insert: `</h3>`

insert: 

In cases where an organisation operating an LIR takes over one region, or more LIRs, a takeover fee is due for every LIR taken over (e.g. if three LIRs are taken over, the fee is paid three times). All current outstanding invoices for the LIRs being taken over will also have to be paid in full. insert: 

insert: 

insert: 

insert: 

The transfer of address allocations also incurs a takeover fee and within that region blocks of class C delete:   network numbers are delegated to service providers and non- delete:   provider registries, some hierarchy in the does not vary according to the amount of address space is delete:   created, similar to the hierarchy in the domain name space. Due delete:   to this hierarchy the reverse Domain Name System mapping can also delete:   be delegated in a similar model as used for the normal Domain delete:   Name System. For instance, the RIPE NCC has been assigned the delete:   complete class C address space starting with 193. It is there- delete:   fore possible to delegate the 193.in-addr.arpa domain completely delete:   to the RIPE NCC, instead of each being transferred (e.g. if three allocations are being transferred from LIR A to LIR B, the fee is only paid once). insert: 

insert: <h2 class="western">

insert: `<a name="3.0">` insert: `</a>` 3.0 Closing an LIR insert: `</h2>`

insert: 

This section is replaced by the RIPE NCC organisational document "Closure of LIR and every reverse mapping in the delete:   193.in-addr.arpa domain to be registered with the INTERNIC. Deregistration of Internet Number Resources" available from the RIPE Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure insert: </a> . insert: 

insert: <h2 class="western">

insert: `<a name="4.0">` insert: `</a>` 4.0 When an LIR is Closed by the RIPE NCC insert: `</h2>`

insert: 

This delete:   implies that all 193.in-addr.arpa resistrations will be done by delete:   the RIPE NCC. Even better, since service providers receive com- delete:   plete class C network blocks section is replaced by the RIPE NCC organisational document "Closure of LIR and Deregistration of Internet Number Resources"available from the RIPE NCC, the RIPE NCC can delete:   delegate the reverse registrations for such complete blocks to delete:   these local registries. This implies that customers of these delete:   service providers no longer have to register their reverse domain delete:   mapping with the root, but the service provider have authority delete:   over that part of the reverse mapping. This decreases the work- delete:   load on the INTERNIC and the RIPE NCC, and at the same time in- delete:   crease the service a provider can offer its customers by improve delete:   response times for reverse mapping changes Document Store at: insert: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure insert: </a> . However there are delete:   some things that need to be examined a bit more closely to avoid delete:   confusion and inconsistencies. These issues are covered in the delete:   next section. delete:   delete:   delete:   Procedures for the delegation of direct subdomains of 193.in- delete:   addr.arpa delete:   delete:   1. A secondary nameserver at ns.ripe.net is mandatory for all delete:   blocks of class C network numbers delegated in the 193.in- delete:   addr.arpa domain. delete:   delete:   2. Because of the increasing importance of correct reverse ad- delete:   dress mapping, for all delegated blocks a good set of secondaries delete:   must be defined. There should be at least 2 nameservers for all delete:   blocks delegated, excluding the RIPE NCC secondary. delete:   delete:   3. The delegation of a class C block in the 193.in-addr.arpa delete:   domain can be requested by sending in a domain object for the delete:   RIPE database to <[email protected]> with all necessary contact delete:   and nameserver information. The RIPE NCC will then forward all delete:   current reverse zones inside this block to the registry, and delete:   after addition of these by the registry, the NCC will check the delete:   working of the reverse server. Once everything is setup proper- delete:   ly, the NCC will delegate the block, and submit the database ob- delete:   ject for inclusion in the database. An example domain object can delete:   be found at the end of this document. delete:   delete:   4. All reverse servers for blocks must be reachable from the delete:   whole of the Internet. In short, all servers must meet similar delete:   connectivity requirements as top-level domain servers. delete:   delete:   5. Running the reverse server for class C blocks does not imply delete:   that one controls that part of the reverse domain, it only im- delete:   plies that one administers that part of the reverse domain. delete:   delete:   6. Before adding individual nets, the administrator of a reverse delete:   domain must check wether all servers to be added for these nets delete:   are indeed setup properly. delete:   delete:   7. There are some serious implications when a customer of a ser- delete:   vice provider that uses address space out of the service provider delete:   class C blocks, moves to another service provider. The previous delete:   service provider cannot force its ex-customer to change network delete:   addresses, and will have to continue to provide the appropriate delete:   delegation records for reverse mapping of these addresses, even delete:   though it they are no longer belonging to a customer. delete:   delete:   8. The registration of the reverse zones for individual class C delete:   networks will usually be done by the registry administering the delete:   class C block this network has been assigned from. The registry delete:   will make the necessary changes to the zone, and update the net- delete:   work objects in the RIPE database for these networks, to reflect delete:   the correct "rev-srv" fields. In case the RIPE NCC receives a delete:   request for the reverse zone of an individual class C network out delete:   of a block that has been delegated, the request will be forwarded delete:   to the zone contact for this reverse block. delete:   delete:   9. The NCC advises the following timers and counters for direct delete:   subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), delete:   2 hours retry (7200 seconds), 7 days expire (604800 seconds) and delete:   1 day Time To Live (86400 seconds). The retry counter should be delete:   lowered where connectivity is unstable. delete:   delete:   Above procedures are defined to ensure the necessary high availa- delete:   bility for the 193 reverse domains, and to minimize confusion. delete:   The NCC will ensure fast repsonse times for addition requests, delete:   and will in principle update the 193.in-addr.arpa domain at least delete:   once per working day. delete:   delete:   Example domain object to request a block delegation delete:   delete:   domain: 202.193.in-addr.arpa delete:   descr: Pan European Organisations class C block delete:   admin-c: Daniel Karrenberg delete:   tech-c: Marten Terpstra delete:   zone-c: Marten Terpstra delete:   nserver: ns.eu.net delete:   nserver: sunic.sunet.se delete:   nserver: ns.ripe.net delete:   changed: [email protected] 930319 delete:   source: RIPE delete:   delete:   delete:   delete:   Procedures for the delegation of individual network zones by the delete:   RIPE NCC. delete:   delete:   The registration of the reverse zones for individual class C net- delete:   works will usually be done by the registry administering the delete:   class C block this network has been assigned from. In case the delete:   zone corresponding to the class C block has not been delegated, delete:   the RIPE NCC will automatically add the reverse nameserver as delete:   specified in the "rev-srv" attribute of the RIPE database object delete:   for this network, using the following procedures: delete:   delete:   1. Because of the increasing importance of correct reverse ad- delete:   dress mapping, for all delegated networks a good set of secon- delete:   daries must be defined. There should be at least two nameservers delete:   for all networks delegated. delete:   delete:   2. The "rev-srv" field should ONLY contain one fully qualified delete:   domain name of a nameserver which is authoritative for the re- delete:   verse zone for this network. delete:   delete:   3. If a network has or is going to have any external connectivi- delete:   ty, it is strongly recommended that it has at least one reverse delete:   nameserver that can be reached from all of the Internet. delete:   delete:   4. The checking and addition of the reverse zones for single net- delete:   works is completely automated at the RIPE NCC. Although we do delete:   our best to check the setup of the nameservers, these does not delete:   receive the same level of scrutiny as nameservers for blocks of delete:   class C network numbers. It is the responsibility of the network delete:   contacts to ensure proper operation. delete:   delete:   5. Any problems regarding the reverse zones in 193.in-addr.arpa delete:   should be directed to <[email protected]>. delete:   delete:   The NCC also suggests that similar procedures are set up for the delete:   delegation of reverse zones for individual class C networks from delete:   the registries to individual organisations. delete:  insert: 

Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR

RIPE Documents Search

ripe-085

State:

Obsoleted

Updated by:

ripe-105 , ripe-127 , 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

Authors:

Marten Terpstra

Date:

May 1993

Download

File:
ASCII | 8.0KB

Changes to Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

Abstract insert: </h2>

Table of Contents insert: </h2>

insert: <a name="1.0"> insert: </a> 1.0 Introduction insert: </h2>

insert: <a name="2.0"> insert: </a> 2.0 LIR Ownership Change insert: </h2>

insert: <a name="2.1"> insert: </a> 2.1 IP Address Space insert: </h3>

insert: <a name="2.2"> insert: </a> 2.2 Service Agreement insert: </h3>

insert: <a name="2.3"> insert: </a> 2.3 Change in Operating Organisation insert: </h3>

insert: <a name="2.4"> insert: </a> 2.4 Contact Person(s) insert: </h3>

insert: <a name="2.5"> insert: </a> 2.5 RegID insert: </h3>

insert: <a name="2.6"> insert: </a> 2.6 Transfers of Address Allocations insert: </h3>

insert: <a name="2.7"> insert: </a> 2.7 Takeover Fee insert: </h3>

insert: <a name="3.0"> insert: </a> 3.0 Closing an LIR insert: </h2>

insert: <a name="4.0"> insert: </a> 4.0 When an LIR is Closed by the RIPE NCC insert: </h2>

RIPE Documents Search

ripe-085

Abstract insert: `</h2>`

Table of Contents insert: `</h2>`

insert: `<a name="1.0">` insert: `</a>` 1.0 Introduction insert: `</h2>`

insert: `<a name="2.0">` insert: `</a>` 2.0 LIR Ownership Change insert: `</h2>`

insert: `<a name="2.1">` insert: `</a>` 2.1 IP Address Space insert: `</h3>`

insert: `<a name="2.2">` insert: `</a>` 2.2 Service Agreement insert: `</h3>`

insert: `<a name="2.3">` insert: `</a>` 2.3 Change in Operating Organisation insert: `</h3>`

insert: `<a name="2.4">` insert: `</a>` 2.4 Contact Person(s) insert: `</h3>`

insert: `<a name="2.5">` insert: `</a>` 2.5 RegID insert: `</h3>`

insert: `<a name="2.6">` insert: `</a>` 2.6 Transfers of Address Allocations insert: `</h3>`

insert: `<a name="2.7">` insert: `</a>` 2.7 Takeover Fee insert: `</h3>`

insert: `<a name="3.0">` insert: `</a>` 3.0 Closing an LIR insert: `</h2>`

insert: `<a name="4.0">` insert: `</a>` 4.0 When an LIR is Closed by the RIPE NCC insert: `</h2>`