ICAO Ipv6 Address Allocation
01. Prefix Length Requested:
02. Org ID:
03. Org Name:
04. Network Name:
** OPTIONAL FIELDS
05. Origin AS:
06. Hostname of DNS Reverse Mapping Nameserver:
06. Hostname of DNS Reverse Mapping Nameserver:
07. Tech POC Handle:
08. Abuse POC Handle:
09. NOC POC Handle:
10. Public Comments:
END OF REGISTRATION SECTION
INITIAL ALLOCATION JUSTIFICATION SECTION
11. Describe the IPv6 services you expect to offer.
12. Provide the target date (month/year) for deployment.
13. How many IPv4 customers do you currently serve?
14. Will you announce the single aggregated IPv6 prefix you
are allocated by ARIN? Indicate YES or NO.
15. Do you plan to assign IPv6 addresses to other organizations?
Indicate YES or NO. If YES, detail this plan.
16. Estimate how much space you plan to assign to customers
during the next 5 years. How many /64s, /56s, /48s, and
other prefix sizes will you be assigning?
17. Provide any additional information for ARIN to consider.
SUBSEQUENT ALLOCATION JUSTIFICATION SECTION
18. Existing IPv6 allocations.
19. Indicate the amount of addresses sub-delegated to
your customers.
20. Indicate the amount of addresses used internally by
your organization.
21. Indicate the amount of addresses that are available.
22. Detail your five year IPv6 plan.
END OF TEMPLATE
If you would like assistance completing this template, please do
not hesitate to contact ARIN's Registration Services Help Desk
at +1 (703) 227-0660. We'll be glad to help you!
ARIN charges a transaction fee and/or a yearly registration fee
for approved requests for IP addresses. IPv6 registrations,
however, may be subject to waivers. For more information, see:
https://www.arin.net/fees/fee_schedule.html#ipv6_alloc
------CUT HERE ------
TEMPLATE INSTRUCTIONS:
Please copy and paste the text-based template into the body of an e-mail
and send to with the subject line, "IPV6 REQUEST".
Please ensure your e-mail client sends ARIN the message as plain ASCII
text, not as HTML.
Please do not attach the template.
You are welcome to attach any supporting documentation.
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.
01. List the amount of address space you wish to request. This
should be /32 or larger.
02. Enter a registered ARIN Org ID. If you are unsure of your Org ID
please search for your organization's name in ARIN's WHOIS
database.
03. Indicate your organization's legally registered business name.
04. 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.
OPTIONAL FIELDS:
05. List all AS numbers from which the requested network may
originate. You can list as many AS numbers as necessary.
You must separate multiple AS numbers with a comma. You may
not list AS number ranges; only list individual AS numbers.
06. Provide fully-qualified host names for the servers that will be
providing ip6.arpa name services. DO NOT LIST IP ADDRESSES.
Networks should provide at least two (but not more than
thirteen) distinct nameservers for providing address-to-name
mapping for hosts in the network. To specify more than two,
duplicate field 06. for each additional server. Do not list
multiple servers on a single line.
07. Indicate the ARIN POC handle of a contact responsible for the
technical aspects of maintaining the IP address space. The
technical POC may make modifications to the allocated block.
Please note your Org ID already has a Technical POC which will,
by default, appear on the resource registration record.
08. Indicate the ARIN POC handle of a 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.
Please note your Org ID may already have an Abuse POC which will,
by default, appear on the resource registration record.
09. Indicate the ARIN POC handle for your NOC. The NOC POC may
not make modifications to the allocated network registration.
Please note your Org ID may already have an NOC POC which will,
by default, appear on the resource registration record.
10. If there are any comments you would like publicly displayed in
ARIN 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
INITIAL ALLOCATION JUSTIFICATION SECTION:
11. List all IPv6 services and products you are (or will be)
offering to your customers.
12. Indicate the month and year you expect to deploy IPv6 on
your network.
13. Indicate the total number of customers you have today to whom
you provide IPv4 services.
14. Specify YES or NO. If you receive an allocation from ARIN
and you will announce the least specific aggregated prefix
to your BGP neighbors, indicate YES. If you plan to
announce more specifics of your allocation to your BGP
neighbors, indicate NO.
15. Indicate YES or NO. If you specify YES, please detail to which
existing customers, or what types of future customers, you
will assign IPv6 addresses.
16. Enumerate your planned 5 year numbering topology by indicating
the number of /64, /56, /48, and other prefix sizes you
intend on assigning to customers.
17. Use this section to provide additional information to ARIN.
If you are attaching any supporting documentation to your
e-mail, please indicate this here. If you are requesting
addresses under ARIN's Micro-allocation for Internal
Infrastructure policy, provide all relevant detail in this
field.
SUBSEQUENT ALLOCATION JUSTIFICATION SECTION:
This section applies only to organizations requesting an additional
allocation of IPv6 address space.
18. List all IPv6 allocations (from any RIR) of which your
organization is presently the registrant.
19. For all networks listed in field 18., indicate the amount
of addresses sub-delegated to your customers. Use any unit
of measurement appropriate to your current addressing topology.
20. For all networks listed in field 18., indicate the amount
of addresses being used internally by your organization.
Use any unit of measurement appropriate to your current
addressing topology.
21. For all networks listed in field 18., indicate the amount
of available addresses.
22. Provide a detailed 5-year plan for the further deployment
of IPv6 throughout your network.