------------------------------------------------------------------- APNIC Document identity Title: IP Network Address Application Form Supporting Notes Short title: ip-address-support-notes Document ref: APNIC-001 Version: 002 Date of original publication: 16 February 1995 Date of this version: 16 February 1995 Review scheduled: n/a Obsoletes: n/a Status: Obsolete Comments: Obsoleted by APNIC-014 and APNIC-015 -------------------------------------------------------------------- Informational Document Asia Pacific Network Information Center IP Network Address Application Form Supporting Notes 1.0 Introduction This document describes the procedure for requesting IP addresses for networks located within the Asia Pacific region. The actual appli- cation form is APNIC-002. After you have finished reading this document please see the APNIC-002 form. Since 1992, the procedures for obtaining IP network numbers from a single organisation in the US have been replaced by a distributed system whereby applications for IP network numbers across the Asia and Pacific Rim regions are processed by local Internet Registries (local IR's). The Global Internet Registry (Global IR) now delegates blocks of IP net- work numbers to APNIC, the registry for the Asia Pacific region, which in turn delegates blocks of IP network numbers to local IR's. Local IR's are of three types: "Service Provider", "Enterprise" and "National". An Internet service provider (ISP) is an organisation that supplies Internet connectivity to it's customers or users. An ISP can become a local IR by agreeing to certain conditions (see APNIC-011). A "National" local IR's handle all requests from organisations that have no connection to the Internet at present or planned. In addition, National IRs may also delegate addresses to ISPs within a national con- text. "National" IR's are often run by a consortium of ISP's as a voluntary and neutral service to the community, thus, please contact the "National" IR ONLY in the event obtaining address space from your ser- vice provider proves impossible. Finally, an "Enterprise" local IR is one which coordinates address space usage for a large enterprise such as large corporations, governmental bodies, etc. Individuals and organizations applying for IP address space should read this document in its entirety as well as keep a copy for reference when filling out the actual application form APNIC-002. 2.0 APNIC Area of Responsibility APNIC is responsible for requests coming from the countries listed below. The two letter code preceding each country is the ISO 3166 code to be used in filling up the application form. For the ISO codes of APNIC Staff [Page 1] APNIC-001.2 February 1995 countries outside the AP region, please see appendix C. AF Afghanistan MN Mongolia AU* Australia MM Myanmar BD Bangladesh NR Nauru BT Bhutan NP Nepal BN Brunei Darussalam NC New Caledonia & Dependencies KH Cambodia NZ New Zealand CN China MP Northern Mariana Islands TP East Timor PK Pakistan FJ Fiji PW Belau GU Guam PG Papua New Guinea HK Hong Kong PH Philippines IN India PN Pitcairn Island ID Indonesia SG Singapore JP* Japan SB Solomon Islands KP Korea, People's Dem.Rep.of LK Sri Lanka KR* Korea, Republic of TW Taiwan, Republic of China LA Lao People's Democratic TH Thailand Republic TK Tokelau Islands MO Macau VU Vanuatu MY Malaysia VN Vietnam MH Marshall Islands WF Wallis & Futuna Islands FM Federated States of WS Western Samoa Micronesia * = Has a delegated national NIC APNIC will also accept requests from Middle Eastern, Central Asian, and Persian countries. However, many of the countries in these regions are already handled by RIPE-NCC and we may refer your application to them. In cases where a country is handled by RIPE-NCC, you may be required to submit a RIPE-NCC application form instead of the APNIC form. If you have questions regarding whether your country is handled by APNIC, please contact us. 3.0 Application Procedures To make a request for IP addresses, kindly complete an IP network address request form APNIC-002. For a sample completed form, refer to Appendix A. After completing the form, please submit it to APNIC. Requests submitted via electronic mail are vastly prefered to any other form of transmission and will be processed with minimal delay. Requests can also be submitted via fax or (as a last resort) postal mail but requests received in these fashions will require additional processing, thus incurring some delay After submitting your application, please allow for one week for processing (two weeks in the case of fax or postal mail requests). Applications for IP address space should be sent APNIC Staff [Page 2] APNIC-001.2 February 1995 via email to: ip-request@rs.apnic.net Note that the processing of your request is semi-automated, the first step being a simple syntax check, so it is possible your request will be returned to you if syntax errors are detected. If you feel your application was not in error, please contact hostmaster@apnic.net. For other means of submissions, please use the following contact informa- tion: Asia Pacific Network Information Center c/o Internet Initiative Japan, Inc. Sanbancho Annex Bldg. 1-4 Sanbancho, Chiyoda-ku Tokyo 102, Japan. Tel: +81-3-5276-3973 Fax: +81-3-5276-6239 Regardless of the amount of address space you are applying for, you should always make your application to the local IR nearest you. Larger requests, however, will most likely require a second opinion from APNIC (and for very large requests, the concurrence of the IANA), so addi- tional delays and/or justification may be required. In an effort to more efficiently utilize the remaining IP address space, the IANA has put in place significant res- trictions on when class B addresses or large amounts of class C address space may be allocated. In particular, to even be considered for a class B address, applicants must provide evidence that the requesting site will have a *minimum* of 4096 end sys- tems *and* 32 IP subnets. Even if these minimum requirements are met, the IANA has indicated preference should go to an appropriately sized block of class C networks over a class B if at all possible. As such, class B addresses are rarely allocated and will require extensive detailed justification. If you feel your request may qualify for a class B or a large block of class Cs, you will need to submit additional engineering information in order for your request to be processed. This additional information should include: - Network deployment plans includiing time schedules. - Network topology descriptions. - Explanation for the necessity of bridging if your network is bridged. - Routing technologies (routers, routing protocols) you will be using. - Any other details which might strengthen the justification for your request. This information is requested to insure the allocation is being APNIC Staff [Page 3] APNIC-001.2 February 1995 made appropriately. As IP address space is a limited resource which is becoming scarce, the IANA, IAB, IETF, and other Internet bodies have established policies to ensure fair and efficient distribution of the remaining IP address space. The registries are required to implement those policies as best they can. Finally, when requesting IP address space, please ensure you have read and understood RFC 1466 which explains the current procedures for allocating IP addresses. For instructions on obtaining a copy of RFC 1466, see appendix B. 4.0 IP Request Form Format This section will guide you in completing the APNIC IP number request form correctly. Note that the various registries may have their own forms and you will likely be required to use those forms due to specific requirements of those registries -- please contact your local registry if unsure. The format of the form is designed to enable APNIC to process your application quickly. Please be careful to follow the information below and as described in examples. A completed template is also included for reference. Please be aware that statements made in this form can be used in consideration of future applications that are made. Part A - Administrative Details The information supplied for this section together with the assigned network numbers will be entered into a database of Asia Pacific network numbers and their contact information which is accessible by the entire Internet community. NETWORK TEMPLATE netname: Please complete with an appropriate network name for the network to be numbered which is short and meaningful. The `netname' is used mainly for administrative purposes like consistency checking of the Internet Registry. You will most likely not see this name appear anywhere, but on forms like this. The network name should be written in less than 25 capital alphabetic letters only. Please do not use punctuation, special characters or a prefix or suffix of 'NET', 'LAN', etc (unless they are part of your company name). Example: netname: TBIT descr: APNIC Staff [Page 4] APNIC-001.2 February 1995 Please complete with a short description of the organisation, including the location. The full postal address is not needed as this is required in the person template. Example: descr: Terabit Labs Inc. descr: Network Bugs Feeding Facility descr: Northtown country: Please give the two letter country code (ISO 3166) which is appropriate for the organisation. We know this gives problems for networks crossing national boundaries, so choose the most appropriate country, based on the location of the admin contact. Please see appendix C if you do not know the appropriate code for your country. Example: country: JP admin-c: Please complete with the name or NIC handle of the person who is the administrative contact for the network. The NIC handle (if known) is preferred. This person must be someone who is physically located at the site of the network. Please do not use formal titles like `Dr' or `Prof.' or `Sir'. Please specify as in the example below (or with the NIC handle). Do not add periods between the names or initials stating first name, last name. Example: admin-c: John E Doe or with a NIC handle admin-c: JD0401 tech-c: Please give the name of technical contact person (or NIC handle as mentioned above). There can be more than one name specified for the technical contact. NOTE: please give names for both the administrative AND the technical contact. If different names are not appropriate, then the same name for both contacts is fine. Example: tech-c: Mark A Smith or with a NIC handle tech-c: MS0403 APNIC Staff [Page 5] APNIC-001.2 February 1995 changed: Email address of the person who is completing the template, followed by the current date. If you do not have email connectivity please leave blank and we will complete it. Please add the date in the format shown below. Example: changed: johndoe@terabit.na 930225 source: Source of the information. For the purposes of this form, it will always be APNIC. This is information which is always required in the database, so it has been added to the form already. PERSON TEMPLATE For each different person specified in the network template, please complete a separate person template, unless the data about those persons is already in the APNIC database. This template should be completed, one for each person mentioned in the "Network" template. This example is for the admin contact: John Doe. person: Please give the full name of the persons specified in the admin-c contact and the tech-c contact fields. The names must be written identically to those given in the "admin-c:" and "tech-c:" attributes (but must not be the NIC handle or official titles like `Dr, Prof. or Sir. Do not add periods between the names or initials stating first name, last name). Example: person: John E Doe address: Please complete with the full postal address, and write as you would for ordinary postal mail using one line for each part of the address as shown below. Example: address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NL-1234 Northtown address: Niue phone: APNIC Staff [Page 6] APNIC-001.2 February 1995 Please give the work telephone number of the person specified above. Please specify the telephone number with + . Most countries should drop the leading zero when specifying their area code. More than one telephone number is fine. Each telephone number should be put on a separate line and written in order of the most appropriate number for the contact person. Example: phone: +81 20 1233 4676 phone: +81 20 1233 4677 ext. 4711 fax-no: Please complete with the facsimile number of the person specified above. Follow the same rules as specified for telephone number above. Example: fax-no: +81 20 12334678 e-mail: Please supply the appropriate electronic mail address for the admin-c (the administrative contact person) and/or the tech-c (the technical contact person). Please ensure that this is a valid RFC-822 domain address. If you DO NOT have e-mail connectivity, please leave this blank as the email attribute will not be included in the administrative details stored in the database for this person. Example: e-mail: johndoe@terabit.na nic-hdl: This refers to a NIC handle which is a unique identifier assigned and used by a registry to unambiguously refer to Internet people. If you do not have a NIC handle, then please leave blank. Example: nic-hdl: JD0401 changed: By whom and when this was last changed. Please complete with your e-mail address followed by the current date in the format which is shown below. If you do not have e-mail connectivity, please leave blank and we will complete this on your behalf. Example: changed: johndoe@terabit.na 930225 APNIC Staff [Page 7] APNIC-001.2 February 1995 source: Source of the information. It will always be APNIC. This is information which is always required in the database, so it has been added already. Part B - Technical Details Information supplied below helps us to evaluate and process your request. It will be kept in CONFIDENCE and is for internal use only. It will NOT be entered into the APNIC Network Management Database. TECHNICAL TEMPLATE host-bits: Please indicate the type of request you are making in terms of bits of host address space. This format reflects the classless network architecture the Internet is moving towards. For example, a request with host-bits: 8 would indicate 2**8 (256) possible host addresses, equivalent to a single class C network in the (deprecated) class-full world. Please use the following guidelines from RFC 1466 to determine how many host-bits you should request: Requires fewer than 256 addresses -> 8 bits of host address (1 class C network) 512 addresses -> 9 bits of host address (2 class C networks) 1024 addresses -> 10 bits of host address (4 class C networks) 2048 addresses -> 11 bits of host address (8 class C networks) 4096 addresses -> 12 bits of host address (16 class C networks) 8192 addresses -> 13 bits of host address (32 class C networks) 16384 addresses -> 14 bits of host address (64 class C networks) 32768 addresses -> 15 bits of host address (128 class C networks) 65536 addresses -> 16 bits of host address (1 class B network) Note that large request may require significant additional documentation. Example: host-bits: 9 connect: Will your network be connecting to the global Internet? Please indicate one of: yes you plan on being fully connected, e.g. all (or most) hosts on your network will have full access to (and be APNIC Staff [Page 8] APNIC-001.2 February 1995 fully accessible from) the global Internet with the inherent security risks this implies. partial part of the network will be connected, but a majority of the hosts on the network will not be global Internet accessible. no you have no intention of having any part of the network connected to the Internet. unsure your plans on connecting to the Internet aren't established at this time. If you answer 'partial' or 'no', we request you review RFC 1597 (but, for a contrary view, please see RFC 1627). If you decide that RFC 1597 private nets will suffice for your needs, you do not need to submit a form to APNIC. Example: connect: yes classless: Will your network be entirely classless? In this context, 'classless' means that your entire network supports variable length subnet masks and that you exchange classless routing information with your service provider. Please answer 'yes', 'no', or 'unsure'. Example: classless: yes single-home: Will your network be connected to the global Internet via exactly one service provider? If you are not attaching to the Internet, please leave this field blank. If you will connect, please answer, 'yes', single-home: yes service-provider: Please provide the name and address of your service provider using multiple service-provider: lines as necessary. If you are not connecting or you are unsure of who you are connecting through, you may leave this field blank. Note: it is requested that you contact your service provider for address space *before* coming to APNIC. Example: service-provider: FOONet, Inc. service-provider: Fubar Bldg., Suite 1234 service-provider: 5678 North Rd. service-provider: South Nowhere, 90123 service-provider: Bhutan APNIC Staff [Page 9] APNIC-001.2 February 1995 sub-registry: Are you planning to become a local Internet registry, e.g., will the addresses you are requesting for your network be delegated to your customers either temporarily or permanently? Please answer 'yes' or you can obtain address space -- APNIC will contact you with the details. Example: sub-registry: no network-plan: Please provide a summary of your network plans for the next two years. The format of this field is: where: is the dotted decimal network number (preceded by x's, e.g. x.x.0.0) is the netmask for the network in dotted decimal form, e.g. 255.255.255.240 is the number of devices initially planned on the network is the number of devices planned on the network after 1 year is the number of devices planned on the network after 2 years is a descriptive remark about the network. Please separate each field with at least one space. You may use as many network-plan: fields as necessary to accurately describe your network. In your device estimates, be sure to include all devices which will need globally unique IP numbers, including PCs, workstations, servers, printers, routers, etc. Example: network-plan: x.x.0.0 255.255.255.240 1 5 11 support group network-plan: x.x.0.16 255.255.255.240 4 8 8 customer svc network-plan: x.x.0.32 255.255.255.240 10 10 10 int. dial up network-plan: x.x.0.48 255.255.255.240 2 10 12 marketting network-plan: x.x.0.64 255.255.255.192 0 0 0 spare network-plan: x.x.0.128 255.255.255.128 1 64 126 customer lines network-plan: x.x.1.0 255.255.255.0 0 128 254 customer lines country-net: Please provide a list of the ISO-3166 country codes for the countries APNIC Staff [Page 10] APNIC-001.2 February 1995 your network will operate in, each separated by spaces or by using multiple net-country: fields. If you do not know the ISO-3166 country code, see Appendix C. Example: country-net: JP AU KR ID country-net: SG TW TH MN TO old-network: If any part of your organisation (including subsidiaries and the parent company) has received address space in the past, please specify the actual network numbers allocated specifying the number of devices on each network using the following format: where: is the dotted decimal network number (preceded by x's, e.g. x.x.0.0) is the netmask for the network in dotted decimal form, e.g. 255.255.255.240 is the number of devices on the network is a descriptive remark about the network. If you have not had networks allocated to you in the past, please leave this field blank. Example: old-network: 202.5.10.0 255.255.255.0 220 R&D Division old-network: 202.5.11.0 255.255.255.128 104 Marketting old-network: 202.5.11.128 255.255.255.128 112 Sales source: Source of the information. It will always be APNIC. This is information which is always required in the database, so it has been added already. Part C - Comments Use this section to provide any comments or additional justification you feel necessary. Part D - Proxy Details This section should be completed *ONLY IF* you are making an appli- cation on behalf of another organisation. Please indicate by whom the application is being made and on behalf of whom, giving all the contact APNIC Staff [Page 11] APNIC-001.2 February 1995 details requested. 5.0 "Non-Connected" Networks and RFC 1597 Current assignment guidelines require address space to be used efficiently. If there is no plan to connect the networks for which address space is requested to the Internet for security reasons or oth- erwise, or if you wish to reserve address space for administrative con- venience, please evaluate if RFC 1597 is appropriate for your network (or part thereof). This RFC contains important information regarding the policies/procedures that should be used when IP address space is requested for networks that do not plan to connect to the Internet in the foreseeable future. However, the use of RFC 1597 private networks is highly controversial. In order to provide a balanced view, we recom- mend reading both RFC 1597 and a contrary view found in RFC 1627. If you have any questions regarding the applicability of these RFCs to your particular case, please contact APNIC. 6.0 "Additional Hints" when Requesting Additional Address Space When additional network numbers are needed by an organisation the application should include information on the utilization of address space already held by the same organisation. This information needs to include the number of actually used/unused IP network numbers, the number of actually installed subnets, hosts connected to these and more structural information which may be appropriate to substantiate the new request. This data for previously assigned network numbers provides essential input for global monitoring of utilization of IP address space and feedback to registry operation. To summarise the object of request- ing this information is to: o ensure proper use is made of the available address space o have single contiguous blocks of addresses assigned if possible (so routing information can be aggregated) For this a good estimate of real network requirements is needed and planning not just for the immediate needs or a specific parts of a net- work is encouraged. 7.0 "Additional Hints" for Requesting Class B Network Numbers The criteria for allocating Class B network addresses are extremely strict. This is due to the global scarcity of these network numbers. Out of necessity the local registries and APNIC must closely examine each and every request received for a class B network address. As a result, the allocation process for class B requests will take longer. Organisations can speed up the process by providing as much information as possible on their initial request to enable a decision to be made APNIC Staff [Page 12] APNIC-001.2 February 1995 without having to request more information. The number of hosts estimated should be substantiated with other data about the network and/or organisation like number of employees, geographical distribution, type of hosts, etc. The clearer you can document that your estimates are carefully derived, the easier it is for us to justify allocation of a class B address. Besides a sufficient number of hosts we must determine that your network cannot be engineered using a number of contiguous class C net- works. If your network consists of a large number of physical networks with relatively small numbers of hosts on each, you will need to con- sider subnetting class C networks. A large number of subnetworks alone is not sufficient justification for allocation of a class B network number. We realise that a number of engineering decisions can be based on administrative convenience. Unfortunately the remaining class B address space is too small to take these considerations into account. The clearer your explanation is, as to why your network *cannot* be engineered using a block of class C network numbers, the easier it is for us to justify allocation of a class B network address. All the above mentioned points apply even more strongly to cases where multiple class B network numbers are requested. Assignments of multiple class B network numbers will only occur when your local regis- try, APNIC, and perhaps the IANA are convinced with a detailed justifi- cation in terms of the criteria mentioned. 8.0 Conclusion In summary, please understand that APNIC does not intend to work against you, but with the whole Internet community to achieve a fair distribution of the remaining address space. The policies and pro- cedures for address space allocation are undergoing constant evolution as the rate of address space consumption ebbs and flows. Registries which allocate the address space are merely the organizations which implement those policies and procedures. You are encouraged to become involved with the relevant organizations such as the Internet Society, the Internet Engineering Task Force, the Internet Engineering Planning Group, etc. which are defining the policies and procedures the regis- tries implement. Finally, if you have any questions about the procedure or the information needed, please do not hesitate to contact APNIC for further guidance. APNIC Staff [Page 13] APNIC-001.2 February 1995 Appendix A -- Example Templates Example of a completed network, person and technical template #[NETWORK TEMPLATE V:2]# netname: TBIT-2 descr: Terabit Labs Inc. descr: Network Bugs Feeding Facility descr: Northtown country: NA admin-c: John E Doe tech-c: Mark A Smith changed: johndoe@terabit.na 940625 source: APNIC #[PERSON TEMPLATE V:2]# person: John E Doe address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NL-1234 Northtown address: Nauru phone: +31 20 987 6542 ext. 4711 fax-no: +31 20 123 3467 e-mail: johndoe@terabit.na nic-hdl: JD0401-NA changed: johndoe@terabit.na 940625 source: APNIC #[PERSON TEMPLATE V:2]# person: Mark A Smith address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NL-1234 Northtown address: Nauru phone: +31 20 987 6542 ext. 4712 fax-no: +31 20 123 3467 e-mail: mark.smith@terabit.na nic-hdl: MS0403-NA changed: mark.smith@terabit.na 940625 source: APNIC #[TECHNICAL TEMPLATE V:2]# APNIC Staff [Page 14] APNIC-001.2 February 1995 host-bits: 8 connect: yes classless: yes single-home: yes service-provider: Brokenet, Inc. service-provider: P. O. Box 1234 service-provider: Ocean City, 102 service-provider: Nauru sub-registry: No network-plan: x.x.0.0 255.255.255.0 4 128 230 campus net country-net: NA TO FJ old-network: 202.10.5.0 255.255.255.0 224 campus net source: APNIC APNIC Staff [Page 15] APNIC-001.2 February 1995 Appendix B -- References APNIC 002 APNIC Staff, "Asia Pacific Network Information Center IP Network Address Application Form", 2/4/95, URL: ftp://archive.apnic.net/apnic/docs/english/apnic-002.txt RFC 1466 E. Gerich, "Guidelines for Management of IP Address Space", 5/26/93, URL: ftp://archive.apnic.net/rfc/rfc1466.txt RFC 1517 R. Hinden, "Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR), 9/24/93, URL: ftp://archive.apnic.net/rfc/rfc1517.txt RFC 1518 Y. Rekhter, T. Li, "An Architecture for IP Address Allocation with CIDR", 9/24/93, URL: ftp://archive.apnic.net/rfc/rfc1518.txt RFC 1519 V. Fuller, T. Li, J. Yu, K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy", 9/24/93, URL: ftp://archive.apnic.net/rfc/rfc1519.txt RFC 1597 Y. Rekhter, R. Moskowitz, D. Karrenberg, G. de Groot, "Address Allocation for Private Internets", 3/17/94, URL: ftp://archive.apnic.net/rfc/rfc1597.txt RFC 1627 E. Lear, E. Fair, D. Crocker, T. Kessler, "Network 10 Considered Harmful (Some Practices Shouldn't be Codified)", 7/1/1994, URL: ftp://archive.apnic.net/rfc/rfc1627.txt These documents are all available from the APNIC document store in the directories mentioned in the URLs. The APNIC document store can be accessed in a number of ways: 1. via anonymous FTP from host archive.apnic.net Using your ftp application (usally called simply 'ftp'), connect to host archive.apnic.net using your email address as the password. For RFCs, use the "change directory" command (typically 'cd') to 'rfc'. For APNIC documents, 'cd' to 'apnic/docs/english'. You may then use the "get" command (typically 'get') to retrieve the file. 2. via gopher from host gopher.apnic.net Using your gopher application (usually called 'gopher'), connect to host gopher.apnic.net. For RFCs go down the "Information About Internet" branch, then down the "RFCs, FYIs, & STDs" branch and choose the correct RFC branch to go down. For APNIC documents, go down the "Information about APNIC branch, then the "docs" branch, then the "english" branch. The actual mechanism you use to traverse branches of the gopher tree depends on your gopher application. APNIC Staff [Page 16] APNIC-001.2 February 1995 3. via electronic mail through the APNIC FTP Email gateway You may send mail to 'ftpmail@postoffice.apnic.net' with the body of the message being standard Unix 'ftp' commands. For more help, send an email message to 'ftpmail@postoffice.apnic.net' with a message body consisting of 'help'. Results will be mailed back to you. Organizations without connectivity wishing to obtain copies of the "Recommended Reading" articles should contact the APNIC or their local or national registry to arrange postal delivery of one or more of the above documents. Note that some fee may be associated with the delivery of hardcopy versions of documents. APNIC Staff [Page 17] APNIC-001.2 February 1995 Appendex C -- ISO 3166 Country Codes Codes from ISO 3166 Updated by the RIPE Network Coordination Centre, in coordination with the ISO 3166 Maintenance Agency at DIN Berlin. Latest change: Thu Feb 10 10:20:28 MET 1994 Country A 2 A 3 Number ---------------------------------------------------------------------- AFGHANISTAN AF AFG 004 ALBANIA AL ALB 008 ALGERIA DZ DZA 012 AMERICAN SAMOA AS ASM 016 ANDORRA AD AND 020 ANGOLA AO AGO 024 ANGUILLA AI AIA 660 ANTARCTICA AQ ATA 010 ANTIGUA AND BARBUDA AG ATG 028 ARGENTINA AR ARG 032 ARMENIA AM ARM 051 ARUBA AW ABW 533 AUSTRALIA AU AUS 036 AUSTRIA AT AUT 040 AZERBAIJAN AZ AZE 031 BAHAMAS BS BHS 044 BAHRAIN BH BHR 048 BANGLADESH BD BGD 050 BARBADOS BB BRB 052 BELARUS BY BLR 112 BELGIUM BE BEL 056 BELIZE BZ BLZ 084 BENIN BJ BEN 204 BERMUDA BM BMU 060 BHUTAN BT BTN 064 BOLIVIA BO BOL 068 BOSNIA AND HERZEGOWINA BA BIH 070 BOTSWANA BW BWA 072 BOUVET ISLAND BV BVT 074 BRAZIL BR BRA 076 BRITISH INDIAN OCEAN TERRITORY IO IOT 086 BRUNEI DARUSSALAM BN BRN 096 BULGARIA BG BGR 100 BURKINA FASO BF BFA 854 BURUNDI BI BDI 108 CAMBODIA KH KHM 116 CAMEROON CM CMR 120 APNIC Staff [Page 18] APNIC-001.2 February 1995 CANADA CA CAN 124 CAPE VERDE CV CPV 132 CAYMAN ISLANDS KY CYM 136 CENTRAL AFRICAN REPUBLIC CF CAF 140 CHAD TD TCD 148 CHILE CL CHL 152 CHINA CN CHN 156 CHRISTMAS ISLAND CX CXR 162 COCOS (KEELING) ISLANDS CC CCK 166 COLOMBIA CO COL 170 COMOROS KM COM 174 CONGO CG COG 178 COOK ISLANDS CK COK 184 COSTA RICA CR CRI 188 COTE D'IVOIRE CI CIV 384 CROATIA (local name: Hrvatska) HR HRV 191 CUBA CU CUB 192 CYPRUS CY CYP 196 CZECH REPUBLIC CZ CZE 203 DENMARK DK DNK 208 DJIBOUTI DJ DJI 262 DOMINICA DM DMA 212 DOMINICAN REPUBLIC DO DOM 214 EAST TIMOR TP TMP 626 ECUADOR EC ECU 218 EGYPT EG EGY 818 EL SALVADOR SV SLV 222 EQUATORIAL GUINEA GQ GNQ 226 ERITREA ER ERI 232 ESTONIA EE EST 233 ETHIOPIA ET ETH 231 FALKLAND ISLANDS (MALVINAS) FK FLK 238 FAROE ISLANDS FO FRO 234 FIJI FJ FJI 242 FINLAND FI FIN 246 FRANCE FR FRA 250 FRANCE, METROPOLITAN FX FXX 249 FRENCH GUIANA GF GUF 254 FRENCH POLYNESIA PF PYF 258 FRENCH SOUTHERN TERRITORIES TF ATF 260 GABON GA GAB 266 GAMBIA GM GMB 270 GEORGIA GE GEO 268 GERMANY DE DEU 276 GHANA GH GHA 288 GIBRALTAR GI GIB 292 GREECE GR GRC 300 GREENLAND GL GRL 304 APNIC Staff [Page 19] APNIC-001.2 February 1995 GRENADA GD GRD 308 GUADELOUPE GP GLP 312 GUAM GU GUM 316 GUATEMALA GT GTM 320 GUINEA GN GIN 324 GUINEA-BISSAU GW GNB 624 GUYANA GY GUY 328 HAITI HT HTI 332 HEARD AND MC DONALD ISLANDS HM HMD 334 HONDURAS HN HND 340 HONG KONG HK HKG 344 HUNGARY HU HUN 348 ICELAND IS ISL 352 INDIA IN IND 356 INDONESIA ID IDN 360 IRAN (ISLAMIC REPUBLIC OF) IR IRN 364 IRAQ IQ IRQ 368 IRELAND IE IRL 372 ISRAEL IL ISR 376 ITALY IT ITA 380 JAMAICA JM JAM 388 JAPAN JP JPN 392 JORDAN JO JOR 400 KAZAKHSTAN KZ KAZ 398 KENYA KE KEN 404 KIRIBATI KI KIR 296 KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF KP PRK 408 KOREA, REPUBLIC OF KR KOR 410 KUWAIT KW KWT 414 KYRGYZSTAN KG KGZ 417 LAO PEOPLE'S DEMOCRATIC REPUBLIC LA LAO 418 LATVIA LV LVA 428 LEBANON LB LBN 422 LESOTHO LS LSO 426 LIBERIA LR LBR 430 LIBYAN ARAB JAMAHIRIYA LY LBY 434 LIECHTENSTEIN LI LIE 438 LITHUANIA LT LTU 440 LUXEMBOURG LU LUX 442 MACAU MO MAC 446 MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF MK MKD 807 MADAGASCAR MG MDG 450 MALAWI MW MWI 454 MALAYSIA MY MYS 458 MALDIVES MV MDV 462 MALI ML MLI 466 MALTA MT MLT 470 MARSHALL ISLANDS MH MHL 584 APNIC Staff [Page 20] APNIC-001.2 February 1995 MARTINIQUE MQ MTQ 474 MAURITANIA MR MRT 478 MAURITIUS MU MUS 480 MAYOTTE YT MYT 175 MEXICO MX MEX 484 MICRONESIA, FEDERATED STATES OF FM FSM 583 MOLDOVA, REPUBLIC OF MD MDA 498 MONACO MC MCO 492 MONGOLIA MN MNG 496 MONTSERRAT MS MSR 500 MOROCCO MA MAR 504 MOZAMBIQUE MZ MOZ 508 MYANMAR MM MMR 104 NAMIBIA NA NAM 516 NAURU NR NRU 520 NEPAL NP NPL 524 NETHERLANDS NL NLD 528 NETHERLANDS ANTILLES AN ANT 530 NEW CALEDONIA NC NCL 540 NEW ZEALAND NZ NZL 554 NICARAGUA NI NIC 558 NIGER NE NER 562 NIGERIA NG NGA 566 NIUE NU NIU 570 NORFOLK ISLAND NF NFK 574 NORTHERN MARIANA ISLANDS MP MNP 580 NORWAY NO NOR 578 OMAN OM OMN 512 PAKISTAN PK PAK 586 PALAU PW PLW 585 PANAMA PA PAN 591 PAPUA NEW GUINEA PG PNG 598 PARAGUAY PY PRY 600 PERU PE PER 604 PHILIPPINES PH PHL 608 PITCAIRN PN PCN 612 POLAND PL POL 616 PORTUGAL PT PRT 620 PUERTO RICO PR PRI 630 QATAR QA QAT 634 REUNION RE REU 638 ROMANIA RO ROM 642 RUSSIAN FEDERATION RU RUS 643 RWANDA RW RWA 646 SAINT KITTS AND NEVIS KN KNA 659 SAINT LUCIA LC LCA 662 SAINT VINCENT AND THE GRENADINES VC VCT 670 SAMOA WS WSM 882 APNIC Staff [Page 21] APNIC-001.2 February 1995 SAN MARINO SM SMR 674 SAO TOME AND PRINCIPE ST STP 678 SAUDI ARABIA SA SAU 682 SENEGAL SN SEN 686 SEYCHELLES SC SYC 690 SIERRA LEONE SL SLE 694 SINGAPORE SG SGP 702 SLOVAKIA (Slovak Republic) SK SVK 703 SLOVENIA SI SVN 705 SOLOMON ISLANDS SB SLB 090 SOMALIA SO SOM 706 SOUTH AFRICA ZA ZAF 710 SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS GS SGS 239 SPAIN ES ESP 724 SRI LANKA LK LKA 144 ST. HELENA SH SHN 654 ST. PIERRE AND MIQUELON PM SPM 666 SUDAN SD SDN 736 SURINAME SR SUR 740 SVALBARD AND JAN MAYEN ISLANDS SJ SJM 744 SWAZILAND SZ SWZ 748 SWEDEN SE SWE 752 SWITZERLAND CH CHE 756 SYRIAN ARAB REPUBLIC SY SYR 760 TAIWAN, PROVINCE OF CHINA TW TWN 158 TAJIKISTAN TJ TJK 762 TANZANIA, UNITED REPUBLIC OF TZ TZA 834 THAILAND TH THA 764 TOGO TG TGO 768 TOKELAU TK TKL 772 TONGA TO TON 776 TRINIDAD AND TOBAGO TT TTO 780 TUNISIA TN TUN 788 TURKEY TR TUR 792 TURKMENISTAN TM TKM 795 TURKS AND CAICOS ISLANDS TC TCA 796 TUVALU TV TUV 798 UGANDA UG UGA 800 UKRAINE UA UKR 804 UNITED ARAB EMIRATES AE ARE 784 UNITED KINGDOM GB GBR 826 UNITED STATES US USA 840 UNITED STATES MINOR OUTLYING ISLANDS UM UMI 581 URUGUAY UY URY 858 UZBEKISTAN UZ UZB 860 VANUATU VU VUT 548 VATICAN CITY STATE (HOLY SEE) VA VAT 336 VENEZUELA VE VEN 862 APNIC Staff [Page 22] APNIC-001.2 February 1995 VIET NAM VN VNM 704 VIRGIN ISLANDS (BRITISH) VG VGB 092 VIRGIN ISLANDS (U.S.) VI VIR 850 WALLIS AND FUTUNA ISLANDS WF WLF 876 WESTERN SAHARA EH ESH 732 YEMEN YE YEM 887 YUGOSLAVIA YU YUG 891 ZAIRE ZR ZAR 180 ZAMBIA ZM ZMB 894 ZIMBABWE ZW ZWE 716 APNIC Staff [Page 23]