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-695: Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

delete:  insert: <h2>

Contents insert: `</h2>`

insert: 

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

insert: 

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

insert: 

3.0 insert: <a href="#transfer"> Transfer of Internet Number Resources insert: </a> insert: 

insert: 

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

insert: 

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

insert: 

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

insert: 

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

insert: 

3.5 insert: <a href="#transfer35"> Transfers Between LIR Accounts Belonging to the Same Member insert: </a> insert: 

insert: 

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

insert: 

insert: 

insert: <h3>

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

insert: 

For the purposes of this document, Internet number resources refer to: insert: 

insert: <ul>

insert: <li>

The registered allocation and assignment records of a member insert: </li>

insert: <li>

In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy “ insert: <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 insert: </a> ”. Such a transfer may also be facilitated through the RIPE NCC Listing Service. insert: </li>

insert: </ul>

insert: 

insert: 

insert: <h3>

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

insert: 

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

insert: <ul>

insert: <li>

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

insert: <li>

The Internet number resources that are registered to these natural or legal persons insert: </li>

insert: </ul>

insert: 

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

insert: 

A member must inform the RIPE NCC if insert:  one or both insert:  of the following changes occurs: insert: 

insert: <ol>

insert: <li>

Internet Number Resource are transferred. Such transfers may take place: insert: </li>

insert: <ul>

insert: <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. insert: </li>

insert: <li>

In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy “ insert: <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 insert: </a> ”. Such a transfer may also be facilitated through the insert: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> RIPE NCC Listing Service insert: </a> .

insert: </li>

insert: </ul>

insert: <li>

The member changes its official legal name insert:  . insert:  Such a change may occur, for example, because of a merger or acquisition of the member's organisation. insert: </li>

insert: </ol>

insert: 

This document describes the procedures for the delegation of au- such changes to be properly communicated and registered with the RIPE NCC. insert: 

insert: 

insert:  Note:
thority of zones insert:  If a 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 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. insert: 

insert: 

If a change in delete:   the 193.x.y address space blocks of 256 class C network numbers delete:   are further delegated to local registries , the possibility ex- delete:   ists to also delegate the zone for these blocks a member's business structure is insert:  not insert:  accompanied by a transfer of Internet number resources or a change in the 193.in- delete:   addr.arpa domain. member's official legal name, then the RIPE NCC does not need to be informed of this change. insert: 

insert: 

This document describes some guidelines 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, “ insert: <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 delete:   procedures End User insert: </a> ”. insert: 

insert: 

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, “ insert: <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 insert: </a> ”. insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="transfer">` insert: `</a>` 3.0 Transfer of Internet Number Resources insert: `</h3>`

insert: 

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. insert: 

insert: <h4>

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

insert: 

For the transfer to be processed, one of the involved parties must submit a request to the RIPE NCC: insert: 

insert: <ul>

insert: <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), the request must be submitted via the LIR Portal. If the requesting party does not have access rights to the LIR portal, the request must be submitted via email to insert: <a href="mailto:[email protected]"> [email protected] insert: </a> insert: </li>

insert: <li>

If this is a transfer of Internet number resource from one member to another party according to RIPE Policy “ insert: <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 insert: </a> ”, the request must be submitted via the insert: <a href="https://my.ripe.net" data-linktype="external" data-val="https://my.ripe.net"> LIR Portal insert: </a> . insert: </li>

insert: </ul>

insert: 

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

insert: 

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

insert: 

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

insert: <ul>

insert: <li>

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

insert: <li>

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

insert: <li>

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

insert: </ul>

insert: 

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 insert: <a href="#memberchanges"> Section 4.0 insert: </a> must be followed prior to the transfer of the Internet number resources. insert: 

insert: 

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, “ insert: <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 insert: </a> ”. insert: 

insert: 

insert:  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) insert:  insert: 

insert: 

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. insert: 

insert: 

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 “ insert: <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 insert: </a> ”. insert: 

insert: 

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

insert: 

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

insert: 

If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated (see Section A.1.1. of the RIPE NCC Procedural Document, “ insert: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources insert: </a> ”). insert: 

insert: 

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

insert: 

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

insert: 

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

insert: 

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

insert: 

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. insert: 

insert: 

The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a contact person or authorised person (e.g., senior manager, legal successor). insert: 

insert: 

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

insert: <ul>

insert: <li>

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

insert: <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. insert: </li>

insert: </ul>

insert: 

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

insert: 

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

insert: <h4>

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

insert: 

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

insert: 

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

insert: 

If the Internet number resources to be transferred are Provider Independent (PI) addresses, 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 insert: <a href="https://www.ripe.net/../participate/resource-management/independent-resources"> Requesting Independent Resources insert: </a> . insert: 

insert: 

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

insert: <h4>

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

insert: 

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 type of delegation 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. insert: 

insert: 

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

insert: <h4>

insert: `<a name="transfer34">` insert: `</a>` 3.4 Internet Number Resource Registration and the delegation of re- delete: ` ` verse zones for individual class C networks RIPE Database Issues insert: `</h4>`

insert: 

insert:  The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the party involved, in 193.x.y. delete:   delete:   delete:   A bit more explained delete:   delete:   With the compliance with the RIPE Policies current at the time of the transfer. insert:  insert: 

insert: 

The receiving member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment of class C network numbers following the CIDR delete:   (RFC 1338) model, approvals. insert: 

insert: 

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

insert: <h4>

insert: `<a name="transfer35">` insert: `</a>` 3.5 Transfers Between LIR Accounts Belonging to the Same Member insert: `</h4>`

insert: 

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy “ insert: <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 insert: </a> ” and will be evaluated in which large chunks of the address space are delete:   delegated to one region, accordance with them. insert: 

insert: 

The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and within that region blocks of class C delete:   network numbers are delegated to service providers 3.1.v. insert: 

insert: 

If after the transfer the member decides to close an LIR account, all outstanding invoices and non- delete:   provider registries, some hierarchy in the 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 and every reverse mapping in the delete:   193.in-addr.arpa domain to be registered with the INTERNIC. 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 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 . 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 outstanding financial obligations for all delete:   blocks of class C network numbers delegated LIR accounts must be paid in the 193.in- delete:   addr.arpa domain. delete:   delete:   2. Because of the increasing importance of correct reverse ad- delete:   dress mapping, for full. insert: 

insert: 

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. insert: 

insert: 

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

insert: 

The RIPE NCC will update the registry, including all delegated blocks a good set of secondaries delete:   must be defined. There should be at least 2 nameservers for RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all delete:   blocks delegated, excluding the RIPE NCC secondary. delete:   delete:   3. The delegation of a class C block RIPE Database objects maintained by them that are related to this transfer. insert: 

insert: 

insert: 

insert: <h3>

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

insert: 

It is the obligation of the member to inform the RIPE NCC immediately if any change in the 193.in-addr.arpa delete:   domain can be requested by sending member's official legal name occurs. insert: 

insert: 

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

insert: <ul>

insert: <li>

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

insert: <li>

The official legal documents supporting this change insert: </li>

insert: </ul>

insert: 

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

insert: 

If the change in a domain object for the delete:   RIPE database to <[email protected]> the member's official legal name occurred without a further change in the member's structure (e.g., merger with all necessary contact delete:   and nameserver information. The RIPE NCC another legal entity, acquisition by/of another legal entity), the member 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:  sign a new RIPE NCC Standard Service Agreement. insert: 

Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

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

Contents insert: </h2>

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

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

insert: <a name="transfer"> insert: </a> 3.0 Transfer of Internet Number Resources insert: </h3>

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

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

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

insert: <a name="transfer34"> insert: </a> 3.4 Internet Number Resource Registration and the delegation of re- delete: <br /> verse zones for individual class C networks RIPE Database Issues insert: </h4>

insert: <a name="transfer35"> insert: </a> 3.5 Transfers Between LIR Accounts Belonging to the Same Member insert: </h4>

insert: <a name="memberchanges"> insert: </a> 4.0 Member Changes Official Legal Name insert: </h3>

RIPE Documents Search

ripe-085

Contents insert: `</h2>`

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

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

insert: `<a name="transfer">` insert: `</a>` 3.0 Transfer of Internet Number Resources insert: `</h3>`

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

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

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

insert: `<a name="transfer34">` insert: `</a>` 3.4 Internet Number Resource Registration and the delegation of re- delete: `<br />` verse zones for individual class C networks RIPE Database Issues insert: `</h4>`

insert: `<a name="transfer35">` insert: `</a>` 3.5 Transfers Between LIR Accounts Belonging to the Same Member insert: `</h4>`

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