Wording of the Virtual Webhosting Standards Policy (fwd)

[Uchenna Ibekwe]

  I agree , I don't think that RAIN should be concerned with legalities of  what the addresses are used for , as long as they put to devices . It would only be important for internet documentation , not for domain documentation.
----- Original Message ----- 
From: "Lee Howard" <lhoward at UU.NET>
To: <ppml at arin.net>
Sent: Friday, April 06, 2001 5:09 PM
Subject: Wording of the Virtual Webhosting Standards Policy (fwd)


I think ARIN should avoid specifying what a Service Provider is or might
be.  What we're talking about is the maintainer who provides IP addresses
to another organization, or the organization providing web hosting.

-
Organizations providing web hosting services must document efficient
utilization of existing IPv4 assignments.  Where possible, name-based
virtual hosting should be provided using HTTP1.1-host headers.  If such
name-based virtual hosting is not possible, documentation explaining why
it is not possible should be provided in the application.
-

I think the justification should be in the form of:

Web Servers Using Name-Based Web Hosting
192.168.10.1 FOO.COM
BAR.COM
BAZ.COM
192.168.10.2 FOO.NET
BAR.NET
BAZ.NET
Web Servers Not Using Name-Based Web Hosting
192.168.11.1 FOOBAR.COM SSL-based page
192.168.11.2 FOOBAR.NET customer server doesn't support

Should this be moved to vwp at arin.net?

Lee

---------- Forwarded message ----------
Date: Fri, 6 Apr 2001 09:12:32 -0700 
From: Jill Kulpinski <Jill.Kulpinski at exodus.net>
To: "'ppml at arin.net'" <ppml at arin.net>
Cc: Jill Kulpinski <Jill.Kulpinski at exodus.net>
Subject: Wording of the Virtual Webhosting Standards Policy 

Hello,  
After attending the ARIN conference this week, we have thought more about a
suggested wording for the Virtual Webhosting Policy.  This would be a change
to what is proposed.
It reads as follows:

When a Service Provider submits a request for public IPv4 address space,
ARIN or the upstream provider will review the requesting organization's
application and justification information to confirm they investigated the
use of HTTP1.1-host header (name-based) virtual hosting or other efficient
methodologies whenever and wherever possible.  If there is reason why
HTTP1.1 host-header (name-based) virtual hosting cannot be utilized,
appropriate documentation explaining the technical justification, must be
supplied.  Specific description of sufficient documentation is to be
determined by ARIN or the upstream provider.
Definitions:
Service Provider:  Any provider of products or services via
the internet
Efficient methodology:  any technology or protocol allowing
not more than one public IPv4 address per device, connected to
the internet directly.


Please make any comments as soon as possible.  There really needs to be a
change here regarding this policy, and it would be very frustrating to have
it continue to be 'suspended' for any greater length of time.
Thanks very much,
Jill