Giganet operates a strict IPv4 justification process where customers request more than the standard IPv4 address allocation against their Internet connection.
This is due to their only been a finite amount of IPv4 addresses remaining, and since 2014, RIPE NCC, the body that is in charge of Internet addressing allocations in the UK and EMEA region, have 'run out' of addresses to hand out. Since this time, each ISP is only able to request an additional /22 or block of 1024 IPv4 addresses, and that's it!
IPv4 addresses, (which are the most prevalent on the Internet), were never designed with today’s super connected world in mind. Therefore, there are maximum of ~4.2 billion IPv4 addresses available and a few million of these are reserved and can’t be allocated to end users.
Therefore, we have to be careful to assign large blocks of IPv4s to customers as we only have a finite resource as do every other ISP. We also have to adhere to RIPE NCC rules. RIPE manage IP addresses in EMEA. A more customers move services to the cloud, IPv4 addresses tend not to be so required as they once were.
IPv6 is the next version and has 340 undecillion available IP addresses! (That’s 2128)
The bad news is that IPv6 and IPv4 are incompatible, so hence why most people require IPv4 IPs still as most of the Internet hasn’t made the transition yet. M12 Solutions will shortly be providing IPv6 addresses and assigning /48 or /56 assignments as standard. That’s a lot. Some customers will continue to need to use IPv4 IPs for to maintain compatibility.
IP JUSTIFICATION FORM
An IP Justification Form needs to be completed via Docusign, and charges agreed where applicable for existing or new customers requiring more IPv4 addresses. Please speak to your account manager for this Form to be sent to you via Docusign. An example is linked in this article. The actual form needs to be completed by Docusign though.
NETWORK ADDRESS TRANSLATION (NAT)
The recommendation is for you to use NAT to share a public IP address with multiple services (port numbers). Most services and firewalls allow you to do this. There are some services such as HTTPS web servers that require their own IP address if you operate more than one HTTP server. You may also have to segregate an IP addresses into a 802.1Q VLAN for PCI compliance. The example in the table on page 1 against IP #3 shows that you can easily share 1 IP for 5 different services hosted on 3 servers.
- If you can clearly use NAT to share IP addresses with no impact to the service, then your case will be rejected.
- If your firewall does not support NAT (also known as SNAT or 1-to-many-NAT), then you are recommended to find a firewall that does support this technology as it’s wasteful to request so many IPs.
- If you are reserving IP addresses for use in 6 months’ time or longer, then your case will be rejected. You cannot stock-pile IPs. This is against RIPE NCC rules. You will need to complete a new IP request form at the time you require more IPs.
- If your immediate requirements permit you to operate on a /29 block, then your case will be rejected.
Please see the attached template for further information and possible applicable charges.
- Pricing is monthly and excludes VAT at the prevailing rate.
- Minimum term matches the connectivity.
- Charges are in addition to the cost of your connectivity.
- Broadband customers can only have one additional framed IPv4 block per line.
- Ethernet customers can have multiple IPv4 subnets, however the charges and allocation limit are based on the total sum of IPv4 blocks.
- Additional IP blocks are provided at the discretion of M12.
- Customers do not own the IPv4 blocks.
- IP address are statically assigned, but M12 may need to reassign customer’s IP allocations, but will take all reasonable measures to avoid disrupting the customer.
- IPv6 addresses will be rolled out late 2018, early 2019.