____________________________________________________ Guidelines for Setting up a Local Internet Registry at the RIPE NCC P. Caslav R. Muit Document: ripe-160 Date: March 12, 1998 ABSTRACT This document aims to provide the necessary information for those who are considering setting up a Local Internet Registry (IR) with the RIPE NCC. In this document, first some guidelines are given on which organisations usually set up a Local IR. Further, the steps necessary to set up a Local IR are described. Finally, the RIPE NCC's IP address first assignment and allocation policy is discussed. 1. Introduction IP addresses for use on the Internet are distributed in a system of hierarchically organized Internet Registries. For Europe, North Africa, and parts of the Middle East, there is a Regional Registry, the RIPE NCC which distributes addresses to "Local Internet Registries" (also called Local IRs, LIRs, or Local Registries) in its region. The Local IRs then assign address space to end users, and for their own network infrastructure. Any organisation who needs to obtain blocks of IP addresses from the RIPE NCC needs to set up a Local Internet Registry. Organisations sometimes open a Local IR because they have no other means of getting address space, or because it is better from the per- spective of Internet Routing. In other cases, they can obtain IP addresses from the (upstream) service provider and there is no need to become a Local IR and obtain address space from the RIPE NCC directly. ____________________________________________________ ripe-160.txt Page 1 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ 2. When to set up a Local Internet Registry When deciding whether or not to become a Local Reg- istry, an organisation should consider how much address space they expect to need in the future, how important having their own routable block is, and whether they are ready for the extra cost, adminis- trative overhead and responsibility of running a Local Registry. In this section, we offer some guidelines on this issue. Note that these are not meant to specify who may or may not set up a registry, but as an aid in the decision process. The policy of the RIPE NCC is to leave the decision up to the organisations them- selves. Anyone signing the Agreement on the Provi- sion and Use of the RIPE NCC services and promising to operate according to the registry guidelines will be accepted as a Local IR, as long as they are located in the RIPE NCC region, or have most of their customers there. Please see: http://www.ripe.net/lir/registries/countries.html for a list of countries in the RIPE NCC region. If your country is not on the list, but you think it should be in our region, please contact us, it could be that there are no Local Internet Registries in your country yet, and you are the first one. Please note that only an organisation that is a legal entity in the RIPE NCC region can set-up a Local Registry. 2.1. Responsibilities of a Local IR A Local IR receives allocations of blocks of IP address space from the RIPE NCC. The Local IR itself is responsible for the assignments of IP addresses that it makes from these allocated blocks. This includes: * Making the right assignment decisions following global assignment policies (as described in ripe-159, section 3 and 4). * Keeping records of the information gathered in the assignment process (as described in ripe-159 section 6) * Storing assignment information in the RIPE Database and keeping this information up to ____________________________________________________ ripe-160.txt Page 2 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ date (as described in ripe-159 section 3) The RIPE NCC has a consistency checking and auditing activity set up to train Local Registries and help them follow the procedures and to ensure that they are following their responsibilities correctly. This is described in ripe-170. 2.2. Costs of operating a Local IR The direct costs of operating a Local IR, i.e. fees paid to the RIPE NCC for services, are outlined in the 'RIPE NCC Fees and Billing Procedures' section below. A Local Registry should also expect costs related to the level of expertise staff of a Local IR needs to obtain and keep, and related to the administrative work operating a Local IR. Depending on the size of the Registry's customer base, it might need to have up to one full time staff member only doing Local IR administrative work. 2.3. Address Space Each Local IR gets a /19 (8192 addresses) allocation in the beginning (after they send in their first assignment request) and they can announce this block as one route to the rest of the Internet. They can use this block for their internal network and if they're a Provider Registry they can also use it for assignments to customers. After the initial block is used up, the Registry gets a new one of a size that matches the growth of their customer base. 2.4. Business Considerations Organisations operating a Local IR are not dependent on others for assigning address space to their own or their customers' networks. When changing upstream providers, an organisation who does not operate a Local IR will probably have to renumber their net- works and return the formerly used address space to the Local IR it was received from. On the other hand, operating a Local IR takes time and financial resources. 2.5. Other Considerations If an organisation is already operating a Local IR in the RIPE NCC region or another part of the world ____________________________________________________ ripe-160.txt Page 3 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ and wants to open another Registry, they'll have to provide the RIPE NCC with a valid reason why they need to have a another Local Registry. The RIPE NCC will ask for some extra information in this case. Also if an organisation is part of a large enter- prise that has address space already, then the RIPE NCC will need some extra information before it can set up a Local IR. We will need to know why address space from the main headquarters cannot be used for the network, and why it is necessary to receive address space from the RIPE NCC instead (or in addi- tion). Again, extra information will be required in this case. 3. Setting up a Local IR The process of setting up a Local IR can be roughly divided into 3 steps: * Establishment of an entry in the Local Internet Registry list * Agreement to Registry Procedures * Agreement on the Provision and Use of the RIPE NCC Services & Paying of Fees The steps need to be performed in order. Please note that much communication is needed between the Local Registry and the RIPE NCC. (For getting the documents listed below, for setting up the registry and for asking for address space.) Therefore, we really require the Local IR to have at least e-mail connectivity. If you do not have an Internet connection yet, please get an (interim) e- mail address before you request to set-up a Local IR. 3.1. Establishment of an Entry in the Local Internet Registry List As a first step, we'll need to collect some adminis- trative information about the new Local IR such as address & telephone numbers, names of contact per- sons, and billing information. Please fill in the form in Appendix A and e-mail it to for processing. After we receive the form we will create an entry for the new registry in ____________________________________________________ ripe-160.txt Page 4 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ the list of Local Internet Registries. After all three steps have been completed, some of the admin- istrative information in this form will be publi- cally accessible on the RIPE NCC web site. For the most part though, the form will only be used inter- nally by the RIPE NCC to keep information about the registry such as address allocations and assign- ments. As soon as we have established an entry for you, you will receive a Registry Identifier which we will use from now on to identify you as a registry and dis- tinguish you from end users. Please see the form bellow. Note that the information you provide in the tem- plate is not stored in the RIPE Database. If you want to change any information about your registry or just want to know about the current contents, please send an E-mail to or . We appreciate it if you help us to keep this information as up to date as possible. 3.2. Agreement to Registry Procedures We have to have a clear assurance from you that you will abide by the Internet Registry rules. The cur- rent documents you definitely should be familiar with are: * ripe-159: European Internet Registry Policies and Procedures * ripe-141: European IP network number applica- tion form * ripe-142: Supporting notes to ripe-141 * ripe-157: RIPE NCC Database Documentation * ripe-170 RIPE NCC Consistency and Auditing Activity * RFC 1918: Address Allocation for Private Inter- nets There are some documents that we'd like to point you to, since you will probably need them at some time. These are however not mandatory to be familiar with at this moment. ____________________________________________________ ripe-160.txt Page 5 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ * ripe-181: Representation of IP Routing Policies in a Routing Registry * ripe-147: European Autonomous System Number Application Form All of these documents can be obtained at www.ripe.net by following the "Documents" link. Please confirm by electronic mail, that you have read and understood the above, and will commit to abide to the guidelines as defined in these docu- ments and future guidelines as defined by the RIPE community. 3.3. Agreement on the Provision and Use of the RIPE NCC Ser- vices and Paying of Fees In order to provide a new Local IR service at the same level as all other contributing registries, we will need two signed service agreements from you. Since we will also sign the agreements you should send them by postal mail to us. Once we receive them, we will also sign them and return one agree- ment to you. Currently our address is: RIPE NCC Singel 258 1016 AB Amsterdam The Netherlands After we have received the signed service agreement, we will send an invoice. Once this is paid, the new Registry can start receiving services. The service agreement, ripe-172, is available on our web site at: http://www.ripe.net/docs/ or on the ftp site at: ftp://ftp.ripe.net/ripe/docs/ for a postscript or text version. Please also see the accompanying documents, ripe-176 (Articles of Assosiation) and ripe-173 (General Terms & Conditions) in the same ftp and web directo- ries. ____________________________________________________ ripe-160.txt Page 6 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ 4. RIPE NCC Fees and Billing Procedures The RIPE NCC charges new registries a one-time "Start-up Fee" as well as a yearly "Service Charge". These fees can change from year to year and there- fore rather than listing them here, please read ripe-175 (RIPE NCC Billing Procedure and Fee Sched- ule) in the same web and ftp directories as the above documents. The yearly fees are based on the size category of the registry. Each registry has a category (for Provider registries it's usually small, medium, or large) based on how many allocations they have received from the RIPE NCC and on the age of the allocations. A new Local Registry usually starts out with a category of small and remains "small" for the following year if they do not get any additional allocations in that first year. How these categories are calculated is described in ripe-163 (RIPE NCC Charging Scheme 1998) in the same web and ftp direc- tories as listed above. A Local Registry is assigned a "minimum" billing category by the RIPE NCC, however a Local Registry can always choose to upgrade itself to a higher cat- egory. Some Local Registries choose to do this in order to make themselves seem bigger to their com- petitors. ;-) There is also a special billing category called "Enterprise" which applies to Local Registries that only assign addresses to their own company's network and not to customers of theirs. Another special cat- egory is "Supernational" for a large Provider Local Registry that has several registries open (usually in several countries) and wants to have one billing address for them all. A new Local IR will receive a bill including the start-up fee and it's yearly fee for this year. The Registry can also choose to pay the fees on a half- yearly or quarterly basis, but there is an extra fee attached to this. The yearly fee will be based on the quarter of the year when the Local IR signs up. So if, for example, a Local Registry signs up with the RIPE NCC in July, they won't have to pay the entire yearly fee for that year, but only half of it. For questions on bills and payments please con- tact . Please note that a Local Registry receives the same kind of service from the RIPE NCC no matter what ____________________________________________________ ripe-160.txt Page 7 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ billing category they are. The reason behind having different billing categories is because larger Local IRs tend to send more requests and generate more work for the RIPE NCC staff. 5. Requesting Address Space for the First Time After an organisation has officially set up a Local Internet Registry (the three steps have been com- pleted) they will receive a message from notifying them that they can start requesting address space from the RIPE NCC. From now on the registry should use the mailbox for requesting address space, or for IP address related-questions. Please do not send address requests to . Before we go on to explain how a Local IR can request its first block of address space, let's clarify some of the terms used by the RIPE commu- nity: An allocation is a block of address space that a Local IR receives from the RIPE NCC. The Local IR can announce the entire allocation as one route to the rest of the Internet and uses this block of address space for its customers and it's own infras- tructure. An assignment is the smaller blocks of address space that a Local IR gives to it's customers for their networks, or uses for its own infrastructure. For example, if a Local IR needs a block of 256 addresses for one of it's Points of Presence, we would call this an "assignment". Assignments usually come out of the Registry's allocation. Assigned address space is actually used to operate networks, whereas allocated address space is held by IRs for future assignments to end users. To receive your first allocation from the RIPE NCC, you need to send your first request for an assign- ment. This can be for an assignment for a customer's network, or for the Registry's own internal infras- tructure. Please fill out a ripe-141 form and send this to . You will need to include your Registry Identifier (the "regid" on the Registry form) at the top of the message. Please always include this regid in all messages sent to the RIPE NCC hostmaster mailbox. The RIPE NCC can only process requests from official Local IRs, so if ____________________________________________________ ripe-160.txt Page 8 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ we receive a message at this mailbox without a "regid", we assume it's from an end-user and reject it. Also please note that the hostmaster mailbox is ticketised to help us keep track of the requests. When you send in a new request, we will assign a ticket number to it. You should then always use that same ticket number for any messages exchanged about that same request. Every new request needs a differ- ent ticket number, so please send new requests with- out any ticket number attached so we can assign a new one. After you have sent in your first request for an address space assignment and a RIPE NCC hostmaster has evaluated, we will allocate a /19 block of addresses (8192 IP addresses) to your Local Reg- istry. To be fair to all Local IRs this amount is the same for each new Registry, (unless it's first assignment is larger than this block). You can announce this prefix to your transit provider. We will at the same time also make the first assign- ment for you. This means we will update the database and inform you about the address space we have assigned. We will take the assigned range out of the beginning of your allocated block. But please note that even though you will now have an allocated block from the RIPE NCC, you can not make any assignments from this range initially with- out asking the RIPE NCC for approval. To make you familiar with the registry procedures and to provide additional support in your start-up phase, we cur- rently follow a "hand-holding" procedure for all new registries. Each new registry gets an "assignment window" (AW). This AW is initially 0. This means that you can not make any assignment without prior approval from the RIPE NCC. After the first request, please continue to send all requests for address space to the RIPE NCC for prior approval. We would like to see a ripe-141 form (European IP Network Number Request Form) completed for every single request for address space that you receive. This applies to requests from your cus- tomers as well as for address space you may need for your internal network. We always expect you to include your own comments and evaluation results in every request you send to us. We will then approve ____________________________________________________ ripe-160.txt Page 9 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ the request or recommend the assignment of a differ- ent amount of address space. If we approve the assignment, we will send you a message notifying you of this, and you will then have to enter the infor- mation about this assignment into the database your- selves. (We only enter the first assignment for you to give you an example, after that, you enter all assignments into the database yourselves) This procedure will only last for a short period of time until we are confident that you are familiar with the registration procedures. We will then increase your assignment window so that you can make assignments up to certain size yourself. For example if we have seen several requests for /25's and /26's from you, we might raise your assignment window to a /25. This means that you can then assign up to 128 addresses to any customer in a one year period. If you get a customer that needs more than 128 addresses, you would still have to send this larger request to the RIPE NCC for approval. All of these issues are described in more detail in ripe-159, section 3 and 4. 6. Training Courses The start-up fee paid by new Local Registries, is used (among other things) to fund the Local IR training courses. This is a one-day course (though it might be expanded to more days in the future) that explains the RIPE database, IP address poli- cies, reverse delegation, the routing registry and other issues. It is only open to Local IRs and is taught by the RIPE NCC staff members. We highly rec- ommend that new Registries send one or two of their staff members to this training course. There is no additional cost for attending this course. Please see: http://www.ripe.net/lir/courses/index.html for information on the location and dates of future training courses. Appendix A Please fill in this form and return it to . Information about how to fill out each field follows below. Please DO NOT send in this entire document, but only the filled out form itself (between the "cut here" marks). You can find an ____________________________________________________ ripe-160.txt Page 10 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ example of a filled out form at the end of this appendix. In addition to the form, we ask a few gen- eral questions. Please also answer these and send them together with the completed form. ____________________________________________________ ripe-160.txt Page 11 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ ---------------- cut here -------------- regid: org: type: address: country: admin-c: tech-c: phone: fax-no: e-mail: remark: lst-localir: lst-provs: lst-contrib: bill-addr: bill-mail: bill-ref: bill-vatno: bill-proto: bill-categ: bill-scheme: bill-remark: reg-ack: Questions: 1. Does the organisation already operate a Local Internet Registry in the RIPE NCC region? If yes, please give us the regid(s) of the Registry and a short explanation why an additional Registry needs to be openned. 2. Does the organisation have another registry in a different region (APNIC or ARIN region)? If yes, please specify the region and explain why you also need to set up a Local Registry in the RIPE NCC region. 3. Does the organisation already have address space? Please list it here. Please only list address space being used for the organisation's own internal net- work, and not address space being used for customers (other than dial-up or web servers). Please include address space for the entire organisation, not just this subsidiary. ---------------- cut here --------------- ____________________________________________________ ripe-160.txt Page 12 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ If at all possible, please send completed forms by electronic mail! Sending in handwritten forms will delay processing considerably! The fields marked "Published in Registry List" are published by the NCC in ftp://ftp.ripe.net/ripe/reg- istries and on http:/www.ripe.net for reference of those looking for a registry. Any questions about this form should be directed to . Description of all the individual fields: Registry Identifier regid: This string uniquely identifies a Local Reg- istry. The format is . where is the ISO3166 countrycode where the registry is located and is a somewhat descriptive identifier unique within the country. If a registry services several countries, please choose the country where the registry has it's main office. A supernational registry can use "eu" as a country code. Please note that this is only an administrative identifier and is not necessarily associated with your bussiness. Since changing this identifier causes a lot of internal administrative work, we will charge a fee for it. Mandatory, Single Line Only, Single Attribute per Object, Published in Registry List, Organisation Name org: A short descriptive name of the organisation running the Local Registry. It is used in lists and wherever a short description is appropriate. Mandatory, Single Line Only, Single Attribute per Object, Published in Registry List, Registry Type type: Tells the RIPE NCC whether this is a PROVIDER Registry that will be assigning addresses to cus- tomers of theirs, or if this is an ENTERPRISE that will only be assigning addresses within its organi- sation. Please fill in either "ENTERPRISE" or "PROVIDER" in this field. ____________________________________________________ ripe-160.txt Page 13 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ Mandatory, Single Line Only, Single Attribute per Object, Published in Registry List, Community Served community: A short and concise description of the community served by this Local Registry. For ser- vice providers something like "The Registry will serve customers of company, an Internet ser- vice provider in countries NN AA BB and CC serving mainly type customers." is sufficient. Please also indicate whether you are prepared to serve those not buying any other service from you. Use multiple lines for longer text. Mandatory, Multi-Line Attribute, Published in Reg- istry List, Postal Address address: The full postal address of the Local Reg- istry. This should be exactly what is needed to deliver postal mail. It should contain the organi- sation name in a suitable form. Multiple lines are represented by multiple 'address' attributes. Mandatory, Multi-Line Attribute, Published in Reg- istry List, Countries Served country: The countries to which this Registry assigns addresses as a blank separated list of ISO3166 codes. Mandatory, Single Line Only, Published in Registry List Administrative Contact admin-c: A reference to the RIPE database object of the person(s) administratively responsible for the Registry. The preferred form is the full name, fol- lowed by the NIC handle (in brackets). * Please see below for more information. Mandatory, Published in Registry List, ____________________________________________________ ripe-160.txt Page 14 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ Technical Contact tech-c: A reference to the RIPE database object of the person(s) executing the Registry work. The pre- ferred form is the full name, followed by the NIC handle (in brackets). * Please see below for more information. Mandatory, Published in Registry List, * PLEASE NOTE: We need the administrative and tech- nical contact persons (admin-c and tech-c) mentioned in the Local Registry form registered in the RIPE database with person templates. We would appreciate it if you send in templates for these persons to the database first. (See ripe-157 Section 2.2.1 on cre- ating a new database object) Telephone Number phone: The general phone number to be called on Reg- istry matters, If more than one is listed the pre- ferred ones should be listed first. Format is + [ext ]. Exten- sions should only be mentioned explicitly if they cannot be dialed directly. Mandatory, Published in Registry List, Telefax Number fax-no: The general FAX number to be used for Reg- istry matters, If more than one is listed the pre- ferred ones should be listed first. Format is + [ext ]. Exten- sions should only be mentioned explicitly if they cannot be dialed directly. Optional, Published in Registry List, Electronic Mail Address e-mail: The general electronic mail address to be used for Registry matters. This has to be in RFC822 format. If there really is no e-mail address yet, specify "none". In this case you will need to notify the RIPE NCC as soon as you do have an e-mail address so we can update it here. ____________________________________________________ ripe-160.txt Page 15 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ Mandatory, Published in Registry List, Remarks remark: Any useful remarks in free form text. Optional, Multi-Line Attribute, Published in Reg- istry List, Local Registries Mailing List lst-localir: The addresses to be added to the mail- ing list of all "Local Internet Registries". This list is used to make general announcements. Relevant discussions about LIR issues are held on the lir-wg mailing list (Local IR working group). At least one address is required to be subscribed to the localir mailing list and it is recommended that registries follow the lir-wg as well. We will therefore sub- scribe the address supplied here to both mailing lists. To change the mailbox subscribed to the localir mailing list, please write to . To change the mailbox subscribed to the lir-wg or to unsubscribe from this list, please mail . Mandatory, Not Published, Providers Mailing List lst-provs: The addresses to be added to the mailing list used to distribute requests for Internet ser- vices received at the RIPE NCC. This should be the mailbox dealing with general enquiries. Optional, Not Published, Contributors Committee Mailing List lst-contrib: The addresses to be added to the mail- ing list of the "RIPE NCC General Assembly". This Assembly consists of all organisations contributing to NCC funding and discusses formal aspects of RIPE NCC operation such as the budgets and charging. Mandatory, Not Published, ____________________________________________________ ripe-160.txt Page 16 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ Billing Address bill-addr: This is the full postal address to send billing related information to. It should contain the name of the responsible person. It has to be present even if bill-protocol is E-MAIL, (please see bellow about billing protocols). Mandatory, Multi-Line Attribute, Not Published, Electronic Billing Address bill-mail: This is the E-Mail address to send billing related information to. Mandatory, Not Published, Billing Reference bill-ref: This is some text that will be included in any bill for reference by the customer, f.i. pur- chase order numbers. Optional, Single Line Only, Single Attribute per Object, Not Published, VAT Number bill-vatno: This is the VAT number which is required for billing registries inside the European Union without Value Added Tax. If we do not have this num- ber, Dutch VAT will be billed. Optional, Single Line Only, Single Attribute per Object, Not Published, Billing Protocol bill-proto: We currently study the possibility to send bills by electronic mail, so you can print them on your printer rather than us printing them on ours and transporting the paper to you. We do not know whether the accountants/lawyers will be happy with that. You can indicate a preference here. E-MAIL means bills can be sent to the bill-mail address by electronic mail if possible. SNAIL-MAIL means that they *have to* be sent to the bill-addr address by postal mail. Currently all bills are being send by SNAIL-MAIL, the e-mail possiblility is an option for ____________________________________________________ ripe-160.txt Page 17 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ the future. Mandatory, Single Line Only, Single Attribute per Object, Not Published, Billing Category bill-categ: This is the current billing category. Unless you are an Enterprise Registry that will only be making assignments within it's own organisation, or a Supernational Registry with points of contact (other registries) in several countries, you should fill in at least "SMALL" (but can choose a higher category voluntarily). Possible categories: ENTERPRISE - enterprise registry SMALL - small provider MEDIUM - medium size provider LARGE - large provider SUPERNATIONAL - supernational, please indicate how many points of contact Mandatory, Single Line Only, Single Attribute per Object, Published in Registry List, Billing Scheme bill-scheme: This is the applicable billing scheme. YEARLY is the normal billing scheme. HALF-YEARLY and QUARTERLY are possible by special prior arrange- ments, but an extra fee is charged. The string LATE after the scheme indicates that we agreed that invoices due in December can be paid in January. See the billing procedure document for details of appli- cable charges etc. Mandatory, Single Line Only, Single Attribute per Object, Not Published, Billing Remark bill-remark: Any useful remarks concerning billing. Optional, Multi-Line Attribute, Not Published, ____________________________________________________ ripe-160.txt Page 18 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ Sample Form regid: nn.example org: E.X.Ample Net type: PROVIDER address: E.X. Ample Networking Ltd. Registry Sq. NN-1822 Internet City Northern Nowhere country: NN AB admin-c: Ad Ministrator (AM999-RIPE) tech-c: Joe Technical (JT1234) phone: +12 345 6789 fax-no: +12 345 9876 e-mail: registry@anet.nn remark: lst-localir: registry@anet.nn lst-provs: sales@anet.nn lst-contrib: ad.ministrator@anet.nn bill-addr: E.X. Ample Networking Ltd. Ad Ministrator Registry Sq. NN-1822 Internet City Northern Nowhere bill-mail: ad.ministrator@anet.nn bill-ref: PO4711 bill-vatno: NN-9876 5432 1 00 bill-proto: E-MAIL bill-categ: SMALL bill-scheme: YEARLY bill-remark: Never Bill Examples. Really! Questions: 1. Does the organisation already operate a Local Internet Registry in the RIPE NCC region? If yes, please give us the regid(s) of the Registry and a short explanation why an additional Registry needs to be openned. E.X. Ample Networking Ltd. already has a Local Reg- istry in the country of Southern Nowhere, regid sn.ample. We are now openning an office in Northern Nowhere and the new office will have it's own AS and it's own routing policy therefore for routing rea- sons we'd like to open another registry and receive a separate allocation. 2. Does the organisation have another registry in a different region (APNIC or ARIN region)? If yes, please specify the region and explain why you also need to set up a Local Registry in the RIPE NCC region. ____________________________________________________ ripe-160.txt Page 19 Guidelines for Setting up a Local Internet Registry Muit, Caslav ____________________________________________________ No registries in other regions. 3. Does the organisation already have address space? Please list it here. Please only list address space being used for the organisation's own internal net- work, and not address space being used for customers (other than dial-up or web servers). Please include address space for the entire organisation, not just this subsidiary. 193.0.0/19 allocated to sn.ample, out of this 193.0.10/23 is being used for the Northern Nowhere network, which will be returned when the new Reg- istry gets it's own allocation. ____________________________________________________ ripe-160.txt Page 20