Wording of the Virtual Webhosting Standards Policy (fwd)

sigma at pair.com sigma at pair.com
Mon Apr 9 13:20:59 EDT 2001

If you use "technically compelling" wording, then you're back to where we
were early last year, when the policy was vigorously protested.  Downstream
allocators will regard that as a blanket excuse to deny space to their
customers, regardless of how ARIN chooses to interpret it for their own

It seemed at the meeting that the intent of requiring any reason at all was
so that ARIN could gather data for future use - not to restrict allocation.
This policy was supposed to be scaled back to a recommendation.


----- Forwarded message from David R Huberman -----

>The consensus that I gleaned at the recent ARIN open public policy meeting
>clearly agreed that a fairly strict policy is supported by the community.
>The burden to conserve address space is undeniably placed on the
>ISP. Those providers who require using IP-based hosting will need to
>explain themselves in some technically compelling manner.

And that's the point of the language I attempted to craft: any technically
compelling reason must be sufficient for ARIN to accept the address
utilization. ARIN cannot just blithely state that "here are certain
technical exceptions - do you fit one of them?"

The lack of specificity in my policy statement affords ARIN staff the
necessary flexibility in determining the needs and goals of the requesting
provider - a situation in which everyone wins, in my opinion.

Again, my policy proposal:

> In the interests of IPv4 address conservation, ARIN strongly encourages
> the use of name-based virtual hosting utilizing HTTP 1.1-host headers.
> ISPs providing web hosting services who are unable to implement name-based
> virtual hosting must provide technically compelling documentation which
> clearly demonstrates efficient utilization of their previous IPv4
> assignments.


| Global Crossing IP Engineering |
| Manager, Global IP Addressing  |
|   TEL: (908) 720-6182          |
|   FAX: (703) 464-0802          |

----- End of forwarded message from David R Huberman -----

More information about the ARIN-PPML mailing list