-------------------------------------------------------------------
APNIC Document identity
Title: Provider Independent IP address return form
Short title: address-return-request
Document ref: APNIC-078
Version: 003
Date of original publication: February 2000
Date of this version: 14 December 2004
Review scheduled: n/a
Obsoletes: Previous versions
Status: Obsolete
Comments: n/a
--------------------------------------------------------------------
Provider Independent IP Address Return Form
This form is intended to be used by organisations wishing to return
historically allocated or assigned Provider Independent IP addresses
and for organisations wishing to exchange three or more non-contiguous
Provider Independent address blocks for one contiguous address block under
the historical prefix exchange policy described in section 7 of "Policies
for historical Internet resources in the APNIC Whois Database" at:
http://ftp.apnic.net/apnic/docs/historical-resource-policies.txt
Only address space allocated or assigned by organisations within the
Asia Pacific region can be returned to APNIC.
For instructions on how to complete this request, please refer to the
notes at the bottom of the form.
There are two sections to this form: Section 1 may be submitted
via email to:
hostmaster@apnic.net
with [IP-RETURN] in the Subject line,
or in type written English via fax to:
+61-7-3858-3199
or in type written English via postal mail (as a last resort) to:
Asia Pacific Network Information Center
Level 1, 33 Park Road
P. O. Box 2131
Milton, QLD 4064
Australia
Please note that if you do not include [IP-RETURN] in the subject
line when emailing the request to <hostmaster@apnic.net> your email
will be filtered out and will not reach our hostmasters.
Section 2 section must be either faxed or sent via postal mail. Note
that for security and verification reasons, we will not accept
Section 2 via email.
If you have any questions regarding this form, you may contact us via
email at <hostmaster@apnic.net> (preferred), fax at the above number,
postal mail at the above address, or via telephone at +61-7-3858-3100
between 9:00 AM and 5:00 PM Australian Eastern Standard Time.
Please allow up to one week for processing electronic mail requests
and up to one month for other forms of submission.
NOTE: PLEASE DO NOT INCLUDE THIS HEADER NOR THE INSTRUCTIONS AT THE
BOTTOM OF THIS FORM WITH YOUR APPLICATION.
- - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - -
#[SECTION 1]#
#[CURRENT REGISTERED TEMPLATE V:1.0]#
inetnum:
netname:
descr:
descr:
country:
admin-c:
tech-c:
remarks:
changed:
mnt-by:
source:
#[ADMINISTRATIVE TEMPLATE V:1.0]#
organisation-name:
requestor-name:
address:
country:
phone:
fax:
allocated-by:
date-allocated:
verify-email:
address-range:
prefix-exchange:
#[NETWORK TEMPLATE V:5.0]#
netname:
descr:
descr:
country:
admin-c:
tech-c:
remarks:
changed:
mnt-by:
source: APNIC
#[PERSON TEMPLATE V:4.0]#
person:
address:
address:
country:
phone:
fax-no:
e-mail:
nic-hdl:
remarks:
changed:
mnt-by:
source: APNIC
Additional Comments:
#[SECTION 2]#
#[FAXED VERIFICATION]#
In a fax with the organisation's letterhead, please include the following:
A. Verification of the address range to be returned to the free pool of
globally unique IPv4 address space
B. Signature of the contact as recorded in the database (if applicable)
AND
Signature of employee with legal authority to sign for the organisation
returning address space
#[TEMPLATES END]#
- - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - - -
1. Instructions For Completing This Form
----------------------------------------
Below are the instructions for completing an APNIC Provider Independent
IP Address Return Form. It is extremely important you provide attributes
for the tags listed below.
Information provided in the ADMINISTRATIVE TEMPLATE will be kept in
strict confidence.
Information provided in the NETWORK and PERSON templates will be made
available over the Internet via WHOIS to whois.apnic.net and other
mechanisms. This information is provided to the Internet community to
aid in diagnosing and resolving issues related to the operation of the
Internet. Any use outside of this context is expressly prohibited
without written permission from APNIC Pty Ltd.
[A] SECTION 1
2. Current Registered Template
------------------------------
Please include the registered object recorded in the respective
database of the organisation that allocated the address range. Most
allocations are recorded in or mirrored by the APNIC database, however
there may be instances where the registration object is recorded in
another database. If the database where the allocation or assignment
is recorded is not a RIPE-181 database (format of the CURRENT REGISTERED
TEMPLATE) then please cut and paste the result of a query to the database
for this template.
This template is used to verify that the address range stated in the
request was allocated to the company wishing to return or exchange the
IP addresses.
Example:
% Rights restricted by copyright. See http://www.apnic.net/db/dbcopyright.html
inetnum: 202.12.28.0 - 202.12.29.255
netname: APNIC-AP
descr: Asia Pacific Network Information Center, Pty. Ltd.
descr: Level 1 - 33 Park Road.
descr: Milton QLD 4064
descr: Australia
country: AU
admin-c: HM20-AP
tech-c: NO4-AP
mnt-by: MAINT-APNIC-AP
changed: paulg@apnic.net 19980918
source: APNIC
3. Administrative Template
--------------------------
ORGANISATION-NAME:
Please include the legal name of the organisation seeking to return
the IP Addresses. This should be the same name as that recorded in
the company letterhead fax to APNIC in Section 2.
Example:
organisation-name: Examplenet Pty Ltd
REQUESTOR-NAME:
Please indicate the name of the person who is returning address space
or requesting a "one-for-one" prefix exchange. In addition, please state
the relationship between the requestor and the organisation, and the job
title of the requestor.
Example:
requestor-name: Joe Bloggs, Employee Examplenet, Sys Admin
ADDRESS:
Please complete with the full postal address written as you would for
postal mail (but do not include the country name inthis field) using
one line for each part of the address as shown below.
Example:
address: Examplenet ISP
address: No 1 Example Street
address: Example, 4064
COUNTRY:
Please give the two letter ISO 3166 code appropriate for the
contact person. Do NOT provide the full name of the country or economy
or the three letter ISO 3166 code. If you do not know the appropriate
ISO 3166 code for this person's address, please see the list of ISO 3166
codes maintained on APNIC at:
http://www.apnic.net/info/reference/lookup_codes.html
This tag is required for all PERSON templates, with only one COUNTRY
tag permitted.
Example:
country: BT
PHONE:
Please provide the work telephone number of the person specified in
the REQUESTER-NAME field of this template as it would be dialed
internationally (without the prefix necessary to reach
an international line). Please do not include the leading zero when
specifying the area/city code unless it is required to correctly dial
the number internationally. The format for the telephone number is:
+<international code>-<area/city code>-<exchange>-<subscriber>
If an extension is necessary, please add "ext <extension>". Please do
not put 'x' or other abbreviations for "extension". You may provide more
than one telephone number. Each telephone number should be put on a
separate line and written in order of the most appropriate number to
the least appropriate.
Example:
phone: +81-20-1233-4676
phone: +81-20-1233-4677 ext 4711
FAX:
Please complete with the facsimile number of the requestor as it would
be dialed internationally (without the prefix necessary to reach an
international line. Please do not include the leading zero when specifying
the area/city code unless it is required to correctly dial the number
internationally. The format for the facsimile number is:
+<international code>-<area/city code>-<exchange>-<subscriber>
You may provide more than one facsimile number. Each facsimile number
should be put on a separate line and written in order of the most
appropriate number to the least appropriate. If the person does not have a
facsimile number, please leave blank.
Example:
fax-no: +81-20-1233-4678
ALLOCATED-BY:
Please state the name of the organisation that allocated or assigned
the block of Provider Independent IP addresses to your company. If the
organisation that allocated or assigned the block of addresses
is an Internet Service Provider that continues to carry on business then
please return the IP addresses to them.
If the organisation is/was an Network Information Centre (NIC) or an
Internet Service Provider that no longer exists, then please proceed with
this request to return the IP addresses to APNIC.
Example:
allocated-by: FOONIC, FOO Network Information Centre
DATE-ALLOCATED:
Using the YYYYMMDD format, please indicate the date the above mentioned
organisation allocated or assigned the IP addresses to your organisation.
Example:
date: 19940803
CONTACT-EMAIL:
Please include a contact email address for the organisation that allocated or
assigned you the Provider Independent IP addresses.
Example:
contact-email: hostmaster@foonic.net
ADDRESS-RANGE:
The ADDRESS-RANGE field provides a summary of the IP address range that is
to be returned to the free pool. If required, you can specify multiple
lines of this field to adequately define all address ranges to be returned.
Please complete it in the following format:
address-range: netname address mask date
where:
netname - as recorded in the database registering the allocation
or assignment.
address - the starting address of the assigned or allocated network
mask - the subnet mask of assigned network in dotted
decimal format, e.g. 255.255.255.0
date - the date the assignment occurred in YYYYMMDD format
PREFIX-EXCHANGE:
If you are returning the IP addresses but do not require a block
from APNIC in exchange, then please state "NO" in this field.
Please state "YES" if you are requesting IP addresses in exchange
for the ones that are to be returned. Please note that if you state "YES"
in this field, you must have at least three fields of ADDRESS-RANGE showing
dis-contiguous IP address blocks. This is a requirement of the "No Questions
Asked Prefix Return Policy"
Example:
prefix-exchange: YES
4. Network Template
-------------------
Please only complete this template if you stated "YES" in the
above field to obtain an allocation from APNIC in exchange for
the returned blocks.
NETNAME:
Please provide a short but meaningfully descriptive name for this
network. The NETNAME is used mainly for administrative purposes such
as consistency checking of the Internet Registry. The network name
should be written as a SINGLE word of less than 25 capital
alphanumeric characters ONLY. It is requested you use a network name
that relates to the organisation the network is being assigned to.
Please do NOT use domain names, such as FOO.COM, as the network name
has no relation with the domain name system. There should be exactly
one NETNAME tag per NETWORK template.
Example:
netname: TBIT
DESCR:
Please complete with a short description of the organisation,
including the location, providing sufficient detail as to distinguish
your organisation from others in the APNIC database, i.e., "descr:
Computer Center" is not sufficient. Do NOT include advertising
information such as "The best internet provider in Foo" and please
limit the number of DESCR lines to 5. This tag is required for all
NETWORK templates.
Example:
descr: Examplenet
descr: Example Internet Service Provider
descr: Exampletown
COUNTRY:
Please give the two letter ISO 3166 code appropriate for the
organisation requesting address space. Do NOT provide the full name of
the country or economy or the three letter ISO 3166 code. If you do not
know the appropriate ISO 3166 code for your organisation, please see the
list of ISO 3166 codes maintained on APNIC at:
http://www.apnic.net/info/reference/lookup_codes.html
We are aware that listing a location may seem arbitrary for networks
crossing national boundaries, so choose the most appropriate ISO 3166
code based on the location of the administrative contact. This tag is
required for all NETWORK templates, with only one COUNTRY tag permitted.
Example:
country: BT
ADMIN-C:
Please provide the APNIC NIC-handle (NIC-handles from other registries
are not accepted) of the person who is the administrative contact for
the network. If you do not have an APNIC NIC-handle, please see the
section below entitled "Obtaining an APNIC NIC-handle". The
administrative contact must be someone who is physically located at the
site of the network and at least one ADMIN-C tag is required for all
NETWORK templates.
Example:
admin-c: JB401-AP
TECH-C:
Please provide the APNIC NIC-handle (other registry NIC-handles are
not currently accepted) of the person who is the technical contact for
the network. If you do not have an APNIC NIC-handle, please see the
section below entitled "Obtaining an APNIC NIC-handle". The technical
contact need not be physically located at the site of the network, but
rather is the person who is responsible for the day-to-day operation
of the network. At least one TECH-C tag is required for all NETWORK
templates.
Example:
tech-c: MS4-AP
REMARKS:
The remarks attribute contains any remarks about this address space
that cannot be expressed in any of the other attributes. Although
multiple lines are allowed, it should be only be used if it provides
extra information to users of the database, and usage should be kept
to a minimum.
Example:
remarks: will be returned to NIC 19950101
CHANGED:
Please provide the e-mail address of the person who is completing the
template followed by the current date in the format of YYYYMMDD (YYYY
is the current year, MM is the month and DD is the day, all 0 values
included). You should supply exactly one CHANGED tag per NETWORK
template if this is an application for a new provider block.
Example:
changed: joebloggs@example.net 19950225
MNT-BY:
Please provide the APNIC allocated maintainer ID. The maintainer ID
provides some level of authorization control over who can update an
object protected by a MNT-BY field. If you do not have a maintainer
ID, you may either leave this field blank and a default maintainer ID
will be created for you (one without any authentication protection) or
you may apply for one using the APNIC Maintainer Object Request form
found at:
ftp://ftp.apnic.net/apnic/docs/maintainer-request
There can be zero or more MNT-BY tags per NETWORK template, however
each maintainer object specified must already exist in the APNIC
Registration database.
Example:
mnt-by: MAINT-FOO-AP
SOURCE:
Source of the information. For the purposes of APNIC forms, it will
always be APNIC. This information is always required in the database
and has already been added to the forms.
Example:
source: APNIC
5. Person Template
------------------
Please only complete this template if you have completed the
Network Template above and require an APNIC NIC-handle.
PERSON:
Please give the full name of the person this template will represent.
Do not use formal titles like `Dr' or `Prof' or `Sir'. Please provide
full names, not initials. The name should be provided as the person
would be addressed in a letter salutation (e.g., given name followed
by family name or family name followed by given name depending on the
the cultural custom). There can be exactly one PERSON field in a
PERSON template.
Example:
person: Joe Bloggs
ADDRESS:
Please complete with the full postal address written as you would for
postal mail (but do not include the name of your country or economy in
this field) using one line for each part of the address as shown below.
Example:
address: Examplenet ISP
address: No 1 Example Street
address: Example, 4064
COUNTRY:
Please give the two letter ISO 3166 code appropriate for the
contact person. Do NOT provide the full name of the country or economy
or the three letter ISO 3166 code. If you do not know the appropriate
ISO 3166 code for this person's address, please see the list of ISO
3166 codes maintained on APNIC at:
http://www.apnic.net/info/reference/lookup_codes.html
This tag is required for all PERSON templates, with only one COUNTRY
tag permitted.
Example:
country: BT
PHONE:
Please provide the work telephone number of the person specified in
this template as it would be dialed internationally (without the prefix
necessary to reach an international line). Please do not include the
leading zero when specifying the area/city code unless it is required to
correctly dial the number internationally. The format for the telephone
number is:
+<international code>-<area/city code>-<exchange>-<subscriber>
If an extension is necessary, please add "ext <extension>". Please do
not put 'x' or other abbreviations for "extension". You may provide more
than one telephone number. Each telephone number should be put on a
separate line and written in order of the most appropriate number to
the least appropriate.
Example:
phone: +81-20-1233-4676
phone: +81-20-1233-4677 ext 4711
FAX-NO:
Please complete with the facsimile number of the requestor as it would
be dialed internationally (without the prefix necessary to reach an
international line. Please do not include the leading zero when specifying
the area/city code unless it is required to correctly dial the number
internationally. The format for the facsimile number is:
+<internatinal code>-<area/city code>-<exchange>-<subscriber>
You may provide more than one facsimile number. Each facsimile number
should be put on a separate line and written in order of the most
appropriate number to the least appropriate. If the person does not have a
facsimile number, please leave blank.
Example:
fax-no: +81-20-1233-4678
E-MAIL:
Please supply the electronic mail address for the person. The
electronic mail address MUST be a valid Internet reachable RFC-822
address with a fully qualified domain name. If you do not have
Internet reachable e-mail connectivity, please leave this field blank.
Multiple e-mail addresses may be specified, with each on a separate
line and written in order of the most appropriate to the least.
Example:
e-mail: joebloggs@example.net
NIC-HDL:
A NIC-handle is a unique identifier used within the Internet registry
database to differentiate between people with the same names. NIC
handles are assigned by registries -- if you do not have one, please
do not make one up; follow the procedures described below in the
section entitled "Obtaining an APNIC NIC-handle" a handle will be
automatically generated for you if you. If you have an APNIC NIC
handle but do not remember it, please make a note of this in the
ADDITIONAL COMMENTS section of the application form and leave this
field blank. If you have a NIC-handle assigned by another registry,
e.g., InterNIC, please provide a full person template anyway using
the auto-generating handles as described below -- the regional
registries are currently investigating ways in which information such
as this can be shared, but no solution has yet been implemented.
Example:
nic-hdl: JB401-AP
REMARKS:
The remarks attribute contains any remarks about this person that
cannot be expressed in any of the other attributes. Although multiple
lines are allowed, it should be only be used if it provides extra
information to users of the database, and usage should be kept to a
minimum.
Example:
remarks: pager can be accessed by <e-mail>-pager
CHANGED:
Please indicate the e-mail address of the person who is completing the
template followed by the current date in the format of YYYYMMDD (YYYY
is the current year, MM is the month and DD is the day, all values 0
filled). You should supply exactly one CHANGED tag per PERSON
template if this is a new person object.
Example:
changed: joebloggs@example.net 19950225
MNT-BY:
Please provide the APNIC allocated maintainer ID. The maintainer ID
provides some level of authorization control over who can update an
object protected by a MNT-BY field. If you do not have a maintainer
ID, you may either leave this field blank and a default maintainer ID
will be created for you (one without any authentication protection) or
you may apply for one using the APNIC Maintainer Object Request Form
found at:
ftp://ftp.apnic.net/apnic/docs/maintainer-request
There can be zero or more MNT-BY tags per request template, however
each maintainer object specified must already exist in the APNIC
Registration Database.
Example:
mnt-by: MAINT-FOO-AP
SOURCE:
Source of the information. For the purposes of APNIC forms, it will
always be APNIC. This information is always required in the database
and has already been added to the forms.
Example:
source: APNIC
ADDITIONAL COMMENTS:
Please include any additional comments you have regarding the reason
for returning the Provider Independent blocks, or the reason for wishing
to exchange the IP Address blocks.
6. Section 2 - Faxed Verification
---------------------------------
This section is intended for security purposes only. In a letterhead
of the organisation registred in the database (as stated in the
CURRENT REGISTERED TEMPLATE) please send a letter faxed to the APNIC
at +61-7-3367-0482. In the faxed letter please include the following:
A. Verification of Address Space to be returned
Please state that you authorise the return of the IP address range/s
spefified in Section 1. Kindly also include the IP address range/s to
be returned to APNIC.
B. Signature of contact recorded in the database (if applicable) and a
legal authority within the organisation to authorise the faxed letter.
7. Application Example
----------------------
#[SECTION 1]#
#[CURRENT REGISTERED TEMPLATE V:1.0]#
inetnum: 202.0.0.0 - 202.0.1.255
netname: EXAMPLE-BLK-1-AP
descr: An example of a completed ISP application form
descr: Please don't send this verbatim to APNIC
country: BT
admin-c: EP10-AP
tech-c: EP10-AP
remarks: Example Provider Independent Assignment
changed: hostmaster@foonic.net 19941214
mnt-by: FOO-MNT
source: FOONIC
inetnum: 202.0.6.0 - 202.0.7.255
netname: EXAMPLE-BLK-2-AP
descr: An example of a completed ISP application form
descr: Please don't send this verbatim to APNIC
country: BT
admin-c: EP10-AP
tech-c: EP10-AP
remarks: Example Provider Independent Assignment
changed: hostmaster@foonic.net 19960203
mnt-by: FOO-MNT
source: FOONIC
inetnum: 211.128.0.0 - 211.128.1.255
netname: EXAMPLE-BLK-3-AP
descr: An example of a completed ISP application form
descr: Please don't send this verbatim to APNIC
country: BT
admin-c: EP10-AP
tech-c: EP10-AP
remarks: Example Provider Independent Assignment
changed: hostmaster@examplenic.net 19950603
mnt-by: EXAMPLE-MNT
source: APNIC
#[ADMINISTRATIVE TEMPLATE V:1.0]#
organisation-name: Examplenet ISP
requestor-name: Joe Bloggs, Emloyee Examplenet, Sys Admin.
address: 223 The Avenue
address: Example City
country: BT
phone: +61-7-3367-0490
fax: +61-7-3367-0482
allocated-by: EXAMPLENIC Example Network Information Centre
allocated-by: FOONIC Foo Network Information Centre
verify-email: hostmaster@examplenic.net
verify-email: hostmaster@foonic.net
address-range: EXAMPLE-BLK-1-AP 202.0.0.0 255.255.255.0 19941214
address-range: EXAMPLE-BLK-2-AP 202.0.6.0 255.255.254.0 19960203
address-range: EXAMPLE-BLK-3-AP 211.128.0.0 255.255.255.0 19950603
prefix-exchange: YES
#[NETWORK TEMPLATE V:5.0]#
netname: EXAMPLENET
descr: Examplenet
descr: Internet Service Provider
country: BT
admin-c: EP10-AP
tech-c: EP10-AP
remarks: Example Provider Independent Assignment
changed: joebloggs@example.net 19991018
mnt-by: APNIC-HM
source: APNIC
#[PERSON TEMPLATE V:4.0]#
person: Example Person
address: No 1 Example Street
address: Example, 4064
country: BT
phone: +61-7-33670490
fax-no: +61-7-33670482
e-mail: example1@example.net
nic-hdl: EP10-AP
remarks: This is an Example Person Object
remarks: Do not try to contact
mnt-by: APNIC-HM
changed: staff@apnic.net 19991018
source: APNIC
Additional Comments:
In the interest of aggregation we would like to advertise one
route instead of three.
#[SECTION 2]#
#[FAXED VERIFICATION]#
In a fax with the organisation's letterhead please include the following:
A. Verification of the Address range to be returned to the free pool of
globally unique IPv4 address space
B. Signature of the contact as recorded in the database (if applicable)
AND
Signature of employee with legal authority to sign for the organisation
returning address space
#[TEMPLATES END]#
=======================END===========================
(c) APNIC Pty Ltd 2000