IP assignment for virtual webhosting

Hi,

On Wed, 17 Nov 1999, Nurani Nimpuno wrote:

[snipp]
> OUR SUGGESTION
> 
> The RIPE NCC has followed the deployment of HTTP 1.1 closely over the past
> year. According to recent surveys, a vast majority of clients now support
> HTTP 1.1 (namebased HTTP requests). It is our belief that the majority of
> webserver applications support namebased webhosting as well.
> 
> In recent years we have seen a boom in the registration of second-level
> domains. This has led to a great demand for webhosting services. Using one
> IP address per domain uses an enormous amount of IP addresses. With HTTP
> 1.1 this is no longer necessary. We therefore suggest to promote namebased
> webhosting and to change the current policy so that IP addresses can no
> longer be assigned for IP-based webhosting.

we would very much welcome this.  We successfully run HTTP host header 
based hosting on all our mass virtual servers.  These are servers with 
mainly static content and some light cgi,php mysql usage.

Usage of IP Addresses for virtual hosting should be restricted to purposes
where this might be explicitly required for example for a SSL certificate
for a server.   But not for running massive hosting of "homepages".

The current policy seems to allow for a LIR to enter /32 for each virtual
server into the database. This is happening in a huge extent bloating up 
the ripe database.  Needles to say that most of this behaviour is propably
automated and we will see lots of duplicate person handles....

Greetings
Christian Kratzer
Toplink

-- 
TopLink Internet Services GmbH			ck at 171.2.195.in-addr.arpa
Christian Kratzer				http://www.toplink.net/
Phone: 	+49 7032 2701-0
Fax: 	+49 7032 2701-19	FreeBSD spoken here!