IP-Hosting Policy Specifics
Alberto Mujica
albertm at innerhost.com
Thu May 3 09:40:02 EDT 2001
Since technical reasons can be pretty specific I agree with the fact that
there should be a list of technical reasons to justify IP address
allocations and an escalation procedure to suggest new ones.
My main concern, would providing SSL to our customers be a sufficient
technical justification?
In theory, SSL can be provided with host names, but Windows 2000 and NT for
example allow binding of a certificate to only one IP Address.
Thanks,
Alberto Mujica
Database Administrator
MCDBA, MCSE, MCP+I, A+
albertm at innerhost.com
-----Original Message-----
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
303/824.2506 (Office)
720/840.5329 (Mobile)
jmacknik at inflow.com
More information about the Vwp
mailing list