Hi At 10:51 17-11-1999 +0100, Nurani Nimpuno wrote:
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.
IMO prohibiting all use of public IP address for virtual webhosting solutions its going to be a step to far for now, since some of those addresses are used in SSL certificates. Maybe if we separate common V W hosting from Secure Web Hosting we can apply diferent policies. For example: Current Special verification Methods can be applyed for Secure Web Hosting address space and analised separatly, while the use of HTTP1.1 is promoted. Pedro Goncalves Telepac - Comunicações Interactivas