|
||
ISP Integration GuideWe are very excited to have ISPs participate and provide P4P services either for field tests, on a long-term basis, or both. This guide provides an overview for what is required by an ISP to configure and provide P4P services. Before reading this guide, please be sure you are familiar with the P4P framework. Deploying a Portal ServerConfiguring the Portal ServerEach ISP installs the Portal Server and generates a configuration for their network. For information, see the Portal Server page for system requirements and links to supporting documentation including a configuration guide and example configurations. SecurityIt is important to note the Portal Server offers an administration interface that is used by our Portal Shell for managing configurations. By default, the administration interface operates over a different port (6672 by default). Thus, it is highly recommended that you block port 6672 (TCP and UDP) on the machine running the Portal Server except to trusted IP addresses. Portal Server DiscoveryOnce your Portal Server is configured and running, users will need to discover your Portal Server. As part of the standardization work in IETF's ALTO Working Group, a single discovery mechanism will be defined. In the meantime, the Yale team maintains a simple centralized directory service for ISP to users so they may lookup the Portal Server. Once your Portal Server is running please email the IP address and port number (please use our IANA-registered port number 6671 if at all possible) to p4p@cs.yale.edu P4P Framework |
