IP-Hosting Policy Specifics
John.Sweeting at teleglobe.com
Thu May 3 08:54:15 EDT 2001
My understanding is that there is no "list" that everyone agrees on and that
is why this policy is being put in place to collect the different "technical
justifications" that people believe exist. It should then be easier to
determine alternatives to these reasons while at the same time allowing
businesses to remain competitive while dealing with their "technical"
challenges. One possible outcome of this policy is a "list" will be put
together that everyone can agree on; this is the way that was decided on to
come up with the "list".
From: Jim Macknik [mailto:jmacknik at inflow.com]
Sent: Thursday, May 03, 2001 8:11 AM
To: 'vwp at arin.net'
Subject: IP-Hosting Policy Specifics
I really think we need ARIN to really lay down what "technical
justifications" there are for requesting IP space for IP-based hosting. This
request has appeared many times on this discussion list, but the only answer
I have seen to date indicates that ARIN requires "technical justification;"
this is a little too vague for businesses that depend on IP space, and the
customers which they support.
Is there a definitive list of justifiable reasoning behind IP-based hosting.
If there is not, then there is no way that anyone offering any IP space to
their customers could be sure they are requesting the right information from
their customers. This could conceivably cause them to lose their ability to
do business if ARIN indicates they don't believe that organization is
providing proper justification.
Is there any way we can come up with a list of justifiable reasons to use
IP-based hosting? If so, can we then also come up with an escalation
procedure for requesting additions to the list as technology and standard
practices change? If we had these in place, then companies offering ISP
services could follow, to the letter, exactly what ARIN needs for them to be
compliant. They would also have an opportunity to argue a case for alternate
technical reasons for IP space.
-= Mack =-
James M. Macknik
Manager, Systems Engineering
2401 15th St. Suite 200
Denver, CO 80202
jmacknik at inflow.com
More information about the Vwp