Template: ARIN-NET-IPv6-3.2.3
**********************************************************************
** As of February 2006 **
** **
** Enter all information to the right of the colon (:). **
** **
** DO NOT modify the format of this template in any way. **
** **
********************* INITIAL ALLOCATION SECTION *********************
** Complete fields 1 through 5 if requesting an initial IPv6 **
** allocation from ARIN. If your organization has already been **
** allocated IPv6 address space from ARIN, skip to field 6. **
**********************************************************************
1. ** Describe what IPv6 services you expect to offer. If available,
** provide the URL that details the services.
Expected services:
2. ** Provide the target date (month/year) for deploying IPv6
** services.
Deployment Date:
3. ** Provide a description of your organization's IPv6 network
** topology using the following format. Include both internal and
** end-user site usage for /48 or larger assignments.
** ----------------------------------------------------------
** Site/ Length of
** Customer Name Address Prefix Description/Comments
** ----------------------------------------------------------
Network Topology Plan:
4. ** Minimum allocation size is /32. Organizations may qualify for an
** initial allocation greater than /32 by submitting documentation
** that reasonably justifies the request.
Initial Prefix Length Requested:
5. ** If requesting more than a /32, provide the number of IPv4
** customers currently registered in ARIN's WHOIS database or an
** RWhois server. If registered in an RWhois server, provide the
** hostname and port number.
IPv4 Customers:
6. ** Provide additional information for ARIN to consider for this
** network request.
Additional Information:
******************* SUBSEQUENT ALLOCATION SECTION ********************
** Complete fields 6 through 11 for subsequent allocations only. **
** If requesting an initial IPv6 allocation, skip to field 12. **
**********************************************************************
7. ** List all IPv6 allocations from ARIN. Include address and prefix.
Existing IPv6 allocation:
8. ** Enter the amount of IPv6 address space issued to customers.
** Information is registered in units of sub-delegated /48
** networks.
Assigned:
9. ** Enter the amount of IPv6 address space used for internal
** purposes. An organization may sub-delegate a /48 per PoP as the
** service infrastructure of an IPv6 service operator.
Internal:
10. ** Enter the amount of unassigned or available IPv6 address space.
Unassigned:
11. ** Minimum allocation size is /32.
Subsequent Prefix Length Requested:
12. ** Detail your organization's IPv6 requirements for the next five
** years.
Five-year Plan:
************************ REGISTRATION SECTION ************************
13. ** REQUIRED. Enter a registered ARIN organization ID.
Org ID:
14. ** REQUIRED. Provide the organization name currently registered to
** your Org ID.
Org Name:
15. ** REQUIRED. Choose a network name using no more than 50
** characters.
Network Name:
16. ** If the network has DNS reverse mapping servers, list the
** hostnames of at least two name servers. Do not provide IP
** addresses. Duplicate the field to specify additional servers.
DNS Reverse Mapping Name Server:
DNS Reverse Mapping 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 line 17 and 18. **
**********************************************************************
17. ** Specify T for Technical, AB for Abuse or N for Network
** Operations Center.
POC Type:
18. ** Provide a POC handle currently registered in ARIN's WHOIS
** database.
POC Handle:
***************** PUBLIC COMMENTS SECTION (Optional) *****************
19. ** Comments listed here will appear in ARIN's WHOIS database.
Public Comments:
END OF TEMPLATE
-----------------------------CUT HERE----------------------------------------
Instructions for Completing the ARIN IPv6 Network Request 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
Internet Service Providers (ISPs) submit this template as part of the
application process for obtaining a block of Internet Protocol version 6
(IPv6) Numbers. Prior to requesting an allocation of addresses, please
refer to:
ARIN's Guidelines for IPv6 Address Space found at:
http://www.arin.net/registration/ipv6/index.html
The action of requesting addresses from ARIN indicates you have read and
agree to abide by these guidelines.
Please note that IPv6 address allocations from ARIN are subject to the
fees outlined at:
http://www.arin.net/billing/fee_schedule.html
Each ISP that is allocated IPv6 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 IPv6 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 "IPV6 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.
INITIAL ALLOCATION SECTION
IPv6 address space is issued based on current need. To qualify for an
initial allocation of IPv6 address space, an organization must:
a. Be an ISP.
b. Not be an end-site.
c. Plan to provide IPv6 connectivity to organizations to which it
will assign /48s, by advertising that connectivity through its
single aggregated address allocation.
d. Be an existing, known ISP in the ARIN region or have a plan for
making at least 200 /48 assignments to other organizations within
five years.
1. Provide a list of services your organization plans to offer with the
IPv6 allocation you are requesting. If your organization has a website
that details this information, provide the URL of this website.
2. Provide a date which your organization plans to deploy the expected
services being offered.
3. Provide the initial network topology and the projected one year network
topology, using the format below.
----------------------------------------------------------
Site/ Length of
Customer Name Address Prefix Description/Comments
----------------------------------------------------------
Atlanta /48 Internal relays
Customer /48 4 networks
4. Indicate the initial size allocation your organization is requesting.
Additional information may be necessary for requests larger than a /32.
5. Provide the number of IPv4 customers your organization has that will be
transitioning to IPv6 services. If this information is represented in
an RWHOIS server, please provide the RWHOIS server.
6. Include any additional information pertaining to this request.
SUBSEQUENT ALLOCATION SECTION
Subsequent allocation will be provided when an organization satisfies the
evaluation threshold of past address utilization in terms of the number of
sites in units of /48 assignments. The HD-Ratio [RFC 3194] is used to
determine the utilization thresholds that justify the allocation of
additional addresses. The HD-Ratio value of 0.94 will be used for
justifying additional IPv6 address space.
Where possible, the allocation will be made from an adjacent address
block, meaning that its existing allocation is extended by one bit to the
left.
7. Provide all existing IPv6 allocations. An example of an IPv6 allocation
is:
2001:0100::/32
8. List the number of /48s that have been issued to your customers.
9. List the number of /48s used internally by your organization.
10. List the number of /48s that are unassigned or available for
reassignment.
11. Indicate the size allocation your organization is requesting.
Additional information may be necessary for requests larger than a
/32.
12. Provide a detailed five-year plan regarding your organization's
allocation of IPv6 space.
REGISTRATION SECTION
13. Enter a registered ARIN Org ID. If you are unsure of your Org ID
please search for your organization name in ARIN's WHOIS.
14. Provide the legal name of your organization as it is registered with
local, regional or national authorities.
15. 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.
16. Organizations should provide at least two, but not more than thirteen
distinct name servers for providing address-to-name mapping for hosts
in 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 reverse mapping name services.
CONTACT SECTION (Optional)
You may add optional technical points of contact (POC) associated with
this network. If no POCs are added, the contacts associated with the
organization will serve as the POCs for this network. Fields 17 and 18
can be duplicated to allow for multiple POCs.
POCs must have a registered ARIN POC handle to be added as a contact on an
IPv6 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
<base>-ARIN, where <base> is a unique tag consisting of initials of a
person or role and a number.
17. Define the single function of the POC to be associated with the
network, as defined above (T, AB or N).
18. Provide the registered ARIN POC handle you wish to use as a contact
for this network.
PUBLIC COMMENTS SECTION (Optional)
19. If there are any comments that you would like publicly displayed in
WHOIS regarding this allocation, detail them here. Suggested
comments are:
Public Comments: http://www.example.net
Public Comments: Standard NOC hours are 7am to 11pm EST
|
