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-679: This document describes the policies for the assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process.

delete:  Introduction delete:   delete:   insert: <h3>

insert: `` Abstract insert: `` insert: `</h3>`

insert: 

This document describes the procedures policies for the delegation assignment of au- globally unique Autonomous System (AS) Numbers within the RIPE NCC service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process. insert: 

insert: 

insert: 

insert: <h3>

insert: `` Contents insert: `` insert: `</h3>`

insert: 

1.0 insert: <a class="anchor-link" title="" href="#Definition" target="_self"> Definition
thority insert: </a> 2.0 insert: <a class="anchor-link" title="" href="#AssignmentCriteria" target="_self"> Assignment Criteria insert:  
insert: </a> 3.0 insert: <a class="anchor-link" title="" href="#Returning" target="_self"> Returning AS Numbers insert:  
insert: </a> 4.0 insert: <a class="anchor-link" title="" href="#Transferring" target="_self"> Transferring AS Numbers insert:  
insert: </a> 5.0 insert: <a class="anchor-link" title="" href="#ASnumbers" target="_self"> 32-bit AS Numbers insert:  
insert: </a> 6.0 insert: <a class="anchor-link" title="" href="#Registration" target="_self"> Registration insert:  
insert: </a> 7.0 insert: <a class="anchor-link" title="" href="#References" target="_self"> References insert:  
insert: </a> 8.0 insert: <a class="anchor-link" title="" href="#Attribution" target="_self"> Attribution insert: </a> insert: 

insert: 

insert: 

insert: <h3>

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

insert: 

An Autonomous System (AS) is a group of zones IP networks run by one or more network operators with a single clearly defined routing policy. When exchanging exterior routing information, each AS is identified by a unique number. Exterior routing protocols such as BGP, described in the 193.in-addr.arpa domain. As insert: <a href="ftp://ftp.ripe.net/rfc/rfc1771.txt"> RFC1771 insert: </a> , "A Border Gateway Protocol 4 (BGP-4)", are used to exchange routing information between Autonomous Systems. An AS will normally use some interior gateway protocol to exchange routing information on its internal networks. insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: 

In order to help decrease global routing complexity, a new AS Number should be used only if a new external routing policy is required, see insert: <a href="ftp://ftp.ripe.net/rfc/rfc1930.txt"> RFC1930 insert: </a> . insert: 

insert: 

A network must be multihomed in order to qualify for an AS Number. insert: 

insert: 

When requesting an AS Number the routing policy of March delete:   16th 1993 the RIPE NCC has been delegated the authority the Autonomous System must be provided. The new unique routing policy should be defined in RPSL language, as used in the RIPE Database. insert: 

insert: 

The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE NCC either directly or through a sponsoring LIR. AS Number assignments are subject to the policies described in the RIPE NCC document entitled “ insert: <a href="http://www.ripe.net/publications/docs/contract-req" data-linktype="external" data-val="http://www.ripe.net/publications/docs/contract-req"> Contractual Requirements for the delete:   193.in-addr.arpa domain Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ”. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `` insert: `</h3>`

insert: 

If an organisation no longer uses the AS Number, it should be returned to the public pool of AS Numbers. The RIPE NCC can then reassign the AS Number to another organisation. insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `` insert: `</h3>`

insert: 

The transfer of Internet number resources is governed by the RIPE Document, " insert: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-val="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external"> RIPE Resource Transfer Policies insert: </a> ". insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `` insert: `</h3>`

insert: 

The RIPE NCC assigns 32-bit AS Numbers according to the following timeline: insert: 

insert: <ul>

insert: <li>

From 1 January 2007 the RIPE NCC will process applications that specifically request 32-bit only AS Numbers (AS Numbers that can not be represented with 16 bits) and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 32-bit only AS Number, the RIPE NCC will assign a 16-bit AS Number. insert: </li>

insert: </ul>

insert: <ul>

insert: <li>

From 1 January 2009 the RIPE NCC will process applications that specifically request 16-bit AS Numbers and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 16-bit AS Number, the RIPE NCC will assign a 32-bit only AS Number. insert: </li>

insert: </ul>

insert: <ul>

insert: <li>

From 1 January 2010 the RIPE NCC will cease to make any distinction between 16-bit AS Numbers and 32-bit only AS Numbers, and it will operate AS Number assignments from the root. Due to the fact that an undifferentiated 32-bit AS Number allocation pool. insert: </li>

insert: </ul>

insert: 

insert:  insert:  insert: 

insert: <h3>

insert: `` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `` insert: `</h3>`

insert: 

The RIPE NCC will register the resources issued in delete:   the 193.x.y address space blocks the RIPE Database. insert: 

insert: 

insert:  insert:  insert: 

insert: <h3>

insert: `` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `` insert: `</h3>`

insert: 

[RFC1771] "A Border Gateway Protocol 4 (BGP-4)" insert: <a href="http://www.ietf.org/rfc/rfc1771.txt"> http://www.ietf.org/rfc/rfc1771.txt insert: </a> insert: 

insert: 

[RFC1930] " Guidelines for creation, selection, and registration 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 in the 193.in- delete:   addr.arpa domain. an Autonomous System (AS)" insert: <a href="http://www.ietf.org/rfc/rfc1930.txt"> http://www.ietf.org/rfc/rfc1930.txt insert: </a> insert: 

insert: 

[RFC2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC insert: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt insert: </a> see Sec. 4.2.1 insert: 

insert: 

insert: 

insert: <h3>

insert: `` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `` insert: `</h3>`

insert: 

This document describes some guidelines 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 is compiled from policies developed by the RIPE community. insert: 

insert: 

The following the CIDR delete:   (RFC 1338) model, in which large chunks of the address space are delete:   delegated to one region, 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 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 people actively contributed 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 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:  making proposals through the RIPE Policy Development Process: insert: 

insert: 

Nick Hilliard, Geoff Huston insert: 

insert: 

insert:  insert:  insert: 

insert: 

insert: 

Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain Autonomous System (AS) Number Assignment Policies

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

insert: `<strong>` Abstract insert: `</strong>` insert: `</h3>`

insert: `<strong>` Contents insert: `</strong>` insert: `</h3>`

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

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: `<strong>` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `</strong>` insert: `</h3>`

RIPE Documents Search

ripe-085

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

insert: <strong> Abstract insert: </strong> insert: </h3>

insert: <strong> Contents insert: </strong> insert: </h3>

insert: <a name="Definition"> insert: </a> 1.0 Definition insert: </h3>

insert: <a name="AssignmentCriteria"> insert: </a> 2.0 Assignment Criteria insert: </h3>

insert: <strong> insert: <a name="Returning"> insert: </a> 3.0 Returning AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Transferring"> insert: </a> 4.0 Transferring AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="ASnumbers"> insert: </a> 5.0 32-bit AS Numbers insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Registration"> insert: </a> 6.0 Registration insert: </strong> insert: </h3>

insert: <strong> insert: <a name="References"> insert: </a> 7.0 References insert: </strong> insert: </h3>

insert: <strong> insert: <a name="Attribution"> insert: </a> 8.0 Attribution insert: </strong> insert: </h3>

RIPE Documents Search

ripe-085

insert: `<strong>` Abstract insert: `</strong>` insert: `</h3>`

insert: `<strong>` Contents insert: `</strong>` insert: `</h3>`

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

insert: `<a name="AssignmentCriteria">` insert: `</a>` 2.0 Assignment Criteria insert: `</h3>`

insert: `<strong>` insert: `<a name="Returning">` insert: `</a>` 3.0 Returning AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Transferring">` insert: `</a>` 4.0 Transferring AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="ASnumbers">` insert: `</a>` 5.0 32-bit AS Numbers insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Registration">` insert: `</a>` 6.0 Registration insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="References">` insert: `</a>` 7.0 References insert: `</strong>` insert: `</h3>`

insert: `<strong>` insert: `<a name="Attribution">` insert: `</a>` 8.0 Attribution insert: `</strong>` insert: `</h3>`