------------------------------------------------------------------- APNIC Document identity Title: Asia Pacific Network Information Center Pilot Project Final Report Short title: project-final-report Document ref: APNIC-009 Version: 001 Date of original publication: 1 July 1994 Date of this version: 1 July 1994 Review scheduled: n/a Obsoletes: n/a Status: Historical Comments: n/a -------------------------------------------------------------------- APNIC-009.0 V. Gebes Informational Document June 1994 Asia Pacific Network Information Center Pilot Project Final Report Issued: July 1, 1994 Expires: Not Applicable 1.0 Introduction In the 10 months of it's operation, the Asia Pacific Network Infor- mation Center pilot project has proven very successful in its mission to identify and provide IP networking coordination and administration ser- vices necessary for the growing population of networking organizations in the AP region. This final report reviews the original goals of the project, and discusses the progress made toward those goals, focusing especially on the revision and expansion of initial plans, the results obtained, and the current status of APNIC operations and activities. Finally, conclusions are drawn about the success of the project and the significance of APNIC operations to networking in the Asia Pacific region. 2.0 Project Review The creation of an APNIC to provide network information and regis- tration services to organizations in the AP region was discussed at the first APCCIRN meeting, in January, 1993[1]. After continued planning among the APCCIRN members, the operational phase of a pilot project to study the necessity of and requirements for an APNIC began on September 1, 1993. This pilot project was scheduled to last for an initial trial period of up to 10 months, and funding for the pilot project was pro- vided by the JPNIC, which generously donated 10% of its 1993 budget to support APNIC operations [2]. The project has proceeded through the following milestones, which mark the progress which was achieved. September 1, 1993 Pilot Project Proposal Issued December 10, 1993 Midterm Report Issued December 10, 1993 APNIC Operational Proposals Document Issued December 10, 1993 Organizational Proposal / Prelim. Budget Issued April 1, 1994 Delegation of class C address space from IANA June 30, 1994 Final Report Issued 3.0 Project Goals for the APNIC V. Gebes [Page 1] APNIC-009.0 June 1994 Several project goals for the APNIC pilot project are discussed in the various documents listed above. In particular, the original propo- sal document, and the operational proposals document state the main goals which guided the planning and operation of the APNIC. 3.1 Original Pilot Project Goals A Pilot Project Proposal was issued on September 1, 1993, outlining the primary goals and objectives of the APNIC pilot project. The pro- ject was intended to provide a testbed for experimentation into the area of network coordination within the AP region and also among the various regional NICs and NCCs. In order to meet these objectives, the Pilot Project Proposal put forth an initial set of functions to be provided by an APNIC, and also a set of requirements which were deemed to be neces- sary to provide those funcitons [2]. 3.1.1 Functions of the APNIC The initial functions identified by the proposal include Internet Registry functions and Routing Registry functions. Internet Registry functions consist mainly of IP address allocation management and WHOIS database administration, and also include such tasks as DNS delegation. Routing Registry functions entail the creation of databases to support regional and global routing, such as routing policy or CIDR aggregation databases. 3.1.2 Requirements of the APNIC The corresponding requirements consisted of funding, hardware, software, and personnel requirements. It is important to note that the requirements specified for the pilot project are somewhat less demanding than those for continued APNIC work, although the basic functionality will not change. A budget proposal for the first 3 years of APNIC operation was issued on December 10, 1993, which outlines the expected requirements and budget needs for this period [3]. 3.2 Extended Proposals for APNIC Although the initially proposed functions and requirements provided the necessary framework for preliminary planning and early operational decisions, actual work toward the establishment and smooth administra- tion of the APNIC exposed many additional areas which also required attention. As a result, a document outlining several proposals for APNIC operations was presented at the APCCIRN meeting in Taiwan in December, 1993, along with the Midterm Report document. These proposals were the result of discussions carried out primarily through the apnic- staff mailing list, one of 3 mailing lists dedicated to APNIC adminis- trative and operational issues. Details concerning the mailing lists V. Gebes [Page 2] APNIC-009.0 June 1994 can be found in Appendix 1. The apnic-staff list was especially instru- mental in shaping the objectives of the APNIC by providing a highly accessable forum for the discussion of actions, policies, and services to be implemented by the APNIC. Briefly, the following proposals were put forth in the document: 1. Definition and provision of various Internet Registry functions of the APNIC 2. Definition of the Asia Pacific region 3. Class B network allocation policy 4. Class C network allocation strategy for the APNIC region 5. Selection of WHOIS database software to be used for APNIC functions and services 6. Adoption of a common NIC domain name format for national NICs in the AP region 7. Creation of a common format for national NIC contact point email addresses 8. Information distribution services to be offered by national NICs 9. Local language support for APNIC documentation and databases 10. Creation of a routing registry to serve the AP region 11. Creation of guidelines for the certification of national NICs in the AP region 12. Creation of a repository for information and statistics about networking in the AP region. These proposals served to further expand upon the APNIC functional goals which were identified in the original pilot project proposal docu- ment. The results of these proposed actions are discussed below. 4. Pilot Project Results The APNIC has been quite successful in meeting the above goals, and continues to refine these goals as more experience is gained through actual operation. Most of the functional aspects of the APNIC which were addressed in the proposals document have been studied to some extent, and many are already being implemented as part of the current V. Gebes [Page 3] APNIC-009.0 June 1994 APNIC operating envirionment. Most significantly, the APNIC has received delegation of the 202.x.x.x and 203.x.x.x C address blocks, from which it is currently allocating addresses to networking organiza- tions in the AP region. As discussed below, the APNIC is providing allocation services both for established national NICs and network pro- viders in the AP region, and also directly to end user organizations which don't have access to such a first level IP regristry or service organization. 4.1 Progress toward implementation of proposed APNIC functionality The following sections review briefly the proposals for APNIC func- tionality listed above, and discuss the progress toward implementation of each of these proposals. 4.1.1 APNIC IR Functions The first and primary goal of the APNIC has been to establish necessary Internet Registry services, and to begin the actual operation of the APNIC based on these services. 4.1.1.1 Asia Pacific Address Block Delegation The most obvious and important function of the APNIC in the short term consists of Internet Registry services for the AP region. The first big step in the implementation of this functionality was taken on April 1, 1994, with the official delegation of the 202.x.x.x and 203.x.x.x class C address blocks from the IANA. In the time since this delegation, the APNIC has been responsible for subdelegation of C address blocks to national NICs and ISPs in the AP region, as well as direct allocation to organizations in areas without such NICs or ISPs. The strategies for subdelegation and assignment of this address space is further disussed later. 4.1.1.2 APNIC Distributed Operation Model With the delegation came the immediate need to implement several of the other proposals for Internet Registry administration, such as WHOIS database selection and operation, DNS operation, and information service provision. In keeping with the distributed nature of the APNIC organi- zation, these services have been offered cooperatively by several of the individual members and organizations participating in the APNIC pilot project. For example, DNS operation has been provided by the AUNIC. In fact, a proposal for officially defining a distributed operating environment for the APNIC was submitted by the KRNIC on December 8, 1993 [4]. This document proposes that APNIC operations be modeled on the InterNIC organization, by distinctly defining three branches, V. Gebes [Page 4] APNIC-009.0 June 1994 Information Services, Registration Services, and Directory Services, to be provided by different national NICs, and possibly on a rotating basis. KRNIC generously offered to help implement one branch of func- tionality for the first 2 years of APNIC operation (1994 - 1995), and has begun operation of a WWW server in support of IS functions. Simi- larly, the TWNIC plans to submit a proposal for operation of a gopher server to supplement current services. 4.1.1.3 APNIC Top Level Information Repository In addition to the information services provided by the KRNIC, the APNIC makes public a growing amount of information through public servers operated on APNIC.NET. All published APNIC proposals, docu- ments, and forms are avialable via gopher and anonymous ftp, for exam- ple. There is also information on other related projects such as the Shared Whois Project (SWIP), which is discussed briefly later. Finally, the WHOIS database which was set up during the first half of the project is now being populated with AP region networking information. This and other APNIC administrative and operational information will continue to be available to the public on this machine. Addition of other informa- tion such as RFCs and Internet Drafts has yet to be completed. 4.1.1.4 Initial Contact Point for AP Networking Information Aside from the IP address allocation work discussed above, perhaps the most time consuming part of APNIC operations consists of responding to queries about connectivity and IP service availability in the AP region. Because the APNIC has reserved a common national NIC domain name for each country which is expected to require APNIC service in the future, as discussed below, several requests come each week from people who have stumbled across the XXNIC.NET domain name, and want to know the current status of networking in a country, how to go about obtaining IP service there, or how to find the email address or network contact point for a particular person or organization. Since often there is little information about the rapidly changing status of connectivity in many of these countries, it can be quite difficult and time consuming to provide quality answers to these queries. It is hopeful that as the database of AP networking information grows, more of this kind of information can be offered in an easily searchable format on public servers by the APNIC. 4.1.1.5 Current Status of the National NICs Although, as discussed further below, no concrete requirements for national NICs have been formalized as of yet, several national NICs have already been established to provide services to networking organizations within their respective countries, and indeed many of these actually predate the APNIC. Currently, national NICs are operating in Australia (AUNIC), Japan (JPNIC), Korea (KRNIC), and Taiwan (TWNIC). V. Gebes [Page 5] APNIC-009.0 June 1994 Additionally, many countries without national NICs do have Internet ser- vice providers, and to facilitate efficient address allocation and effective implementation of CIDR, the APNIC policy has been to allocate a block of C addresses from within a country block to such providers, as per the "super-block" allocation scheme described later. The creation of national NICs in countries with any significant amount of networking activity is considered extremely important. Because of limits on the APNIC's manpower, language, and budget resources, such organizations will play a key role in ensuring quality NIC services to all users. It is hoped that the continued promotion of country NICs will result in many such organizations, which can both better serve the end users in their particular countries, and also relieve the APNIC of some operational burden by distributing the workload. This promotion activity will remain one of the APNIC's prime objectives. 4.1.2 Definition of AP region There was quite a bit of discussion both among APNIC staff members and between the APNIC and other regional coordinating bodies (ie InterNIC and RIPE NCC) concerning exactly which countries and terri- tories should be considered part of the AP region for APNIC purposes. For example, it is likely to be unclear at times whether requests from a certain country should be handled by RIPE or by the APNIC. The defini- tion of AP in this case has been left specifically vague, so that later coordination between the APNIC, InterNIC, and RIPE, for example, may be employed to make decisions about the operational jurisdiction of each. Currently, however, a preliminary list of countries which the APNIC expects to serve can be obtained by noting the countries for which the APNIC has reservied a XXNIC.NET domain name, as explained later. This list is also attached as APPENDIX 2. While this is in no way intended to be a strict definition of limits for APNIC operational jurisdiction, this list does serve to give a general idea of the expected area of APNIC operations. 4.1.3 Class B network allocation policy The APNIC has implemented the proposal to become a "first line" interface for class B as well as class C requests quite successfully, in many cases being able to educate applicants of address space limitations and of network design techniques which allow them to substantially reduce the amount of address space requested. Often applicants are unaware of options such as VLSMs and private network addressing, and are able to lower the number of addresses requested when presented with these options. Because of the amount of time and technical expertise required to help users in this way, we believe that it is essential for V. Gebes [Page 6] APNIC-009.0 June 1994 regional and national NICs to provide this support for class B applica- tion processing. This enables distribution of the workload among the various NICs and further results in the initial processing of requests being done at the level closest to the applicant, allowing a higher degree of coordination with the applicant and hopefully a corresponding higher quality of service. Applications which are judged by the APNIC address allocation staff to provide sufficient justification for a class B network are forwarded to the InterNIC for processing. Justification is judged using the guidelines presented in RFC 1466. The APNIC staff believes that this procedure for processing class B requests has proven to be quite useful and effective. 4.1.4 Class C network allocation policy The APNIC has implemented the "superblock" allocation scheme for class C networks, as described in the proposals document. In review, this scheme aims to provide a flexible framework for allocations and delegations of the class C address space set aside for the AP region on a country by country basis. By reserving loosly defined "super-blocks" of addresses for a particular country, it is hoped that an adjustable amount of address space can be allocated to a country as needed, while also maximizing the usefulness of CIDR in restricting the growth of the global routing table. The scheme, as currently implemented, is set up as follows. At the time of delegation, a map of prior allocations in the 202.x.x.x and 203.x.x.x address blocks was created to show currently used or delegated addresses in that area. Then for each country, a best guess estimate was made of future address usage, and a rough idea of the "superblock boundaries" was formed. New allocations and delegations to a particular country or ISP are made from one end of the superblock for that country, and expand toward the next superblock, allowing the super- blocks to flexibly grow to a "right size" through further IP address allocations. It is hoped that this allocation scheme will have the following effects (1) Flexible address allocation for each country Because this allocation policy allows for the superblocks to grow toward each other as addresses within that block are allocated, the scheme should be effective in keeping a country's assigned address space con- tiguous to a large degree, without the necessity to make initial con- crete estimates of future address utilization. If the utilization of one block is very low, for example the next block can expand into it as V. Gebes [Page 7] APNIC-009.0 June 1994 needed. (2) Increase in CIDR benefits By assigning the address space for a country to be as contiguous as possible,it is expected that CIDR can be used more effectively to con- trol the growth of the global routing table. Additionally, the practice of assigning service provider blocks within a country "superblock" enhances these positive effects, because there is opportunity for route aggregation at both the service provider level and the country level. Also, if a user changes service providers without renumbering, it may still be possible to aggregate at the national (or regional) level some- where, assuming that the old and new service providers are both in the same country (or region) superblock. It is still too soon to see how much effect this allocation scheme will have on the regional and global routing structure, and analyzing these effects will continue to be one of the APNIC's primary concerns. 4.1.5 Selection of WHOIS software The APNIC obtained and installed the WHOIS database software in use by the European regional registry, RIPE. This software is currently being used to manage network and user data for APNIC operations and has proven quite sastifactory for this task. Additionally, there are two other projects in which the APNIC is currently participating to support the global distribution of networking information in the various regional and national NIC whois databases. The shared whois project (SWIP) was formed to address the problem of inconsistant data in multiple (eg regional, etc.) whois databases. By defining common data exchange formats and procedures, it is hoped that the distributed databases can be kept synchronized. The APNIC will participate in the SWIP project, and use the resulting formats and pro- cedures to facilitate data transactions with other NICs. More informa- tion on the shared whois project is available on apnic.net in the direc- tory /pub/projects/swip. In addition to the shared whois project, a new version of the whois protocol called referral whois (rwhois) is being implemented to support queries of distributed data. This should also aid in the management of network information by the various NICs. Rwhois provides a mechanism allowing easy lookup of information in distributed servers by providing referral records pointing to a server which "knows more" about the queried information. With this new functionality, querying clients can be further improved to follow referral records, increasing the speed and accuracy of whois database searches. The APNIC will be active in V. Gebes [Page 8] APNIC-009.0 June 1994 testing this software with the other regional NICs. 4.1.6 Common NIC domain name format The proposal to create a common domain name format for regional and national NICs has been implemented, and currently each existing national NIC in the AP region has taken the domain name XXNIC.NET, where XX corresponds to the 2 letter ISO country code for the particular country (eg AUNIC.NET, KRNIC.NET, etc.). Additionally, the APNIC has reserved such domain names for each country which is expected to be served by APNIC, but which has not yet established a national NIC. A complete list may be found in APPENDIX 2. This can sometimes be confusing for users who happen to find the XXNIC.NET domain name, and then mistakenly think that it implies the existance of an organized network or service provider in the specified country. The user will then typically contact the APNIC for more infor- mation. Since the APNIC is the proper first point of contact for coun- tries without a national NIC in the AP region, this may actually be viewed as a somewhat effective way of advertising the existance of the APNIC to users who might not find it otherwise. 4.1.7 Common NIC contact point As with the common NIC domain name format described above, a common NIC contact point email address has been implemented to facilitate con- tacting national NICs in the AP region. The mail address hostmaster@xxnic.net provides a consistently named point of contact to help make queries for information, etc. easier for users. Currently, each NIC has prepared such a point of contact address. 4.1.8 Information Distribution The proposal to mirror national NIC archives on a central APNIC machine has not been implemented yet. Although several of the national NICs have valuable information stored on their respective servers avail- able for public access, limited time and hardware have slowed the crea- tion of mirrors on an APNIC machine. As part of the KRNIC's offer to provide information services, some information is currently available on the krnic.net machine, however, such as the APCCIRN country files describing connectivity in the APNIC region. 4.1.9 Use of local languages Although it is hoped that local language support for many of the informational documents and registration forms distributed by the APNIC can be realized it has become exceedingly clear that support from the national NICs or other local networking coordination centers will be V. Gebes [Page 9] APNIC-009.0 June 1994 imperative to make this happen. Because the APNIC will not, in general, have the resources to support each local language in the AP region, it is hoped that the APNIC's encouragement of national NICs for countries with developing network resource needs will help create this local language support indirectly. Of course, many of the already well esta- blished national NICs, such as the JPNIC for example, already have an extensive amount of translated or locally generated material in the local language and publicly available. This is another example of the importance of a national NIC in providing high quality service to net- working users. 4.1.10 Routing Registry Work toward the implementation of routing registry functionality at the APNIC has been delayed due to a lack of manpower and a lower prior- ity for completion than the Internet Registry functionality. Because of the relatively simple routing topology in the APNIC region, the routing registry will be most valuable for experimentation purposes in the short term. It is hoped that such experimentation can begin soon, however, and that it will provide useful information toward better understanding of global routing issues, and eventually for dealing with increasingly complex global routing topology. 4.1.11 Certification of national NICs The APNIC staff is currently collaborating with other regional NICs to identify guidelines for the establishment of national NICs. These guidelines will address the requirements for any organization which wishes to provide NIC services for its country. Additionally, the pro- cedure for certification may be addressed. 4.1.12 Statistics Collection and Repository The final proposal in the proposals document discussed the collec- tion and distribution of information describing the networking environ- ment in the AP region. Previously, the only organized database for this sort of information was the APCCIRN country files on the APCCIRN ftp server. The APNIC staff hopes to augment this information with statist- ical information such as number and service area of various IP providers in the AP region, host numbers, and information on the number and bandwidth of links in the region. Although the actual creation of such a statistics database is not expected to be completed immediately, the APNIC staff has initiated some preliminary study, and is currently studying methods for mapping links and providers in the AP region. An inherent problem is that with the rapid rate of growth and change in the AP region, such a database will tend to become outdated very quickly. So it will be very important to V. Gebes [Page 10] APNIC-009.0 June 1994 develop a format which is easily maintained and updated. It is planned that this information will be made public, and is hoped that it may be very helpful in answering the various queries received by the APNIC regarding networking in the AP region. 5.0 Current Status and Issues 5.1 Status The APNIC is now in full operation, providing the services speci- fied above to the AP networking community on an ongoing basis. Currently, the APNIC receives between approximately 5 and 15 service requests per day, including IP address requests, requests for informa- tion about networking in a particular country, and requests for informa- tion about the APNIC itself. This is in addition to the work on pro- jects such as SWIP, which are necessary for coordination with other national NICs. There is also a significant amount of coordination with other national NICs, and between the APNIC staff members themselves, which is to be expected given the distributed nature of the APNIC. 5.2 Issues In addition to the issues already discussed, there are many other items which have come to require significant attention. 5.2.1 Creation of Machine Readable Application Forms As part of the preparation for offering IR services, the APNIC created an application form for requesting IP address space, and this form is being used for requests currently. Unfortunately, the format of the form is not exceedingly convenient as input to a program, making it slightly difficult to develop tools for machine processing of requests. Also, because the requested information is somewhat different between the APNIC and InterNIC application forms, inconsistancies and confusion with registered items can often occur. For these reasons, there is a need to work with other NICs to create a new application form which allows more consistency of distributed data, and also is designed to be easily processed by computer programs. 5.2.2 Development of Registration Support Tools Currently a great amount of time is spent by APNIC staff for appli- cation requests because of several factors, such as necessity of techni- cal support for the user, and actual registration data entry. The latter is especially frustrating because it could be automated to a great degree. If the application forms are changed to be more easily processed programatically, as discussed above, a great gain in effi- ciency is possible if tools are developed to input data directly from V. Gebes [Page 11] APNIC-009.0 June 1994 application forms into the registration databases. Such a registration system would both reduce the amount of time necessary for registration procedures and presumably would help to eliminate data entry errors as well. 5.2.3 Standardization of IP Address Usage Reports for NICs Because the APNIC staff hopes to keep some basic statistics on IP address utilization in the AP region, it would be helpful if there was some standard format for national NICs to report on address utilization. This would include such information as the number of address requests received, the number of hosts estimated, the number of addresses requested, and the number of networks allocated. Currently, the APNIC is requesting that the national NIC would pro- vide this kind of information when a new address block becomes neces- sary. A standard format would facilitate the easy transfer of data, and also make it easier to analyze the data which was collected. 5.2.4 Need for Full Time Technical Support Operational experience with APNIC has shown that a greater amount of technical resources is necessary than originally anticipated. Because of the high level of support that is often necessary for address application processing and the corresponding allocation procedures, full time technical support is an absolute necessity. Furthermore, as the networking community continues to grow in the AP region, it can be expected that this situation will be exacerbated. It seems likely that at least two technically skilled staff members will be required to pro- vide adequate services. 5.2.5 Finalization of Budgeting and Future Operations Clearly the most important issue facing the APNIC at this point in time is the finalization of plans for continuing the work which is now underway. Since the original proposal only specified a ten month period for conducting the pilot project experiment, there is currently no offi- cial plan describing the transition to a full time organization. Propo- sals for such transition and the operation of an interim APNIC during that transition are outside the scope of this report, and will be dealt with separately. 6.0 Summary and Conclusions Over the last 10 month period, the APNIC has been very active in defining and implementing programs necessary to meet the growing needs of networking organizations on the Asia Pacific region. The first half of the operating period was spent studying these needs in order to plan V. Gebes [Page 12] APNIC-009.0 June 1994 the functionality of the APNIC as to meet them in the best way. The overall organization of the APNIC was designed to allow a great degree of distributed operation, in order to take the most advantage of the geographically separated staff members. This was facilited greatly by the apnic-staff mailing list mentioned earlier. As some organizational experience was gained, the APNIC staff was able to more specifically define project goals, resulting in a new set of proposals presented along with the Midterm Report in December, 1993. Implementation of most of these proposals was soon begun, along with other necessary prepara- tions to begin full Internet Registry operation in the second half of the project. The delegation of the 202 and 203 C address blocks occured on April 1, 1994, marking the beginning of APNIC Internet Registry service opera- tion. Since that time, the APNIC has been responsible for delegations and allocations of addresses within the AP region from these blocks. Currently, more efficient operational methods are being explored, along with requirements for continuing the operations work currently under way. The progress of the APNIC pilot project was very significant, and is expected to continue at a fast pace. Through the various services offered by the APNIC and the creation and support of more national NICs in the AP region, it is believed that networking organizations can be provided a very high level of service, which might not be available oth- erwise. Also, essential regional services such as coordination between NICs and routing registry functions will also be instrumental in promot- ing increased internetworking in the AP region. 7.0 References [1] Chon, K., "Minutes of the January 1993 Honolulu APCCIRN Meeting", nic.nm.kr:/apccirn/021.minute.Jan93, January 1993. [2] Murai, J., and Conrad, D., "Asia Pacific Network Information Center Pilot Project Proposal", apnic.net:/apnic/docs/english/apnic-003.txt, August 1993. [3] APNIC Staff, "Asia Pacific Network Information Center Organizational Proposals and a Preliminary Budget", apnic.net:/apnic/docs/english/apnic-005.txt, December 1993. [4] Park, T., "Proposal for Distributed APNIC Operations", apnic.net:/apnic/docs/english/apnic-007.txt, December 1993. V. Gebes [Page 13] APNIC-009.0 June 1994 8.0 Author's Address Vincent J. Gebes AT&T Jens Spin Project No. 25 Mori Bldg, Roppongi, Minato-ku Tokyo, 106 Japan Email: vgebes@spin.ad.jp V. Gebes [Page 14] APNIC-009.0 June 1994 Appendix 1 - APNIC Pilot Project Mailing lists The APNIC-MEMBER list is intended to provide a mailing list of pol- itical contacts who will be consulted on issues of a politically sensi- tive nature. The general rule for this list is a single member per country. The APNIC-MEMBER list consists of: G.Huston@aarnet.edu.au (Australia, AARNet, Geoff Houston) cclaw@usthk.ust.hk (Hong Kong, HARNET, Lawrence H.Y Law) chehoocheng@cuhk.hk (Hong Kong, Cheng Che Hoo) ramki@ern.doe.ernet.in (India, ERNET, S. Ramakrishnan) nakayama@nic.ad.jp (Japan, JPNIC, Masaya Nakayama) taeha@nic.nm.kr (Korea, KRNIC, Taeha Park) rafee@jaring.ism.my (Malaysia, JARING , M. Rafee Yusoff) J.Houlker@waikato.ac.nz (New Zealand, NZREIN, John Houlker) milton@solomon.technet.sg (Singapore, Technet, Milton Choo) gihan@cse.mrt.ac.lk (Sri Lanka, University of Moratuwa, Gihan Dias) wschen@twnmoe10.bitnet (Taiwan, TANET, Wen-sung Chen) kk@cs.ait.ac.th (Thailand, AIT, Kanchana Kanchanasut) narayan@caren.net (CAREN, Devendra Narayan) chon@cosmos.kaist.ac.kr (APCCIRN Chair, Kilnam Chon) jun@wide.ad.jp (APEPG Chair, Jun Murai) qianhl%bepc2@scs.slac.stanford.edu (China, Academia Sinica, Qian Hualin) The APNIC-STAFF list is intended for people who can actively con- tribute to the establishment of the APNIC. The APNIC-STAFF list con- sists of: hi@csce.kyushu-u.ac.jp Masaki Hirabaru, JPNIC nakayama@nic.ad.jp Masaya Nakayama, JPNIC davidc@apnic.net David Conrad, IIJ, Inc asaba@iij.ad.jp Toshiya Asaba, IIJ, Inc taeha@nic.nm.kr Taeha Park, KRNIC uhhyung@nic.nm.kr Uhhyung Choi, KRNIC vgebes@spin.ad.jp Vince Gebes, AT&T Jens Spin Project noi@chula.ac.th Somjai Boonsiri, Chulalongkorn Univ. fyta@chula.ac.th Yunyong Teng-amnuay, Chula. Univ. kunchit@chula.ac.th Kunchit Charmaraman, Chula. Univ. a.linton@aarnet.edu.au Andy Linton, AUNIC g.huston@aarnet.edu.au Geoff Huston, AUNIC jodi@uhunix.uhcc.hawaii.edu Jodi Chu, University of Hawaii thong@chula.ac.th Thongchai Rojkangsadan, Chula. Univ. g33cjt@ncr4.acc.chula.ac.th Chaiyasut Jongtavornvitaya, C. U. milton@mozart.technet.sg Milton Choo, TechNet s91242ms@sfc.keio.ac.jp Motoko Seko, Keio University/APNIC s92334yn@sfc.keio.ac.jp Youko Nakamura, Keio University/APNIC s91494am@sfc.keio.ac.jp Ayako Monobe, Keio University/APNIC V. Gebes [Page 15] APNIC-009.0 June 1994 j.houlker@waikato.ac.nz John Houlker, University of Waikato winnie@sfc.wide.ad.jp Xinghan Suen, Keio University/APNIC candy@moers2.edu.tw Yu-Hsuan Chen, Taiwan Ministry of Ed. yokkom@krnic.net Youngjoon Baek, KRNIC ccc_rex@waikato.ac.nz Rex Croft, Waikato University jm@eng.isas.ac.jp Jun Matsukata, JPNIC hbwang@ns.cnc.ac.cn Hongbing Wang, Chinese Academy of Sci. rpl@sisig.admu.edu.ph Richard Lozada, Philnet rrc@sisig.pfi.net Rosario Carlos, Philnet Patrick.Kelly@kuentos.Guam.net Patrick Kelly, Kuentos, Inc sham@ms.mimos.my Samsidarwati Mohd. Isa, MIMOS mal@ms.mimos.my Mohamed b. Awang-Lah, MIMOS The APNIC-ALL list is intended for discussions regarding the APNIC. There are no restrictions to joining this list. The APNIC-ALL list con- sists of: staff@ripe.net yin@orion.arc.nasa.gov lgamble@atlas.arc.nasa.gov aarnet@aarnet.edu.au j.houlker@waikato.ac.nz w.teahan@waikato.ac.nz nznic@waikato.ac.nz ohbyeon@garam.kreonet.re.kr chon@cosmos.kaist.ac.kr syhan@cosmos.kaist.ac.kr nic@nic.nm.kr phon@nwg.nectec.or.th cheng@nwg.nectec.or.th kk@cs.ait.ac.th prachak@chula.ac.th fyta@chula.ac.th qianhl%bepc2@scs.slac.stanford.edu haoxin%bepc2@scs.slac.stanford.edu milton@solomon.technet.sg lim@solomon.technet.sg chehoocheng@cuhk.hk philip-leung@cuhk.hk mingfung@cuhk.hk cclaw@usthk.ust.hk rafee@jaring.ism.my kumar_s@usp.ac.fj narayan@caren.net matsuzaki@vnet.ibm.com akazawa@who.ch ken@dss.com asaba@iij.ad.jp V. Gebes [Page 16] APNIC-009.0 June 1994 matsumoto@spin.ad.jp vgebes@spin.ad.jp asano@nacsis.ac.jp apnic-jp@nic.ad.jp zhou@bitnic.bitnet V. Gebes [Page 17] APNIC-009.0 June 1994 Appendix 2 - Reserved National NIC Domain Names Below is a list of national Network Information Center names which APNIC has reserved pending the establishment of the national NICs in question. Where "(allocated)" following the domain name, the national NIC has been established and the DNS delegation has been transfered from APNIC to the national NIC. Asia Pacific Network Information Centers: (Oceania) American Samoa ASNIC.NET Australia AUNIC.NET (allocated) Christmas Island CXNIC.NET Cocos (Keeling) Islands CCNIC.NET Cook Islands CKNIC.NET Fiji FJNIC.NET French Polynesia PFNIC.NET Guam GUNIC.NET Kiribati KINIC.NET Marshall Islands MHNIC.NET Micronesia FMNIC.NET Nauru NRNIC.NET New Caledonia NCNIC.NET New Zealand NZNIC.NET Niue NUNIC.NET Palau PWNIC.NET Papua New Guinea PGNIC.NET Samoa WSNIC.NET Solomon Islands SBNIC.NET Tonga TONIC.NET Tuvalu TVNIC.NET Vanuatu VUNIC.NET (Southeast and Pacific Asia): Cambodia KHNIC.NET East Timor TPNIC.NET Indonesia IDNIC.NET Korea (DPR of) KPNIC.NET Korea (Republic of) KRNIC.NET (allocated) Japan JPNIC.NET (allocated) Laos LANIC.NET Malaysia MYNIC.NET Myanmar MMNIC.NET Philippines PHNIC.NET Singapore SGNIC.NET Taiwan TWNIC.NET (allocated) Thailand THNIC.NET (allocated) V. Gebes [Page 18] APNIC-009.0 June 1994 Viet Nam VNNIC.NET (Central Asia): Afghanistan AFNIC.NET China CNNIC.NET Hong Kong HKNIC.NET Macau MONIC.NET Mongolia MNNIC.NET Bangladesh BDNIC.NET Bhutan BTNIC.NET Brunei Darussalam BNNIC.NET India INNIC.NET Maldives MVNIC.NET Nepal NPNIC.NET Pakistan PKNIC.NET Sri Lanka LKNIC.NET (Western Asia): Armenia AMNIC.NET Azerbaijan AZNIC.NET Iran IRNIC.NET Iraq IQNIC.NET Kazakhstan KZNIC.NET Kyrgyzstan KGNIC.NET Tajikistan TJNIC.NET Turkmenistan TMNIC.NET Uzbekistan UZNIC.NET (Middle East): Bahrain BHNIC.NET Israel ILNIC.NET Jordan JONIC.NET Kuwait KWNIC.NET Lebanon LBNIC.NET Oman OMNIC.NET Qatar QANIC.NET Saudi Arabia SANIC.NET Syria SYNIC.NET United Arab Emirates AENIC.NET Yemen YENIC.NET V. Gebes [Page 19]