- lir-wg - mailman.ripe.net

Document Anncouncement: Procedures for DNS Delegation in the IN-ADDR.ARPA Domain
by Daniel Karrenberg 06 Dec '93

06 Dec '93

#<text/plain [Document Announcement] New/Revised RIPE Document Announcement -------------------------------------- A revised document is available from the RIPE document store. Ref: ripe-105 Title: Procedures for DNS Delegation in the IN-ADDR.ARPA Domain Author: Daniel Karrenberg, Marten Terpstra Date: 6 December 1993 Format: PS=33719 TXT=11597 Bytes Obsoletes: ripe-85 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document describes the procedures for the delegation of zones in European subdomains of IN-ADDR.ARPA. #<text/plain [Retrieval Methods] FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get filename". The relevant filenames for this document are: ripe-105.txt for the ASCII version ripe-105.ps for the PostScript version Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. #@text/plain; \ type=text [FTP ASCII version] \ access-type=anon-ftp; \ name="ripe-105.txt"; \ directory="ripe/docs/ripe-docs"; \ site="ftp.ripe.net" #@text/plain; \ type=text [Have mail-server send document] \ access-type=mail-server; \ server="mail-server(a)ripe.net"; \ body="SEND ripe/docs/ripe-docs/ripe-105.txt" #@application/postscript; \ type=postscript [FTP PostScript version] \ access-type=anon-ftp; \ name="ripe-105.ps"; \ directory="ripe/docs/ripe-docs"; \ site="ftp.ripe.net"

1 0

Document Announcement: IP Address Space Assignment Procedures
by Daniel Karrenberg 06 Dec '93

06 Dec '93

New/Revised RIPE Document Announcement -------------------------------------- A revised document is available from the RIPE document store. Ref: ripe-104 Title: IP Address Space Assignment Procedures Author: Daniel Karrenberg, Marten Terpstra Date: 6 December 1993 Format: PS=29433 TXT=9761 Bytes Obsoletes: ripe-72 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document describes the procedures for the assignment of IP address space by European local Internet Registries. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get filename". The relevant filenames for this document are: ripe-104.txt for the ASCII version ripe-104.ps for the PostScript version Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-104.txt

1 0

Re: NIC Handles
by Bjorn Eriksen 30 Nov '93

30 Nov '93

>After some more discussion with the InterNIC it looks like we cannot >avoid giving *everyone* in the RIPE database a handle soon. Otherwise >the database exchange with the InterNIC would be too difficult. Just wondered how long it would take until something like a handle had to be introduced. --Bjorn

1 0

Re: NIC Handles
by Daniel Karrenberg 30 Nov '93

30 Nov '93

After some more discussion with the InterNIC it looks like we cannot avoid giving *everyone* in the RIPE database a handle soon. Otherwise the database exchange with the InterNIC would be too difficult. So contrary to what I said last week we will need to do that soon. I will send out a draft RIPE document later today. Please comment a.s.a.p. so that we can act quickly. Daniel

1 0

Document Announcement
by Anne Lord 29 Nov '93

29 Nov '93

New/Revised RIPE Document Announcement -------------------------------------- A new document below is available from the RIPE document store. Ref: ripe-101 Title: List of Internet Registries in Europe Author: RIPE NCC Date: 29 November 1993 Format: TXT=29262 Short content description ------------------------- This is a list of Local Internet Registries in Europe. The document is intended to clarify who to contact if IP network numbers are needed. FTP Access ---------- All RIPE documents and Internet RFC`s are available via anonymous FTP from host ftp.ripe.net. Type "ftp ftp.ripe.net". Login with username "anonymous" supplying your email address as the password. After logging in, type "cd ripe/docs/ripe-docs" followed by the command "get ripe-101.txt". Electronic Mail Retrieval of Documents -------------------------------------- Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to: mail-server(a)ripe.net with "send HELP" in the body text. RIPE NCC Interactive Information Server --------------------------------------- Type "telnet host info.ripe.net". This is a menu driven service allows the document store to be browsed. After reading documents you are prompted as to whether you would like to receive an email copy of the document you have just read. If you would, you simply enter your email address and the document will be mailed to you. Below are details of alternative methods of access. Gopher Access ------------- The same documents are available via a "gopher" server at "gopher gopher.ripe.net". WAIS Access ----------- There is also a "WAIS" server at wais.ripe.net, where there is a WAIS index for RIPE documents "ripe-docs.src" WWW Access ---------- For those who wish to add this home page at the RIPE NCC to their own customized home pages, it can be accessed as: http://www.ripe.net/ripe/default.html MIME Mail Reader ---------------- Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RIPE document. SEND ripe/docs/ripe-docs/ripe-101.txt

1 0

IP Address Space Assignment Procedures (ripe-72++)
by Daniel Karrenberg 25 Nov '93

25 Nov '93

Dear IRs European Internet Registry: IP Address Space Assignment Procedures Daniel Karrenberg Marten Terpstra Document ID: ripe-xx Obsoletes: ripe-72 ABSTRACT This document describes the procedures for the assignment of IP address space by European local Inter- net Registries. Introduction The originally centralised procedures for obtaining IP network numbers from the Global Internet Registry (known as the InterNIC, previously the DDN NIC) have been replaced by a distributed alloca- tion scheme. Blocks of Internet network numbers are now delegated by the Global Internet Registry to the RIPE NCC, who in turn delegates blocks of numbers to local Internet Registries (IRs). The local IRs in turn, make the majority of IP network number assignments across Europe. The procedures described in this document are designed to ensure fair distribution and optimal utilisation of the available address space. ripe-xx.txt - 2 - Class C Address Space Allocation Procedures The RIPE NCC currently has been delegated the following class C net- work number ranges: 192.162.0.0 - 192.162.255.0 192.163.0.0 - 192.168.255.0 193.0.0.0 - 193.255.255.0 194.0.0.0 - 194.255.255.0 Local IRs accepting a block of class C numbers agree to adhere to the following procedures: 1. The RIPE NCC will delegate blocks of class C networks to local IRs. Normally the size of a delegation will be 256 contiguous networks on a 16-bit boundary. This can be requested from <hostmaster(a)ripe.net>. If the local registry already has delegated blocks a summary of usage of these blocks has to be submitted at the same time. 2. Full information about reassigned network numbers must be reported back to the RIPE NCC in RIPE database format. The complete entries should be sent immediately after assignment, certainly not later than one working day after assignment, to <auto-assign(a)ripe.net>. This will cause the information to be included in the RIPE database automatically and an acknowledge- ment message to be returned. 3. Local IRs are required to have reliable and expedient Internet electronic mail connectivity in order to exchange messages among themselves, with requestors and with the RIPE NCC. E- mail is the preferred method of communication for registry pur- poses, followed by FAX. Paper mail is to be avoided wherever possible. Telephone communications should be confirmed by e- mail for documentation purposes and to avoid misunderstandings whenever appropriate. 4. IRs will keep records of correspondence and information exchanges in conjunction with the registry function for later review and the resolution of disputes. IRs will hold this information in strict confidence and use it only to review requests and in audit procedures or to resolve disputes. ripe-xx.txt - 3 - 5. Requests for address space should be reasonable and accompanied by enough technical details to justify the amount of address space requested. If at all possible requesters should be encouraged to submit their addressing/subnetting plan because this provides an excellent means of assessing whether the address space is going to be used effectively. 6. Requesters already holding address space are required to list the address space they already hold and give a summary of current address space utilisation which shows why additional address space is needed. All IRs should prevent stockpiling of address space. 7. It is recommended that assignment of a block of more than 32 class C network numbers (13 or more bits of address space) should only be made after a second opinion has been obtained from the RIPE NCC at <hostmaster(a)ripe.net>. This second opinion shall be documented with the request for later review. 8. On first request from the RIPE NCC, the class C network numbers not yet reassigned, must be returned to the RIPE NCC. 9. The RIPE Database is the only authoritative registry for the status of a particular network number from a RIPE NCC delegated block. A network number from such a block is considered unas- signed if it is not registered in the RIPE database. 10. Reassignment of class C network numbers should be done in a manner that facilitates Supernetting (see next section). 11. Requests shall be reviewed using Internet-wide guidelines used by all Internet registries as described in documents such as RFC1466. The local registries shall strive to align their review process with other local registries and the RIPE NCC. 12. Wherever possible IRs should use the European form in order to make review and passing of requests between IRs easy. The form should be translated and adapted to local circumstances as necessary. Aggregation (CIDR) IRs reassigning IP network numbers need to be familiar with RFC1519. This document can be obtained from the RFC section of the RIPE docu- ment store or other RFC servers. ripe-xx.txt - 4 - Classless addressing aims to reduce the increase of routing table size in the current Internet. It creates a hierarchy of IP network numbers, which can then be aggregated resulting in less routing table entries in routing equipment. This proposal has formally been adopted by the IAB/IESG/IETF, and it has an impact on the address assignment strategy, which is documented in RFC1466 and RFC1467. Here is how it works: If an organisation A needs 8 class C network numbers, the numbers should be given out in such a way that the routing information for each of these 8 networks could appear as one entry with the correct mask in routing tables. More concretely: Service provider S hands out networks 192.24.8 through 192.24.15 to organisation A. These networks can then appear in routing equipment as a supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C network numbers appear as one routing table entry. The guidelines that can be derived from the Supernetting proposal are: 1. IRs shall allocate class C network numbers in blocks suitable for aggregation. The blocks should be bit-aligned, i.e. con- tiguous, size a power of 2 and start on a multiple of the block size. 2. The blocks allocated to an organisation should be sufficient for a reasonable expected growth over the immediate future. Gaps caused by rounding to the next reasonably sized CIDR block can be reserved for the organisation holding the preceeding addresses. Note that this differs from earlier recommendations to reserve address space for expected growth in the medium term. 3. Multi-homed organisations may obtain address space from one of their providers, the RIPE NCC, or the global NIC, as is appropriate to their network configuration. These organisations are strongly encouraged to contact the RIPE NCC for guidance. Class B Network Number Allocation Procedure European organisations can obtain class B networks numbers from the RIPE NCC only. Local IRs and end-user organisations can request Class B network numbers on a case-by-case basis from the RIPE NCC. It is preferred if requests are channeled via the local IRs ripe-xx.txt - 5 - initially. The procedures are similar to the class C procedures outlined above which apply wherever applicable. In addition the fol- lowing extra considerations have to be made: 1. Because class B address space is a critical resource, a request for a class B network number must be accompanied by a justifi- cation in terms of the requesting organisation's size, current network size and expected network growth. Submission of the addressing/subnetting plan detailing the proposed use of the address space is mandatory. 2. The requester should also make clear why they cannot use a block of class C network numbers to achieve their goals. Please see the European IP Network Number Application Form for more details on class B network number requests. This form must be used for class B address space requests. Class A Network Number Allocation Procedure Class A network numbers are assigned extremely rarely and only in cases where there is a technical need to have more than 65000 hosts on a single physical network. Review takes place on a global scale and takes considerable time. If you are convinced you need a class A network number, please contact the NCC. If you have any questions concerning this, please do not hesitate to call or mail us at hostmaster(a)ripe.net. ripe-xx.txt

3 4

Procedures for DNS Delegation in the IN-ADDR.ARPA Domain
by Daniel Karrenberg 24 Nov '93

24 Nov '93

European Internet Registry: Procedures for DNS Delegation in the IN-ADDR.ARPA Domain Daniel Karrenberg Marten Terpstra November 1993 Document-ID: ripe-zz Obsoletes: ripe-85 ABSTRACT 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 network numbers, class A, class B and 192.x.y.0 class Cs are randomly assigned. Subdomains of IN-ADDR.ARPA describing reverse mappings for randomly assigned networks have to be handled globally and are handled by the InterNIC <hostmaster(a)rs.internic.net>. ripe-zz.txt - 2 - Hierarchically Assigned Numbers The subdomains of IN-ADDR.ARPA corresponding to the hierarchically assigned network numbers are administered by the RIPE NCC. These network numbers currently are 193.0.0.0 - 194.255.255.0 Although the procedures described below refer to the 193.x.y block of addresses, for clarity they apply to all such blocks. 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 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 regis- tries. 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 next section. Procedures 1. A secondary nameserver at ns.ripe.net is mandatory for immediate subdomains of the 193.IN-ADDR.ARPA domain. ripe-zz.txt - 3 - 2. Because of the importance of correct reverse address mapping, for all delegated blocks a good set of secondaries must be defined. There should be at least 2 nameservers for all blocks delegated, excluding the RIPE NCC secondary. Operators of the primary nameservers should be familiar with RFC1537. 3. The delegation of an immediate subdomain of 193.IN-ADDR.ARPA domain corresponding to a block of 256 class C network numbers can be requested by sending a request confirming that the procedures described in this document will be followed to <hostmaster(a)ripe.net>. The request should be accompanied by a domain object for the RIPE database with all necessary contact and nameserver information. An example domain object can be found at the end of this document. 4. When receiveing such a request the RIPE NCC will forward data about any currently registered reverse zones inside this block to the registry. After addition of these by the registry, the NCC will check the working of the reverse server. 5. Once everything is set up properly, the NCC will set up ns.ripe.net as secondary nameserver, delegate the block, and include the domain object in the RIPE database. 6. All reverse servers for blocks must be reachable from the the Internet. In short, all servers must meet similar connec- tivity requirements as top-level domain servers. 7. 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. 8. 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. 9. 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. ripe-zz.txt - 4 - 10. 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. 11. 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 mail address specified in the SOA RR for the zone concerned. 12. The NCC advises the following timers and counters for direct subdomains of 193.IN-ADDR.ARPA: 8 hours refresh (28800 seconds), 2 hours retry (7200 seconds), 7 days expire (604800 seconds) and 1 day Time To Live (86400 seconds). The retry counter should be lowered where connectivity is unstable. 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. Example domain object to request a block delegation 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: marten(a)ripe.net 930319 source: RIPE Delegation of Individual Network Zones 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. ripe-zz.txt - 5 - 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. The NCC uses the following procedures for the delegation of indivi- dual network zones. Local registries should use similar guidelines. 1. Because of the importance of correct reverse address map- ping, for all delegated networks a good set of secondaries must be defined. There should be at least two nameservers for all networks delegated. 2. Each "rev-srv" attribute in the RIPE database should ONLY con- tain one fully qualified domain name of a nameserver which is authoritative for the reverse zone for this network. There should be one "rev-srv" attribute for each nameserver. 3. If a network has or is going to have any external connec- tivity, it is strongly recommended that it has at least one reverse nameserver that can be reached from all of the Inter- net. 4. Although we do our best to check the setup of the nameservers, these do not receive the same level of scrutiny as nameservers for blocks of class C network numbers. It is the responsibility of the network contacts to ensure proper opera- tion. 5. Any problems regarding the reverse zones in 193.IN-ADDR.ARPA should be reported to <hostmaster(a)ripe.net>. 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. If you have any questions or suggestions concerning this document, please contact the RIPE NCC at <hostmaster(a)ripe.net>. ripe-zz.txt

2 2

Syntax errors in database
by Marten Terpstra 23 Nov '93

23 Nov '93

Folks, As promised at the last RIPE meeting, we have run a full syntax check on the complete database, and the results of that check are available for anonymous ftp. The files are split by object type, and contain only objects that generated a warning or error. If you have some time to maybe look at some of your info, please look in: ftp.ripe.net:ripe/dbase/errors/ If you have questions about errors/warnings found, please let us know. -Marten

1 0

The European Internet Registry System
by Daniel Karrenberg 22 Nov '93

22 Nov '93

Dear IRs, we are about to circulate the long overdue revisions of ripe-72 and ripe-85. Shortly there will also be a new document titled "The European Internet Registry System" giving general information about the European Internet Registry framework. This will be targeted to give new people background information and explain terminology: IR, regional IR, Local IR: provider, last-resort ... Assuming there is general consensus about the content I would like to publish those documents by December 6th. Otherwise they will have to wait until the January RIPE meeting. I hope this won't be necessary though because the old docs are really in need of revision. Daniel

1 0

Changing the CIDR Assignment Strategy
by Daniel Karrenberg 22 Nov '93

22 Nov '93

We will circulate a revision of ripe-72 shortly. We suggest to change the recommendation for address space reservations. Below we give the reasoning behind this. Discussion Welocme For the NCC team Daniel Previously the RIPE NCC has recommended IRs to reserve some address space contiguous to assigned address space for future expansion. The reasoning was that this would further aggregation and keep the routing table sizes down in the long term, while being slightly inefficient on address space usage in the short term. However recently we had to start delegating blocks from 194.x.y, when 193.x.y had slightly more than 25% of address space assigned. This caused us to review assignements and we have found a lot of reserved address space causing fragmentation. This experience suggests that the address space usage problems created by those reservations outweigh the possible aggregation benefits. If a block of equal size to the one actually assigned is reserved, address space utilisation is halved in return for a possible 50% reduction in routing table size. Relatively speaking this looks like a good tradeoff. In absolute terms however substantial amounts of address space are traded in to save 1 (in words: one) additional routing table entry. If some address space is reserved and exactly that amount is needed later the reserved space can be assigned and aggregated into the same CIDR route, not expanding the routing tables at all, saving one additional routing table entry. Note that this small absolute gain can only be realised if the reserved space indeed fits the need exactly! If no reservation is made at all and more address space is needed at a later stage, another block of appropriate size can always be assigned. Since there are now two blocks these can be aggregated into two routes instead of the one which would have resulted if a suitable reservation had been made. The effect of the reserved address space is not only decreased utilisation but also creates fragmentation of the address space which makes it difficult to find block of appropriate size for new requests. Considering this it does not make sense to reserve anything but very small amounts of address space or unused parts of CIDR blocks. Thus the current recommendation is to reserve only address space that is needed to "round" the requested space to the next suitable block boundary.

1 0