[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00

INTERNET-DRAFT                                                 Joe Touch
WREC Working Group                                                   ISI
draft-ietf-wrec-res-00.txt                                     March 22, 1999
                                                 Expires: Sept. 22, 1999

             Web Caching and Replication -- Research Issues

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026 except that the right to
   produce derivative works is not granted.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

NOTE [Ed. - included in the I-D only]

   This is a working document. Not all sections are complete, or will
   necessarily be included in the final drafts. The editor and
   contributors of individual sections should not be taken as endorsing
   any of the solutions proposed here.

   Contributors of new items or items listed but lacking contacts are
   encouraged to send the template in the Appendix to the editor of this
   document (touch@isi.edu).

   Send comments on individual sections to the contact of that section,
   and CC touch@isi.edu, please.

Abstract

   This document summarizes open research issues in the support
   distributed caching and replication of web objects.  The potential
   solutions and mechanisms described are preliminary. This document



Expires Sept. 22, 1999                                          [Page 1]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   does not endorse the suitability of these mechanisms for use in the
   Internet, or in private networks. This document focuses on the
   research issues, and mentions candidate solutions only in the context
   of these issues.

   This document is a product of the IETF Web Caching and Replication
   (WREC) WG.  Comments are solicited and should be addressed to the
   author.

Table of Contents

   ??


1.  Introduction


   This document summarizes the research issues of web caching and
   replication. It focuses on issues whose solutions are either unknown
   or are under current development, and not yet ready for standardiza-
   tion. This document is intended to define the unsolved or incom-
   pletely solved issues, to give the community a uniform basis for the
   development of mechanisms to address these issues in the future.

   The principle of this document is to focus on the research issues
   themselves, rather than to focus on candidate solutions in particu-
   lar. Solutions will be described only insofar as they can be shown to
   address a definite issue.

   The document is organized as follows:

       Background:             common background for the discussions

       Template description:   defines a common template format
                               for the presentation of the issues

       Research Issues:        a list of the research issues,
                               in the common template format

                               issues are presented in arbitrary order
                               [Ed. - unless we find a better order]


2.  Background


   (to be completed)




Expires Sept. 22, 1999                                          [Page 2]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


3.  Template Description


   Each item in this section will consist of the following template:

           2.3.1. Name:
           2.3.1.1. Definition:
           2.3.1.2. Goal:
           2.3.1.3. Layers:
           2.3.1.3. Indications:
           2.3.1.4. Contraindications:
           2.3.1.5. Components:
           2.3.1.6. Proposed solutions:
           2.3.1.7. Security Issues:
           2.3.1.8. Contact:

   The following is a discussion of the component sections:


3.1.  Name

   The name is a brief label suitable to uniquely identify the issue in
   other text discussions. It should be brief enough to use repeatedly
   in text, or include a suitable acronym if not. The words described
   must be in common use, or as defined in the web caching and replica-
   tions taxonomy [WREC-TAX]. The name should not be longer than five
   (5) simple words, and compound words and adjectives should be used
   sparingly.

3.2.  Definition

   The definition is a terse description of the issue, suitable to
   uniquely identify the key features of the issue. It should be
   minimal, providing only necessary and sufficient terms to identify
   the issue. The definition should refer to published work, where pos-
   sible, providing additional information.

3.3.  Goal

   The goal is a terse description of the reason for seeking a solution
   to the issue, in terms of objectively measurable gains. The gains, if
   not manifest, should also be justified.

3.4.  Layers

   This item describes the layer at which the issue is predominant. It
   must be a subset of only the following terms: LINK, NETWORK, TRAN-
   SPORT, MIDDLEWARE, and APPLICATION. Link, network, transport, and



Expires Sept. 22, 1999                                          [Page 3]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   application are as commonly referred to in the ISO standard reference
   model. Middleware is hereby defined as "common layered services
   between the traditional application and transport layers", i.e., the
   sum of services provided by the traditional ISO session and presenta-
   tion layers, or anything else considered below the application, but
   above the transport layers.

3.5.  Indications

   This item specifies the conditions where solutions to the issue are
   of significant, measurable benefit, vs. not addressing the issue. The
   specification should be terse, and necessary and sufficient.  The
   benefits should not depend on a particular solution, but rather apply
   most generally to any viable solution to the issue.

3.6.  Contraindications

   This item specifies the conditions where solutions to the issue are
   if significant, measurable detriment, vs. not addressing the issue.
   The description is subject to the same qualifications as 'Indica-
   tions'.

3.7.  Components:

   This item is a brief description of the key components of the issue.
   The components may be subordinate issues described elsewhere in this
   document, or key mechanisms required to address the issue. The com-
   ponent issues should be necessary and sufficient.

3.8.  Proposed solutions:

   This item is a brief description of candidate solutions. It should be
   sufficient to indicate which solutions there are, and to define their
   important aspects only. This section is not intended to replace a
   published reference for a solution, and should not itself be suffi-
   cient as a reference for a solution. It should only describe what the
   solutions are, and how they differ.

3.9.  Security Issues:

   This item should address the unique security considerations of the
   issue only. It should be limited to security issues that necessarily
   occur as a result of any solution to the issue, rather than address-
   ing the security of any particular proposed solution.

3.10.  Contact:

   The submitter must provide a contact name, address, and e-mail, for



Expires Sept. 22, 1999                                          [Page 4]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   feedback during the revision process.

   [Ed. - to be decided whether these names will be co-authors, or also
   listed as section authors, rather than just contacts]


4.  Research Issues


The following is a preliminary (alphabetical) list of issues and con-
tacts.  If a contact is not listed, we are looking for volunteers :-).

------------------------------------------------------------

    Client to Replica Communication
        ?

    Common Policy Management
        ?

    Common Security
        ?

    Inter-replica communication
        Demand Driven Acceleration Mirror Replication
        [CODA] CODA
        ?

    Object distribution
        Leandro Navarro's Object Distribution Network
        Leandro Navarro, leandro@ac.upc.es

    Object selection
        Leandro Navarro's Object Routing Network
        SONAR [SONAR] [I2-DSI]
        Internet-Draft draft-moore-sonar-03.txt, Work in progress
        LSAM / REF
        ?

    Multicast
        LSAM's mcast groups
        Joe Touch, touch@isi.edu

    Multimedia
        ?

    Priorities / Differentiated Service
        LSAM's prioritized service



Expires Sept. 22, 1999                                          [Page 5]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


        Lars Eggert, larse@isi.edu

    Push (unsolicited response)
        LSAM, LOWLAT
        Ivan Lovric (ivan.lovric@cnet.francetelecom.fr)
                cache pre-filling extensions to ICP
        ?

    Routing
        Leandro Navarro's (leandro@ac.upc.es) Object Routing Network

    Topology
        Leandro Navarro's (leandro@ac.upc.es) Object Topology Network
        topology-d (katia@isi.edu)

------------------------------------------------------------

[Ed. - Placeholder]


4.1.  Name: (placeholder)


4.1.1.  Definition:

   (REQUIRED - even if preliminary -- separate paragraphs with single
   blank lines)

4.1.2.  Goal:

   (to be completed)

4.1.3.  Components:

   (to be completed)

4.1.4.  Proposed solutions:

   (to be completed)

4.1.5.  Security Issues:

   (to be completed)

4.1.6.  Contact:

   (REQUIRED)




Expires Sept. 22, 1999                                          [Page 6]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   (PUT REFERENCES HERE, MANUALLY NUMBERED)



5.  Security Considerations

   Security considerations are addressed in the individual discussions
   of each research issue.

   [Ed. - this section should have an additional summary of the main
   security considerations, i.e., to indicate the predominant issues. As
   such, it should be updated later.]


6.  Acknowledgements


   [Ed. - to be completed later.]


7.  References



   [WWW] Berners-Lee, T., et al., "The World-Wide Web," Communications
       of the ACM, V37, Aug. 1994, pp. 76-82.

   [TCP] Postel, Jon, "Transmission Control Protocol," Network Working
       Group RFC-793/STD-7, ISI, Sept. 1981.

   [CODA] Carnegie Melon University. Coda Overview and Background.
       Available from
       http://www.cs.cmu.edu/afs/cs.cmu.edu/project/coda/Web/docs-
       coda.html
          [Ed. - we need an archival source for this reference]

   [SONAR] Moore, K., Cox, J., Green, S. "SONAR - A Network Proximity
       Service," (work in progress).

   [I2-DSI] Beck, M., Moore, T., "The Internet 2 Distributed Storage
       Infrastructure Project: An Architecture for Internet Content
       Channels," http://www.cs.utk.edu/~mbeck/i2-dsi-channels.html
          [Ed. - we need an archival source for this reference]

   [POLICY] IETF.  Policy Framework (policy) working group.
       http://www.ietf.org/html.charters/policy-charter.html
          [Ed. - is only the output of a WG is 'citeable'?]




Expires Sept. 22, 1999                                          [Page 7]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   [LDAP] Wahl, M., Howes, T., Kille, S., "Lightweight Directory Access
       Protocol (v3)".  RFC-2551, Dec. 1997.

   [NDS] Novell Inc.  Novell Directory Services (NDS).
       http://www.novell.com/catalog/qr/sne14310.html
          [Ed. - we need an archival source for this reference]

   [BORDER] Novell, Inc. BorderManager FastCache Services.
       http://www.novell.com/catalog/qr/sne34192.html
          [Ed. - we need an archival source for this reference]

   [NRS] Novell Inc.  Novell Replication Services (NRS).
       http://www.novell.com/catalog/qr/sne24120.html
          [Ed. - we need an archival source for this reference]

   [X509] IETF. Public-Key Infrastructure (X.509)(pkix) working group.
       Available from http://www.ietf.org/html.charters/pkix-
       charter.html
          [Ed. - is only the output of a WG is 'citeable'?]

   [SSL] A. Frier, P. Karlton, and P. Kocher, "The SSL 3.0 Protocol",
       Netscape Communications Corp., Nov 18, 1996.
          [Ed. - is there a tech report number??]

   [IPSEC] IETF. IP Security Protocol (ipsec) working group.
       http://www.ietf.org/html.charters/ipsec-charter.html
          [Ed. - is only the output of a WG is 'citeable'?]

   [WREC-TAX] Melve, I., ??, "(WREC Taxonomy Document)," (work in pro-
       gress).

Author's Address

   Joe Touch
   University of Southern California/Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292-6695
   USA
   Phone: +1 310-822-1511 x151
   Fax:   +1 310-823-6714
   URL:   http://www.isi.edu/touch
   Email: touch@isi.edu


8.  Appendix: Note to contributors (in I-D only)


   Contributors of new items or items listed but lacking contacts are



Expires Sept. 22, 1999                                          [Page 8]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


   encouraged to send the following template, filled-in, to
   touch@isi.edu. Send comments on individual sections to the contact of
   that section, and CC touch@isi.edu, please.

   Some recommendations:
           Entries should focus on the issue, rather particular solutions.

           Descriptions should be general, and avoid solution-specific
           constraints.

           Entries should be kept as brief as possible.

           Entries must be in __plain text__ (no formatting),
           with blank lines separating paragraphs.

           Entries should include their own references. See the
           suffix of this document for samples. Note that only
           appropriate references, in the proper form, should
           be included - see RFC2026.

   ------------------------------------------------------------
   Name:                   short name (3-5 words)
   Definition:             define the issue
   Goal:                   define the reason to solve the issue
   Layers:                 specify which layers the issue resides
   Indications:            state conditions where issue solutions help
   Contraindications:      state conditions where issue solutions hurt
   Components:             define the key aspects of the issue
   Proposed solutions:     summarize candidate solutions
   Security Issues:        address the security considerations
   Contact:                contact name and e-mail for this section
   ------------------------------------------------------------

   Feel free to submit a placeholder with the following
   fields completed:

           Name
           Definition (preliminary)
           Layers
           Contact

   If there are multiple submitters for a section, or if there
   is overlap, we will coordinate among the submitters to collaborate
   on the section.

   The following nroff source template should used for contributions.
   Remember to edit out the Internet Draft page headers and footers.




Expires Sept. 22, 1999                                          [Page 9]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


------------------------------ cut here ------------------------------
.in 0
.NH 2
Name: (REQUIRED - short name, 3-5 words)
.XS
(copy short name here)
.XE
.LP
.in 0
.NH 3
Definition:
.LP
.in 3
(REQUIRED - even if preliminary -- separate paragraphs with single blank lines)
.in 0
.NH 3
Goal:
.LP
.in 3
(to be completed)
.in 0
.NH 3
Layers:
.LP
.in 3
(REQUIRED: - one of "link, network, transport, middleware, application")
.in 0
.NH 3
Indications:
.LP
.in 3
(to be completed)
.in 0
.NH 3
Contraindications:
.LP
.in 3
(to be completed)
.in 0
.NH 3
Components:
.LP
.in 3
(to be completed)
.in 0
.NH 3
Proposed solutions:
.LP



Expires Sept. 22, 1999                                         [Page 10]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999


.in 3
(to be completed)
.in 0
.NH 3
Security Issues:
.LP
.in 3
(to be completed)
.in 0
.NH 3
Contact:
.LP
.in 3
(REQUIRED)

(PUT REFERENCES HERE, MANUALLY NUMBERED)
------------------------------ cut here ------------------------------


































Expires Sept. 22, 1999                                         [Page 11]


Touch            Web Cach. and Repl. -- Research Issues   March 22, 1999





















































Expires Sept. 22, 1999                                         [Page 12]


Table of Contents



Introduction ......................................................    2
Background ........................................................    2
Template Description ..............................................    3
Research Issues ...................................................    5
(placeholder) .....................................................    6
Security Considerations ...........................................    7
Acknowledgements ..................................................    7
References ........................................................    7
Appendix: Note to contributors (in I-D only) ......................    8



































Expires Sept. 22, 1999                                          [Page 1]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/