1. Will you be using a firewall with Network Address Translation (NAT)?

A firewall or similar means of restricting access to and from machines connected to an internal LAN that do not require globally routable IP addresses could allow the customer to use a RFC-1918 specified private network (see [RFC 1918] Y. Rekhter, B. Moskowitz, D. Karrenberg, G.J. de Groot, E. Lear, "Address Allocation for Private Internets").

If you use private addressing, the On-Site / Surfin America, LLC assigned /27 block of globally routable IP addresses may be used by the customer for the router, firewall, and public servers (E-Mail, WWW, FTP, etc.) which need to be reachable from the outside world. Many routers and Firewall/Proxy servers can use network address translation to allow client machines that need access to the outside, to do so transparently.

More information on Firewalls may be found in the Firewall Howto.

2. Do you have client machines that do not need a fixed IP address?

You might be able to use DHCP, a method of dynamically assigning IP addresses to hosts. If you have hosts that are not in use all the time, you can use DHCP to allocate addresses to those machines on a need basis. For further information, please take a look at some of the following:

• The DHCP FAQ
• RFC 1541 -- Dynamic Host Configuration Protocol
• RFC 1534 -- Interoperation Between DHCP and BOOTP
• RFC 1533 -- DHCP Options and BOOTP Vendor Extensions

3. Do you have an existing net block, either from another provider or from the ARIN directly?

Customers who have existing IP address blocks smaller than a /19 with previous providers or independently with the ARIN will be requested to re-number within the On-Site / Surfin America, LLC CIDR (Classless Internet Domain Routing) blocks.

Customers who have a block with a mask prefix of /19 or smaller (32 or more contiguous Class Cs) CIDR range should inform On-Site / Surfin America, LLC before line installation.

On-Site / Surfin America, LLC will not announce CIDR blocks longer than a /19 due to ISP Filter Policies which are designed to prevent an explosion of the global routing table. You can monitor the size of the global Internet routing table from the Routing Table History taken from the Weekly CIDR Report.

For more information, please see: CIDR FAQ - Explanation of CIDR notation and usage [RFC1518] Y. Rekhter, T. Li, An Architecture for IP Address Allocation with CIDR [RFC1817] CIDR and Classful Routing

 

Requesting more Address Space

 

If you will still need more IP addresses from On-Site / Surfin America, LLC, please ensure you meet the following requirements and provide answers to the relevant questions via email.

In order for On-Site / Surfin America, LLC to obtain more IP addresses from ARIN, we have to satisfy at least the following requirements:
 

1. inverse addressing in place for all current addresses
2. at least 80% usage of our current IP address allocation
3. effective and efficient use of existing allocation

 
On-Site / Surfin America, LLC follows the same guidelines before assigning more IP addresses to our customers.
 

1. Inverse DNS must be in place for existing hosts showing at least 80% utilization of current address block.

On-Site / Surfin America, LLC requires that you have inverse addressing in place for all of your hosts. Inverse addressing will not only make our network run smoother, but will help the performance on your line as well. Many ftp and web servers look for an inverse address for your host before allowing you to access them.

If you maintain your own DNS with On-Site / Surfin America, LLC acting as a "silent" secondary, please make sure that your tables are up to date. If On-Site / Surfin America, LLC acts as your primary DNS, make sure that you inform us of any additions or changes you make to the number of machines that are addressable via DNS.

For more information, please see RFC 1293
 

2. Hosts listed must respond to ping (ICMP Echo).

On-Site / Surfin America, LLC requires that you be using at least 80% of the IP addresses that are already allocated to you. This prevents people from unknowingly wasting IP addresses. On-Site / Surfin America, LLC defines using an address as being able to see that the machine connected to that address is alive. We do this by using the ping utility.
 

3. How many Internet accessible hosts do you have today; will you in the next 3 months; in the next year?

It is on these numbers that On-Site / Surfin America, LLC bases address assignments.

If you are requesting a new block of addresses for the purpose of creating two separate networks, we suggest that you subnet your existing block of IP addresses first, if this is possible. For some more information on subnetting, please refer to the following sources: 

• Subnetting Your Class C Address
• RFC 950 -- Internet Standard Subnetting Procedure
• RFC 1219 -- Suggested Procedure to assign Subnet addresses
• RFC 2050 -- Internet Registry IP Allocation Guidelines

All requests for network address assignment should be accompanied by a network map. On-Site / Surfin America, LLC will assign the appropriate size CIDR block to the customer based on this map. In making the assignment On-Site / Surfin America, LLC may suggest alternate means of network design to conserve address space based on the network map provided.

The network map will usually consist of a drawn representation of what your network looks like. The following should be shown on your network map:

The number of hosts and their placement relative to any routers, bridges, or filters/firewalls. Any existing and planned subnetting. Planned network segments should be clearly marked as "expansion areas". Do you use DHCP? where? Do you use Address Translation on your internal networks? where? Firewalls, especially proxy firewalls Dial-Up Ports (how many do you have?)

A simple diagram accounting for your presently assigned IP address space is essential. Every IP address currently allocated to you must be represented in some fashion.

Also represented on this map should be your future expansion plans. On-Site / Surfin America, LLC would like to know what you plan to do with your future allocations. We use this map to help determine the allocation we will give you now and reserve for your future use.

Some examples of wrong and right network maps are:

Wrong:

--router--+--Bob's office, 2 PCs, printer
|
Empty Cube--+--Sharon's cube. 486/66,
|
+--Networked printer. 

Wrong:

On-Site / Surfin America, LLC---router---our network

Right:

On-Site / Surfin America, LLC----router--+---Open network
|20 workstations running DHCP
|Web server, Mail server, News server, /28
|Planned expansion: 20 more hosts.
|
+---Dialin Pool, 12 lines, /28
|Planned expansion:    16 lines
|
|
|
Proxy Firewall
|
|
+---Private network, numbered out of 
10.0.0.0/8

Conclusion
 

After review of the network map and confirmation of your network utilization On-Site / Surfin America, LLC will consider making additional address assignments.

On-Site / Surfin America, LLC will provide the customer with as many addresses as needed to operate on the Internet. The customer is expected to utilize these addresses effectively and not simply based on convenience. All requests for a change in a customers IP allocation should be sent to NOC@surfnj.net with the necessary documentation as specified above.

 

References and Recommended Reading
 

• [RFC1517] R. Hinden, Applicability Statement for Implementation of Classless Inter-Domain Routing(CIDR)
• INTERNET-number-template - v 2.0 InterNIC
• SWIP-Template-1.4 - InterNIC Registration Services