apnic-all

From nakayama@is.apnic.net Thu Sep 2 09:03:20 1993

Received: from is.apnic.net (is.nic.ad.jp) by nic.nm.kr (4.1/SMI-4.1)

id AA11904; Thu, 2 Sep 93 09:03:20 KST

Errors-To: apnic-all-request@apnic.net

Received: by is.apnic.net (5.67+1.6W/6.4JAIN-1.1)

id AA05039; Thu, 2 Sep 93 08:58:32 JST

Return-Path: <nakayama@is.apnic.net>

Message-Id: <9309012358.AA11036@sh.nic.ad.jp>

To: apnic-all@apnic.net

Date: Thu, 02 Sep 1993 08:58:30 +0900

From: Masaya NAKAYAMA <nakayama@nic.ad.jp>

X-Sequence: APNIC-ALL 1

Subject: (APNIC-ALL 1) Announcemnt from a staff of APNIC pilot project

Errors-To: apnic-all-request@apnic.net

Sender: apnic-all-request@apnic.net

Dear Sirs.

I'm sorry too late to setup our mailing list for APNIC pilot project

on apnic.net.

I prepare three kinds of mailing list on this machine.

apnic-all@apnic.net:

All members who are interested in APNIC pilot project.

It also includes members listed in apnic-all@nic.nm.kr.

(apnic-all@nic.nm.kr includes apnic-all@nic.ad.jp)

apnic-member@apnic.net:

Actual APNIC pilot project members.

It includes NIC persons and/or network providers who can

coordinate thier own country.

apnic-staff@apnic.net:

It includes the staff of this pilot project.

Currentry 4 members listed in JPNIC/APNIC proposal

is included.

However the attendance at APCCIRN meeting held in SF know the APNIC

pilot project proposal, I think some members in this list do not know

them. The following material is the reviced version of APNIC pilot

project proposal.

Prof. Murai should announce this matter, but he is still in USA.

So I will forward it to this list. Please contact with me if you

cannot contact with him.

=====================================================================

Asia Pacific Network Information Center Pilot Project

1. Introduction

In order to continue the effort of coordinating the various regional

Network Information Centers and other organizations involved in

Internetworking in the Asia Pacific region, this document proposes a

pilot project to implement an Asia Pacific Network Information Center.

1.1 Purpose

This pilot project proposes to provide a testbed for experimentation

into the area of network coordination in the Asia Pacific region. The

areas of study will include IP address allocation strategies,

coordination with other regional NICs and NCCs such as the InterNIC

and RIPE NCC, determination of the requirements and means to fulfill

those requirements for the operation of the APNIC, and experimentation

with various software tools used for coordinating various aspects of

Internetworking interactions.

1.2 Scope

This pilot project, coordinated under the auspices of the APCCIRN, is

intended to provide network coordination services to the Asia Pacific

region in an experimental fashion. Further action in terms of APNIC

support and continuation of the services provided by the APNIC will be

dependent upon lessons learned during the pilot project.

1.3 Duration

The APNIC pilot project will operate for up to 10 months, starting on

September 1, 1993.

1.4 Reporting

The personnel involved in the APNIC pilot project will produce 2

reports for the APCCIRN. The first will be a mid-term report,

presented during the Winter, 1993 APCCIRN meeting, and the other will

be a final report which will be presented during the Summer, 1994

APCCIRN meeting.

2. Functions

For the purposes of this pilot project, the functions performed by the

APNIC can be broken up into two broad categories. Ordered by

priority, they are:

1) Internet Registry

2) Routing Registry

Other functions typically performed by Network Information Centers, such

as information provision and direct user support are beyond the scope of

this pilot project.

2.1 Internet Registry Functions

The Internet Registry category includes such services as allocating

IP addresses as a designated regional Internet Registry, organizing

and maintaining a "White Pages" of network points of contact, and

of lesser priority for this pilot project, maintaining a database

of DNS delegations for network name lookup.

2.2 Routing Registry Functions

The routing registry category describes those functions which have

been pinpointed as necessary for maintenance and support of routing

issues in the global Internet. These issues include maintaining a

database of routing policies and, when the need exists in the Internet

at large, organizing and maintaining a database of CIDR aggregations.

3. Requirements

The requirements for this pilot project are broken down into

four categories: funding, hardware, software, and personnel.

3.1 Funding

All funding for the APNIC pilot project will be derived from JPNIC

resources. The JPNIC has committed 10% of its resources to fulfill

the APNIC funding requirements. During the pilot project,

investigation of other avenues of funding for continuation of the

services provided by the APNIC will be undertaken.

3.2 Hardware

For the purposes of this pilot project, the hardware requirements will

be limited to a single workstation class computer with sufficient disk

and network capacity to fulfill the needs of the project. JPNIC has

agreed to share the use of its machines for the APNIC pilot.

3.3 Software

The APNIC pilot project will require software to create and maintain

the databases for both the Internet Registry functions and the Routing

Registry functions.

The software for the Internet Registry functions will consist of

database and other software that will allow the process of allocating

and registering IP addresses to be made as automatic as possible.

JPNIC has indicated that software written and used by JPNIC for the

maintenance of the Japanese Internet registry will be available for

use for the APNIC pilot project and it is assumed that software

packages from other NICs and NCCs may also be used.

In terms of software for the routing registry functions of this pilot

project, the RIPE NCC routing registry tools will be used.

3.4 Personnel

The personnel requirements for this project have been broken down

as follows:

0.25 FTE Managerial support

0.50 FTE Technical support

1.00 FTE Administrative support

These personnel requirements will be fulfilled by drawing from the

resources of JPNIC as well as other interested parties. Specifically,

the following personnel have indicated their interest in contributing

to this pilot project:

Masaki Hirabaru, Kyushu University

Taeha Park, KAIST

Masaya Nakayama, University of Tokyo

David Conrad, Internet Initiative Japan, Inc.

Since the APNIC will be involved in regional networking issues, it is

hoped that other members of the Asia Pacific networking community will

be able to contribute to this pilot project.

4. Conclusion

This document outlines a proposal for the establishment of an Asia

Pacific Network Information Center which will investigate the

requirements for the operation of a network information center in the

Asia Pacific region. The pilot project will start on September 1 and

will operate for up to 10 months, will concentrate on Internet and

routing registry functions, and will produce two reports for the

APCCIRN. It is hoped this pilot project will provide information

which may be of help in establishing a permanent network information

center in the Asia Pacific Region.

=====================================================================

From nakayama@is.apnic.net Thu Sep 2 10:54:07 1993

Received: from daiduk.kaist.ac.kr by nic.nm.kr (4.1/SMI-4.1)

id AA12197; Thu, 2 Sep 93 10:54:07 KST

Errors-To: apnic-all-request@apnic.net

Received: from is.apnic.net (is.nic.ad.jp) by daiduk.kaist.ac.kr (4.1/KAISTNet-Relay-3.2)

id AA27754; Thu, 2 Sep 93 10:58:35 KST

Received: by is.apnic.net (5.67+1.6W/6.4JAIN-1.1)

id AA05208; Thu, 2 Sep 93 10:48:40 JST

Return-Path: <nakayama@is.apnic.net>

Message-Id: <9309020148.AA01259@sh.nic.ad.jp>

To: apnic-all@apnic.net

Date: Thu, 02 Sep 1993 10:48:28 +0900

From: Masaya NAKAYAMA <nakayama@nic.ad.jp>

X-Sequence: APNIC-ALL 2

Subject: (APNIC-ALL 2) members list in this ML

Errors-To: apnic-all-request@apnic.net

Sender: apnic-all-request@apnic.net

I put the following members in apnic-all@apnic.net.

G.Huston@aarnet.edu.au

# New Zeeland

j.houlker@waikato.ac.nz

# Korea

ohbyeon@garam.kreonet.re.kr

taeha@nic.nm.kr

# Thai

phon@nwg.nectec.or.th

cheng@nwg.nectec.or.th

kk@cs.ait.ac.th

# Taiwan

qianhl%bepc2@scs.slac.stanford.edu

# Singapore

milton@solomon.technet.sg

# Japan

asaba@iij.ad.jp

davidc@iij.ad.jp

matsumoto@spin.ad.jp

nakayama@nic.ad.jp

goto@ntt-20.ntt.jp

akiko@nacsis.ac.jp

jm@eng.isas.ac.jp

asano@nacsis.ac.jp

# CAREN

narayan@caren.net

# Others

matsuzaki@vnet.ibm.com

akazawa@who.ch

# ken@dss.com

apnic-all@nic.nm.kr

################################

hi@nic.ad.jp

jun@wide.ad.jp

ikoh@halla.dacom.co.kr

taeha@cosmos.kaist.ac.kr

gih@aarnet.edu.au

w.teahan@waikato.ac.nz

nznic@waikato.ac.nz

ftya@chulkn.chula.ac.th

phon@nwg.nectec.or.th

rafee@jaring.ism.my

philip-leung@cuhk.hk

chehoocheng@cuhk.hk

From nakayama@is.apnic.net Thu Sep 2 11:16:38 1993

Received: from is.apnic.net (is.nic.ad.jp) by nic.nm.kr (4.1/SMI-4.1)

id AA12462; Thu, 2 Sep 93 11:16:38 KST

Errors-To: apnic-all-request@apnic.net

Received: by is.apnic.net (5.67+1.6W/6.4JAIN-1.1)

id AA05262; Thu, 2 Sep 93 11:11:51 JST

Return-Path: <nakayama@is.apnic.net>

Message-Id: <9309020211.AA01654@sh.nic.ad.jp>

To: apnic-all@apnic.net

In-Reply-To: Your message of "Thu, 02 Sep 1993 10:48:28 JST."

<9309020148.AA01259@sh.nic.ad.jp>

Date: Thu, 02 Sep 1993 11:11:49 +0900

From: Masaya NAKAYAMA <nakayama@nic.ad.jp>

X-Sequence: APNIC-ALL 3

Subject: (APNIC-ALL 3) Re: (APNIC-ALL 2) members list in this ML

Errors-To: apnic-all-request@apnic.net

Sender: apnic-all-request@apnic.net

Sorry, I did miss operation in MH. And sent incomplete message.

>> I put the following members in apnic-all@apnic.net.

>>

>> apnic-all@nic.nm.kr

I think some members get duplicate messages. Because I just put

apnic-all@nic.nm.kr in the list and I do not know your alias name.

1. If you get duplicate messages from apnic-all@apnic.net,

please let me know which is the duplicate entry.

2. We cannot reach pluto.dss.com. And I just commented out

the following entry.

>> # ken@dss.com

3. I got the message from daemon@chulkn.chuula.ac.th as follows.

|------------------------- Message log follows: -------------------------|

no valid recipients were found for this message

|------------------------- Failed addresses follow: ---------------------|

<ftya@chulkn.chula.ac.th> ... unknown user

|------------------------- Message text follows: ------------------------|

If you know the new address for "Y. Teng-amnuay", please let me know it.

4. If you know the right persons who shuld entry apnic-member@apnic.net,

please send their address to apnic-staff@apnic.net.

Thanks.