WEBDAV Working Group                                            J. Slein
Internet-Draft                                                     Xerox
Expires: January 23, March 10, 2004                                     J. Whitehead
                                                         U.C. Santa Cruz
                                                                J. Davis
                                                               CourseNet
                                                                G. Clemm
                                                                Rational
                                                                  C. Fay
                                                                 FileNet
                                                             J. Crawford
                                                                     IBM
                                                         J. Reschke, Ed.
                                                              greenbytes
                                                           July 25,
                                                      September 10, 2003

                  WebDAV Redirect Reference Resources
               draft-ietf-webdav-redirectref-protocol-03.txt
               draft-ietf-webdav-redirectref-protocol-04

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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.

   This Internet-Draft will expire on January 23, March 10, 2004.

Copyright Notice

   Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

   This is one of a pair of specifications that extend the WebDAV
   Distributed Authoring Protocol to enable clients to create new access
   paths to existing resources.  The two protocol extensions have very
   different characteristics that make them useful for different sorts
   of applications.

   The present specification defines redirect reference resources.  A redirect
   reference resource is a resource whose default response is an HTTP/1.1 HTTP/
   1.1 302 (Found) status code, redirecting the client to a different
   resource, the target resource.  A redirect reference makes it
   possible to access the target resource indirectly, through any URI
   mapped to the redirect reference resource.  There are no integrity
   guarantees associated with redirect reference resources.

   The related specification [B], defines bindings, and the BIND method
   for creating them.  Creating a new binding to a resource indirectly
   creates one or more new URIs mapped to that resource, which can then
   be used to access it.  Servers are required to insure the integrity
   of any bindings that they allow to be created.

   Distribution of this document is unlimited. Please send comments to
   the Distributed Authoring and Versioning (WebDAV) working group at
   w3c-dist-auth@w3.org [1], which may be joined by sending a message
   with subject "subscribe" to w3c-dist-auth-request@w3.org [2].

   Discussions of the WEBDAV working group are archived at URL: http://
   lists.w3.org/Archives/Public/w3c-dist-auth/.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   7   5
   2.   Notational Conventions . . . . . . . . . . . . . . . . . . .   9   7
   3.   Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  10   8
   4.   Overview of Redirect Reference Resources . . . . . . . . . .  11   9
   5.   Creating a Redirect Reference Resource . . . . . . . . . . .  12  10
   5.1  MKRESOURCE . . . . . . . . . . . . . . . . . . . . . . . . .  12  10
   5.2  Example: Creating a Redirect Reference Resource with
        MKRESOURCE . . . . . . . . . . . . . . . . . . . . . . . . .  13  11
   6.   Operations on Redirect Reference Resources . . . . . . . . .  15  13
   6.1  Example: GET on a Redirect Reference Resource  . . . . . . .  16  14
   6.2  Example: PUT on a Redirect Reference Resource with
        Apply-To-Redirect-Ref  . . . . . . . . . . . . . . . . . . .  16  14
   6.3  Example: PROPPATCH on a Redirect Reference Resource  . . . .  17  15
   7.   Operations on Collections That Contain Redirect Reference
        Resources  . . . . . . . . . . . . . . . . . . . . . . . . .  18  16
   7.1  MOVE and DELETE on Collections That Contain Redirect
        References . . . . . . . . . . . . . . . . . . . . . . . . .  18  16
   7.2  LOCK on a Collection That Contains Redirect References . . .  19  17
   7.3  Example: PROPFIND on a Collection with Redirect Reference
        Resources  . . . . . . . . . . . . . . . . . . . . . . . . .  19  17
   7.4  Example: PROPFIND with Apply-To-Redirect-Ref on a
        Collection with Redirect Reference Resources . . . . . . . .  20  18
   7.5  Example: COPY on a Collection That Contains a Redirect
        Reference Resource . . . . . . . . . . . . . . . . . . . . .  22  20
   7.6  Example: LOCK on a Collection That Contains a Redirect
        Reference Resource . . . . . . . . . . . . . . . . . . . . .  23  21
   8.   Operations on Targets of Redirect Reference Resources  . . .  26  24
   9.   Relative URIs in DAV:reftarget . . . . . . . . . . . . . . .  27  25
   9.1  Example: Resolving a Relative URI in a MKRESOURCE Request  .  27  25
   9.2  Example: Resolving a Relative URI in a Multi-Status
        Response . . . . . . . . . . . . . . . . . . . . . . . . . .  28  26
   10.  Redirect References to Collections . . . . . . . . . . . . .  30  28
   11.  Headers  . . . . . . . . . . . . . . . . . . . . . . . . . .  32  30
   11.1 Redirect-Ref Response Header . . . . . . . . . . . . . . . .  32  30
   11.2 Apply-To-Redirect-Ref Request Header . . . . . . . . . . . .  32  30
   12.  Properties . . . . . . . . . . . . . . . . . . . . . . . . .  33  31
   12.1 reftarget Property . . . . . . . . . . . . . . . . . . . . .  33  31
   12.2 location Pseudo-Property . . . . . . . . . . . . . . . . . .  33  31
   13.  XML Elements . . . . . . . . . . . . . . . . . . . . . . . .  34  32
   13.1 redirectref XML Element  . . . . . . . . . . . . . . . . . .  34  32
   14.  Extensions to the DAV:response XML Element for
        Multi-Status Responses . . . . . . . . . . . . . . . . . . .  35  33
   15.  Capability Discovery . . . . . . . . . . . . . . . . . . . .  36  34
   15.1 Example: Discovery of Support for Redirect Reference
        Resources  . . . . . . . . . . . . . . . . . . . . . . . . .  36  34
   16.  Security Considerations  . . . . . . . . . . . . . . . . . .  37  35
   16.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . .  37  35
   16.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . . .  37  35
   16.3 Redirect Reference Resources and Denial of Service . . . . .  37  35
   16.4 Revealing Private Locations  . . . . . . . . . . . . . . . .  37  35
   17.  Internationalization Considerations  . . . . . . . . . . . .  39  37
   18.  IANA Considerations  . . . . . . . . . . . . . . . . . . . .  40  38
   19.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . .  41  39
        Normative References . . . . . . . . . . . . . . . . . . . .  42
        Informative References . . . . . . . . . . . . . . . . . . .  43  40
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  44  40
   A.   Changes to the WebDAV Document Type Definition . . . . . . .  46  42
   B.   Change Log (to be removed by RFC Editor before
        publication) . . . . . . . . . . . . . . . . . . . . . . . . .  47  43
   B.1  Since draft-ietf-webdav-redirectref-protocol-02  . . . . . .  47  43
   B.2  Since draft-ietf-webdav-redirectref-protocol-03  . . . . . .  43
   C.   Resolved issues (to be removed by RFC Editor before
        publication) . . . . . . . . . . . . . . . . . . . . . .  48
   C.1  lc-11-pagination . .  44
   C.1  lc-07-bind . . . . . . . . . . . . . . . . . . . .  48
   C.2  lc-09-notational-after-introduction . . . . .  44
   C.2  lc-08-bind . . . . . . .  48
   C.3  lc-13-usually . . . . . . . . . . . . . . . . . .  44
   C.3  lc-34-bind . . . . .  48
   C.4  lc-16-insure . . . . . . . . . . . . . . . . . . . .  44
   C.4  lc-83-bind . . . .  48
   C.5  lc-17-location . . . . . . . . . . . . . . . . . . . . .  44
   C.5  lc-12-bind . .  49
   C.6  lc-21-bind . . . . . . . . . . . . . . . . . . . . . . .  45
   C.6  lc-35-bind . .  49
   C.7  lc-46-bind . . . . . . . . . . . . . . . . . . . . . . . .  45
   C.7  lc-01-body .  49
   C.8  lc-26-lang . . . . . . . . . . . . . . . . . . . . . . . .  45
   C.8  lc-14-bind .  49
   C.9  lc-03-mkresource-response-cacheability . . . . . . . . . . .  50
   C.10 lc-02-status-codes . . . . . . . . . . . . .  45
   C.9  lc-15-direct-ref . . . . . . . .  50
   C.11 lc-27-lang . . . . . . . . . . . . . .  46
   C.10 lc-39-no-reference-or-direct-resource  . . . . . . . . . . .  50
   C.12 lc-30-headers  46
   C.11 lc-40-direct . . . . . . . . . . . . . . . . . . . . . . .  50
   C.13 lc-32-ORDERPATCH .  46
   C.12 lc-45-apply-to-rr  . . . . . . . . . . . . . . . . . . . . .  51
   C.14 lc-51-repeat  47
   C.13 lc-01A-body  . . . . . . . . . . . . . . . . . . . . . . . .  51
   C.15 lc-59-depth  47
   C.14 lc-31-MKCOL  . . . . . . . . . . . . . . . . . . . . . . . .  51
   C.16 lc-65-lock  47
   C.15 lc-67-redirectref  . . . . . . . . . . . . . . . . . . . . .  47
   C.16 lc-54-s10  . . . .  51
   C.17 lc-66-depth . . . . . . . . . . . . . . . . . . . . .  48
   C.17 lc-78-directory  . . .  52
   C.18 lc-69-424 . . . . . . . . . . . . . . . . . . .  48
   C.18 lc-82-iana . . . . . .  52
   C.19 lc-68-lock . . . . . . . . . . . . . . . . . . .  48
   D.   Open issues (to be removed by RFC Editor before
        publication) . . . . . .  52
   C.20 lc-52-no-relative . . . . . . . . . . . . . . . . . .  49
   D.1  lc-85-301  . . .  53
   C.21 lc-64-reftarget . . . . . . . . . . . . . . . . . . . . . .  53
   C.22 lc-70-relative  49
   D.2  lc-38-not-hierarchical . . . . . . . . . . . . . . . . . . .  49
   D.3  lc-36-server . . . .  53
   C.23 lc-73-asciiart . . . . . . . . . . . . . . . . . . . .  49
   D.4  lc-33-forwarding . . .  53
   C.24 lc-77-webdav-applications . . . . . . . . . . . . . . . . .  54
   C.25 lc-10-title . .  49
   D.5  lc-56-notjusthttp  . . . . . . . . . . . . . . . . . . . . .  50
   D.6  lc-37-integrity  .  54
   C.26 lc-81-typo . . . . . . . . . . . . . . . . . . . . .  50
   D.7  3-terminology-redirectref  . . . .  54
   C.27 lc-18-resource-types . . . . . . . . . . . . .  50
   D.8  lc-43-webdav . . . . . . .  54
   C.28 lc-84-ext . . . . . . . . . . . . . . . . .  50
   D.9  lc-19-direct-ref . . . . . . . .  54
   D.   Open issues . . . . . . . . . . . . . .  51
   D.10 lc-04-standard-data-container  . . . . . . . . . .  56
   D.1  lc-85-301 . . . . .  51
   D.11 lc-05-standard-data-container  . . . . . . . . . . . . . . .  51
   D.12 lc-20-intro-mkresource . . . . .  56
   D.2  lc-07-bind . . . . . . . . . . . . . .  51
   D.13 lc-22-coll . . . . . . . . . . .  56
   D.3  lc-08-bind . . . . . . . . . . . . . .  52
   D.14 lc-25-atomic . . . . . . . . . . .  56
   D.4  lc-34-bind . . . . . . . . . . . . .  52
   D.15 lc-41-no-webdav  . . . . . . . . . . . .  56
   D.5  lc-35-bind . . . . . . . . . .  52
   D.16 lc-42-no-webdav  . . . . . . . . . . . . . . .  57
   D.6  lc-83-bind . . . . . . .  52
   D.17 lc-58-update . . . . . . . . . . . . . . . . . .  57
   D.7  lc-12-bind . . . . . .  53
   D.18 lc-23-body . . . . . . . . . . . . . . . . . . .  57
   D.8  lc-38-not-hierarchical . . . . . .  53
   D.19 lc-24-properties . . . . . . . . . . . . .  57
   D.9  lc-36-server . . . . . . . . .  53
   D.20 lc-47-207  . . . . . . . . . . . . . . .  58
   D.10 lc-33-forwarding . . . . . . . . . .  54
   D.21 lc-48-s6 . . . . . . . . . . . .  58
   D.11 lc-56-notjusthttp . . . . . . . . . . . . . .  54
   D.22 lc-28-lang . . . . . . .  58
   D.12 lc-01-body . . . . . . . . . . . . . . . . . .  55
   D.23 lc-29-lang . . . . . . .  58
   D.13 lc-37-integrity . . . . . . . . . . . . . . . . . .  55
   D.24 lc-49-put  . . . .  59
   D.14 lc-14-bind . . . . . . . . . . . . . . . . . . . . .  55
   D.25 lc-44-pseudo . . . .  59
   D.15 lc-15-direct-ref . . . . . . . . . . . . . . . . . . . .  55
   D.26 lc-61-pseudo . .  59
   D.16 lc-39-no-reference-or-direct-resource . . . . . . . . . . .  59
   D.17 lc-40-direct . . . . . . . . . . .  56
   D.27 lc-60-ex . . . . . . . . . . . . .  60
   D.18 lc-43-webdav . . . . . . . . . . . . .  56
   D.28 lc-62-oldclient  . . . . . . . . . . .  60
   D.19 lc-19-direct-ref . . . . . . . . . . .  56
   D.29 lc-63-move . . . . . . . . . . .  60
   D.20 lc-45-apply-to-rr . . . . . . . . . . . . . .  56
   D.30 lc-06-reftarget-relative . . . . . . .  61
   D.21 lc-04-standard-data-container . . . . . . . . . . .  57
   D.31 lc-57-noautoupdate . . . .  61
   D.22 lc-05-standard-data-container . . . . . . . . . . . . . . .  61
   D.23 lc-20-intro-mkresource . .  57
   D.32 lc-71-relative . . . . . . . . . . . . . . . . .  61
   D.24 lc-22-coll . . . . . .  57
   D.33 lc-53-s10  . . . . . . . . . . . . . . . . . . .  62
   D.25 lc-25-atomic . . . . . .  58
   D.34 lc-72-trailingslash  . . . . . . . . . . . . . . . . . .  62
   D.26 lc-41-no-webdav . .  58
   D.35 lc-50-blindredirect  . . . . . . . . . . . . . . . . . . . .  62
   D.27 lc-42-no-webdav  . . . . . . . . . . . . . . . . . . . . . .  62
   D.28 lc-58-update . . . . . . . . . . . . . . . . . . . . . . . .  63
   D.29 lc-01A-body  . . . . . . . . . . . . . . . . . . . . . . . .  63
   D.30 lc-23-body . . . . . . . . . . . . . . . . . . . . . . . . .  63
   D.31 lc-24-properties . . . . . . . . . . . . . . . . . . . . . .  64
   D.32 lc-47-207  . . . . . . . . . . . . . . . . . . . . . . . . .  64
   D.33 lc-48-s6 . . . . . . . . . . . . . . . . . . . . . . . . . .  64
   D.34 lc-28-lang . . . . . . . . . . . . . . . . . . . . . . . . .  65
   D.35 lc-29-lang . . . . . . . . .  58
   D.36 lc-74-terminology  . . . . . . . . . . . . . . . .  65
   D.36 lc-31-MKCOL . . . . .  59
   D.37 lc-75-ignore . . . . . . . . . . . . . . . . . . .  65
   D.37 lc-49-put . . . . .  59
   D.38 lc-76-location . . . . . . . . . . . . . . . . . . . .  65
   D.38 lc-44-pseudo . . .  59
   D.39 lc-79-accesscontrol  . . . . . . . . . . . . . . . . . . . .  59
   D.40 lc-80-i18n .  66
   D.39 lc-61-pseudo . . . . . . . . . . . . . . . . . . . . . . . .  66
   D.40 lc-60-ex  60
   D.41 lc-55-iana . . . . . . . . . . . . . . . . . . . . . . . . .  60
        Intellectual Property and Copyright Statements .  66
   D.41 lc-62-oldclient . . . . . . . . . . . . . . . . . . . . . .  67
   D.42 lc-63-move . . . . . . . . . . . . . . . . . . . . . . . . .  67
   D.43 lc-67-redirectref  . . . . . . . . . . . . . . . . . . . . .  67
   D.44 lc-06-reftarget-relative . . . . . . . . . . . . . . . . . .  67
   D.45 lc-57-noautoupdate . . . . . . . . . . . . . . . . . . . . .  68
   D.46 lc-71-relative . . . . . . . . . . . . . . . . . . . . . . .  68
   D.47 lc-53-s10  . . . . . . . . . . . . . . . . . . . . . . . . .  68
   D.48 lc-72-trailingslash  . . . . . . . . . . . . . . . . . . . .  69
   D.49 lc-54-s10  . . . . . . . . . . . . . . . . . . . . . . . . .  69
   D.50 lc-50-blindredirect  . . . . . . . . . . . . . . . . . . . .  69
   D.51 lc-74-terminology  . . . . . . . . . . . . . . . . . . . . .  70
   D.52 lc-75-ignore . . . . . . . . . . . . . . . . . . . . . . . .  70
   D.53 lc-76-location . . . . . . . . . . . . . . . . . . . . . . .  70
   D.54 lc-78-directory  . . . . . . . . . . . . . . . . . . . . . .  70
   D.55 lc-79-accesscontrol  . . . . . . . . . . . . . . . . . . . .  71
   D.56 lc-80-i18n . . . . . . . . . . . . . . . . . . . . . . . . .  71
   D.57 lc-55-iana . . . . . . . . . . . . . . . . . . . . . . . . .  71
   D.58 lc-82-iana . . . . . . . . . . . . . . . . . . . . . . . . .  71
        Intellectual Property and Copyright Statements . . . . . . .  72

1. Introduction

   This is one of a pair of specifications that extend the WebDAV
   Distributed Authoring Protocol to enable clients to create new access
   paths to existing resources.  This capability is useful for several
   reasons:

   URIs of WebDAV-compliant resources are hierarchical and correspond to
   a hierarchy of collections in resource space.  The WebDAV Distributed
   Authoring Protocol makes it possible to organize these resources into
   hierarchies, placing them into groupings, known as collections, which
   are more easily browsed and manipulated than a single flat
   collection. However, hierarchies require categorization decisions
   that locate resources at a single location in the hierarchy, a
   drawback when a resource has multiple valid categories. For example,
   in a hierarchy of vehicle descriptions containing collections for
   cars and boats, a description of a combination car/boat vehicle could
   belong in either collection. Ideally, the description should be
   accessible from both. Allowing clients to create new URIs that access
   the existing resource lets them put that resource into multiple
   collections.

   Hierarchies also make resource sharing more difficult, since
   resources that have utility across many collections are still forced
   into a single collection. For example, the mathematics department at
   one university might create a collection of information on fractals
   that contains bindings to some local resources, but also provides
   access to some resources at other universities.  For many reasons, it
   may be undesirable to make physical copies of the shared resources on
   the local server: to conserve disk space, to respect copyright
   constraints, or to make any changes in the shared resources visible
   automatically. Being able to create new access paths to existing
   resources in other collections or even on other servers is useful for
   this sort of case.

   The redirect reference resources defined here provide a mechanism for
   creating alternative access paths to existing resources.  A redirect
   reference resource is a resource in one collection whose purpose is
   to forward requests to another resource (its target), possibly in a
   different collection.  In this way, it allows clients to submit
   requests to the target resource from another collection.  It
   redirects most requests to the target resource using the HTTP 302
   (Found) status code, thereby providing a form of mediated access to
   the target resource.

   The companion specification [B], defines the BIND method, a different
   mechanism for allowing clients to create alternative access paths to
   existing WebDAV-compliant resources. The BIND method lets clients
   associate a new URI with an existing WebDAV resource.  This URI can
   then be used to submit requests to the resource.  Since URIs of
   WebDAV-compliant resources are hierarchical, and correspond to a
   hierarchy of collections in resource space, the BIND method also has
   the effect of adding the resource to a collection.  As new URIs are
   associated with the resource, it appears in additional collections.

   Redirect references and bindings have very different characteristics:

   A redirect reference is a resource, and so can have properties and a
   body of its own.  Properties of a redirect reference resource can
   contain such information as who created the reference, when, and why.
   Since redirect reference resources are implemented using HTTP 302
   responses, it generally takes two round trips to submit a request to
   the intended resource.  Servers are not required to enforce the
   integrity of redirect references.  Redirect references work equally
   well for local resources and for resources that reside on a different
   server from the reference.

   By contrast, a BIND request does not create a new resource, but
   simply makes available a new URI for submitting requests to an
   existing resource.  The new URI is indistinguishable from any other
   URI when submitting a request to a resource.  Only one round trip is
   needed to submit a request to the intended target.  Servers are
   required to enforce the integrity of the relationships between the
   new URIs and the resources associated with them.  Consequently, it
   may be very costly for servers to support BIND requests that cross
   server boundaries.

   The remainder of this document is structured as follows: Section 3
   defines terms that will be used throughout the specification.
   Section 4 provides an overview of redirect reference resources.
   Section 5 discusses how to create a redirect reference resource.
   Section 6 defines the semantics of existing methods when applied to
   redirect reference resources, and Section 7 discusses their semantics
   when applied to collections that contain redirect reference
   resources. Sections 8 through 10 discuss several other issues raised
   by the existence of redirect reference resources.  Sections 11
   through 14 define the new headers, properties, and XML elements
   required to support redirect reference resources.  Section 15
   discusses capability discovery.  Sections 16 through 18 present the
   security, internationalization, and IANA concerns raised by this
   specification. The remaining sections provide a variety of supporting
   information.

2. Notational Conventions

   Since this document describes a set of extensions to the WebDAV
   Distributed Authoring Protocol [RFC2518], itself an extension to the
   HTTP/1.1 protocol, the augmented BNF used here to describe protocol
   elements is exactly the same as described in Section 2.1 of
   [RFC2616]. Since this augmented BNF uses the basic production rules
   provided in Section 2.2 of [RFC2616], these rules apply to this
   document as well.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3. Terminology

   The terminology used here follows and extends that in the WebDAV
   Distributed Authoring Protocol specification [RFC2518]. Definitions
   of the terms resource, Uniform Resource Identifier (URI), and Uniform
   Resource Locator (URL) are provided in [RFC2396].

   Reference Resource

      A resource whose purpose is to forward requests to another
      resource.  Reference resources are an alternative mechanism to
      bindings (defined in [B]) for allowing clients to create multiple
      URIs that can be used to submit requests to the same resource.

   Redirect Reference Resource

      A resource that allows clients to forward requests to another
      resource using the HTTP 1.1 302 (Found) response mechanism.  The
      client is aware that this type of reference resource is mediating
      between it and the target resource.

   Direct Reference Resource

      Direct Reference Resources are out of scope for this
      specification, but are defined here for contrast with redirect
      reference resources.   A direct reference resource automatically
      forwards requests to another resource, in a way that is
      transparent to the client.

   Non-Reference Resource

      A resource that is not a reference to another resource.

   Target Resource

      The resource to which requests are forwarded by a reference
      resource.

4. Overview of Redirect Reference Resources

   For all operations submitted to a redirect reference resource, the
   default response is a 302 (Found), accompanied by the Redirect-Ref
   header (defined in Section 11.1 below) and the Location header set to
   the URI of the target resource.  With this information, the client
   can resubmit the request to the URI of the target resource.

   A redirect reference resource never automatically forwards requests
   to its target resource.  It is this characteristic that distinguishes
   redirect reference resource from direct reference resources and from
   bindings.  It is also what helps to insure that redirect reference
   resources will be simple to implement and that cross-server
   references will be possible.  If the redirect reference resource were
   required to forward requests automatically, the server would need
   proxy capabilities in order to support cross-server references.

   If the client is aware that it is operating on a redirect reference
   resource, it can resolve the reference by retrieving the reference
   resource's DAV:reftarget property (defined in Section 12.1 below),
   whose value contains the URI of the target resource.  It can then
   submit requests to the target resource.

   A redirect reference resource is a new type of resource. To
   distinguish redirect reference resources from non-reference
   resources, a new value of the DAV:resourcetype property (defined in
   [RFC2518]), DAV:redirectref, is defined in Section 13.1 below.

   Since a redirect reference resource is a resource, it can have its
   own properties and body, and methods can be applied to the reference
   resource as well as to its target resource.  The
   Apply-To-Redirect-Ref request header (defined in Section 11.2 below)
   is provided so that referencing-aware clients can control whether an
   operation is applied to the redirect reference resource or to its
   target resource.  The Apply-To-Redirect-Ref header can be used with
   most requests to redirect reference resources.  This header is
   particularly useful with PROPFIND, to retrieve the reference
   resource's own properties.

5. Creating a Redirect Reference Resource

   The MKRESOURCE method is used to create new redirect reference
   resources.  As defined in Section 5.1, MKRESOURCE can be used to
   create a resource of any type other than standard data containers and
   collections.  In order to create a redirect reference resource using
   MKRESOURCE, the values of two properties must be set in the body of
   the MKRESOURCE request.  The value of DAV:resourcetype MUST be set to
   DAV:redirectref, a new value of DAV:resourcetype defined in Section
   13.1. The value of DAV:reftarget MUST be set to the URI of the target
   resource.

   Used in this way, the MKRESOURCE method creates a redirect reference
   resource whose target is identified by the DAV:reftarget property.

5.1 MKRESOURCE

   The MKRESOURCE method requests the creation of a resource and
   initialization of its properties.  It allows resources other than
   standard data containers and collections to be created and their
   properties initialized in one atomic operation.

   Preconditions:

      A resource MUST NOT exist at the Request-URI.

   Request Marshalling:

      The location of the new resource to be created is specified by the
      Request-URI.

      The request body of the MKRESOURCE method MUST consist of the
      DAV:propertyupdate XML element defined in Section 12.13 of
      [RFC2518].

   Postconditions:

      If the response status code is 201, a new resource exists at the
      Request-URI.

      The body of the new resource is empty.

      The properties of the new resource are as specified by the
      DAV:propertyupdate request body, using PROPPATCH semantics. If the
      DAV:propertyupdate does not specify a DAV:resourcetype, the
      resource will be a standard data container.

      If the response status code is not 201, then a new resource is not
      created at the Request-URI, and any existing resource at the
      Request-URI is unaffected.

   Response Marshalling:

      Responses from a MKRESOURCE request MUST NOT be cached, as
      MKRESOURCE has non-idempotent semantics.

      The following status codes can be expected in responses to
      MKRESOURCE:

      201 (Created): The new resource was successfully created.

      207 (Multi-Status): This response is generated if an error was
      encountered while initializing the properties of the resource, in
      which case the response is as defined in Section 8.2.1 of
      [RFC2518].

      403 (Forbidden): The server does not allow the creation of the
      requested resource type at the requested location, or the parent
      collection of the Request-URI exists but cannot accept members.

      409 (Conflict): A resource cannot be created at the Request-URI
      because the parent collection for the resource does not exist, or
      because there is already a resource at that request-URL.

      423 (Locked): The Request-URI is locked, and the lock token was
      not passed with the request.

      507 (Insufficient Storage): The server does not have sufficient
      space to record the state of the resource.

5.2 Example: Creating a Redirect Reference Resource with MKRESOURCE

   >> Request:

   MKRESOURCE /~whitehead/dav/spec08.ref HTTP/1.1
   Host: www.ics.uci.edu
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propertyupdate xmlns:D="DAV:">
     <D:set>
       <D:prop>
         <D:resourcetype><D:redirectref/></D:resourcetype>
       <D:reftarget>
         <D:href>/i-d/draft-webdav-protocol-08.txt</D:href>
       </D:reftarget>
     </D:prop>
     </D:set>
   </D:propertyupdate>

    >> Response:

   HTTP/1.1 201 Created

   This request resulted in the creation of a new redirect reference
   resource at www.ics.uci.edu/~whitehead/dav/spec08.ref, which points
   to the resource identified by the DAV:reftarget property. In this
   example, the target resource is identified by the URI http://
   www.ics.uci.edu/i-d/draft-webdav-protocol-08.txt. The redirect
   reference resource's DAV:resourcetype property is set to
   DAV:redirectref.

6. Operations on Redirect Reference Resources

   Although non-referencing-aware clients cannot create reference
   resources, they should be able to submit requests through the
   reference resources created by reference-aware WebDAV clients.  They
   should be able to follow any references to their targets.  To make
   this possible, a server that receives any request made via a redirect
   reference resource MUST return a 302 (Found) status code, unless the
   request includes an Apply-To-Redirect-Ref header. The client and
   server MUST follow [RFC2616] Section 10.3.3 "302 Found," but with
   these additional rules:

   o  The Location response header MUST contain an absolute URI that
      identifies the target  61

1. Introduction

   This is one of a pair of specifications that extend the reference resource.

   o  The response MUST include the Redirect-Ref header.  This header
      allows reference-aware WebDAV
   Distributed Authoring Protocol to enable clients to recognize the resource as
      a reference resource and understand the reason create new access
   paths to existing resources.  This capability is useful for the
      redirection.

   A reference-aware WebDAV client can act on this response in one several
   reasons:

   URIs of
   two ways.  It can, like a non-referencing client, resubmit the
   request WebDAV-compliant resources are hierarchical and correspond to the URI in the Location header
   a hierarchy of collections in order to operate on the
   target resource.  Alternatively, resource space.  The WebDAV Distributed
   Authoring Protocol makes it can resubmit the request possible to the
   URI of the redirect reference resource with the Apply-To-Redirect-Ref
   header organize these resources into
   hierarchies, placing them into groupings, known as collections, which
   are more easily browsed and manipulated than a single flat
   collection. However, hierarchies require categorization decisions
   that locate resources at a single location in order to operate on the reference hierarchy, a
   drawback when a resource itself.  If the
   Apply-To-Redirect-Ref header is present, has multiple valid categories. For example,
   in a hierarchy of vehicle descriptions containing collections for
   cars and boats, a description of a combination car/boat vehicle could
   belong in either collection. Ideally, the request MUST description should be applied
   accessible from both. Allowing clients to create new URIs that access
   the reference existing resource itself, and a 302 response MUST NOT be
   returned.

   A reference-aware client may know before submitting its request lets them put that
   the Request-URI identifies resource into multiple
   collections.

   Hierarchies also make resource sharing more difficult, since
   resources that have utility across many collections are still forced
   into a redirect reference resource. In this
   case, if single collection. For example, the client wants mathematics department at
   one university might create a collection of information on fractals
   that contains bindings to apply the method some local resources, but also provides
   access to the reference
   resource, some resources at other universities.  For many reasons, it can save
   may be undesirable to make physical copies of the round trip caused by shared resources on
   the 302 response by
   using an Apply-To-Redirect-Ref header in its initial request local server: to the
   URI.

   A few methods need additional explanation:

   The Apply-To-Redirect-Ref header can be used with GET conserve disk space, to respect copyright
   constraints, or HEAD to
   retrieve make any changes in the entity headers shared resources visible
   automatically. Being able to create new access paths to existing
   resources in other collections or even on other servers is useful for
   this sort of a case.

   The redirect reference resource.  When
   Apply-To-Redirect-Ref is used with GET or HEAD, the Redirect-Ref
   entity header MUST be returned. resources defined here provide a mechanism for
   creating alternative access paths to existing resources.  A redirect
   reference resource MAY have a body, though none is defined
   for it a resource in this specification.  The PUT method can be used, with
   Apply-To-Redirect-Ref, one collection whose purpose is
   to create or replace the body of a redirect
   reference resource.

   Since MKCOL and MKRESOURCE fail when applied forward requests to existing resources,
   if the client attempts another resource (its target), possibly in a
   different collection.  In this way, it allows clients to resubmit the request submit
   requests to the target
   resource, the request MUST fail (unless the reference resource is a
   dangling reference).  Similarly, if the client attempts to resubmit
   the request from another collection.  It
   redirects most requests to the reference target resource with an Apply-To-Redirect-Ref
   header, using the request MUST fail.

6.1 Example: GET on a Redirect Reference Resource

    >> Request:

   GET /bar.html HTTP/1.1
   Host: www.foo.com

    >> Response:

   HTTP/1.1 HTTP 302 Found
   Location: http://www.svr.com/Internet/xxspec08.html
   Redirect-Ref:

   Since /bar.html is
   (Found) status code, thereby providing a form of mediated access to
   the target resource.

   A redirect reference resource and the
   Apply-To-Redirect-Ref header is not included in the request, the
   response is a 302 (Found).  The Redirect-Ref header informs resource, and so can have properties and a
   reference-aware client that this is not an ordinary HTTP 1.1
   redirect, but is
   body of its own.  Properties of a redirect reference resource.  The URI of the
   target resource is provided in the Location header so that the client can resubmit
   contain such information as who created the reference, when, and why.

   Since redirect reference resources are implemented using HTTP 302
   responses, it generally takes two round trips to submit a request to
   the target intended resource.

6.2 Example: PUT  Servers are not required to enforce the
   integrity of redirect references.  Redirect references work equally
   well for local resources and for resources that reside on a Redirect Reference Resource with
    Apply-To-Redirect-Ref

    >> Request:

   PUT /bar.html HTTP/1.1
   Host: www.foo.com
   Apply-To-Redirect-Ref:
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   . . . some content . . .

    >> Response:

   HTTP/1.1 200 OK

   Although /bar.html different
   server from the reference.

   The remainder of this document is structured as follows: Section 3
   defines terms that will be used throughout the specification.
   Section 4 provides an overview of redirect reference resources.
   Section 5 discusses how to create a redirect reference resource, resource.
   Section 6 defines the presence semantics of
   the Apply-To-Redirect-Ref header prevents a 302 response, and instead
   causes the request existing methods when applied to be
   redirect reference resources, and Section 7 discusses their semantics
   when applied to collections that contain redirect reference
   resources. Sections 8 through 10 discuss several other issues raised
   by the existence of redirect reference resource.  The
   result in this case is that resources.  Sections 11
   through 14 define the new headers, properties, and XML elements
   required to support redirect reference resource is replaced resources.  Section 15
   discusses capability discovery.  Sections 16 through 18 present the
   security, internationalization, and IANA concerns raised by this
   specification. The remaining sections provide a
   non-reference resource having variety of supporting
   information.

2. Notational Conventions

   Since this document describes a set of extensions to the content submitted with WebDAV
   Distributed Authoring Protocol [RFC2518], itself an extension to the request.

6.3 Example: PROPPATCH on a Redirect Reference Resource

    >> Request:

   PROPPATCH /bar.html HTTP/1.1
   Host: www.foo.com
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propertyupdate xmlns:D="DAV:"
   xmlns:Z="http://www.w3.com/standards/z39.50/">
     <D:set>
       <D:prop>
         <Z:authors>
           <Z:Author>Jim Whitehead</Z:Author>
           <Z:Author>Roy Fielding</Z:Author>
         </Z:authors>
       </D:prop>
     </D:set>
     <D:remove>
       <D:prop>
         <Z:Copyright-Owner/>
       </D:prop>
     </D:remove>
   </D:propertyupdate>

    >> Response:
   HTTP/1.1 302 Found
   Location: http://www.svr.com/Internet/xxspec08.html
   Redirect-Ref:

   Since /bar.html protocol, the augmented BNF used here to describe protocol
   elements is a redirect reference resource exactly the same as described in Section 2.1 of
   [RFC2616]. Since this augmented BNF uses the basic production rules
   provided in Section 2.2 of [RFC2616], these rules apply to this
   document as well.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and the
   Apply-To-Redirect-Ref header is not included "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3. Terminology

   The terminology used here follows and extends that in the request, WebDAV
   Distributed Authoring Protocol specification [RFC2518]. Definitions
   of the
   response is a terms resource, Uniform Resource Identifier (URI), and Uniform
   Resource Locator (URL) are provided in [RFC2396].

   Redirect Reference Resource

      A resource created to redirect all requests made to it, using 302 (Found).  The Redirect-Ref header informs
      (Found), to a
   reference-aware client defined target resource.

   Non-Reference Resource

      A resource that this is not an ordinary HTTP 1.1
   redirect, but is a redirect reference to another resource.

   Target Resource

      The URI of the
   target resource is provided in the Location header so that the client
   can resubmit the request to the target which requests are forwarded by a reference
      resource.

7. Operations on Collections That Contain

4. Overview of Redirect Reference Resources

   Consistent with the rules in Section 6, the response for each
   redirect reference encountered while processing a collection MUST be
   a 302 (Found) unless a Apply-To-Redirect-Ref header is included with
   the request.  The overall response will therefore be a 207
   (Multi-Status). Since

   For all operations submitted to a Location header and Redirect-Ref header
   cannot be returned for each redirect reference encountered, the same
   information is provided using properties in resource, the
   default response elements for
   those resources.  The DAV:location pseudo-property and the
   DAV:resourcetype property MUST be included with the 302 status code.
   This necessitates an extension to the syntax of the DAV:response
   element that was defined in [RFC2518]. The extension is defined a 302 (Found), accompanied by the Redirect-Ref
   header (defined in Section 14 below.

   A referencing-aware client can tell from the DAV:resourcetype
   property that 11.1 below) and the collection contains a redirect reference resource.
   The DAV:location pseudo-property contains Location header set to
   the absolute URI of the target resource.  A referencing-aware  With this information, the client
   can either use resubmit the request to the URI
   value of the DAV:location pseudo-property target resource.

   A redirect reference resource never automatically forwards requests
   to resubmit its request to target resource. Redirect resources bring the same benefits as
   links in HTML documents. They can be created and maintained without
   the involvement or even knowledge of their target resource. This
   reduces the cost of linking between resources."

   If the client is aware that it is operating on a redirect reference
   resource, or it can submit resolve the request reference by retrieving the reference
   resource's DAV:reftarget property (defined in Section 12.1 below),
   whose value contains the URI of the target resource.  It can then
   submit requests to the target resource.

   A redirect reference resource with Apply-To-Redirect-Ref.

   It is recommended that future editors a new type of resource. To
   distinguish redirect reference resources from non-reference
   resources, a new value of [RFC2518] define the
   DAV:location pseudo-property DAV:resourcetype property (defined in [RFC2518], so that non-referencing
   clients will also be able to use the response to operate on the
   target resource.  (This will also enable clients to operate on
   traditional HTTP/1.1 302 responses
   [RFC2518]), DAV:redirectref, is defined in Multi-Status responses.) Until
   then, non- referencing clients will not be able to process 302
   responses from Section 13.1 below.

   Since a redirect reference resources encountered while
   processing resource is a collection. resource, it can have its
   own properties and body, and methods can be applied to the reference
   resource as well as to its target resource.  The
   Apply-To-Redirect-Ref request header (defined in Section 11.2) MAY be
   used with any request on a collection.  If present, it will be 11.2 below)
   is provided so that referencing-aware clients can control whether an
   operation is applied to all the redirect reference resources encountered while
   processing the collection.

7.1 MOVE and DELETE on Collections That Contain Redirect References

   DELETE removes the binding that corresponds to the Request-URI.  MOVE
   removes that binding and creates a new binding resource or to the same its
   target resource.
   In cases where DELETE and MOVE are applied  The Apply-To-Redirect-Ref header can be used with
   most requests to a collection, these
   operations affect all the descendents of the collection, but they do
   so indirectly.  There redirect reference resources.  This header is no need to visit each descendent in order
   particularly useful with PROPFIND, to
   process retrieve the request.  Consequently, even if there are redirect reference resources in
   resource's own properties.

5. Creating a tree that Redirect Reference Resource

   The MKRESOURCE method is being deleted or moved, there
   will be no 302 responses from the used to create new redirect reference
   resources.

7.2 LOCK on a Collection That Contains Redirect References

   LOCK poses special problems because it is atomic. An attempt  As defined in Section 5.1, MKRESOURCE can be used to lock
   (with Depth: infinity)
   create a collection that contains redirect references
   will always fail.  The Multi-Status response will contain resource of any type other than standard data containers and
   collections.  In order to create a 302
   response for each redirect reference.

   Reference-aware clients can lock the collection by reference resource using
   Apply-To-Redirect-Ref, and, if desired, lock
   MKRESOURCE, the values of two properties must be set in the targets body of
   the
   redirect references individually.

   Non-referencing clients must resort MKRESOURCE request.  The value of DAV:resourcetype MUST be set to locking each resource
   individually.

7.3 Example: PROPFIND on a Collection with Redirect Reference Resources

   Suppose
   DAV:redirectref, a PROPFIND request with Depth: infinity is submitted new value of DAV:resourcetype defined in Section
   13.1. The value of DAV:reftarget MUST be set to the
   following collection, with URI of the members shown here:

   http://www.svr.com/MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut

    >> Request:

   PROPFIND /MyCollection/ HTTP/1.1
   Host: www.svr.com
   Depth: infinity
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV: ">
     <D:prop xmlns:J="http://www.svr.com/jsprops/">
       <D:resourcetype/>
       <J:keywords/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="DAV:" xmlns:J="http://www.svr.com/jsprops/">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
           <J:keywords>diary, interests, hobbies</J:keywords>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype/>
           <J:keywords>diary, travel, family, history</J:keywords>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:status>HTTP/1.1 302 Found</D:status>
       <D:prop>
         <D:location>
           <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
         </D:location>
         <D:resourcetype><D:redirectref/></D:resourcetype>
       </D:prop>
     </D:response>
   </D:multistatus>

   In target
   resource.

   Used in this example way, the Depth header MKRESOURCE method creates a redirect reference
   resource whose target is set identified by the DAV:reftarget property.

5.1 MKRESOURCE

   The MKRESOURCE method requests the creation of a resource and
   initialization of its properties.  It allows resources other than
   standard data containers and collections to infinity, be created and their
   properties initialized in one atomic operation.

   Preconditions:

      A resource MUST NOT exist at the
   Apply-To-Redirect-Ref header is not used. Request-URI.

   Request Marshalling:

      The collection contains
   one URI that identifies a redirect reference resource. location of the new resource to be created is specified by the
      Request-URI.

      The response
   element for request body of the redirect reference resource has a status MKRESOURCE method MUST consist of 302
   (Found), and includes a DAV:prop the
      DAV:propertyupdate XML element with defined in Section 12.13 of
      [RFC2518].

   Postconditions:

      If the DAV:location
   pseudo-property and response status code is 201, a new resource exists at the DAV:resourcetype property to allow clients to
   retrieve
      Request-URI.

      The body of the new resource is empty.

      The properties of its target resource.  (The response
   element for the redirect reference new resource does not include are as specified by the
   requested properties.  The client can submit another PROPFIND
      DAV:propertyupdate request
   to body, using PROPPATCH semantics. If the URI in
      DAV:propertyupdate does not specify a DAV:resourcetype, the DAV:location pseudo-property to retrieve those
   properties.)

7.4 Example: PROPFIND with Apply-To-Redirect-Ref on
      resource will be a Collection with
    Redirect Reference Resources

   Suppose standard data container.

      If the response status code is not 201, then a PROPFIND request with Apply-To-Redirect-Ref and Depth =
   infinity new resource is submitted to the following collection, with not
      created at the members
   shown here:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut

    >> Request:

   PROPFIND /MyCollection/ HTTP/1.1
   Host: www.svr.com
   Depth: infinity
   Apply-To-Redirect-Ref:
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV:">
     <D:prop>
       <D:resourcetype/>
       <D:reftarget/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype/>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:redirectref/></D:resourcetype>
           <D:reftarget>
             <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
           </D:reftarget>
         </D:prop>
       <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
   </D:multistatus>

   Since Request-URI, and any existing resource at the Apply-To-Redirect-Ref header
      Request-URI is present, the unaffected.

   Response Marshalling:

      Responses from a MKRESOURCE request MUST NOT be cached, as
      MKRESOURCE has non-idempotent semantics.

      The following status codes can be expected in responses to
      MKRESOURCE:

      201 (Created): The new resource was successfully created.

      207 (Multi-Status): This response shows is generated if an error was
      encountered while initializing the properties of the redirect reference resource resource, in
      which case the collection
   rather than the properties response is as defined in Section 8.2.1 of its target.
      [RFC2518].

      403 (Forbidden): The Apply-To-Redirect-Ref
   header also prevents a 302 response from being returned for server does not allow the
   redirect reference resource.

7.5 Example: COPY on a Collection That Contains a Redirect Reference
    Resource

   Suppose a COPY request is submitted to creation of the following collection, with
      requested resource type at the members shown:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut with target
                                   /Someplace/nunavut.map

    >> Request:

   COPY /MyCollection/ HTTP/1.1
   Host: www.svr.com
   Depth: infinity
   Destination: http://www.svr.com/OtherCollection/
    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
     <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
     <D:status>HTTP/1.1 302 Found</D:status>
     <D:prop>
       <D:location>
         <D:href>http://www.svr.com//Someplace/nunavut.map</D:href>
       </D:location>
       <D:resourcetype><D:redirectref/></D:resourcetype>
     </D:prop>
     </D:response>
   </D:multistatus>

   In this case, since /MyCollection/nunavut is a redirect reference
   resource, requested location, or the COPY operation was only parent
      collection of the Request-URI exists but cannot accept members.

      409 (Conflict): A resource cannot be created at the Request-URI
      because the parent collection for the resource does not exist, or
      because there is already a partial success.  The
   redirect reference resource at that request-URL.

      423 (Locked): The Request-URI is locked, and the lock token was
      not copied, but a 302 response was
   returned for it.  So passed with the request.

      507 (Insufficient Storage): The server does not have sufficient
      space to record the resulting collection is as follows:

   /OtherCollection/
         (non-reference resource) diary.html

7.6 state of the resource.

5.2 Example: LOCK on a Collection That Contains Creating a Redirect Reference Resource

   Suppose a LOCK request is submitted to the following collection, with
   the members shown:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut MKRESOURCE

   >> Request:

   LOCK /MyCollection/

   MKRESOURCE /~whitehead/dav/spec08.ref HTTP/1.1
   Host: www.svr.com www.ics.uci.edu
   Content-Type: text/xml text/xml; charset="utf-8"
   Content-Length: nnnn
   Authorizaton: Digest username="jas",
      realm=jas@webdav.sb.aol.com, nonce=". . . ",
      uri="/MyCollection/tuva",
      response=". . . ", opaque=". . . " xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:lockinfo
   <D:propertyupdate xmlns:D="DAV:">
     <D:lockscope><D:exclusive/></D:lockscope>
     <D:locktype><D:write/></D:locktype>
     <D:owner>
       <D:href>http://www.svr.com/~jas/contact.html</D:href>
     </D:owner>
   </D:lockinfo>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: nnnn

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="Dav:">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop><D:lockdiscovery/></D:prop>
         <D:status>HTTP/1.1 424 Failed Dependency</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:status>HTTP/1.1 424 Failed Dependency</D:status>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:status>HTTP/1.1 302 Found</D:status>
     <D:set>
       <D:prop>
         <D:location>
           <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
         </D:location>
         <D:resourcetype><D:redirectref/></D:resourcetype>
       <D:reftarget>
         <D:href>/i-d/draft-webdav-protocol-08.txt</D:href>
       </D:reftarget>
     </D:prop>
     </D:response>
   </D:multistatus>

   The server returns a 302 response code for the redirect reference
   resource in the collection.  Consequently, neither the collection nor
   any of the resources identified by its internal member URIs were
   locked. A referencing-aware client can submit a separate LOCK
     </D:set>
   </D:propertyupdate>

    >> Response:

   HTTP/1.1 201 Created

   This request
   to the URI resulted in the DAV:location pseudo-property returned for the
   redirect reference resource, and can resubmit the LOCK request with
   the Apply-To-Redirect-Ref header to the collection.  At that point
   both the reference resource and its target resource will be locked
   (as well as the collection and all the resources identified by its
   other members).

8. Operations on Targets of Redirect Reference Resources

   Operations on targets creation of a new redirect reference resources have no effect
   on
   resource at www.ics.uci.edu/~whitehead/dav/spec08.ref, which points
   to the reference resource.

9. Relative URIs in DAV:reftarget

   The URI in resource identified by the href in a DAV:reftarget property MAY be a relative
   URI. property. In this case, the base URI to be used for resolving
   example, the relative
   URI to absolute form target resource is identified by the URI used in the HTTP message to identify
   the http://
   www.ics.uci.edu/i-d/draft-webdav-protocol-08.txt. The redirect
   reference resource to which the DAV:reftarget resource's DAV:resourcetype property
   belongs.

   When DAV:reftarget occurs in the body of a MKRESOURCE request, the
   base URI is constructed as follows: Its scheme component is "http",
   its authority component is the value of the Host header in the
   request, and its path component is set to
   DAV:redirectref.

6. Operations on Redirect Reference Resources

   Although non-referencing-aware clients cannot create reference
   resources, they should be able to submit requests through the Request-URI in the request.
   See Section 5 of [RFC2396] for a discussion of relative URI
   reference resources created by reference-aware WebDAV clients.  They
   should be able to follow any references and how to resolve them.

   When DAV:reftarget appears in the context of a Multi-Status response,
   it is in their targets.  To make
   this possible, a DAV:response element server that contains a single DAV:href
   element. The value of this DAV:href element serves as the base URI
   for resolving receives any request made via a relative URI in DAV:reftarget.  The value of DAV:href
   may itself be relative, in which case it must be resolved first in
   order to serve as the base URI for the relative URI in DAV:reftarget.
   If redirect
   reference resource MUST return a 302 (Found) status code, unless the DAV:href element is relative, its base
   request includes an Apply-To-Redirect-Ref header. The client and
   server MUST follow [RFC2616] Section 10.3.3 "302 Found," but with
   these additional rules:

   o  The Location response header MUST contain an absolute URI is constructed from
   the scheme component "http", that
      identifies the value target of the Host reference resource.

   o  The response MUST include the Redirect-Ref header.  This header in
      allows reference-aware WebDAV clients to recognize the
   request, resource as
      a reference resource and understand the request-URI.

9.1 Example: Resolving a Relative URI reason for the
      redirection.

   A reference-aware WebDAV client can act on this response in one of
   two ways.  It can, like a MKRESOURCE Request

    >> Request:

   MKRESOURCE /north/inuvik HTTP/1.1
   Host: www.somehost.edu
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propertyupdate xmlns:D="DAV:">
     <D:set>
       <D:prop>
         <D:resourcetype><D:redirectref/></D:resourcetype>
         <D:reftarget>
           <D:href>mapcollection/inuvik.gif</D:href>
         </D:reftarget>
       </D:prop>
     </D:set>
   </D:propertyupdate>

    >> Response:

   HTTP/1.1 201 Created

   In this example, the base URI is http://www.somehost.edu/north/
   inuvik. Then, following non-referencing client, resubmit the rules in [RFC2396] Section 5,
   request to the
   relative URI in DAV:reftarget resolves to the absolute URI http://
   www.somehost.edu/north/mapcollection/inuvik.gif.

9.2 Example: Resolving a Relative URI Location header in a Multi-Status Response

    >> Request:

   PROPFIND /geog/ HTTP/1.1
   Host: www.xxsvr.com
   Apply-To-Redirect-Ref:
   Depth: 1
   Content-Type: text/xml
   Content-Length: nnn

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV:">
     <D:prop>
       <D:resourcetype/>
       <D:reftarget/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: nnn

   <?xml version="1/0" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>/geog/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>/geog/stats.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:redirectref/></D:resourcetype>
           <D:reftarget>
             <D:href>statistics/population/1997.html</D:href>
           </D:reftarget>
         </D:prop>
       <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
   </D:multistatus>

   In this example, order to operate on the relative URI statistics/population/1997.html is
   returned as
   target resource.  Alternatively, it can resubmit the value request to the
   URI of reftarget for the redirect reference resource
   identified by href /geog/stats.html.  The href with the Apply-To-Redirect-Ref
   header in order to operate on the reference resource itself.  If the
   Apply-To-Redirect-Ref header is itself present, the request MUST be applied
   to the reference resource itself, and a relative
   URI, which resolves 302 response MUST NOT be
   returned.

   A reference-aware client may know before submitting its request that
   the Request-URI identifies a redirect reference resource. In this
   case, if the client wants to http://www.xxsrv.com/geog/stats.html.  This is apply the base URI for resolving method to the relative URI reference
   resource, it can save the round trip caused by the 302 response by
   using an Apply-To-Redirect-Ref header in reftarget. its initial request to the
   URI.

   A few methods need additional explanation:

   The
   absolute URI of reftarget is http://www.xxsrv.com/geog/statistics/
   population/1997.html.

10. Redirect References Apply-To-Redirect-Ref header can be used with GET or HEAD to Collections

   In a Request-URI /segment1/segment2/segment3, any of
   retrieve the three
   segments may identify entity headers of a redirect reference resource.  (See [RFC2396],
   Section 3.3,  When
   Apply-To-Redirect-Ref is used with GET or HEAD, the Redirect-Ref
   entity header MUST be returned.

   A redirect reference resource MAY have a body, though none is defined
   for definitions of "path" and "segment".)  If any
   segment it in this specification.  The PUT method can be used, with
   Apply-To-Redirect-Ref, to create or replace the body of a Request- URI identifies redirect
   reference resource.

6.1 Example: GET on a Redirect Reference Resource

    >> Request:

   GET /bar.html HTTP/1.1
   Host: www.foo.com

    >> Response:

   HTTP/1.1 302 Found
   Location: http://www.svr.com/Internet/xxspec08.html
   Redirect-Ref:

   Since /bar.html is a redirect reference resource,
   the response is a 302. The value of resource and the Location
   Apply-To-Redirect-Ref header is not included in the 302 request, the
   response is as follows: a 302 (Found).  The leftmost path segment of the request-URI Redirect-Ref header informs a
   reference-aware client that identifies this is not an ordinary HTTP 1.1
   redirect, but is a redirect reference resource, together with all path segments and
   separators to the left resource.  The URI of it, the
   target resource is replaced by provided in the value of Location header so that the
   redirect reference resource's DAV:reftarget property (resolved to an
   absolute URI).  The remainder of client
   can resubmit the request-URI is concatenated request to
   this path.

   Note: If the DAV:reftarget property ends target resource.

6.2 Example: PUT on a Redirect Reference Resource with
    Apply-To-Redirect-Ref

    >> Request:

   PUT /bar.html HTTP/1.1
   Host: www.foo.com
   Apply-To-Redirect-Ref:
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   . . . some content . . .

    >> Response:

   HTTP/1.1 200 OK

   Although /bar.html is a "/" and redirect reference resource, the remainder presence of
   the Request-URI is non-empty (and therefore must begin with Apply-To-Redirect-Ref header prevents a "/
   "), 302 response, and instead
   causes the final "/" request to be applied to the reference resource.  The
   result in this case is that the DAV:reftarget property reference resource is dropped before replaced by a
   non-reference resource having the
   remainder of content submitted with the Request-URI is appended.

   Consider Request-URI /x/y/z.html.  Suppose that /x/ request.

6.3 Example: PROPPATCH on a Redirect Reference Resource

    >> Request:

   PROPPATCH /bar.html HTTP/1.1
   Host: www.foo.com
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propertyupdate xmlns:D="DAV:"
   xmlns:Z="http://www.w3.com/standards/z39.50/">
     <D:set>
       <D:prop>
         <Z:authors>
           <Z:Author>Jim Whitehead</Z:Author>
           <Z:Author>Roy Fielding</Z:Author>
         </Z:authors>
       </D:prop>
     </D:set>
     <D:remove>
       <D:prop>
         <Z:Copyright-Owner/>
       </D:prop>
     </D:remove>
   </D:propertyupdate>

    >> Response:

   HTTP/1.1 302 Found
   Location: http://www.svr.com/Internet/xxspec08.html
   Redirect-Ref:

   Since /bar.html is a redirect reference resource whose target resource and the
   Apply-To-Redirect-Ref header is collection /a/, which
   contains redirect reference resource y whose target resource not included in the request, the
   response is
   collection /b/, which contains a 302 (Found).  The Redirect-Ref header informs a
   reference-aware client that this is not an ordinary HTTP 1.1
   redirect, but is a redirect reference resource z.html
   whose resource.  The URI of the
   target resource is /c/d.html.

   /x/y/z.html
       |
       | /x -> /a
       |
       v
   /a/y/z.html
       |
       | /a/y -> /b
       |
       v
   /b/z.html
       |
       | /b/z.html -> /c/d.html
       |
       v
   /c/d.html

   In this case provided in the Location header so that the client must follow up three separate 302 responses
   before finally reaching
   can resubmit the target resource.  The server responds request to the initial request target resource.

7. Operations on Collections That Contain Redirect Reference Resources

   Consistent with the rules in Section 6, the response for each
   redirect reference encountered while processing a collection MUST be
   a 302 (Found) unless a Apply-To-Redirect-Ref header is included with Location: /a/y/z.html, and
   the
   client resubmits the request to /a/y/z.html. request.  The server responds to
   this request with overall response will therefore be a 302 with Location: /b/z.html, 207
   (Multi-Status). Since a Location header and Redirect-Ref header
   cannot be returned for each redirect reference encountered, the client
   resubmits same
   information is provided using properties in the request to /b/z.html. response elements for
   those resources.  The server responds to this
   request with a 302 with Location: /c/d.html, DAV:location pseudo-property and the client resubmits
   the request to /c/d.html.  This final request succeeds.

11. Headers

11.1 Redirect-Ref Response Header

   Redirect-Ref = "Redirect-Ref:"
   DAV:resourcetype property MUST be included with the 302 status code.
   This necessitates an extension to the syntax of the DAV:response
   element that was defined in [RFC2518]. The Redirect-Ref header extension is used defined in all 302 responses
   Section 14 below.

   A referencing-aware client can tell from redirect
   reference resources.  Its presence informs reference-aware clients the DAV:resourcetype
   property that the response is not a plain HTTP/1.1 redirect, but is a response
   from collection contains a redirect reference resource.

11.2 Apply-To-Redirect-Ref Request Header

   Apply-To-Redirect-Ref = "Apply-To-Redirect-Ref" ":"
   The optional Apply-To-Redirect-Ref header DAV:location pseudo-property contains the absolute URI of the
   target resource.  A referencing-aware client can be used on any either use the URI
   value of the DAV:location pseudo-property to resubmit its request to a redirect reference resource.  When
   the target resource, or it is used, can submit the request MUST
   be applied to the redirect
   reference resource itself, and a 302 response MUST
   NOT be returned.

   If the Apply-To-Redirect-Ref header with Apply-To-Redirect-Ref.

   It is used on a request to any other
   sort recommended that future editors of resource besides a redirect reference resource, [RFC2518] define the server
   SHOULD ignore it.

12. Properties

12.1 reftarget Property

   Name: reftarget

   Namespace: DAV:

   Purpose: A property of redirect reference resources
   DAV:location pseudo-property in [RFC2518], so that provides an
      efficient way for non-referencing
   clients will also be able to discover use the URI of response to operate on the
   target resource.  This is a read-only property after its initial
      creation. Its value can only be set  (This will also enable clients to operate on
   traditional HTTP/1.1 302 responses in a MKRESOURCE request.

   Value: href containing the URI of the target resource.  This value
      MAY Multi-Status responses.) Until
   then, non-referencing clients will not be able to process 302
   responses from redirect reference resources encountered while
   processing a relative URI. collection.

   The reftarget property can occur Apply-To-Redirect-Ref header (defined in Section 11.2) MAY be
   used with any request on a collection.  If present, it will be
   applied to all redirect reference resources encountered while
   processing the
      entity bodies of MKRESOURCE requests collection.

7.1 MOVE and of responses to PROPFIND
      requests.

   <!ELEMENT reftarget href >

12.2 location Pseudo-Property

   Name: location

   Namespace: DAV:

   Purpose: For use with 302 (Found) response codes in Multi-Status
      responses.  It contains DELETE on Collections That Contain Redirect References

   DELETE removes the absolute URI of binding that corresponds to the temporary location
      of Request-URI.  MOVE
   removes that binding and creates a new binding to the same resource.
   In cases where DELETE and MOVE are applied to a collection, these
   operations affect all the context of redirect reference resources,
      this value is the absolute URI descendents of the target resource.  It collection, but they do
   so indirectly.  There is
      analogous no need to visit each descendent in order to
   process the Location header request.  Consequently, even if there are redirect
   reference resources in HTTP a tree that is being deleted or moved, there
   will be no 302 responses defined in
      [RFC2616] Section 10.3.3 "302 Found."  Including from the location
      pseudo-property in redirect reference resources.

7.2 LOCK on a Multi- Status response requires an extension Collection That Contains Redirect References

   LOCK poses special problems because it is atomic. An attempt to lock
   (with Depth: infinity) a collection that contains redirect references
   will always fail.  The Multi-Status response will contain a 302
   response for each redirect reference.

   Reference-aware clients can lock the syntax collection by using
   Apply-To-Redirect-Ref, and, if desired, lock the targets of the DAV:response element defined in [RFC2518],
      which is defined in Section 14 below.  This pseudo-property is not
      expected
   redirect references individually.

   Non-referencing clients must resort to be stored locking each resource
   individually.

7.3 Example: PROPFIND on the reference resource. It is modeled as
      a property only so that it can be returned inside a DAV:prop
      element in Collection with Redirect Reference Resources

   Suppose a Multi-Status response.

   Value: href containing the absolute URI of PROPFIND request with Depth: infinity is submitted to the target resource.

   <!ELEMENT location href >

13. XML Elements

13.1 redirectref XML Element

   Name: redirectref

   Namespace: DAV:

   Purpose: Used as
   following collection, with the value of members shown here:

   http://www.svr.com/MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut

    >> Request:

   PROPFIND /MyCollection/ HTTP/1.1
   Host: www.svr.com
   Depth: infinity
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV: ">
     <D:prop xmlns:J="http://www.svr.com/jsprops/">
       <D:resourcetype/>
       <J:keywords/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="DAV:" xmlns:J="http://www.svr.com/jsprops/">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
           <J:keywords>diary, interests, hobbies</J:keywords>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype/>
           <J:keywords>diary, travel, family, history</J:keywords>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:status>HTTP/1.1 302 Found</D:status>
       <D:prop>
         <D:location>
           <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
         </D:location>
         <D:resourcetype><D:redirectref/></D:resourcetype>
       </D:prop>
     </D:response>
   </D:multistatus>

   In this example the DAV:resourcetype property Depth header is set to
      specify that infinity, and the resource type
   Apply-To-Redirect-Ref header is not used.  The collection contains
   one URI that identifies a redirect reference resource.

   <!ELEMENT redirectref EMPTY >

14. Extensions to the DAV:response XML Element  The response
   element for Multi-Status
    Responses

   As described in Section 7, the redirect reference resource has a status of 302
   (Found), and includes a DAV:prop element with the DAV:location
   pseudo-property and the DAV:resourcetype property may be returned in the DAV:response element
   of a 207 Multi-Status response, to allow clients to resubmit their
   requests to
   retrieve the target resource properties of a redirect reference its target resource.

   Whenever these properties are included in a Multi-Status response,
   they are placed in a DAV:prop  (The response
   element associated with the href to
   which they apply.  This structure provides a framework for future
   extensions by other standards that may need to include additional
   properties in their responses.

   Consequently, the definition of redirect reference resource does not include the DAV:response XML element changes
   requested properties.  The client can submit another PROPFIND request
   to the following:

   <!ELEMENT response (href, ((href*, status, prop?) | (propstat+)),
   responsedescription?) >

15. Capability Discovery

   Sections 9.1 and 15 of [RFC2518] describe the use of compliance
   classes with the DAV header URI in responses to OPTIONS, to indicate
   which parts of the WebDAV Distributed Authoring protocols the
   resource supports. This specification defines an OPTIONAL extension DAV:location pseudo-property to [RFC2518].  It defines retrieve those
   properties.)

7.4 Example: PROPFIND with Apply-To-Redirect-Ref on a new compliance class, called
   redirectrefs, for use Collection with the DAV header in responses to OPTIONS
   requests.  If
    Redirect Reference Resources

   Suppose a resource does support redirect references, its
   response to an OPTIONS PROPFIND request may indicate that it does, by listing
   the new redirectrefs compliance class in the DAV headerand by listing
   the MKRESOURCE method as one it supports.

   When responding with Apply-To-Redirect-Ref and Depth:
   infinity is submitted to an OPTIONS request, any type of resource can
   include redirectrefs in the value of the DAV header.  Doing so
   indicates that the server permits a redirect reference resource at following collection, with the request URI.

15.1 Example: Discovery of Support for Redirect Reference Resources members
   shown here:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut

    >> Request:

   OPTIONS /somecollection/someresource

   PROPFIND /MyCollection/ HTTP/1.1
   HOST: somehost.org
   Host: www.svr.com
   Depth: infinity
   Apply-To-Redirect-Ref:
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV:">
     <D:prop>
       <D:resourcetype/>
       <D:reftarget/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: xxxx

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
         </D:prop>
         <D:status>HTTP/1.1 200 OK
   Date: Tue, 20 Jan 1998 20:52:29 GMT
   Connection: close
   Accept-Ranges: none
   Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE,
   MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, MKRESOURCE
   DAV: 1, 2, redirectrefs

   The DAV OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype/>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:redirectref/></D:resourcetype>
           <D:reftarget>
             <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
           </D:reftarget>
         </D:prop>
       <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
   </D:multistatus>

   Since the Apply-To-Redirect-Ref header in is present, the response indicates that shows
   the properties of the resource /
   somecollection/someresource is level 1 and level 2 compliant, as
   defined in [RFC2518].  In addition, /somecollection/someresource
   supports redirect reference resources.  The Allow header indicates
   that MKRESOURCE requests can be submitted to /somecollection/
   someresource. The Public header shows that other Request-URIs on resource in the
   server support additional methods.

16. Security Considerations

   This section collection
   rather than reporting a 302 status.

7.5 Example: COPY on a Collection That Contains a Redirect Reference
    Resource

   Suppose a COPY request is provided submitted to make applications that implement this
   protocol aware of the security implications of this protocol.

   All of following collection, with
   the security considerations of members shown:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut with target
                                   /Someplace/nunavut.map

    >> Request:

   COPY /MyCollection/ HTTP/1.1 and the WebDAV
   Distributed Authoring Protocol specification also apply to this
   protocol specification.
   Host: www.svr.com
   Depth: infinity
   Destination: http://www.svr.com/OtherCollection/

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
     <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
     <D:status>HTTP/1.1 302 Found</D:status>
     <D:prop>
       <D:location>
         <D:href>http://www.svr.com//Someplace/nunavut.map</D:href>
       </D:location>
       <D:resourcetype><D:redirectref/></D:resourcetype>
     </D:prop>
     </D:response>
   </D:multistatus>

   In addition, this case, since /MyCollection/nunavut is a redirect reference resources
   introduce several new security concerns and increase
   resource, the risk of some
   existing threats.  These issues are detailed below.

16.1 Privacy Concerns

   By creating COPY operation was only a partial success.  The
   redirect reference resources on resource was not copied, but a trusted server, it is
   possible 302 response was
   returned for it.  So the resulting collection is as follows:

   /OtherCollection/
         (non-reference resource) diary.html

7.6 Example: LOCK on a hostile agent to induce users to send private
   information to Collection That Contains a target on Redirect Reference
    Resource

   Suppose a different server.   This risk LOCK request is
   mitigated somewhat, since clients are required submitted to notify the user of following collection, with
   the redirection for any request other than GET or HEAD. (See
   [RFC2616], Section 10.3.3 members shown:

   /MyCollection/
        (non-reference resource) diary.html
        (redirect reference resource) nunavut

    >> Request:

   LOCK /MyCollection/ HTTP/1.1
   Host: www.svr.com
   Content-Type: text/xml
   Content-Length: nnnn
   Authorizaton: Digest username="jas",
      realm=jas@webdav.sb.aol.com, nonce=". . . ",
      uri="/MyCollection/tuva",
      response=". . . ", opaque=". . . "

   <?xml version="1.0" ?>
   <D:lockinfo xmlns:D="DAV:">
     <D:lockscope><D:exclusive/></D:lockscope>
     <D:locktype><D:write/></D:locktype>
     <D:owner>
       <D:href>http://www.svr.com/~jas/contact.html</D:href>
     </D:owner>
   </D:lockinfo>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: nnnn

   <?xml version="1.0" ?>
   <D:multistatus xmlns:D="Dav:">
     <D:response>
       <D:href>http://www.svr.com/MyCollection/</D:href>
       <D:propstat>
         <D:prop><D:lockdiscovery/></D:prop>
         <D:status>HTTP/1.1 424 Failed Dependency</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/diary.html</D:href>
       <D:status>HTTP/1.1 424 Failed Dependency</D:status>
     </D:response>
     <D:response>
       <D:href>http://www.svr.com/MyCollection/nunavut</D:href>
       <D:status>HTTP/1.1 302 Found.)

16.2 Redirect Loops

   Although Found</D:status>
       <D:prop>
         <D:location>
           <D:href>http://www.inac.gc.ca/art/inuit/</D:href>
         </D:location>
         <D:resourcetype><D:redirectref/></D:resourcetype>
       </D:prop>
     </D:response>
   </D:multistatus>

   The server returns a 302 response code for the redirect loops were already possible reference
   resource in HTTP 1.1, the
   introduction collection.  Consequently, neither the collection nor
   any of the MKRESOURCE method creates resources identified by its internal member URIs were
   locked. A referencing-aware client can submit a new avenue separate LOCK request
   to the URI in the DAV:location pseudo-property returned for
   clients the
   redirect reference resource, and can resubmit the LOCK request with
   the Apply-To-Redirect-Ref header to create loops accidentally or maliciously.  If the collection.  At that point
   both the reference resource and its target are on resource will be locked
   (as well as the same server, collection and all the server
   may be able to detect MKRESOURCE requests that would create loops.
   See also [RFC2616], Section 10.3 "Redirection 3xx."

16.3 resources identified by its
   other members).

8. Operations on Targets of Redirect Reference Resources and Denial of Service

   Denial of service attacks were already possible by posting URLs that
   were intended for limited use at heavily used Web sites.  The
   introduction of MKRESOURCE creates a new avenue for similar denial

   Operations on targets of
   service attacks.  Clients can now create redirect reference resources
   at heavily used sites to target locations that were not designed for
   heavy usage.

16.4 Revealing Private Locations

   There are several ways that redirect have no effect
   on the reference resources may reveal
   information about directory structures.  First, resource.

9. Relative URIs in DAV:reftarget

   The URI in the href in a DAV:reftarget property of every redirect reference resource contains MAY be a relative
   URI. In this case, the base URI of to be used for resolving the
   target resource.  Anyone who has access relative
   URI to absolute form is the reference resource can
   discover URI used in the directory path that leads HTTP message to identify
   the target resource.   The
   owner of the target redirect reference resource may have wanted to limit knowledge of
   this directory structure.

   Sufficiently powerful access control mechanisms can control this risk to some extent.  Property-level access control could prevent users
   from examining which the DAV:reftarget property.  (The Location header
   returned property
   belongs.

   When DAV:reftarget occurs in responses to requests on redirect reference resources
   reveals the same information, however.)  In some environments, the
   owner body of a resource might be able to use access control to prevent
   others from creating references to that resource.

   This risk is no greater than MKRESOURCE request, the similar risk posed by HTML links.

17. Internationalization Considerations

   This specification follows
   base URI is constructed as follows: Its scheme component is "http",
   its authority component is the practices value of [RFC2518] the Host header in encoding all
   human-readable content using XML [XML] the
   request, and its path component is the Request-URI in the treatment request.
   See Section 5 of names.
   Consequently, this specification complies with the IETF Character Set
   Policy [RFC2277].

   WebDAV applications MUST support the character set tagging, character
   set encoding, [RFC2396] for a discussion of relative URI
   references and how to resolve them.

   When DAV:reftarget appears in the language tagging functionality context of the XML
   specification.  This constraint ensures a Multi-Status response,
   it is in a DAV:response element that contains a single DAV:href
   element. The value of this DAV:href element serves as the human-readable
   content base URI
   for resolving a relative URI in DAV:reftarget.  The value of this specification complies with [RFC2277].

   As DAV:href
   may itself be relative, in [RFC2518], names which case it must be resolved first in this specification fall into three
   categories: names of protocol elements such
   order to serve as methods and headers,
   names of XML elements, and names of properties.  Naming of protocol
   elements follows the precedent base URI for the relative URI in DAV:reftarget.
   If the DAV:href element is relative, its base URI is constructed from
   the scheme component "http", the value of HTTP, using English names encoded the Host header in USASCII for methods the
   request, and headers.  The names of XML elements used the request-URI.

9.1 Example: Resolving a Relative URI in a MKRESOURCE Request

    >> Request:

   MKRESOURCE /north/inuvik HTTP/1.1
   Host: www.somehost.edu
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxx

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propertyupdate xmlns:D="DAV:">
     <D:set>
       <D:prop>
         <D:resourcetype><D:redirectref/></D:resourcetype>
         <D:reftarget>
           <D:href>mapcollection/inuvik.gif</D:href>
         </D:reftarget>
       </D:prop>
     </D:set>
   </D:propertyupdate>

    >> Response:

   HTTP/1.1 201 Created

   In this specification are English names encoded example, the base URI is http://www.somehost.edu/north/
   inuvik. Then, following the rules in UTF-8.

   For error reporting, [RFC2518] follows [RFC2396] Section 5, the convention of HTTP/1.1
   status codes, including with each status code a short, English
   description of
   relative URI in DAV:reftarget resolves to the code (e.g., 423 Locked).  Internationalized
   applications will ignore absolute URI http://
   www.somehost.edu/north/mapcollection/inuvik.gif.

9.2 Example: Resolving a Relative URI in a Multi-Status Response

    >> Request:

   PROPFIND /geog/ HTTP/1.1
   Host: www.xxsvr.com
   Apply-To-Redirect-Ref:
   Depth: 1
   Content-Type: text/xml
   Content-Length: nnn

   <?xml version="1.0" ?>
   <D:propfind xmlns:D="DAV:">
     <D:prop>
       <D:resourcetype/>
       <D:reftarget/>
     </D:prop>
   </D:propfind>

    >> Response:

   HTTP/1.1 207 Multi-Status
   Content-Type: text/xml
   Content-Length: nnn

   <?xml version="1/0" ?>
   <D:multistatus xmlns:D="DAV:">
     <D:response>
       <D:href>/geog/</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:collection/></D:resourcetype>
         </D:prop>
         <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
       <D:propstat>
         <D:prop><D:reftarget/></D:prop>
         <D:status>HTTP/1.1 404 Not Found</D:status>
       </D:propstat>
     </D:response>
     <D:response>
       <D:href>/geog/stats.html</D:href>
       <D:propstat>
         <D:prop>
           <D:resourcetype><D:redirectref/></D:resourcetype>
           <D:reftarget>
             <D:href>statistics/population/1997.html</D:href>
           </D:reftarget>
         </D:prop>
       <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
     </D:response>
   </D:multistatus>

   In this message, and display an appropriate
   message in example, the user's language and character set.

   This specification introduces no new strings that are displayed to
   users relative URI statistics/population/1997.html is
   returned as part of normal, error-free operation of the protocol.

   For rationales for these decisions and advice value of reftarget for application
   implementors, see [RFC2518].

18. IANA Considerations

   This document uses the namespaces defined reference resource
   identified by [RFC2518] for properties
   and XML elements.  All other IANA considerations mentioned in
   [RFC2518] also apply href /geog/stats.html.  The href is itself a relative
   URI, which resolves to this document.

19. Acknowledgements http://www.xxsrv.com/geog/stats.html.  This draft has benefited from thoughtful discussion by Jim Amsden,
   Peter Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen,
   Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand,
   Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Hunt,
   Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel
   LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra
   Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness,
   John Stracke, John Tigue, John Turner, Kevin Wiggen, and others.

Normative is
   the base URI for resolving the relative URI in reftarget.  The
   absolute URI of reftarget is http://www.xxsrv.com/geog/statistics/
   population/1997.html.

10. Redirect References

   [RFC2277]  Alvestrand, H., "IETF Policy on Character Sets and
              Languages", BCP 18, RFC 2277, January 1998.

   [RFC2119]  Bradner, S., "Key words to Collections

   In a Request-URI /segment1/segment2/segment3, any of the three
   segments may identify a redirect reference resource.  (See [RFC2396],
   Section 3.3, for use definitions of "path" and "segment".)  If any
   segment in RFCs a Request- URI identifies a redirect reference resource,
   the response is a 302. The value of the Location header in the 302
   response is as follows:

   The leftmost path segment of the request-URI that identifies a
   redirect reference resource, together with all path segments and
   separators to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2396]  Berners-Lee, T., Fielding, R. the left of it, is replaced by the value of the
   redirect reference resource's DAV:reftarget property (resolved to an
   absolute URI).  The remainder of the request-URI is concatenated to
   this path.

   Note: If the DAV:reftarget property ends with a "/" and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

   [RFC2518]  Goland, Y., Whitehead, E., Faizi, A., Carter, S. the remainder
   of the Request-URI is non-empty (and therefore must begin with a "/
   "), the final "/" in the DAV:reftarget property is dropped before the
   remainder of the Request-URI is appended.

   Consider Request-URI /x/y/z.html.  Suppose that /x/ is a redirect
   reference resource whose target resource is collection /a/, which
   contains redirect reference resource y whose target resource is
   collection /b/, which contains redirect reference resource z.html
   whose target resource is /c/d.html.

   /x/y/z.html
       |
       | /x -> /a
       |
       v
   /a/y/z.html
       |
       | /a/y -> /b
       |
       v
   /b/z.html
       |
       | /b/z.html -> /c/d.html
       |
       v
   /c/d.html

   In this case the client must follow up three separate 302 responses
   before finally reaching the target resource.  The server responds to
   the initial request with a 302 with Location: /a/y/z.html, and D.
              Jensen, "HTTP Extensions for Distributed Authoring --
              WEBDAV", RFC 2518, February 1999.

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P. the
   client resubmits the request to /a/y/z.html.  The server responds to
   this request with a 302 with Location: /b/z.html, and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

   [XML]      Bray, T., Paoli, J., Sperberg-McQueen, C. the client
   resubmits the request to /b/z.html.  The server responds to this
   request with a 302 with Location: /c/d.html, and E. Maler,
              "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C
              REC-xml, October 2000, <http://www.w3.org/TR/2000/
              REC-xml-20001006>.

Informative References

   [B]  Clemm, G., Crawford, J., Reschke, J., Slein, J. the client resubmits
   the request to /c/d.html.  This final request succeeds.

11. Headers

11.1 Redirect-Ref Response Header

   Redirect-Ref = "Redirect-Ref:"

   The Redirect-Ref header is used in all 302 responses from redirect
   reference resources.  Its presence informs reference-aware clients
   that the response is not a plain HTTP/1.1 redirect, but is a response
   from a redirect reference resource.

11.2 Apply-To-Redirect-Ref Request Header

   Apply-To-Redirect-Ref = "Apply-To-Redirect-Ref" ":"

   The optional Apply-To-Redirect-Ref header can be used on any request
   to a redirect reference resource.  When it is used, the request MUST
   be applied to the reference resource itself, and J.
        Whitehead, "Binding Extensions a 302 response MUST
   NOT be returned.

   If the Apply-To-Redirect-Ref header is used on a request to any other
   sort of resource besides a redirect reference resource, the server
   SHOULD ignore it.

12. Properties

12.1 reftarget Property

   Name: reftarget

   Namespace: DAV:

   Purpose: A property of redirect reference resources that provides an
      efficient way for clients to WebDAV", Internet Draft (work
        in progress) draft-ietf-webdav-bind-02, June 2003.

URIs

   [1]   <mailto:w3c-dist-auth@w3.org>

   [2]   <mailto:w3c-dist-auth-request@w3.org?subject=subscribe>

   [3]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [4]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [5]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [6]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [7]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [8]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [9]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0296.html>

   [10]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [11]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0191.html>

   [12]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0222.html>

   [13]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [14]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [15]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [16]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0301.html>
   [17]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [18]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [19]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [20]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [21]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [22]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0303.html>

   [23]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [24]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [25]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [26]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [27]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [28]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [29]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [30]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [31]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [32]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>
   [33]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0286.html>

   [34]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0287.html>

   [35]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [36]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [37]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0289.html>

   [38]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0285.html>

   [39]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0284.html>

   [40]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0306.html>

   [41]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0188.html>

   [42]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0288.html>

   [43]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [44]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [45]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0290.html>

   [46]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0291.html>

   [47]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0294.html>

   [48]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>
   [49]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0295.html>

   [50]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0189.html>

   [51]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0189.html>

   [52]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [53]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [54]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [55]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0292.html>

   [56]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0293.html>

   [57]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0308.html>

   [58]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0188.html>

   [59]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [60]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [61]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0297.html>

   [62]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0298.html>

   [63]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [64]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>
   [65]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [66]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0299.html>

   [67]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0302.html>

   [68]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [69]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [70]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [71]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [72]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [73]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0222.html>

   [74]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0307.html>

   [75]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [76]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0304.html>

   [77]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [78]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0304.html>

   [79]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0300.html>

   [80]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>
   [81]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [82]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [83]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [84]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [85]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [86]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0305.html>

   [87]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

Authors' Addresses

   J. Slein
   Xerox Corporation
   800 Phillips Road, 105-50C
   Webster, NY  14580

   EMail: jslein@crt.xerox.com

   Jim Whitehead
   UC Santa Cruz, Dept. discover the URI of the target
      resource.  This is a read-only property after its initial
      creation. Its value can only be set in a MKRESOURCE request.

   Value: href containing the URI of the target resource.  This value
      MAY be a relative URI.  The reftarget property can occur in the
      entity bodies of MKRESOURCE requests and of responses to PROPFIND
      requests.

   <!ELEMENT reftarget href >

12.2 location Pseudo-Property

   Name: location

   Namespace: DAV:

   Purpose: For use with 302 (Found) response codes in Multi-Status
      responses.  It contains the absolute URI of the temporary location
      of the resource.  In the context of redirect reference resources,
      this value is the absolute URI of the target resource.  It is
      analogous to the Location header in HTTP 302 responses defined in
      [RFC2616] Section 10.3.3 "302 Found."  Including the location
      pseudo-property in a Multi- Status response requires an extension
      to the syntax of the DAV:response element defined in [RFC2518],
      which is defined in Section 14 below.  This pseudo-property is not
      expected to be stored on the reference resource. It is modeled as
      a property only so that it can be returned inside a DAV:prop
      element in a Multi-Status response.

   Value: href containing the absolute URI of the target resource.

   <!ELEMENT location href >

13. XML Elements

13.1 redirectref XML Element

   Name: redirectref

   Namespace: DAV:

   Purpose: Used as the value of the DAV:resourcetype property to
      specify that the resource type is a redirect reference resource.

   <!ELEMENT redirectref EMPTY >

14. Extensions to the DAV:response XML Element for Multi-Status
    Responses

   As described in Section 7, the DAV:location pseudo-property and the
   DAV:resourcetype property may be returned in the DAV:response element
   of Computer Science
   1156 High Street
   Santa Cruz, CA  95064
   US

   EMail: ejw@cse.ucsc.edu

   J. Davis
   CourseNet Systems
   170 Capp Street
   San Francisco, CA  94110

   EMail: jrd3@alum.mit.edu
   G. Clemm
   Rational Software Corporation a 207 Multi-Status response, to allow clients to resubmit their
   requests to the target resource of a redirect reference resource.

   Whenever these properties are included in a Multi-Status response,
   they are placed in a DAV:prop element associated with the href to
   which they apply.  This structure provides a framework for future
   extensions by other standards that may need to include additional
   properties in their responses.

   Consequently, the definition of the DAV:response XML element changes
   to the following:

   <!ELEMENT response (href, ((href*, status, prop?) | (propstat+)),
   responsedescription?) >

15. Capability Discovery

   Sections 9.1 and 15 of [RFC2518] describe the use of compliance
   classes with the DAV header in responses to OPTIONS, to indicate
   which parts of the WebDAV Distributed Authoring protocols the
   resource supports. This specification defines an OPTIONAL extension
   to [RFC2518].  It defines a new compliance class, called
   redirectrefs, for use with the DAV header in responses to OPTIONS
   requests.  If a resource does support redirect references, its
   response to an OPTIONS request may indicate that it does, by listing
   the new redirectrefs compliance class in the DAV headerand by listing
   the MKRESOURCE method as one it supports.

   When responding to an OPTIONS request, any type of resource can
   include redirectrefs in the value of the DAV header.  Doing so
   indicates that the server permits a redirect reference resource at
   the request URI.

15.1 Example: Discovery of Support for Redirect Reference Resources

    >> Request:

   OPTIONS /somecollection/someresource HTTP/1.1
   HOST: somehost.org

    >> Response:

   HTTP/1.1 200 OK
   Date: Tue, 20 Maguire Road
   Lexington, MA  02173-3104

   EMail: geoffrey.clemm@us.ibm.com

   C. Fay
   FileNet Corporation
   3565 Harbor Boulevard
   Costa Mesa, CA  92626-1420

   EMail: cfay@filenet.com

   J. Crawford
   IBM Research
   P.O. Box 704
   Yorktown Heights, NY  10598

   EMail: ccjason@us.ibm.com

   Julian F. Reschke (editor)
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW  48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   EMail: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/

Appendix A. Changes Jan 1998 20:52:29 GMT
   Connection: close
   Accept-Ranges: none
   Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE,
   MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, MKRESOURCE
   DAV: 1, 2, redirectrefs

   The DAV header in the response indicates that the resource /
   somecollection/someresource is level 1 and level 2 compliant, as
   defined in [RFC2518].  In addition, /somecollection/someresource
   supports redirect reference resources.  The Allow header indicates
   that MKRESOURCE requests can be submitted to /somecollection/
   someresource. The Public header shows that other Request-URIs on the
   server support additional methods.

16. Security Considerations

   This section is provided to make applications that implement this
   protocol aware of the security implications of this protocol.

   All of the security considerations of HTTP/1.1 and the WebDAV
   Distributed Authoring Protocol specification also apply to this
   protocol specification.  In addition, redirect reference resources
   introduce several new security concerns and increase the risk of some
   existing threats.  These issues are detailed below.

16.1 Privacy Concerns

   By creating redirect reference resources on a trusted server, it is
   possible for a hostile agent to induce users to send private
   information to a target on a different server.   This risk is
   mitigated somewhat, since clients are required to notify the WebDAV Document Type Definition

   <!-- XML Elements from Section 13 -->
   <!ELEMENT redirectref EMPTY >
   <!--  -->Property Elements from user of
   the redirection for any request other than GET or HEAD. (See
   [RFC2616], Section 12 -->
   <!ELEMENT reftarget href>
   <!ELEMENT location href>
   <!-- Changes 10.3.3 302 Found.)

16.2 Redirect Loops

   Although redirect loops were already possible in HTTP 1.1, the
   introduction of the MKRESOURCE method creates a new avenue for
   clients to create loops accidentally or maliciously.  If the DAV:response Element from Section 14 -->
   <!ELEMENT response (href, ((href*, status, prop?) | (propstat+)),
   responsedescription?) >

Appendix B. Change Log

B.1 Since draft-ietf-webdav-redirectref-protocol-02

   Julian Reschke takes editorial role (added
   reference resource and its target are on the same server, the server
   may be able to authors list). Cleanup
   XML indentation. Start adding all unresolved last call issues. Update
   some author's contact information. Update references, split into
   "normative" detect MKRESOURCE requests that would create loops.
   See also [RFC2616], Section 10.3 "Redirection 3xx."

16.3 Redirect Reference Resources and "informational". Remove non-RFC2616 headers
   ("Public") from examples. Fixed width problems in artwork. Start
   resolving editorial issues.

Appendix C. Resolved issues

   Issues Denial of Service

   Denial of service attacks were already possible by posting URLs that
   were intended for limited use at heavily used Web sites.  The
   introduction of MKRESOURCE creates a new avenue for similar denial of
   service attacks.  Clients can now create redirect reference resources
   at heavily used sites to target locations that were either rejected or resolved in this version not designed for
   heavy usage.

16.4 Revealing Private Locations

   There are several ways that redirect reference resources may reveal
   information about collection structures.  First, the DAV:reftarget
   property of this
   document.

C.1 lc-11-pagination

   Type: change

   [3]

   reuterj@ira.uka.de (2000-02-07): Don't paginate every redirect reference resource contains the review draft.

   Resolution: We will paginate in accordance with IETF rules, but will
   try to produce a nicely formatted review spec as well.

C.2 lc-09-notational-after-introduction

   Type: change

   [4]

   reuterj@ira.uka.de (2000-02-07): Move Notational Conventions after
   Introduction.

   Resolution: Section will be moved.

C.3 lc-13-usually

   Type: change

   [5]

   reuterj@ira.uka.de (2000-02-07): Intro, para 4: Change "usually" URI of the
   target resource.  Anyone who has access to
   "possibly" in the sentence "A redirect reference resource is a
   resource in one can
   discover the collection whose purpose is to forward requests path that leads to
   another the target resource.   The
   owner of the target resource (its target), usually in a different collection."

   Resolution: Agreed.

C.4 lc-16-insure

   Type: change

   [6]

   reuterj@ira.uka.de (2000-02-07): Section 4, para 2: Change "It is
   also what insures" may have wanted to "It is also what helps limit knowledge of
   this collection structure.

   Sufficiently powerful access control mechanisms can control this risk
   to insure".

   Resolution: Agreed.

C.5 lc-17-location

   Type: change

   [7]

   reuterj@ira.uka.de (2000-02-07): Section 4, para 3: Clients should
   use some extent.  Property-level access control could prevent users
   from examining the DAV:reftarget property.  (The Location header, not header
   returned in responses to requests on redirect reference resources
   reveals the DAV:reftarget property, same information, however.)  In some environments, the
   owner of a resource might be able to find use access control to prevent
   others from creating references to that resource.

   This risk is no greater than the similar risk posed by HTML links.

17. Internationalization Considerations

   This specification follows the
   location practices of [RFC2518] in encoding all
   human-readable content using XML [XML] and in the target. The purpose treatment of names.
   Consequently, this specification complies with the DAV:reftarget property
   should be to let IETF Character Set
   Policy [RFC2277].

   WebDAV applications MUST support the client update its value.

   Resolution: We need both Location (which is absolute) character set tagging, character
   set encoding, and target
   (which may be relative). See also issue 6, 43.

C.6 lc-21-bind

   Type: change

   [8]

   reuterj@ira.uka.de (2000-02-07): Get rid of the binding-dependent language in the last para tagging functionality of Section 5.

   Resolution: Delete all but the first sentence in this paragraph.

C.7 lc-46-bind

   Type: change

   [9]

   yarong@Exchange.Microsoft.com (2000-02-11): Remove dependency on
   bindings from second paragraph of section 5.

   Resolution: Agreed.

C.8 lc-26-lang

   Type: edit

   [10]

   reuterj@ira.uka.de (2000-02-07): Change "is not created" to "was not
   created" in para 4 under Postconditions of MKRESOURCE.

   Resolution: Editor's discretion.

C.9 lc-03-mkresource-response-cacheability

   Type: change

   [11]

   joe@orton.demon.co.uk (2000-01-26): Saying that responses to
   MKRESOURCE SHOULD NOT be cached suggests XML
   specification.  This constraint ensures that there are sometimes
   good reasons to cache responses. Is this the case?

   Resolution: Responses to MKREF MUST NOT be cached.

C.10 lc-02-status-codes

   Type: change

   [12]

   joe@orton.demon.co.uk (2000-01-29): List only new status codes for
   MKRESOURCE. Don't discuss previously-defined status codes.

   Resolution: Follow same practice as in binding spec: for existing
   status codes, describe new circumstances that might cause them. Make
   it clear that we are not redefining these codes.

C.11 lc-27-lang

   Type: edit

   [13]

   reuterj@ira.uka.de (2000-02-07): Section 6: Change
   "non-referencing-aware clients" to "clients not aware human-readable
   content of this
   protocol".

   Resolution: Editor's discretion.

C.12 lc-30-headers

   Type: edit

   [14]

   reuterj@ira.uka.de (2000-02-07): Section 6, "When Apply-To-RR is used specification complies with GET or HEAD..." Either give a precise list [RFC2277].

   As in [RFC2518], names in this specification fall into three
   categories: names of protocol elements such as methods and headers,
   names of XML elements, and names of properties.  Naming of protocol
   elements follows the headers that
   MUST be returned, or change MUST to SHOULD with the list precedent of examples.

   Resolution: Delete "along with all HTTP headers that make sense HTTP, using English names encoded
   in USASCII for
   reference resources (for example, Cache-Control, Age, Etag, Expires, methods and Last-Modified)." See also issue 48.

C.13 lc-32-ORDERPATCH

   Type: edit

   [15]

   reuterj@ira.uka.de (2000-02-07): Section 6. Don't talk about
   ORDERPATCH, since it hasn't been specified anywhere.

   Resolution: Agreed. See also issue 48.

C.14 lc-51-repeat

   Type: change

   [16]

   yarong@Exchange.Microsoft.com (2000-02-11): headers.  The first sentence names of XML elements used
   in this paragraph says only what's clear from RFC 2518, so will cause
   confusion by its presence. Delete it. The last sentence specification are English names encoded in UTF-8.

   For error reporting, [RFC2518] follows the convention of this
   paragraph lists methods. That's a bad idea. Remove it.

   Resolution: Delete entire paragraph.

C.15 lc-59-depth

   Type: change

   [17]

   reuterj@ira.uka.de (2000-02-14): Section 7: When a method is being
   applied to a collection HTTP/1.1
   status codes, including with Depth > 0, let Apply-To-Redirect-Ref
   contain each status code a list of URIs. This way you could have it apply to some
   subset short, English
   description of the redirect references code (e.g., 423 Locked).  Internationalized
   applications will ignore this message, and display an appropriate
   message in the collection.

   Resolution: Declined. Too complex, user's language and character set.

   This specification introduces no use case for it.

C.16 lc-65-lock

   Type: change

   [18]

   reuterj@ira.uka.de (2000-02-14): "In the case of a redirect reference
   resource, I think the intended meaning of WebDAV is new strings that the resource
   itself is the internal member are displayed to be locked, not the target resource.
   In so far, I think,
   users as part of normal, error-free operation of the Apply-To-Redirect-Ref header should
   implicitly always be set, protocol.

   For rationales for these decisions and advice for application
   implementors, see [RFC2518].

18. IANA Considerations

   All IANA considerations mentioned in [RFC2518] also apply to this
   document.

19. Acknowledgements

   This draft has benefited from thoughtful discussion by Jim Amsden,
   Peter Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen,
   Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand,
   Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Hunt,
   Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel
   LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Joe Orton,
   Surendra Koduru Reddy, Juergen Reuter, Max Rible, Sam Ruby, Bradley
   Sergeant, Nick Shelness, John Stracke, John Tigue, John Turner, Kevin
   Wiggen, and a LOCK request others.

Normative References

   [RFC2277]  Alvestrand, H., "IETF Policy on Character Sets and
              Languages", BCP 18, RFC 2277, January 1998.

   [RFC2119]  Bradner, S., "Key words for a collection MUST
   fail if use in the hierarchy of collections there is an ordinary redirect
   reference as internal member."

   Resolution: Declined. Behavior will be the same RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2396]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

   [RFC2518]  Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
              Jensen, "HTTP Extensions for all methods. No
   exceptions. Consistency / simplicity override other considerations

C.17 lc-66-depth

   Type: change Distributed Authoring --
              WEBDAV", RFC 2518, February 1999.

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

   [XML]      Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
              "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C
              REC-xml, October 2000, <http://www.w3.org/TR/2000/
              REC-xml-20001006>.

   [1]   <mailto:w3c-dist-auth@w3.org>

   [2]   <mailto:w3c-dist-auth-request@w3.org?subject=subscribe>

   [3]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [4]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [5]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0286.html>

   [6]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [7]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [8]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0287.html>

   [9]   <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0188.html>

   [10]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [11]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [12]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0290.html>

   [13]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0291.html>

   [14]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0295.html>

   [15]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0188.html>

   [16]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [17]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [18]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0304.html>

   [19]

   reuterj@ira.uka.de (2000-02-14): 7.3, 7.4: Change "Depth=infinity" to
   "Depth: infinity".

   Resolution: Agreed.

C.18 lc-69-424

   Type: change  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [20]

   reuterj@ira.uka.de (2000-02-14): 7.6: Thinks there should not be 424
   returned for diary.html because it is not an ancestor of a member
   that caused the lock to fail.

   Resolution: No change needed. The interpretation of "dependency" in
   the example is correct. It doesn't have to do with ancestor
   relationship, only with what caused operation to fail.

C.19 lc-68-lock

   Type: change  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [21]

   reuterj@ira.uka.de (2000-02-14): 7.6: The LOCK example responds with
   207, as does the example in RFC 2518, but section 8.10.4  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0289.html>

   [22]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0285.html>

   [23]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0284.html>

   [24]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0306.html>

   [25]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0288.html>

   [26]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0290.html>

   [27]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0294.html>

   [28]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [29]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0189.html>

   [30]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0189.html>

   [31]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [32]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [33]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [34]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0292.html>

   [35]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0293.html>

   [36]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0308.html>

   [37]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [38]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [39]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0297.html>

   [40]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0298.html>

   [41]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [42]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0266.html>

   [43]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0299.html>

   [44]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0302.html>

   [45]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [46]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [47]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [48]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [49]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0222.html>

   [50]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0307.html>

   [51]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [52]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0304.html>

   [53]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [54]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0300.html>

   [55]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [56]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0316.html>

   [57]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [58]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [59]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0359.html>

   [60]  <http://lists.w3.org/Archives/Public/w3c-dist-auth/2000JanMar/
         0305.html>

Authors' Addresses

   J. Slein
   Xerox Corporation
   800 Phillips Road, 105-50C
   Webster, NY  14580

   EMail: jslein@crt.xerox.com

   Jim Whitehead
   UC Santa Cruz, Dept. of RFC 2518
   says if the lock cannot be granted to all resources the response MUST
   be 409 conflict.

   Resolution: We'll keep 207 and encourage RFC 2518 Computer Science
   1156 High Street
   Santa Cruz, CA  95064
   US

   EMail: ejw@cse.ucsc.edu

   J. Davis
   CourseNet Systems
   170 Capp Street
   San Francisco, CA  94110

   EMail: jrd3@alum.mit.edu

   G. Clemm
   Rational Software Corporation
   20 Maguire Road
   Lexington, MA  02173-3104

   EMail: geoffrey.clemm@us.ibm.com
   C. Fay
   FileNet Corporation
   3565 Harbor Boulevard
   Costa Mesa, CA  92626-1420

   EMail: cfay@filenet.com

   J. Crawford
   IBM Research
   P.O. Box 704
   Yorktown Heights, NY  10598

   EMail: ccjason@us.ibm.com

   Julian F. Reschke (editor)
   greenbytes GmbH
   Salzmannstrasse 152
   Muenster, NW  48159
   Germany

   Phone: +49 251 2807760
   Fax:   +49 251 2807761
   EMail: julian.reschke@greenbytes.de
   URI:   http://greenbytes.de/tech/webdav/

Appendix A. Changes to say the same.
   (This inconsistency in RFC 2518 is on the WebDAV issues list.)

C.20 lc-52-no-relative

   Type: change

   [22]

   yarong@Exchange.Microsoft.com (2000-02-11): Don't allow relative
   URIs. Delete section 9.

   Resolution: Declined. Some applications need relative URI.

C.21 lc-64-reftarget

   Type: change

   [23]

   reuterj@ira.uka.de (2000-02-14): Perhaps make DAV:location a real
   property, instead of DAV:reftarget, and require it to be an absolute
   URI.

   Resolution: Declined. Some applications need relative URI. See also
   issue 52.

C.22 lc-70-relative

   Type: change

   [24]

   reuterj@ira.uka.de (2000-02-14): Section 9, para 1: Maybe say that
   the resulting absolute URI could be any of a number of URIs,
   depending on which URI is used in the request to identify the
   redirect reference.

   Resolution: No change needed.

C.23 lc-73-asciiart

   Type: change

   [25]

   reuterj@ira.uka.de (2000-02-14): Document Type Definition

   <!-- XML Elements from Section 10: Replace the ascii art
   with Juergen's suggestion (see his message).

   Resolution: Replace.

C.24 lc-77-webdav-applications

   Type: change

   [26]

   reuterj@ira.uka.de (2000-02-22): 13 -->
   <!ELEMENT redirectref EMPTY >
   <!--  -->Property Elements from Section 16: Change "WebDAV
   applications" 12 -->
   <!ELEMENT reftarget href>
   <!ELEMENT location href>
   <!-- Changes to "applications that implement this protocol".

C.25 lc-10-title

   Type: change

   [27]

   reuterj@ira.uka.de (2000-02-07): Change the title of 16.4 so that it
   is not a sentence.

   Resolution: DAV:response Element from Section 14 -->
   <!ELEMENT response (href, ((href*, status, prop?) | (propstat+)),
   responsedescription?) >

Appendix B. Change Log (to be removed by RFC Editor before publication)

B.1 Since draft-ietf-webdav-redirectref-protocol-02

   Julian Reschke takes editorial role (added to "Revealing Private Locations".

C.26 lc-81-typo

   Type: change

   [28]

   reuterj@ira.uka.de (2000-02-22): Section 17: Typo "As authors list). Cleanup
   XML indentation. Start adding all unresolved last call issues. Update
   some author's contact information. Update references, split into
   "normative" and "informational". Remove non-RFC2616 headers
   ("Public") from examples. Fixed width problems in [WebDAV}"

   Resolution: Fixed.

C.27 lc-18-resource-types

   Type: change

   [29]

   reuterj@ira.uka.de (2000-02-07): Need a registration procedure for
   resource types to insure interoperability.

   Resolution: We won't hold up this spec artwork. Start
   resolving editorial issues.

B.2 Since draft-ietf-webdav-redirectref-protocol-03

   Added Joe Orton and Juergen Reuter to establish a registration
   procedure. We will mention in IANA considerations that as the number
   of resource types grows the need for a registration procedure
   increases, but that there is none at this time.

C.28 lc-84-ext

   Type: change
   [30]

   reuterj@ira.uka.de (2000-02-22): Appendix 24.1: This is not an
   extension but a replacement for the WebDAV definition of the response
   element.

   Resolution: Fixed. Acknowledgements section. Close
   more editorial issues. Remove dependencies on BIND spec.

Appendix D. Open C. Resolved issues

D.1 lc-85-301

   Type: change

   ejw@cse.ucsc.edu (2000-01-03): Support creation (to be removed by RFC Editor before
            publication)

   Issues that were either rejected or resolved in this version of other than 302
   redirects, especially 301.

D.2 this
   document.

C.1 lc-07-bind

   Type: change

   [31]

   [3]

   reuterj@ira.uka.de (2000-02-07): Abstract should discuss only
   redirect references, not bindings. Expand discussion of redirect
   references.

   Resolution: Abstract will discuss only redirect references. See also
   issue 34.

D.3

C.2 lc-08-bind

   Type: change

   [32]

   [4]

   reuterj@ira.uka.de (2000-02-07): Get rid of cross-references to the
   binding spec: in the abstract, in the introduction, in the definition
   of Reference Resource.

   Resolution: Cross-references to bindings will be removed. See also
   issue 34.

D.4

C.3 lc-34-bind

   Type: change

   [33]

   [5]

   yarong@Exchange.Microsoft.com (2000-02-11): NoBind: Remove all
   cross-references to the binding spec. Prefer also removing all
   mention of bindings.

   Resolution: Agreed. See also issues 7, 8, 14

D.5 lc-35-bind

   Type: change

   [34]

   yarong@Exchange.Microsoft.com (2000-02-11): ReallyNoBind: Remove
   paras. 6 and 8 from Intro. Remove all
   cross-references to the binding spec. Prefer also removing all
   mention of bindings.

   Resolution: Agreed. See also issue 14.

D.6 issues 7, 8, 14

C.4 lc-83-bind

   Type: change

   [35]
   [6]

   reuterj@ira.uka.de (2000-02-22): References: Get rid of the reference
   to the bindings spec.

D.7

   Resolution: Agreed.

C.5 lc-12-bind

   Type: change

   [36]

   [7]

   reuterj@ira.uka.de (2000-02-07): First 3 paragraphs of Introduction
   are identical to those in binding spec. Make sure that any changes
   made there are also incorporated here.

   Resolution: These paragraphs will change as necessary to make the
   redirect spec completely independent of the rest of WebDAV.

D.8 lc-38-not-hierarchical

C.6 lc-35-bind

   Type: change

   [37]

   [8]

   yarong@Exchange.Microsoft.com (2000-02-11): Not Hierarchical: The
   first sentence of ReallyNoBind: Remove
   paras. 6 and 8 from Intro.

   Resolution: Agreed. See also issue 14.

C.7 lc-01-body

   Type: change

   [9]

   joe@orton.demon.co.uk (2000-01-26): Entity Bodies for Redirect
   References: Clarify: Are there 2 resources, one that redirects and
   one that responds with its own entity body? Clarify: What is the second paragraph
   effect of PUT for a URI that currently maps to a redirect reference?

   Resolution: Redirect resource MUST NOT have a body. See also issue
   last call issue 23.

C.8 lc-14-bind

   Type: change
   [10]

   reuterj@ira.uka.de (2000-02-07): Limit the introduction discussion of bindings to
   just what is needed to understand the differences from redirect spec asserts that
   references. Maybe the URIs of WebDAV compliant resources
   match to collections. The WebDAV standard makes no such requirement.
   I therefore move paragraph in the Intro that this sentence be stricken. starts "By
   contrast, a BIND request . . ." is all that is needed.

   Resolution: State Get rid of discussion of bindings altogether. See also
   issue 34, 35.

C.9 lc-15-direct-ref

   Type: change

   [11]

   reuterj@ira.uka.de (2000-02-07): Don't define Direct Reference
   Resource, since direct references are out of scope. (If you do keep
   the more general HTTP rationale first (alternative
   names for definition, say explicitly that a direct reference resource is a
   type of reference resource.)

   Resolution: Remove definition of Direct Reference Resource. See also
   issue 39.

C.10 lc-39-no-reference-or-direct-resource

   Type: change

   [12]

   yarong@Exchange.Microsoft.com (2000-02-11):
   NoReferenceOrDirectResource: Remove the same resource), then introduce definitions of "Reference"
   and "Direct Reference Resource." Change the collection hierarchy
   rationale, which applies only if you are in definition of "Redirect
   Reference Resource" to be: Redirect Resource: A resource created to
   redirect all requests made to it, using 302 (Found), to a WebDAV-compliant space.

D.9 lc-36-server defined
   target resource.

   julian.reschke@greenbytes.de (2003-07-27): (Rename from "redirect
   reference resource" to "redirect resource" delayed for now).

   Resolution: Agreed. See also issue 15.

C.11 lc-40-direct

   Type: change

   [38]

   [13]
   yarong@Exchange.Microsoft.com (2000-02-11): Servers: Replace Assorted changes to
   Section 4, para 2 to get rid of the word "forward" and the word
   "server" and remove comparison with "unrelated system" throughout. direct references.

   Resolution: Try replacing "server" with "host" in some contexts,
   rephrasing in passive voice in others. See also issue 40.

D.10 lc-33-forwarding 33 (forward). See also issue 36 (server).
   Remove discussion of direct references.

C.12 lc-45-apply-to-rr

   Type: change

   [39]

   [14]

   yarong@Exchange.Microsoft.com (2000-02-11): Forwarding: Replace
   "forward" with "redirect" throughout.

   Resolution: Use "redirect" Suggested replacement
   text for this paragraph, which briefly introduces
   Apply-To-Redirect-Ref. Includes a note that even with this header,
   the behavior redirect resources do
   exhibit. Use "forward" response may be a 302.

   Resolution: See issue 19 for replacement text. Disagree. Redirect
   reference will never respond to Apply-To-RR with 302.

C.13 lc-01A-body

   Type: change

   [15]

   joe@orton.demon.co.uk (2000-01-26): In the contrasting behavior (passing a method definition of MKRESOURCE,
   "Body" needs to be defined or else terminology changed.

   Resolution: We will use MKREF instead of MKRESOURCE.

C.14 lc-31-MKCOL

   Type: edit

   [16]

   reuterj@ira.uka.de (2000-02-07): Section 6, para on MKRESOURCE and
   MKCOL is obvious and doesn't need to the target with no client action needed). Define these two
   terms. be stated. Maybe show in an
   example.

   Resolution: Agreed. See also issue 40.

D.11 lc-56-notjusthttp 48.

C.15 lc-67-redirectref

   Type: change

   [40]
   [17]

   reuterj@ira.uka.de (2000-02-14): 7.4: The explanation should not
   contrast displaying the properties of the redirect ref with
   displaying the properties of its target, but with returning a 302.

   Resolution: Revise as recommended.

C.16 lc-54-s10

   Type: change

   [18]

   yarong@Exchange.Microsoft.com (2000-02-11): Make it clear The Note: in examples section 10
   has the same problem pointed out in Bindings.NoSlash and text needs to be
   fixed. It contradicts RFC 2518 and 2616, which both assume that a URL
   and the redirection URI could be non-HTTP. same URL + "/" may map to different resources.

   Resolution: We agree Agreed in mailing list discussions that it no change is possible to create redirect
   references to non-HTTP resources. Add example.

D.12 lc-01-body
   needed.

C.17 lc-78-directory

   Type: change

   [41]

   joe@orton.demon.co.uk (2000-01-26): Entity Bodies

   [19]

   reuterj@ira.uka.de (2000-02-22): Section 16.4: Change "directory" to
   "collection". Not new to this protocol. Holds for Redirect
   References: Clarify: Are there 2 resources, one any protocol that redirects
   has hierarchical access paths.

C.18 lc-82-iana

   Type: change

   [20]

   reuterj@ira.uka.de (2000-02-22): Section 18: Just reference [WebDAV]
   and
   one that responds with its own entity body? Clarify: What is the
   effect of PUT for a URI that currently maps to a redirect reference? say this protocol does not introduce any new considerations.

   Resolution: Redirect resource MUST NOT have a body. See also issue
   last call Simplify, then resolve issue 23.

D.13 lc-37-integrity 55.

Appendix D. Open issues (to be removed by RFC Editor before publication)

D.1 lc-85-301

   Type: change

   [42]

   ejw@cse.ucsc.edu (2000-01-03): Support creation of other than 302
   redirects, especially 301.

D.2 lc-38-not-hierarchical

   Type: change

   [21]

   yarong@Exchange.Microsoft.com (2000-02-11): Integrity: Intro, para 7
   "Servers are not required to enforce Not Hierarchical: The
   first sentence of the integrity second paragraph of redirect
   references." Integrity is not defined. Replace with something
   clearer.

   Resolution: Rewrite to say that the server MUST NOT update introduction of the target
   See also issue 6.

D.14 lc-14-bind

   Type: change

   [43]

   reuterj@ira.uka.de (2000-02-07): Limit
   redirect spec asserts that the discussion URIs of bindings to
   just what is needed WebDAV compliant resources
   match to understand collections. The WebDAV standard makes no such requirement.
   I therefore move that this sentence be stricken.

   Resolution: State the differences from redirect
   references. Maybe more general HTTP rationale first (alternative
   names for the paragraph in same resource), then introduce the Intro that starts "By
   contrast, collection hierarchy
   rationale, which applies only if you are in a BIND request . . ." is all that is needed.

   Resolution: Get rid of discussion of bindings altogether. See also
   issue 34, 35.

D.15 lc-15-direct-ref WebDAV-compliant space.

D.3 lc-36-server

   Type: change

   [44]

   reuterj@ira.uka.de (2000-02-07): Don't define Direct Reference
   Resource, since direct references are out of scope. (If you do keep
   the definition, say explicitly that a direct reference resource is a
   type of reference resource.)

   [22]

   yarong@Exchange.Microsoft.com (2000-02-11): Servers: Replace "server"
   with "unrelated system" throughout.

   Resolution: Remove definition of Direct Reference Resource. Try replacing "server" with "host" in some contexts,
   rephrasing in passive voice in others. See also issue 39.

D.16 lc-39-no-reference-or-direct-resource 40.

D.4 lc-33-forwarding

   Type: change
   [45]

   [23]

   yarong@Exchange.Microsoft.com (2000-02-11):
   NoReferenceOrDirectResource: Remove the definitions of "Reference"
   and "Direct Reference Resource." Change Forwarding: Replace
   "forward" with "redirect" throughout.

   Resolution: Use "redirect" for the definition of "Redirect
   Reference Resource" to be: Redirect Resource: A resource created to behavior redirect all requests made to it, using 302 (Found), to resources do
   exhibit. Use "forward" for the contrasting behavior (passing a defined method
   on to the target resource.

   Resolution: Agreed. with no client action needed). Define these two
   terms. See also issue 15.

D.17 lc-40-direct 40.

D.5 lc-56-notjusthttp

   Type: change

   [46]

   [24]

   yarong@Exchange.Microsoft.com (2000-02-11): Assorted changes Make it clear in examples
   and text that the redirection URI could be non-HTTP.

   Resolution: We agree that it is possible to
   Section 4, create redirect
   references to non-HTTP resources. Add example.

D.6 lc-37-integrity

   Type: change

   [25]

   yarong@Exchange.Microsoft.com (2000-02-11): Integrity: Intro, para 2 7
   "Servers are not required to get rid of the word "forward" and enforce the word
   "server" and remove comparison integrity of redirect
   references." Integrity is not defined. Replace with direct references. something
   clearer.

   Resolution: Rewrite to say that the server MUST NOT update the target
   See also issue 33 (forward). See also issue 36 (server).
   Remove discussion 6.

D.7 3-terminology-redirectref

   Type: change

   [26]

   julian.reschke@greenbytes.de (2003-07-27): Consider global rename of direct references.

D.18
   "redirect reference resource" to "redirect resource".

D.8 lc-43-webdav

   Type: change

   [47]

   [27]

   yarong@Exchange.Microsoft.com (2000-02-11): Get rid of the
   DAV:reftarget property.

   Resolution: DAV:reftarget is readonly and is present only for
   redirect references that are also WebDAV resources. We'll also have a
   method for setting target; Redirect-Ref header (returned on all 302
   responses) will have the target as its value. See also issue 6, 17,
   50.

D.19

D.9 lc-19-direct-ref

   Type: change

   [48]

   [28]

   reuterj@ira.uka.de (2000-02-07): Section 4, para 5 and Section 6,
   para 3 discussions of the Apply-to-Redirect-Ref header make it sound
   as if we are specifying direct reference behavior.

   Resolution: Change these passages so that the contrast is between
   applying the method to the redirect reference and responding with a
   302.

D.20 lc-45-apply-to-rr

   Type: change

   [49]

   yarong@Exchange.Microsoft.com (2000-02-11): Suggested replacement
   text for this paragraph, which briefly introduces
   Apply-To-Redirect-Ref. Includes a note that even with this header,
   the response may be a 302.

   Resolution: See issue 19 for replacement text. Disagree. Redirect
   reference will never respond to Apply-To-RR with 302.

D.21

D.10 lc-04-standard-data-container

   Type: change

   [50]

   [29]

   joe@orton.demon.co.uk (2000-01-26): "Standard data container" needs
   to be defined in the context of MKRESOURCE

   Resolution: Not relevant once we switch to MKREF.

D.22

D.11 lc-05-standard-data-container

   Type: change

   [51]

   [30]

   joe@orton.demon.co.uk (2000-01-26): Inconsistency about whether a
   "standard data container" can be created with MKRESOURCE or not.

   Resolution: Not relevant once we switch to MKREF.

D.23

D.12 lc-20-intro-mkresource

   Type: change

   [52]

   [31]

   reuterj@ira.uka.de (2000-02-07): Section 5: Start with "The new
   MKRESOURCE method" to make it clear that it is being introduced for
   the first time here.

   Resolution: Say "The MKREF method defined normatively here . . ."

D.24

D.13 lc-22-coll

   Type: change

   [53]

   [32]

   reuterj@ira.uka.de (2000-02-07): Inconsistency about whether
   collections can be created with MKRESOURCE.

   Resolution: Not relevant for MKREF.

D.25

D.14 lc-25-atomic

   Type: change

   [54]

   [33]

   reuterj@ira.uka.de (2000-02-07): Is MKRESOURCE atomic as viewed by a
   client? Can another client access the new resource's properties
   before they have been fully initialized? Maybe the MKRESOURCE request
   should let the client ask for it to be atomic.

   Resolution: No longer relevant once we switch to MKREF with no
   request body.

D.26

D.15 lc-41-no-webdav

   Type: change

   [55]

   [34]

   yarong@Exchange.Microsoft.com (2000-02-11): Make redirect references
   independent of the rest of WebDAV. The creation method for redirect
   references shouldn't require an XML request body.

   Resolution: We will make redirect references independent of the rest
   of WebDAV. MKREF will not have an XML request body.

D.27

D.16 lc-42-no-webdav

   Type: change

   [56]

   [35]
   yarong@Exchange.Microsoft.com (2000-02-11): Use a creation method
   that creates only redirect references. The MKRESOURCE method hinders
   experiment because a user of a server who wishes to add support for
   the creation of a new resource type can't simply throw in another
   Apache module and allow it to provide the code for the new resource
   type. They have to find the code used for MKRESOURCE and change it to
   support the new resource type.

   Resolution: We will replace MKRESOURCE with MKREF, which creates only
   redirect reference resources.

D.28

D.17 lc-58-update

   Type: change

   [57]

   [36]

   yarong@Exchange.Microsoft.com (2000-02-11): There needs to be a way
   to update the target of a redirect reference.

   Resolution: Agreed. See also issues 6, 43.

D.29 lc-01A-body

   Type: change

   [58]

   joe@orton.demon.co.uk (2000-01-26): In the definition of MKRESOURCE,
   "Body" needs way
   to be defined or else terminology changed.

   Resolution: We will use MKREF instead update the target of MKRESOURCE.

D.30 a redirect reference.

   Resolution: Agreed. See also issues 6, 43.

D.18 lc-23-body

   Type: change

   [59]

   [37]

   reuterj@ira.uka.de (2000-02-07): Section 5.1: Get rid of the
   statement that the body of the resource is empty (PostConditions). It
   would be good if the response to GET included a response body that
   could be shown to a user by a client that doesn't do automatic
   redirection. There is a related problem in Section 6 on PUT. It is
   wrong to assume that what is PUT to a resource is what GET will
   return. In Section 6, say "A PUT with Apply-To-RR MAY contain a
   request body. The semantics of the request body is out of scope for
   this specification..." Also fix the discussion of example 6.2.

   Resolution: Redirect references cannot have bodies. GET with
   Apply-To-RR MUST fail with 403. PUT with Apply-To-RR MUST fail with
   403. See also issue 1.

D.31

D.19 lc-24-properties

   Type: change

   [60]

   [38]
   reuterj@ira.uka.de (2000-02-07): Section 5.1: Replace the sentence
   "The properties of the new resource are as specified by the
   DAV:propertyupdate request body, using PROPPATCH semantics" with the
   following: "The MKRESOURCE request MAY contain a DAV:propertyupdate
   request body to initialize resource properties. Herein, the semantics
   is the same as when sending a MKRESOURCE request without a request
   body, followed by a PROPPATCH with the DAV:propertyupdate request
   body."

   Resolution: No longer relevant once we switch to MKREF with no
   request body.

D.32

D.20 lc-47-207

   Type: change

   [61]

   [39]

   yarong@Exchange.Microsoft.com (2000-02-11): In line with his wish to
   get rid of the request message body of MKRESOURCE, 207 would not be
   an appropriate response code. The description of 409 might lead
   someone to believe that you can't create redirect references outside
   of WebDAV namespaces. Suggests a different description.

   Resolution: No longer relevant - MKREF can't get a 207 response.
   Revise to make it clear that the first condition will only occur in
   WebDAV-compliant namespaces.

D.33

D.21 lc-48-s6

   Type: change

   [62]

   [40]

   yarong@Exchange.Microsoft.com (2000-02-11): Replace all of section 6
   with just this: A redirect resource, upon receiving a request without
   an Apply-To-Redirect-Ref header, MUST respond with a 302 (Found)
   response. The 302 (Found) response MUST include a location header
   identifying the target and a Redirect-Ref header. If a redirect
   resource receives a request with an Apply-To-Redirect-Ref header then
   the redirect reference resource MUST apply the method to itself
   rather than blindly returning a 302 (Found) response.

   Resolution: Keep a summary along the lines of Yaron's proposal (don't
   use the word "blindly"). Keep the bullets detailing the headers to be
   returned. Delete the rest, including the examples. See also issue 28,
   29, 30, 31, 32.

D.34

D.22 lc-28-lang

   Type: edit

   [63]

   [41]

   reuterj@ira.uka.de (2000-02-07): Section 6: Get rid of the sentence
   "A reference-aware WebDAV client can act on this response in one of
   two ways." A client can act on the response in any way it wants.

   Resolution: Agreed. See also issue 48.

D.35

D.23 lc-29-lang

   Type: edit

   [64]

   [42]

   reuterj@ira.uka.de (2000-02-07): Section 6, para 4: Obvious, doesn't
   need to be stated. Maybe note in an example.

   Resolution: Agreed. See also issue 48.

D.36 lc-31-MKCOL

   Type: edit

   [65]

   reuterj@ira.uka.de (2000-02-07): Section 6, para on MKRESOURCE and
   MKCOL is obvious and doesn't need to be stated. Maybe show in an
   example.

   Resolution: Agreed. See also issue 48.

D.37

D.24 lc-49-put

   Type: change
   [66]

   [43]

   yarong@Exchange.Microsoft.com (2000-02-11): Remove the last sentence
   of Example 6.2, which says that PUT replaces the reference with a
   different resource.

   Resolution: No longer relevant. Deleted this example in response to
   issue 48.

D.38

D.25 lc-44-pseudo

   Type: change

   [67]

   [44]

   yarong@Exchange.Microsoft.com (2000-02-11): Instead of adding an
   optional prop XML element to the response element in 207 responses,
   define a new location XML element and a new refresource XML element.

   Resolution: Agree to define new XML elements that are not
   pseudo-properties. Disagreement about whether refresource is needed.

   See issue 61.

D.39

D.26 lc-61-pseudo

   Type: change

   [68]

   [45]

   reuterj@ira.uka.de (2000-02-14): Section 7: It doesn't make sense to
   ask future editors of RFC 2518 to define DAV:location with the
   semantics it has here. RFC 2518 should provide the information in the
   Location header somehow in multistatus responses, but not by using
   properties.

   Resolution: Define an XML element for location that is not a
   pseudo-property. We'll keep the recommendation that RFC 2518 add this
   for 302 responses. See also issue 44.

D.40

D.27 lc-60-ex

   Type: change

   [69]

   [46]

   reuterj@ira.uka.de (2000-02-14): Section 7, para 3: Make it clear
   that these are just examples of client behavior, and are not meant to
   limit the client's behavior to these options.

   Resolution: Agreed to delete this paragraph. Continue discussion of
   what information should be returned with 302 in multistatus. Just
   location? Also redirectref?

D.41

D.28 lc-62-oldclient

   Type: change

   [70]

   [47]

   reuterj@ira.uka.de (2000-02-14): Section 7: It's too strong to claim
   that non-referencing clients can't process 302 responses occurring in
   Multi-Status responses. They just have an extra round trip for each
   302.

   Resolution: Remove last sentence of the paragraph that recommends
   changes to RFC 2518.

D.42

D.29 lc-63-move
   Type: change

   [71]

   [48]

   reuterj@ira.uka.de (2000-02-14): Section 7.1: Is MOVE atomic from the
   perspective of a client? Agrees that there should be no 302s for
   member redirect references, but finds the rationale dubious.

   Resolution: Remove 7.1. Reword 7.2 to avoid concerns with "poses
   special problems" and "due to atomicity".

D.43 lc-67-redirectref

   Type: change

   [72]

   reuterj@ira.uka.de (2000-02-14): 7.4: The explanation should not
   contrast displaying the properties of the redirect ref with
   displaying the properties of its target, but with returning a 302.

   Resolution: Revise as recommended.

D.44

D.30 lc-06-reftarget-relative

   Type: change

   [73]

   [49]

   joe@orton.demon.co.uk (2000-01-29): Why does the spec talk about
   relative URIs in DAV:reftarget in MKRESOURCE requests? Is the server
   required to resolve the relative URI and store it as absolute? Is the
   server required to keep DAV:reftarget pointing to the target resource
   as the reference / target move, or is DAV:reftarget a dead property?

   Resolution: DAV:reftarget is readonly and present only on redirect
   references that are also WebDAV resources. Add a method for setting
   the target. Change definition of Redirect-Ref header so that it has
   the target as its value (comes back on all 302 responses). Server
   MUST store the target exactly as it is set. It MUST NOT resolve
   relatives to absolutes and MUST NOT update if target resource moves.
   See also issue 17, 43, 50, 57

D.45

D.31 lc-57-noautoupdate

   Type: change

   [74]

   [50]

   yarong@Exchange.Microsoft.com (2000-02-11): Add language to forbid
   servers from automatically updating redirect resources when their
   targets move.

   Resolution: Agreed. See also issue 6.

D.46

D.32 lc-71-relative

   Type: change

   [75]

   [51]
   reuterj@ira.uka.de (2000-02-14): Section 9: Base URI should be the
   Request-URI or href minus its final segment.

   Resolution: Fix this.

D.47

D.33 lc-53-s10

   Type: change

   [76]

   [52]

   yarong@Exchange.Microsoft.com (2000-02-11): The behavior described in
   this section would have a very serious impact on the efficiency of
   mapping Request-URIs to resources in HTTP request processing. Also
   specify another type of redirect resource that does not behave as in
   section 10, but instead would "expose the behavior we see today in
   various HTTP servers that allow their users to create 300 resources."
   Be sure we know what behavior will be if the redirect location is not
   an HTTP URL, but, say ftp.

   Resolution: We won't define 2 sorts of redirect references here.
   Servers SHOULD respond with 302 as described here, but if they can't
   do that, respond with 404 Not Found. (It's hard to modularize the
   behavior specified - it impacts processing Not Found cases of all
   methods, so you can't just add it to an HTTP server in a redirect ref
   module.)

D.48

D.34 lc-72-trailingslash

   Type: change

   [77]

   [53]

   reuterj@ira.uka.de (2000-02-14): Section 10: Forbid DAV:reftarget
   from ending in "/"

   Resolution: Make the note warn about the possibility of two slashes
   in a row, recommend against ending target with a slash, since that
   could result in two slashes in a row.

D.49 lc-54-s10

   Type: change

   [78]

   yarong@Exchange.Microsoft.com (2000-02-11): The Note: in section 10
   has the same problem pointed out in Bindings.NoSlash and needs to be
   fixed. It contradicts RFC 2518 and 2616, which both assume that a URL
   and the same URL + "/" may map to different resources.

   Resolution: Agreed in mailing list discussions that no change is
   needed.

D.50

D.35 lc-50-blindredirect

   Type: change

   [79]

   [54]

   yarong@Exchange.Microsoft.com (2000-02-11): Replace current language
   explaining the purpose of the Redirect-Ref header with language that
   simply states that it marks blind 302 responses from redirect
   resources. (Section 6.3, 11.1)

   Resolution: Section 6.3 was removed in response to issue 48. In 11.1,
   change the definition of the Redirect-Ref header to have the value of
   the target (relative URI) as its value. Then we don't need a method
   for retrieving the target's relative URI. Presence of the
   Redirect-Ref header lets the client know that the resource accepts
   Apply-To-RR header and the new method for updating target. Reject
   Yaron's suggested language, but make the above changes.

D.51

D.36 lc-74-terminology

   Type: change

   [80]

   [55]

   reuterj@ira.uka.de (2000-02-14): "plain HTTP/1.1 redirect" - find
   some good name for this an use it consistently

D.52

D.37 lc-75-ignore

   Type: change

   [81]

   [56]

   reuterj@ira.uka.de (2000-02-14): 11.2: "If the Apply-To-Redirect-Ref
   header is used on a request to any other sort of resource besides a
   redirect reference resource, the server SHOULD ignore it." Don't need
   to say this since HTP already says that any header that is not
   understood should be ignored.

D.53

D.38 lc-76-location

   Type: change

   [82]

   [57]

   reuterj@ira.uka.de (2000-02-22): 12.2: Make DAV:location a real
   (live) property, get rid of the DAV:reftarget property

D.54 lc-78-directory

   Type: change

   [83]

   reuterj@ira.uka.de (2000-02-22): Section 16.4: Change "directory" to
   "collection". Not new to this protocol. Holds for any protocol that
   has hierarchical access paths.

D.55

D.39 lc-79-accesscontrol

   Type: change

   [84]

   [58]

   reuterj@ira.uka.de (2000-02-22): Section 16.4: "In some environments,
   the owner of a resource might be able to use access control to
   prevent others from creating references to that resource." That would
   not be consistent with the concept of redirect references as weak
   links (e.g. think of moving a resource to a different locationo that
   is already the target of some redirection reference.

D.56

D.40 lc-80-i18n

   Type: change

   [85]

   [59]

   reuterj@ira.uka.de (2000-02-22): Section 17: Could get rid of a lot
   of this section, since this protocol extends WebDAV. Just reference
   [WebDAV].

D.57

D.41 lc-55-iana

   Type: change

   [86]

   [60]

   yarong@Exchange.Microsoft.com (2000-02-11): Expand the IANA section
   to list all methods, headers, XML elements, MIME types, URL schemes,
   etc., defined by the spec.

   Resolution: Agreed.

D.58 lc-82-iana

   Type: change

   [87]

   reuterj@ira.uka.de (2000-02-22): Section 18: Just reference [WebDAV]
   and say this protocol does not introduce any new considerations.

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.

Full Copyright Statement

   Copyright (C) The Internet Society (2003). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.