1997/01/21 運営委員会
                                                        資料 3-8
		国際連携検討部会報告


1. APNICの香港会合 (General Meeting)

General Meetingが1月31日に香港で開催される。
会合の案内は http://www.apnic.net/agm.html に掲載されている。
予定されている議題は以下の通り。

  8:00 -  9:00  Registration and Continental Breakfast
  9:00 -  9:30  Call to order and Administrivia
  9:30 - 10:30  Executive Council Elections (2 seats)
 10:30 - 11:00  APNIC Secretariat Status Report
 11:00 - 12:00  Funding Plan Modifications discussions and voting
 12:00 -  1:30  Lunch (not provided)
  1:30 -  2:30  APNIC Activities Plan discussions and voting
  2:30 -  4:45  Member Updates
  4:45 -  5:00  Adjournment

(1) Executive councilの5名のメンバーのうち2名が改選となる。
    現メンバーを下記に示す。

    David Conrad - Director General
    Geoff Huston (Australia) - 18 Month Term
    Jun Murai (Japan) - 18 Month Term
    Tan Tze Meng (Malaysia) - 18 Month Term
    Sanjaya (Indonesia) - 6 Month Term
    B.A.C. Abeyantha (Sri lanka) (Absent) - 6 Month Term

(2) Funding Planの議論はJPNICにとって関係が深い。

   a) Setting non-membership fees based on address space utilization

   b) Creation of a "confederation" fee category which has fees based
      on the number of members.

   この(b)については、次のような会費の原案がある。
   USD5,000 ＋ USD500×会員数。つまり200会員を擁するconfederationの
   APNIC会費は 5,000 + 100,000 = USD105,000 となる。

(3) Member update の内容は、これまでの会合における発表を参考にすると、
    次のような項目について、OHP/displayで説明するのが良いと思われる。

   1. JPNIC の概要 (会員数、予算の額(*)、事務局のスタッフの数(*))
   2. IP address の割当の状況 (1996 or 推移)
   3. domain 名の割当の状況 (1996 or 推移)
   4. AS number の割当 (*)
   5. IP address に関して： portable address の扱い
   6. domain 名に関して： ne の導入、一意性の制約を緩和、brand domain の議論、
                          地域ドメイン(*)

 (*) の項目は、これまでの APNIC における JPNIC の発表に対して、他の
     国から質問が出たことがあるもの。

2. APNIC Executive Council

General Meetingの前日(1月30日)にExecutive Councilが開かれる。
予定されている議題は次のようである。

a) APNIC headquarters location
b) APNIC budget situation
c) APNIC "surplus"
d) APNIC Ltd. Stock

(a)に関する現在(本資料執筆時点)の状況では、オーストラリアにheadquartersを置き、
日本はbranch officeとするという提案が予想される。

上記の他に、APNICからISPにアドレスを最初に割当てる際のdefaultを /22
から /19に増加させる(RIPE-NCCに揃える)、という提案が審議される見通しである。

========

[Confederation に関するドキュメント]
ftp:://ftp.apnic.net/apnic/docs/apnic-051.txt

Introduction

This document describes the concepts of and the requirements necessary
to become an APNIC recognized Internet Service Provider Confederation.
ISP Confederations are intended to provide a means by which a group of
service providers can group together to provide resource allocation
and registration services tailored to their specific local language
and cultural requirements as well as a way of reducing the burden of
the APNIC membership fees to individual member organizations.  

Internet Service Provider Confederations

APNIC, having limited resources, is unable to provide allocation and
registration services tailored to specific cultural or language
requirements.  In realization of these limitations, APNIC has created
the concept of Internet Service Provider (ISP) Confederations.  ISP
Confederations are defined to be a group of three or more Internet
connectivity service providing organizations (commercial or
non-commercial) which have formed a separate independent organization
to provide the resource allocation and registration services.  This
independent organization, refered to in this document as the
"confederation registry", is assumed to be neutral and unbiased to all
confederation members.

A confederation's membership can be defined in many ways.  In some
cases, a confederation may be formed by a national government or other
national body and be intended to provide allocation and registry
services to service providers within the national boundaries.  In
other cases, competitive Internet service providers in multiple
regions may join together to form a confederation with the only
constraint on membership being a willingness to abide by the
confederation's oprational and organizational rules.  In all cases,
however, it is expected that the definitions for membership within a
confederation are well defined and published.  In addition, there is
no requirement for organizations which may be included within the
definition of a particular confederation's membership requirements
must make use of that confederation's services -- any ISP is free to
obtain resources directly from APNIC should they so choose.

Establishment Requirements

To become an APNIC recognized Internet Service Provider confederation
and have resources delegated from APNIC, a confederation registry must
be estabished under the following requirements:

1) The confederation registry must be an independent, non-profit
   entity (not necessarily incorporated, however this is recommended)
   administratively distinct from any one particular confederation
   member.  This allows the confederation registry to act in a neutral
   and unbiased fashion towards all members.

2) The confederation registry must be composed of three or more
   non-affiliated Internet connectivity service providing
   organizations which provide Internet connectivity services which
   require delegation of blocks of addresses.  This requirement 
   ensures the overhead associated with a confederation is distributed
   over a sufficient number of organizations as well as reducing the
   likelihood of confederations being established to circumvent
   existing registry policies.

3) The confederation registry must pay a yearly fee to APNIC
   consisting of US $5000 plus US $500 per member (e.g., if a
   confederation has 5 members its yearly fee will be US $5000 + 5 *
   US $500 == US $7500).  This requirement will ensure APNIC has
   sufficient resources to continue processing confederation requests.

4) The allocation body of the confederation registry must demonstrate
   an understanding and willingness to abide by the guidelines
   documented in RFCs 2050 and 1930.  This requirement ensures
   allocations made by the confederation are appropriate and
   consistent with existing registry guidelines.

5) The confederation registry must provide documents describing (in
   English):

	a) Confederation organizational structure and procedures
	   including administrative structure and chain of appeal
           thereby giving APNIC the information necessary to
           adjudicate disputes brought before it;

	b) Membership eligibility requirements and termination
	   procedures thereby allowing APNIC for redirect requests
           to confederations where appropriate

	c) Member organizations including

		i) Member organization's name

		ii) Member organization's postal address

		iii) Member organization's email, telephone and
		     facsimile numbers

		iv) Member organization's APNIC account name (if such
		    exists)

           thereby reducing the likelihood of organizations joining
           multiple confederations in order to circumvent allocation
           restrictions.

	d) IP address allocation guidelines beyond those documented
	   in RFC 2050.

	e) AS number allocation guidelines beyond those documented in
	   RFC 1930.

The documents described in (5) will be made available to the Internet
community via APNIC's FTP and Web services.  Modifications to a
confederation's structure, its membership, or any of its policies must
be reported to APNIC within five working days.

In addition to these requirements, it is assumed confederations
operate their own registration database systems.  If the primary
language of the confederation is not English, it is suggested the
confederation database be provided in the appropriate local language.
In any case, however, the operation of a local database does not
relieve the confederation of having to update the APNIC database as
the APNIC database is considered authoritative for all address blocks
delegated by APNIC.

Operational Requirements

Confederations will be allocated blocks of addresses and autonomous
sytem numbers which are intended to be sub-allocated to confederation
member organizations, with the amount of address space allocated by
APNIC rounded up to the next power-of-two block.  It is expected the
confederation will allocate resources to their members in a fashion
similar to the allocation mechanisms documented in RFC 2050 (e.g.,
"slow-start") and RFC 1930.  When a member has consumed its
allocation, the member should contact the confederation administrator
to request additional address space.  If the confederation
administrator has insufficient resources to meet the member's request,
the confederation administrator should request additional space from
APNIC via the appropriate form.  When APNIC receives this form, APNIC
will review the allocation history for the confederation and verify
reassignments have been made appropriately.  Assuming all requirements
have been met, APNIC will allocate additional resources sufficient to
enable the confederation to operate 3 to 6 months without need of
additional address space.

APNIC always reserves the right to reduce or withhold resource
allocations to confederations which do not conform to APNIC or
accepted Internet allocation policies.

Should a confederation be established which has as a member an
existing APNIC member, APNIC will not allocate a new block to the
confederation for that member immediately, but will instead transfer
control of that block to the confederation.  

Conclusion

Internet Service Provider Confederations are intended to provide
resource allocation and registration services to subsets of the Asia
Pacific Internet community which APNIC serves.  These confederations
allow for local language and culture issues to be address more readily
than APNIC can provide for as well as allowing confederation members
with a way to reduce fees paid directly to APNIC for APNIC membership.

========