Template: ARIN-EXPERIMENTAL-5.0
**********************************************************************
** As of March 2011 **
** **
** Enter all information to the right of the colon (:). **
** **
** DO NOT modify the format of this template in any way. **
** **
*********************** JUSTIFICATION SECTION ************************
0. API Key:
1. ** List the URL where the experiment is publicly documented.
URL:
2. ** Describe any technical coordination done with other organizations
** that has taken into consideration any potential negative impact of
** the proposed experiment on the operation of the Internet and its
** deployed services, and consideration of any related experimental
** activity.
Technical Coordination:
3. ** Start date of proposed experiment.
Start Date:
4. ** End date of proposed experiment.
End Date:
** ##------------ IPv4 12-MONTH PROJECTION SUBSECTION -------------**
** The Numbering Resources are allocated on a lease/license basis
** for a period of one year. If an organization requires more resources
** than stipulated by the minimum allocation sizes in force at the time of
** their request, their experimental documentation should have clearly
** described and justified why this is required.
5. ** If you are requesting IPv4 addresses, list the number of addresses
** in /24s that will be needed for the next 12 months.
Projections:
6. ** Provide any additional information you would like ARIN to
** consider for this experimental network registration request.
Additional Information:
** ##------------ IPv6 12-MONTH PROJECTION SUBSECTION -------------**
** The Numbering Resources are allocated on a lease/license basis
** for a period of one year. If an organization requires more resources
** than stipulated by the minimum allocation sizes in force at the time of
** their request, their experimental documentation should have clearly
** described and justified why this is required.
7. ** If you are requesting IPv6 addresses, list the number of addresses
** in /32s that will be needed for the next 12 months.
Projections:
8. ** Provide any additional information you would like ARIN to
** consider for this experimental network registration request.
Additional Information:
** ##--------- AUTONOMOUS SYSTEM NUMBER PROJECTION SUBSECTION -----**
** The Numbering Resources are allocated on a lease/license basis
** for a period of one year. If an organization requires more resources
** than stipulated by the minimum allocation sizes in force at the time of
** their request, their experimental documentation should have clearly
** described and justified why this is required.
9. ** If you are requesting an ASN, list the number of ASNs that will be
** needed for the next 12 months.
ASNs needed:
10. ** Provide any additional information you would like ARIN to
** consider for this experimental network registration request.
Additional Information:
************************ REGISTRATION SECTION ************************
11. ** REQUIRED. Enter the Org ID currently registered in ARIN's WHOIS
** database.
Org ID:
12. ** REQUIRED. Provide the organization name currently registered to
** your Org ID.
Org Name:
13. ** REQUIRED. Choose a name for the network, using no more than 50
** characters. It may contain letters, numbers and/or dashes (-).
Network Name:
14. ** If the network has in-addr.arpa servers, list the hostnames of
** at least two name servers. Do not provide IP addresses.
** Duplicate field name to specify additional servers.
IN-ADDR Name Server:
IN-ADDR Name Server:
********************* CONTACT SECTION (Optional) *********************
** The person or role in this section serves as a **
** supplemental contact to the organization POC(s). To **
** specify multiple contacts, duplicate lines 16 and 17. **
**********************************************************************
15. ** Specify T for Technical, AB for Abuse or N for Network
** Operations Center.
POC Type:
16. ** Provide a POC handle currently registered in ARIN's WHOIS
** database.
POC Handle:
***************** PUBLIC COMMENTS SECTION (Optional) *****************
17. ** Comments listed here will appear in ARIN's WHOIS database.
Public Comments:
END OF TEMPLATE
-----------------------------CUT HERE ----------------------------------------
Instructions for Completing the ARIN Experimental Allocation Template
Please complete the template and submit via e-mail to hostmaster@arin.net.
The ARIN Registration Services Department will acknowledge receipt of your
completed request via e-mail.
BACKGROUND
Experimental address allocations offer a systematic means of receiving
Numbering Resources on a temporary basis as part of a recognized
experiment in Internet technology deployment.
For more information on requesting experimental allocations, refer to:
https://www.arin.net/policy/nrpm.html#eleven
Please note that experimental numbering resources from ARIN are subject to
the fees outlined at:
https://www.arin.net/fees/fee_schedule.html#experiment
Each organization that is allocated Internet Protocol (IP) address space
from ARIN must first establish an Organization Identification (Org ID)
with ARIN. The Org ID is an alphanumeric identifier that references an ISP
in the ARIN registration system. If you do not have an Org ID, or you wish
to establish a new organization ID, complete and submit an Organization
Template before submitting this template. Refer to the Organization
Template instructions for more information.
In order to ensure prompt and accurate processing of your experimental
Network Request Template, please follow the instructions below. Any errors
found may result in the template being returned for correction. If after
reading these instructions, you still have questions, contact the ARIN
Registration Services Department Help Desk:
via e-mail: hostmaster@arin.net
via phone: +1-703-227-0660
========================================================================
TEMPLATE INSTRUCTIONS
Please enter "Experimental Numbering Resource Request" in the subject line
of the e-mail message.
IMPORTANT NOTE: Do not remove or modify the template header, i.e. the line
beginning with "Template:" or the footer, i.e. "END OF TEMPLATE". Both are
required for processing. All lines that begin with ## are guidelines on
how to supply the appropriate information, and are not necessary for
processing.
JUSTIFICATION SECTION
The JUSTIFICATION SECTION asks for information pertaining to the details
of your experiment.
00. An API Key is a string of characters you can use to identify
yourself to ARIN. You must first set up an ARIN Online account
and create your API Key.
https://www.arin.net/public/register_1.xhtml
Your ARIN Online account must be linked to a POC authorized to
make the request. Find more information about API Keys at:
https://www.arin.net/features/api_keys.html
1. List the URL where the details of your experiment are outlined.
2. Describe any technical coordination with other organizations that you
have done and whether consideration of negative impact on the operation
of the Internet have been discussed as a result of your experiment.
3. List the date that the experiment will start.
4. List the date that the experiment will end.
IPv4 12-MONTH PROJECTION SUBSECTION
5. List your projections in the number of /24s needed.
6. Include any additional information pertaining to this request.
IPv6 12-MONTH PROJECTION SUBSECTION
7. List your projections in the number of /32s needed.
8. Include any additional information pertaining to this request.
AUTONOMOUS SYSTEM NUMBER 12-MONTH PROJECTION SUBSECTION
9. List the number of ASNs that will be needed for the next 12 months.
10. Include any additional information pertaining to this request.
REGISTRATION SECTION
11. Enter a registered ARIN Org ID. If you are unsure of your Org ID
please search for your organization name in ARIN's WHOIS.
12. Provide the legal name of your organization as it is registered with
local, regional or national authorities.
13. The network name is used as an identifier. Supply a short name
consisting of a combination of up to 50 letters and/or numbers for the
network. You may use a dash (-) as part of the network name, but no
other special characters, such as periods or underscores.
14. Networks should provide at least two, but not more than thirteen
distinct name servers for providing address-to-name mapping for
hostsin the network. To specify more than two, duplicate the field for
each additional server. Do not list multiple servers on a single line.
Provide fully-qualified host names for the servers that will be
providing in-addr name services.
CONTACT SECTION (Optional)
You may add optional points of contact (POC) associated with this network.
If no POCs are added, the contact associated with the organization will
serve as the POCs for this network. Fields 16 and 17 can be duplicated to
allow for multiple POCs.
POCs must have a registered ARIN POC handle to be added as a contact on an
experimental network request. If you are unsure of a POC's handle, perform
a "last name, first name" search in the WHOIS database. If you do not have
a POC handle, or you wish to register an additional contact, complete and
submit the POC template prior to submitting this template. Refer to the
POC template instructions for more information.
The applicable POC types include:
a. Technical (T) - Optional contact responsible for the technical
aspects of maintaining the assigned network address space. This POC
should be able to answer troubleshooting and operational questions
about the network. The technical POC may make modifications to the
assigned block.
b. Abuse (AB) - Optional contact responsible for handling operational
aspects of the acceptable or appropriate uses of the allocated
network. The abuse POC may not make modifications to the allocated
network registration.
c. Network Operations Center (N) - Optional contact responsible for
network operations and troubleshooting. The POC from the Network
Operations Center, also known as the NOC, may not make modifications
to the allocated network registration.
Each POC in the ARIN database is assigned a handle in the format
-ARIN, where is a unique tag consisting of initials of a
person or role and a number.
15. Define the single function of the POC to be associated with the
network, as defined above (T, AB or N).
16. Provide the registered ARIN POC handle you wish to use as a contact
for this network.
PUBLIC COMMENTS SECTION (Optional)
17. If there are any comments that you would like publicly displayed in
ARIN's Whois, detail them here. All public comments must be operational
in nature. All comments must be accurate. ARIN reserves the right to
edit or remove public comments.
Suggested comments are:
Public Comments: http://www.example.net
Public Comments: Standard NOC hours are 7am to 11pm EST