At a glance
- Provide: how many IPs, what will use them, why they need public addressing, and why private or shared addressing will not work.
- Does not count: convenience, past practice, an application name, or a block size request without supporting technical need.
- Thresholds: 50% of usable addresses planned for the requested block, 80% of usable addresses in use across retained existing blocks.
When a request is required
A Public IP Request is required when your site's total would exceed 16 public IP addresses. A /27 or larger block always exceeds that limit.
Every address in a Bigleaf-provided block counts toward the 16-address limit, usable or not. BYOIP address space does not count.
Your Bigleaf Channel Manager or Sales Engineer can provide the IP Justification (IPJ) Form. You can also download the LAN network form from the Attachments list at the bottom of this article. If you need a LAN route, the LAN route form is in the same list.
Every request is reviewed as submitted. Approval is not guaranteed.
What to provide
For each category of use, provide:
- How many IP addresses you need
- What equipment, applications, or services will use them
- Why those resources require public IP addresses
- Why private or shared addressing cannot meet the requirement
Describe your actual infrastructure and intended configuration, not only the name of an application.
A technical need is a requirement that private or shared addressing cannot meet. It can come from a protocol or service, or be imposed by a contract, standard, or regulation. Identify the specific requirement and explain why public addressing is necessary.
What a complete request looks like
A good justification names the actual infrastructure and explains why it needs public addressing. List each category of use on its own row, with its quantity and its justification. The quantities and uses below are illustrative only and are not automatically approved.
Example request
| Quantity of IPs | Usage | Justification |
|---|---|---|
| 2 | Web servers | One public IP will be used by a load balancer in front of our customer portal and other web services that customers access from the internet. Multiple services will share that IP using separate hostnames or DNS records. A second public IP will be assigned to a system in our DMZ that hosts a partner API accessed externally by our partners. |
| 2 | We host email on site using two mail servers. Our public MX records list one server as primary and the other as secondary, so each server has its own public IP address. | |
| 2 | Remote-access VPN | One public IP will be assigned to the VPN concentrator used by employees connecting remotely. The second will be assigned to a separate VPN concentrator in our DMZ for contractors and vendors, where firewall policies restrict access to designated systems. |
What does not count as a technical need
None of these is sufficient by itself.
- Administrative convenience. Public addressing is preferred because it is simpler or easier to manage.
- Past practice. Public addressing is requested because the environment has always been configured that way.
- An application or service name. Naming what will use the address, without explaining why it requires a public address.
- A request for a specific block size without supporting technical need. Public IP blocks are requests and are subject to review rather than being automatically approved.
Utilization requirements
Every request must show that the address space will be used. Two rules apply. The first applies to every request. The second applies only if you keep existing Bigleaf blocks.
| Applies to | Required utilization |
|---|---|
| The block you are requesting | Planned usage must be at least 50% of the usable addresses in the requested block. |
| Existing blocks you are keeping | If you keep existing Bigleaf blocks and request more space, at least 80% of the usable addresses across those blocks together must be in use, and the request must show a technical need for more addresses. |
Show utilization with the same breakdown as the example request above: one row per use. For the requested block, quantities are planned usage. For existing blocks, they are addresses currently in use.
Comments
0 comments
Article is closed for comments.