Project plan

Web Cache, DESIRE II

Project name	DESIRE II, web cache
Project leader	Ingrid Melve
Start date	01 July 1998	Date, plan	07 July 1998
End date	30 June 2000	Project number	RE4004

WP4 Caching

validating new technology for web caching and implementation of services

WP5 Demonstration and Dissemination

encouraging the use of DESIRE II results by involving external user groups, providing workshops and documentation

4.7 Administration

Tasks:

• web info
• reporting

Deployment WP5

Two workshops aimed at Internet Service Providers will pass on knowledge gained in WP4 of the benefits of caching and how to set it up.

Partners:

• TERENA
• UNINETT
• SURFnet

4.1 Extending mesh

Extending the caching mesh established in DESIRe to the European level. This will be achieved by the provision of workshops for the cache coordinators in Internet Service Providers, information on cache meshes and sharing experiences of providing caching as an operational service.

Responsible partner: SURFnet

Tasks:

• system management UNINETT 1.10.1998 - 1.5.1999
• investigate Internet Exchange point proxy SURFnet 1.1.1999 - 1.1.2000
• distributed gigaPOP cache mesh SURFnet ongoing
• liaison with TF-CACHE UNINETT, SURFnet ongoing

4.2 General deployment

Increasing the general deployment of caching within the national networks. Again this will mainly rely on the encouragement of network service providers and providing support with advice, information and, where necessary, the direct support of personnel. Responsible partner: UNINETT.

Tasks:

• cache appliance (part of SamsonII project, and NetCache license) UNINETT 1.11.1998
• updating web information UNINETT ongoing

4.3 workshops

Responsible party: TERENA

Tasks:

• develop program (peer review by TF-CACHE)
• arranging workshops Jan'99/Jan'2000
• reporting from workshop

Workshops will have the program peer reviewed by TF-CACHE, after being developed by the DESIRE cache team. Co-location with RIPE meetings.

Development WP4

Partners:

• UNINETT
• SURFnet

Work in WP4 will use the caching mesh already established in Norway and the Netherlands both as a test bed for improved caching techniques and as the basis for an extended caching mesh covering the European research networks and involving commercial Internet Service Providers.

4.4 Mesh auto configuration

Reducing the amount of (error-prone) manual configuration that is required to establish a functioning caching mesh.

• developing methods to automatically control web traffic routing
• determine optimal configurations
• automatically configure clients
• reduce the manual intervention required to set up and maintain a web cache

Responsible partner: UNINETT

Tasks:

• sibling killing scripts (TF-CACHE, with Andreas Papst) UNINETT
• investigate and test transparent caching SURFnet, UNINETT
  • redirection
  • L4 switching
• load balancing SURFnet
• service discovery SURFnet, UNINETT 1.1.1999 - 1.7.1999
• info, web pages SURFnet, UNINETT ongoing
• query routing SURFnet, UNINETT ongoing
  • WCCP
  • CARP

4.5 Inter cache communication

Investigating techniques to increase the functionality and performance of the protocols which interconnect caching servers.

• improvements in the communication between caching servers
• investigate multicast use
• persistent protocols
• new protocols and protocol extensions

Responsible partner: SURFnet

Tasks:

• Cache Digest 1.7.1998 - 1.7.1999
  • beta testing SURFnet - 1.10.1998
  • deployment SURFnet, UNINETT
• technology watch protocolsSURFnet ongoing
• follow TF-CACHE projects: ASbased routing and BestPath UNINETT 1.9.1998 - 1.4.1999
• clustering vs loosely coupled caches
• URN/query routing Bristol (check info)

4.6 testing software and hardware

Responsible partner: SURFnet

Tasks:

• documenting test criteria SURFnet, UNINETT - 1.10.1998
• follow benchmarking efforts UNINETT, SURFnet 1.9.1998 - 1.1.1999
• statistics, technology watch UNINETT ongoing
  • DePStat package (?)
  • Calamaris C++
• Squid v1.2,beta SURFnet until stable release/RSN
• testing emerging commercial products
  • Cisco Cache Engine UNINETT, SURFnet - 1.1.1999
  • Novell's borderware SURFnet 1.1.1999
  • NetCache
    • C630 (production run) UNINETT ongoing
    • C230 SURFnet 1.9.1998
  • CacheFlow? UNINETT 1.10.1998 - 1.1.1999
  • Inktomi Traffic Server (?) SURFnet - 1.3.1999

Administrivia

• Gantt chart
• Budget

We will be using the same email address as for the first part of DESIRE cache-desire@uninett.no

Budget

manhours, money, travel, total (public/private??)

Partner	Manhours
TERENA	???
SURFnet	???
UNINETT	1950

meetings

Date	Place/event	Theme
3/9 Sept 1998	TNC, Dresden (TF-CACHE)	First cache meeting
Dec98 / Jan99	before D4.1	Finalizing D4.1 Video conference, if possible
Summer 1999	TNC/NORDUnet99, Lund	Planning year 2, summing up year 1

Contact persons

Deliverables

ID	Month	Type	Title
D4.1	1.2.1999	RE	Review of new caching technology and opportunities
D4.2	1.1.2000	RE	Report on cache mesh configuration

Milestones

Month

ID	Title
M4.1	July 1999	Overview of inter cache communication
N4.1.1	May 1999	Web pages on proxy management
N4.2.1	November 1998	Web pages on cache appliance in SamsonII (UNINETT)
M4.3.1	January 1999	Workshop on web caching, for network administrators
M4.5.3.1	January 2000	Workshop on web caching, for network administrators
N4.4.1	May 1999	Web pages on auto configuration, sibling killing
N4.4.2	July 1999	Web pages on service discovery
N4.4.3	January 1999	Web pages on load balancing
N4.4.4	February 1999	Web pages on transparent caching
N4.5.1	October 1998	Cache Digest beta testing results
N4.5.2	April 1999	Results from application level routing in TF-CACHE available
N4.5.3	??????	URN resolution/ subject based routing
N4.6.1	October 1998	Documenting test criteria
N4.6.2	January 1999	Web pages on benchmarking
N4.6.3	October 1998	Web pages on commercial proxy software
M4.2	July 1999	Guidelines for auto configuration