Plan 9 from Bell Labs’s /sys/src/pub/doc/arin/asn-request.txt

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


Template: ARIN-ASN-REQUEST-4.0
**  As of July 2006
**  Detailed instructions are located below the template.

01. Org ID:  
02. Org Name:
03. AS Name:

    ** Do you want to specifically request a 4-byte AS number
    ** instead of a traditional 2-byte AS number? Indicate
    ** YES or NO. If you are unsure, see detailed instructions
    ** for an explanation of 2-byte vs. 4-byte AS numbers.
04. 4-byte AS number: 

** OPTIONAL FIELDS
05. Tech POC Handle:
06. Abuse POC Handle:
07. NOC POC Handle:  
08. Public Comments:

END OF REGISTRATION SECTION

JUSTIFICATION SECTION
09. Are you applying as a multi-homed network?

10. What exterior gateway protocol will you use with 
    the requested AS number?

11. Provide the date you intend to start using the AS number.

12. Indicate all IP address blocks currently in use in 
    your network.

13. List the AS numbers of your providers/peers
     AS number:
     Organization name:
     AS number:
     Organization name:

14. If you are not going to be multi-homed, describe your
    site's unique routing policy.

15. 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!

-----------------------------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, "ASN
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. 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.

02. Indicate your organization's legally registered business name.

03. The AS name is used as an identifier. Supply a short name
    consisting of a combination of up to 50 letters and/or numbers. 
    You may use a dash (-) as part of the AS name, but no other 
    special characters, such as periods or underscores.

04. As of January 1, 2007, ARIN will assign a 4-byte (32-bit) AS 
    number to any organization explicitly asking for it. 

    ARIN assigns both 2-byte (16-bit) and 4-byte (32-bit) AS 
    numbers. Traditional AS numbers were always 2-bytes, 
    starting at AS1 and ending at AS65535. The introduction of 
    4-byte AS numbers extends the assignable range from AS65536 
    through AS4294967295 (that's 4.2 billion).

    Question 04. on this template asks you whether you would 
    like to request a 4-byte AS number. If so, indicate "YES". 
    When indicating "YES", please ensure your routing equipment 
    and any transit providers or peers are ready and able to 
    accept 4-byte AS numbers when exchanging routing information 
    via BGP.

    If you are unsure whether to request a 2-byte or 4-byte AS 
    number, ARIN advises you to indicate "NO" in field 04. Doing 
    so will result in the assignment of the traditional 2-byte 
    AS number.


OPTIONAL FIELDS:

05. Indicate the ARIN POC handle of a contact responsible for the 
    technical aspects of maintaining your network. The technical 
    POC may make modifications to the AS number registration.

    Please note your Org ID already has a Technical POC which will,
    by default, appear on the resource registration record. 

06. Indicate the ARIN POC handle of a contact responsible for 
    handling operational aspects of the acceptable or appropriate 
    uses of your network. The abuse POC may not make modifications 
    to the AS number registration.

    Please note your Org ID may already have an Abuse POC which will,
    by default, appear on the resource registration record.

07. Indicate the ARIN POC handle for your NOC. The NOC POC may
    not make modifications to the AS number registration record.

    Please note your Org ID may already have an NOC POC which will,
    by default, appear on the resource registration record.

08. If there are any comments you would like publicly displayed in 
    ARIN WHOIS regarding this registration, detail them here.

    Suggested comments are:
        Public Comments: http://www.example.net
        Public Comments: Standard NOC hours are 7am to 11pm EST


JUSTIFICATION SECTION:

09. If your organization is connected, or intends to connect, 
    to the Internet via two separate ISPs or peers, please 
    indicate YES. If you are requesting an AS number for
    a unique routing policy, please indicate NO.

10. Indicate the exterior gateway protocol your organization 
    will use to configure its routers with the requested AS 
    number.

11. Indicate the date when your connection to a second ISP
    or peer will be turned up. If connectivity through more
    than one ISP or peer is already live, please indicate 
    "IMMEDIATELY".

12. List all CIDR prefixes currently in use in your network.
     
13. Provide the AS numbers and organization names of at least
    two ISPs or peers to whom you are, or immediately intend 
    to be, connected.

14. If your organization is not multi-homed and you would 
    like to request an AS number because your routing policy 
    is different from your border gateway peers, please 
    detail your organization's unique routing policy.

15. 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.