-------------------------------------------------------------------
APNIC Document identity
Title: Draft APNIC Confederation Agreement
Short title: confed-agreement
Document ref: DRAFT-CON-AG
Version: 001
Date of original publication: August 1998
Date of this version: August 1998
Review scheduled: n/a
Obsoletes: n/a
Status: Obsolete
Comments: This draft is a work in progress.
--------------------------------------------------------------------
Draft APNIC Confederation Agreement
Memorandum of Understanding and Agreement
between
APNIC Pty Ltd.
and
________________________________________________________
("the confederation")
This agreement is signed both by a representative of APNIC and a
representative of the confederation and represents an understanding
between both parties regarding the requirements necessary for
allocations of resources to the confederation for sub-delegation to
its membership. This agreement is intended to remove any possible
misunderstanding of the requirements placed upon both parties by
resource allocation requests.
1. APNIC agrees:
1.1 to provide a minimum of six (6) months notice prior to changes in
policies and/or procedures affecting the confederation after which
those policies and/or procedures will be implemented;
1.2 to not delay allocations due to inefficiencies of "historical"
allocations or assignments made by any organization served by the
confederation. For the purposes of this agreement, "historical"
is taken to mean earlier than June 1, 1996;
1.3 to keep all resource allocation information provided to APNIC for
at least five (5) years;
1.4 that allocation policies and procedures for APNIC confederations
(outside of those defined in RFCs 2050 and 1930) will be defined
via consultation between APNIC and the confederations themselves
with final approval of the resulting policies and procedures made
by the APNIC Executive Council. After such definition and
approval, APNIC will make the confederation policies and
procedures publicly available in written form on the APNIC archive
server and web page;
1.5 provide templates, guidelines, examples, etc., of policies and
procedures that are applicable to all confederations from which
new confederation policies and procedures may be based should the
confederations so desire;
1.6 to send "reception confirmation" message immediately upon receipt
of e-mail and respond substantively to requests within 5 working
days. For the purposes of this agreement, "respond substantively"
may include responses from automated parsers, status reports of
request processing, requests for additional information,
explanations why additional information is necessary, or
delegation information. In those cases where APNIC is not able to
respond substantively within 5 working days, APNIC will provide a
detailed explanation as to the reasons for the delays and the
steps taken to insure such delays do not occur in the future;
1.7 by January 1, 1999 to be able to respond substantively to requests
within 3 working days of the receipt of e-mail;
1.8 to allocate resources sufficient for 3 to 6 months of routine
sub-delegations by the confederation based on historical
allocation patterns with consideration of the predicted request
patterns of the members of the confederation;
1.9 to allocate additional resources to a confederation when the
confederation receives a "trigger" request which it cannot grant
with the remaining free resources in its free pool if "sufficient
information" is provided. For the purposes of this agreement,
"sufficient information" is defined to be:
1.9.1 a description of all allocations, assignments, and
reservations done by the confederation directly in
summary form as described in the APNIC Confederation
Request Form;
AND
1.9.2 information on all non-historical allocations and
assignments made by the member of the confederation that
triggered the request by the confederation provided to a
level of detail that permits APNIC to understand how the
member of the confederation is utilizing at least 80% of
the resources delegated to it and, in those cases where
a resource isn't being utilized efficiently and/or
appropriately according to current Internet practices
and technologies, the reasons for the inefficiency or
inappropriate use.
In those cases where there is a dispute on whether "sufficient
information" has been provided, the specific case will be referred
to the APNIC Executive Council for a final decision;
In order to prevent allocations to a confederation being blocked
by a confederation member which is not able to document its
utilization in a timely fashion, APNIC will choose another member
of the confederation with equivalent resource consumption at
random;
1.10 to implement WHOIS server technology that permits referrals to
conformant external WHOIS servers by January, 2000;
1.11 limit bulk accessibility to WHOIS contact information for all
records in the APNIC database;
2. The confederation agrees to:
2.1 insure its members obtain all addresses and/or AS numbers from
exactly one source;
2.2 provide English versions of the confederations allocation and
assignment policies;
2.3 investigate the use of allocation and/or assignment policies
similar in function to the "slow start" and "assignment window"
policies in use by APNIC and make use of those policies should the
confederation not have an alternative;
2.4 prior to the next request for resources, provide all
non-historical allocation and assignment information made directly
by the confederation to its members.
2.5 for the purposes of database cleanup, within one year, the
confederation will provide information on all allocations and
assignments made by confederation directly;
2.6 collect members' end-user assignment information for previous
allocations *before* allocating new address space to members.
This information should include as much information as is included
in the APNIC Second Opinion Request form;
2.7 collect members' infrastructure information to explain those
addresses not utilized in customer assignments;
2.8 within one year and prior to the confederation allocating
additional address space to organizations which have obtained
historical address space, the confederation will obtain from the
organization requesting address space usage information comparable
with the summary information requested in cust-network fields of
the Confederation Address Request form for all address space
maintained by that organizations;
2.9 where applicable, work with its members to insure that within one
year the confederation's WHOIS database is updated within 3 work
days of sub-assignment or sub-allocation by the confederation's
members;
2.10 regularly provide English translations of the confederation's
WHOIS database records in APNIC (RIPE DB) WHOIS format via the
e-mail "auto-dbm" interface. For the purposes of this agreement,
"regularly" is defined to be at least once every three months
until the confederation's database is updated within 24 working
hours of sub-allocation or sub-assignment by the confederation's
members, at which time the confederation will regularly provide
updates at least once a week via the e-mail "auto-dbm" interface.
2.11 insure the information presented to APNIC in the Confederation
Request form is consistent, implementable, and conforms to APNIC
allocation policies (that is, subnet masks/host estimates match,
that infrastructure is documented and meets requirements, that
customer assignments meet customer requirements (e.g. not /24
boundaries, or administrative ease.))
2.12 have the ability to provide additional justification and/or
corroborating information in those cases which do not appear to
conform with standard address allocation practices,
2.13 suggest to new confederation members that have addresses
allocated by other registries that they should renumber into a
new contiguous block, and obtain from those confederation members
an agreement stating that they will not get internet resources
from more than one registry at one time.
2.14 obtain official agreement from new confederation members that
they are aware of the confederation's allocation policies prior
to address allocation
3. Both Parties agree:
3.1 that requests to add, delete, and/or modify any of the above
clauses may be done by either party
3.2 to accept for review any request to add, delete, and/or modify any
clause of this agreement
3.3 that additions, deletions, and/or modifications to any clause will
be done by mutual consent of both parties. If both parties are
not able to reach agreement, the APNIC Executive Council will act
as final arbiter.
3.4 that the final approval of all issues decided on the confederation
mailing list or in this agreement is the prerogative of the APNIC
Executive Council.
This agreement is signed and dated, by the following parties:
APNIC Representative:
___________________________________________
(signature)
_________________________________, _________
(printed name, date)
----
Representative of the confederation:
___________________________________________
(signature)
_________________________________, _________
(printed name, date)