Template: ARIN-REASSIGN-DETAILED-4.2 ** As of October 2007 ** Detailed instructions are located below the template. 01. Downstream Org ID: ** IF DOWNSTREAM ORG ID IS PROVIDED SKIP TO LINE 20. 02. Org Name: 03. Org Address: 03. Org Address: 04. Org City: 05. Org State/Province: 06. Org Postal Code: 07. Org Country Code: 08. Org POC Handle: ** IF POC HANDLE IS PROVIDED SKIP TO LINE 20. 09. Org POC Contact Type (P or R): 10. Org POC Last Name or Role Account: 11. Org POC First Name: 12. Org POC Company Name: 13. Org POC Address: 13. Org POC Address: 14. Org POC City: 15. Org POC State/Province: 16. Org POC Postal Code: 17. Org POC Country Code: 18. Org POC Office Phone Number: 19. Org POC E-mail Address: ** NETWORK SECTION 20. IP Address and Prefix or Range: 21. Network Name: 22. Origin AS: 23. Hostname of DNS Reverse Mapping Nameserver: 23. Hostname of DNS Reverse Mapping Nameserver: ** OPTIONAL RESOURCE CONTACT SECTION 24. Net POC Type (T, AB, or N): 25. Net POC Handle: ** IF POC HANDLE IS PROVIDED SKIP TO LINE 37. 26. Net POC Contact Type (P or R): 27. Net POC Last Name or Role Account: 28. Net POC First Name: 29. Net POC Company Name: 30. Net POC Address: 30. Net POC Address: 31. Net POC City: 32. Net POC State/Province: 33. Net POC Postal Code: 34. Net POC Country Code: 35. Net POC Office Phone Number: 36. Net POC E-mail Address: ** OTHER OPTIONAL FIELDS 37. Public Comments: 38. Additional Information: 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, "REASSIGN DETAILED". Please ensure your e-mail client sends ARIN the message as plain ASCII text, not as HTML. Please do not attach the template. 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. If the downstream organization to whom you are reassigning addresses already has an Org ID, please specify it in field 01. then skip to field 20. 02. Provide the legal name of the customer receiving the reassignment as it is registered with local, regional or national authorities. 03. Indicate the street address for the customer receiving the reassignment. Although the template provides only two address fields, you may duplicate field 03. as many times as necessary to capture the entire address. 04. Indicate the city of the customer receiving the reassignment. 05. Indicate the state or province of the customer receiving the reassignment. 06. Provide the postal code of the customer receiving the reassignment. 07. Provide the ISO-3166 two-character country code of the customer receiving the reassignment. You can find a complete listing of country codes at: http://www.arin.net/community/countries.html 08. Indicate the ARIN POC handle of a contact responsible for the administrative and technical operations of the organization. If no handle has been registered for the POC, please fill-out fields 09. through 19. 09. Only fill-out this field if you have not specified a registered ARIN POC handle in field 08. A POC can be either a person or a role account. Indicate P for person or R for role. The Contact Type cannot be updated. 10. If the POC is a role account, enter the entire role account name. For example: Last Name or Role Account: Network Operations Center If the POC is a person, enter only the last name. For example: Last Name or Role Account: Smith 11. If the POC is a person, the first name is required. If the POC is a role account, the first name should be left blank. 12. If the POC is a role, a company name is required. This will help distinguish the Hostmaster from ABC Company from the Hostmaster at XYZ Company. It is optional for persons. 13. The street address for the POC is required. Although the template provides only two address lines, you may duplicate 13. as many times as necessary to capture your entire address. However, do not include the city, state or province, postal code or country code in this field. An example is: Address: 111 Scenic Overview Drive Address: Suite 400 Address: IP Management Department 14. Provide the city of the POC. The city is a required field. 15. For the United States and Canada, provide the two-letter state or province abbreviation for the POC. For other countries, provide the abbreviated or full state/province name, if applicable. 16. Provide the applicable postal code for the locality of the POC. As an example, for the United States, use the zip code. If the country does not use postal codes, leave the field blank. 17. Provide the ISO-3166 two-character country code of the POC. You can find a complete listing of country codes at: http://www.arin.net/community/countries.html 18. Provide the office telephone number of the POC, including country and area codes. Only numbers and the characters + - () are valid. Do not include phone extensions and additional instructions in the phone number field. 19. Enter the e-mail address of the POC. RFC 822 describes valid e-mail addresses. At least one e-mail address is required to process a new POC. To add a second e-mail address, duplicate field 19. and include both e-mail addresses on the template. NETWORK SECTION: 20. Indicate the network to be reassigned to the organization. Valid values are: 10.0.0.0/24 10.0.0.0 - 10.0.0.255 21. 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 network name, but no other special characters, such as periods or underscores. 22. List all AS numbers from which the 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. 23. Provide fully-qualified host names for the servers that will be providing in-addr.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 23. for each additional server. Do not list multiple servers on a single line. 24. Define the function of the POC. Specify "T" for resource technical contact, specify "AB" for resource abuse contact, or specify "N" for resource NOC contact. You can also specify more than one value, separating them with commas (e.g. "T, AB"). You can duplicate fields 24. through 36. as many times as necessary to specify multiple POCs for a registration. 25. Indicate the ARIN POC handle of a contact responsible for the function specified in field 24. If no handle has been registered for the POC, please fill-out fields 26. through 36. 26. Only fill-out this field if you have not specified a registered ARIN POC handle in field 25. A POC can be either a person or a role account. Indicate P for person or R for role. The Contact Type cannot be updated. 27. If the POC is a role account, enter the entire role account name. For example: Last Name or Role Account: Network Operations Center If the POC is a person, enter only the last name. For example: Last Name or Role Account: Smith 28. If the POC is a person, the first name is required. If the POC is a role account, the first name should be left blank. 29. If the POC is a role, a company name is required. This will help distinguish the Hostmaster from ABC Company from the Hostmaster at XYZ Company. It is optional for persons. 30. The street address for the POC is required. Although the template provides only two address lines, you may duplicate 30. as many times as necessary to capture your entire address. However, do not include the city, state or province, postal code or country code in this field. An example is: Address: 111 Scenic Overview Drive Address: Suite 400 Address: IP Management Department 31. Provide the city of the POC. The city is a required field. 32. For the United States and Canada, provide the two-letter state or province abbreviation for the POC. For other countries, provide the abbreviated or full state/province name, if applicable. 33. Provide the applicable postal code for the locality of the POC. As an example, for the United States, use the zip code. If the country does not use postal codes, leave the field blank. 34. Provide the ISO-3166 two-character country code of the POC. You can find a complete listing of country codes at: http://www.arin.net/community/countries.html 35. Provide the office telephone number of the POC, including country and area codes. Only numbers and the characters + - () are valid. Do not include phone extensions and additional instructions in the phone number field. 36. Enter the e-mail address of the POC. RFC 822 describes valid e-mail addresses. At least one e-mail address is required to process a new POC. To add a second e-mail address, duplicate field 36., and include both e-mail addresses on the template. OTHER OPTIONAL FIELDS: 37. If there are any comments that you would like publicly displayed in ARIN WHOIS, detail them here. Suggested comments are: Public Comments: http://www.example.net Public Comments: Standard NOC hours are 7am to 11pm EST 38. Use this section to provide additional information to ARIN.