Plan 9 from Bell Labs’s /sys/src/pub/doc/arin/v6-end-user.txt

Copyright © 2021 Plan 9 Foundation
Distributed under the MIT License.
Download the Plan 9 distribution.


Template: ARIN-NET-END-USER-IPv6-4.1
**  As of February 2007
**  Detailed instructions are located below the template.

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 ASSIGNMENT JUSTIFICATION SECTION
11. Have you been issued IPv4 addresses by ARIN on or after
    December 22, 1997?
    Indicate YES or NO. If YES, skip 12., 13., and 14.

12. List all transit providers and any peers.
     
13. Indicate all IPv4 addresses in use in your network today.

14. Provide a complete numbering topology detailing how
    you are currently utilizing IPv4 addressses:

    --------------------------------------------------------------
    IP address/subnet       description      # of addresses in use
    --------------------------------------------------------------

15. If you are requesting a /47 or larger, provide a proposed
    numbering topology detailing how you will utilize IPv6
    addresses. If you are requesting a /48, skip this question.
    ----------------------------------------------------------
    Site            Prefix Size           Description/Comments
    ----------------------------------------------------------

** SUBSEQUENT ASSIGNMENT JUSTIFICATION SECTION

16. List all IPv6 assignments obtained directly from ARIN.

17. Indicate the number of used /48s.

18. Indicate the number of available /48s.

19. Provide any additional information for ARIN to consider.

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_assign

-----------------------------CUT HERE ---------------------------

TEMPLATE INSTRUCTIONS:

Please copy and paste the text-based template into the body of an
e-mail and send to hostmaster@arin.net 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 /48 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 ASSIGNMENT JUSTIFICATION SECTION:

11. Indicate "YES" if you have received or been approved for any
    IPv4 end-user assignments directly by ARIN. Qualifying assignments
    only include registrations made on or after December 22, 1997. 
    If you indicate "YES", please skip questions 12., 13., and 14. 

12. List all networks from whom you purchase transit or with whom
    you exchange peering information. You may list these as 
    organization names or AS numbers.

13. Indicate all IPv4 address space in use in your network today.
    The public IPv4 address space listed in this field should be 
    explicitly reassigned or registered to you in ARIN's WHOIS 
    database or in a public RWhois server.

14. Please provide a comprehensive numbering topology, accounting
    for every IP address in use in your network today. ARIN staff
    will use this chart to determine if you meet the minimum
    criteria for requesting IPv4 address space from ARIN, which,
    in turn, is justification for receiving an IPv6 end-user
    assignment, per the policy criteria.

15. If you are requesting an IPv6 assignment larger than a /48,
    you must justify this larger assignment. To do so, please provide 
    a proposed numbering topology for how you will use the requested 
    IPv6 prefix from ARIN. Please only detail /48 and larger site 
    assignments. More granular detail may be asked for during the 
    request process, but is not necessary for the purposes of 
    completing the request template.


SUBSEQUENT ASSIGNMENT JUSTIFICATION SECTION:

This section applies only to organizations requesting an additional
assignment of IPv6 address space.

16. List all IPv6 assignments from ARIN of which your 
    organization is presently the registrant.

17. For all networks listed in field 16., indicate the number
    of /48s being used internally by your organization.

18. For all networks listed in field 16., indicate the number
    of /48s presently unutilized.

19. Use this section to provide additional information to ARIN.
    If you are attaching any supporting documentation to your
    e-mail, please indicate this here.



Bell Labs OSI certified Powered by Plan 9

(Return to Plan 9 Home Page)

Copyright © 2021 Plan 9 Foundation. All Rights Reserved.
Comments to webmaster@plan9.bell-labs.com.