> I think you should add a topic like 'Bandwidth reduction by compression
> techniques' because data replication won't be popular if it causes network
> congestion.
>
> Also, I consider that the manual configuration is a technical issue among
> others; I thought that the main problem to solve in the WG was, on the one
> hand, the copyright problem when pushing data, on the other hand, the
> right for the user to decide wether its accesses are cached or not
> (ethical problem). None of these topics is listed in the proposed charter
> whereas most of the discussions during the BOF concerned these problems.
>
>
> ----
> ivan.lovric@cnet.francetelecom.fr
> tél : (+33) 02 31 75 91 25
>
> ----------
> De : Scott Michel[SMTP:scottm@rush.aero.org]
> Répondre à : scottm@cs.uc.a.edu
> Date : jeudi 24 septembre 1998 00:10
> A : webrepl@cs.utk.edu
> Objet : Start of a proto-charter for wrec
>
> [wrec == Web REplication and Caching. I've started a proto-charter and
> invite discussion and suggestions. Don't be afraid to invite other
> mailing lists where this discussion should take place to add constructive
> remarks.]
>
>
> Web Replication and Caching Working Group (wrec)
>
>
> Last Modified: <continuously>
>
>
> Working Group Chairs:
> ---------------------
> Pain Sponge 1 (Scott Michel volunteers joyfully and cheerfully)
> Pain Sponge 2
>
>
> Applications Area Director(s):
> ------------------------------
>
> Keith Moore <moore@cs.utk.edu>
> Patrik Faltstrom <paf@swip.net>
>
>
> Applications Area Advisor:
> --------------------------
>
> None as yet... How 'bout Jim Gettys or Peter Danzig?
>
>
> Mailing Lists:
> --------------
>
> General Discussion: webrepl@cs.utk.edu
> To subscribe: webrepl-request@cs.utk.edu
> In body: subscribe webrepl
>
>
> Description of Working Group:
> -----------------------------
>
> The World Wide Web (WWW) infrastructure has a well-defined protocol
> interface
> between the web client/browser and web server. This infrastructure
> includes
> the use of proxies and proxy caches located in between the client and the
> server. While the benefits of proxies and proxy caches are not the subject
> of
> controversy, manual configuration is required to inform the web client of
> the
> proxy's presence, limiting voluntary adoption.
>
> Proxies and proxy caches perform more than simple client request
> interception
> and processing; they may also mirror content or perform request routing
> between structured collections of proxies. There is no "one size fits all"
> proxy structure and thus there is a need to define and develop an
> architecture
> for heterogenous proxy structures to internetwork.
>
> The goal of this working group is to define and specify solutions in the
> following areas:
>
> - Proxy architecture and requirements,
>
> - Proxy autodiscovery protocols and mechansims,
>
> - Security scenarios for proxies and proxy caches.
>
>
> Goals and Milestones
> --------------------
>
>
> Internet Drafts
> ---------------
>
>
> RFCs
> ---
>
> --
> Scott Michel scottm@aero.org
> Member of Technical Staff, CSRD 310/336-5034
> The Aerospace Corporation
>
>
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:25 MST