CUT HERE

Transcription

1 Template: ARIN-IPv6-NET-MOD-5.0 ** As of XXX 2010 ** Detailed instructions are located below the template. 00. API Key: 01. Registration Action (M or R): 02. IPv6 Address and Prefix: 03. Network Name: 04. Origin AS: 05. Tech POC Handle: 06. Abuse POC Handle: 07. NOC POC Handle: 08. Public Comments: 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) We'll be glad to help you! CUT HERE TEMPLATE INSTRUCTIONS: Please copy and paste the text-based template into the body of an and send to with the subject line, "IPv6 NETWORK MODIFICATION". Please ensure your 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. 00. An API Key is a string of characters you can use to identify yourself to ARIN. You must first set up an ARIN Online account and create your API Key. Your ARIN Online account must be linked to a POC authorized to make the request. Find more information about API Keys at: This template allows you to modify information for an existing network, remove a downstream network, or return a network to ARIN. The registration action is required. Valid values are: M for Modify R for Remove/Return 02. Indicate the network to be modified or returned. You must indicate the network in CIDR format, for example: 2001:0100:0100::/48 You cannot modify or return multiple discontiguous networks with this template. Please submit a separate IPv6 Network

2 Modification template for each distinct contiguous network registration. 03. If you do not wish to modify the network name, this field should be left blank. If you wish to modify the network name, 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. OPTIONAL FIELDS: 04. 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. 05. 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 IP address space registration record. Although the template provides only one Tech POC field, you may duplicate field 05. to list multiple Tech POCs. If you are modifying a network record and would like to remove all Tech POCs, enter NONE in this field. 06. 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 IP address space registration record. Although the template provides only one Abuse POC field, you may duplicate field 06. to list multiple Abuse POCs. If you are modifying a network record and would like to remove all Abuse POCs, enter NONE in this field. 07. 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. Although the template provides only one NOC POC field, you may duplicate field 07. to list multiple NOC POCs. If you are modifying a network record and would like to remove all NOC POCs, enter NONE in this field. 08. If there are any comments you would like publicly displayed in ARIN's Whois regarding this registration, detail them here.

3 Suggested comments are: Public Comments: Public Comments: Standard NOC hours are 7am to 11pm EST If you are modifying a network record and would like to remove the public comments, enter NONE in this field.

4 Template: ARIN-IPv6-REASSIGN-5.0 ** As of XXX 2010 ** Detailed instructions are located below the template. 00. API Key: 01. Downstream Org ID: ** IF DOWNSTREAM ORG ID IS PROVIDED SKIP TO LINE 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 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 Address: ** NETWORK SECTION 20. IP Address and Prefix or Range: 21. Network Name: 22. Origin AS: 23. Justification: ** OPTIONAL FIELDS 24. Public Comments: 25. 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) We'll be glad to help you! CUT HERE TEMPLATE INSTRUCTIONS: Please copy and paste the text-based template into the body of an and send to with the subject line, "IPV6-REASSIGN". Please ensure your client sends ARIN the message as plain ASCII text, not as HTML.

5 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. 00. An API Key is a string of characters you can use to identify yourself to ARIN. You must first set up an ARIN Online account and create your API Key. Your ARIN Online account must be linked to a POC authorized to make the request. Find more information about API Keys at: 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 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 two-letter abbreviation of the state or province of the customer receiving the reassignment. 06. Indicate the postal code of the customer receiving the reassignment. 07. Indicate the ISO-3166 two-character country code of the customer receiving the reassignment. You can find a complete listing of country codes at: 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 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. A role account is not associated with a particular person, but with an office, position or task and is usually shared by multiple people. Valid values are: P or PERSON for Person R or ROLE for Role The Contact Type cannot be updated. 10. If the POC is a role account, enter the entire role account name. For example:

6 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 POC Name cannot be updated. 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. POC Name cannot be updated. 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 fields, you may duplicate field 13. as many times as necessary to capture the entire address. 14. Provide the city of the POC. The city is a required field. 15. Indicate the two-letter abbreviation of the state or province of the POC. 16. Indicate the postal code of the POC, if applicable. 17. Provide the ISO-3166 two-character country code of the POC. You can find a complete listing of country codes at: 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 address of the POC. RFC 2822 describes valid addresses. At least one address is required to process a new POC. To add a second address, duplicate field 19., and include both addresses on the template. NETWORK SECTION: 20. Indicate the network to be reassigned to the organization. You must indicate the network in CIDR format, for example: 2001:0100:0100::/ 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. If the downstream organization already has a reallocation or reassignment of IPv6 addresses, you must provide justification detail to ARIN explaining why you are reassigning additional space.

7 This is a free-form field. OPTIONAL FIELDS: 24. If there are any comments that you would like publicly displayed in ARIN's Whois, detail them here. Suggested comments are: Public Comments: Public Comments: Standard NOC hours are 7am to 11pm EST 25. Use this section to provide additional information to ARIN.

8 Template: ARIN-IPv6-REALLOCATE-5.0 ** As of XXX 2010 ** Detailed instructions are located below the template. 00. API Key: 01. Downstream Org ID: ** IF DOWNSTREAM ORG ID IS PROVIDED SKIP TO LINE 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 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 Address: ** NETWORK SECTION 20. IP Address and Prefix or Range: 21. Network Name: 22. Origin AS: 23. Justification: ** OPTIONAL FIELDS 24. Public Comments: 25. 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) We'll be glad to help you! CUT HERE TEMPLATE INSTRUCTIONS: Please copy and paste the text-based template into the body of an and send to with the subject line, "IPV6-REALLOCATE". Please ensure your client sends ARIN the message as plain ASCII text, not as HTML.

9 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. 00. An API Key is a string of characters you can use to identify yourself to ARIN. You must first set up an ARIN Online account and create your API Key. Your ARIN Online account must be linked to a POC authorized to make the request. Find more information about API Keys at: If the downstream organization to whom you are reallocating addresses already has an Org ID, please specify it in field 01. then skip to field Provide the legal name of the customer receiving the reallocation as it is registered with local, regional or national authorities. 03. Indicate the street address for the customer receiving the reallocation. 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 reallocation. 05. Indicate the two-letter abbreviation of the state or province of the customer receiving the reallocation. 06. Indicate the postal code of the customer receiving the reallocation. 07. Indicate the ISO-3166 two-character country code of the customer receiving the reallocation. You can find a complete listing of country codes at: 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 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. A role account is not associated with a particular person, but with an office, position or task and is usually shared by multiple people. Valid values are: P or PERSON for Person R or ROLE 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

10 If the POC is a person, enter only the last name. For example: Last Name or Role Account: Smith POC Name cannot be updated. 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. POC Name cannot be updated. 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 fields, you may duplicate field 13. as many times as necessary to capture the entire address. 14. Provide the city of the POC. The city is a required field. 15. Indicate the two-letter abbreviation of the state or province of the POC. 16. Indicate the postal code of the POC, if applicable. 17. Provide the ISO-3166 two-character country code of the POC. You can find a complete listing of country codes at: 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 address of the POC. RFC 2822 describes valid addresses. At least one address is required to process a new POC. To add a second address, duplicate field 19., and include both addresses on the template. NETWORK SECTION: 20. Indicate the network to be reallocation to the organization. You must indicate the network in CIDR format, for example: 2001:0100:0100::/ 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. If the downstream organization already has a reallocation or reallocation of IPv6 addresses, you must provide justification detail to ARIN explaining why you are reallocating additional space. This is a free-form field.

11 OPTIONAL FIELDS: 24. If there are any comments that you would like publicly displayed in ARIN's Whois, detail them here. Suggested comments are: Public Comments: Public Comments: Standard NOC hours are 7am to 11pm EST 25. Use this section to provide additional information to ARIN.