Support Center

IP Address Public Policy

IP addresses are allocated to NTT DATA from the Regional Internet Registries (RIRs) and National Internet Registries (NIRs) such as APNIC (Asia Pacific Network Information Center), ARIN (American Registry of Internet Numbers), JPNIC (Japan Network Information Center), LACNIC (Latin America and Caribbean Network Information Centre), NIC.BR (Núcleo de Informação e Coordenação do Ponto BR) and RIPE (Réseaux IP Européens). In turn, NTT DATA assigns those IP addresses to our customers for use while connected to the NTT DATA network. The size of the IP address assignments vary and is solely based on the continually demonstrated and documented need of the customer.

Table of Contents

1. Introduction
2. Guidelines for Customers
3. Documentation Required
4. IP Address Justification (IPJ) Forms
5. References

I. Introduction

The NTT DATA IP Address Policy has been created with guidance from various Request For Comments documents (RFCs) and the existing policies of the RIRs and NIRs from which NTT DATA obtains IP addresses

Due to the dynamic nature of the internet, NTT DATA reserves the right to change this document at any time without prior notice. Please check the NTT DATA Global IP Network’s website for the latest version of this policy, as the latest version of the policy will supersede all others.

NTT DATA distributes IP addresses with three goals in mind:

1. Conservation: The objective distribution of globally unique IP address space according to the operational needs of customers. NTT DATA tries to prevent stockpiling in order to maximize the utilization of IP address space.
2. Routability: The distribution of globally unique IP address space in a manner which minimizes fragmentation and permits scalability in the internet routing table. The assignment of IP address space by NTT DATA does not guarantee routability due to other ISPs routing policies.
3. Registration: NTT DATA is required by RIR/NIRs to provide information on which entity is using the IP space. This information can be provided either via SWIP or an RWhois server. NTT DATA documents the assignment of IP addresses to a customer via a publicly available Referral WHOIS (rwhois) server. This information includes: company name, postal address, e-mail address, IP addresses assigned, and telephone number.

NTT DATA realizes that conservation and routability can be conflicting goals. NTT will review individual cases when there are conflicts to try to work out an appropriate compromise

II. Guidelines for Customers

NTT DATA has developed the following guidelines that will be applied to customer requests for IP address space:

1. IP addresses are assigned in blocks that conform to Classless Inter-Domain Routing (CIDR) boundaries.
2. IP addresses are assigned for the duration of the customer’s connection to the NTT DATA Global IP Network and must be routed on the NTT DATA Global IP Network. The IP addresses assigned are not portable. In the event that the customer disconnects from the NTT DATA Global IP Network or stops routing the addresses on the NTT Global IP Network, a 30 calendar day grace period will be given for the customer to renumber out of their assigned IP address space. The 30 calendar day grace period will begin from the date the route announcement was last seen announced directly by the customer to the NTT DATA network as determined by NTT DATA or 30 calendar days prior to their billing termination date, whichever occurs first.
3. At no time shall a current NTT DATA customer use and/or announce NTT DATA IP addresses that have not been specifically assigned to them. Former NTT DATA customers and non-customers may not use and/or announce any NTT DATA IP addresses except in cases where a formal agreement has been reached (e.g. BGP multihoming). Unauthorized use and/or announcement of NTT DATA IP addresses will result in the immediate reclamation of the unauthorized IP addresses and may jeopardize current and future IP address assignments from NTT DATA.
4. In the event that an NTT DATA customer (Customer A) acquires/merges/takes over another NTT DATA customer (Customer B), the resulting customer of record will be required to renumber “Customer B” into IP address space assigned to “Customer A”. Should the resulting customer require additional space to accommodate this renumbering, they will need to complete an IP Address Justification (IPJ) form (documenting their address space utilization) for review and approval by NTT DATA.
5.  At any time, NTT DATA may require a customer to justify its IP address assignment. If the customer is unable to do so, its ability to obtain future assignments may be jeopardized and its existing assignments may be revoked.
6.  IP addresses are assigned to customers using a “slow-start” process. New customers will receive a minimal assignment based on their immediate requirement. Thereafter, the size of assigned IP address blocks may be increased based on the speed that the customer utilizes all previously assigned IP address blocks.
7. RIR/NIRs may set a maximum size of the IP address assignment that NTT DATA is allowed to make. If a customer requests an assignment size that is above the RIR/NIR size limit, the RIR/NIR reserves the right to review and approve the assignment. The RIR/NIR may have different guidelines than NTT DATA does for reviewing and approving the assignment and the customer would be required to adhere to the RIR/NIR’s guidelines in this instance.
8. The Internet community filters IPV6 announcements based on the IPV6 allocations from RIR/NIRs. The allocations (and filtering) are necessary in order to minimize routing table expansion. Any customer requiring BGP multi-homing, now or in the future, should apply for Provider Independent (PI) IPv6 space directly from their RIR/NIR. RIR/NIRs can also allocate /48 critical infrastructure space if justified (eg. root domain operators). Customers with multiple connections to the NTT DATA Global IP Network may announce prefixes smaller than /48 along with their RIR/NIR allocation to effectively manage their inbound traffic, but the smaller prefixes will not be propagated beyond the AS2914 backbone. More information regarding each RIR/NIR’s IPv6 assignment and allocation policies can be found on their respective websites.
9. When a customer requests an IP address space assignment from NTT DATA that will be used for IP-based web hosting, the customer will need to provide technical justification as to why they are providing IP-based web hosting instead of name-based web hosting. NTT is required to provide this information to the RIRs.
10. IP addresses assigned to the customer are for the customer’s use and may not be reassigned.  NTT DATA will only register RPKI ROAs for assigned IP addresses with an origin AS (Autonomous System) matching the customer’s AS number used to peer with NTT DATA.
11.  NTT DATA reserves the right to assign IP addresses from RIR allocations of its choice. As a result, IP addresses assigned to customers may not be from the RIR or NIR governing the region where the customer intends to use the assigned IP addresses.
12. Geolocation and geocoding of IP address assignments will be provided on a best effort basis using the method described in RFC9092. NTT DATA will not provide any support related to geolocation issues related to assigned IP addresses outside of updating the applicable geofeed files, which can be requested by opening a trouble ticket with NTT DATA’s Global IP Network Operations Center.
13. Network prefix size of the requested assignment cannot be guaranteed and may be provided in multiple smaller assignments equal to the number of /24 equivalents requested. All /24 and larger assignments will maintain a minimum length of /24.
14. Returned assignments must be the same size as originally assigned; partial returns are not accepted.
15. For customer IP address assignments of /24 and larger, NTT DATA will not manage reverse DNS but can delegate this responsibility to the customer’s DNS servers. However, NTT DATA reserves the right to revoke the delegation without notice if the customer’s DNS servers fail to respond for the delegated in-addr.arpa zones for more than 7 calendar days, unless otherwise agreed upon.

III. Documentation Required

Before NTT DATA makes an IP address assignment to a customer, the following documentation must be submitted by the customer. NTT DATA will not begin the IP address assignment process until all of the required documentation has been submitted. A link to the NTT DATA Global IP Network IP Address Justification (IPJ) form is included in section IV.

1. Documentation of existing IP address space usage. This shows how any space the customer has is currently being used, along with projections for the next 3 and 6 months.
2. Documentation showing how the requested IP space will be used. This shows how the customer plans to use the space immediately, along with projections for the next 3 and 6 months.
3. A network topology map for all requests of 128 IP addresses (/25) or larger..
4. A description of the network routing plans, along with any protocols used and the protocol limitations.
5. For customers requesting space for web hosting, a list of IP addresses currently being used for web hosting, and a list of domains being hosted. If IP-based hosting is being done, a list of technical reasons why named-based hosting cannot be done must be included.

This information will be used by NTT DATA ONLY to justify the assignment of IP addresses to a customer. The information may also be given to the RIRs if they request it as part of reviewing their allocations to NTT.

NTT reserves the right to amend this policy at any time.

IV. IP Address Justification (IPJ) Forms

IP Address Justification (IPJ) Form, Microsoft Word version

V. NTT Announcement of Customer-Owned IP Addresses

V. NTT DATA Announcement of Customer-Owned IP Addresses
Customers may request NTT DATA to originate route announcements of IP address space assigned to them by a Regional Internet Registry (RIR) from NTT DATA’s Autonomous System Number (ASN). In such cases, NTT DATA requires that the customer registers and maintains a Resource Public Key Infrastructure Route Origin Authorization (RPKI ROA) with AS2914 or another ASN communicated by NTT DATA as the Origin AS. This is in order to show that NTT DATA is authorized to announce the IP address space by the assignee. Requests to announce customer-owned IP addresses are reviewed on a case-by-case basis and it is at NTT DATA’s sole discretion to originate or withdraw the route announcement, regardless of if a ROA exists.

VI. References

[RFC 2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and Postel, J.,
“INTERNET REGISTRY IP ALLOCATION GUIDELINES”, November 1996.

www.arin.net/policy/nrpm.html

www.ripe.net/ripe/docs/iprequestform.html

www.ripe.net/ripe/docs/ipv4-policies.html