Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)
draft-murchison-webdav-prefer-09

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Kenneth Murchison 
Last updated 2016-10-14
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Independent Submission                                      K. Murchison
Internet-Draft                                                       CMU
Updates: 7240 (if approved)                             October 14, 2016
Intended status: Standards Track
Expires: April 17, 2017

    Use of the Prefer Header Field in Web Distributed Authoring and
                          Versioning (WebDAV)
                    draft-murchison-webdav-prefer-09

Abstract

   This specification defines how the HTTP Prefer header field can be
   used by a WebDAV client to request that certain behaviors be employed
   by a server while constructing a response to a request.

Editorial Note (To be removed by RFC Editor before publication)

   Please send comments to the Web Distributed Authoring and Versioning
   (WebDAV) mailing list at <mailto:w3c-dist-auth@w3.org> [1], which may
   be joined by sending a message with subject "subscribe" to
   <mailto:w3c-dist-auth-request@w3.org> [2].  This mailing list is
   archived at <http://lists.w3.org/Archives/Public/w3c-dist-auth/> [3].

Open Issues

   o  Does this draft also update the RFCs for CalDAV, CardDAV, and
      those documenting the effected HTTP methods?

   o  Should we explitcly mention that this draft applies to any/all
      *DAV protocols (e.g.  CalDAV and CardDAV)?  Would a title change
      be in order?

   o  Should we use a non-protocol-specific REPORT example such as
      DAV:sync-collection rather than using CalDAV:calendar-multiget?

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Murchison                Expires April 17, 2017                 [Page 1]
Internet-Draft              Prefer in WebDAV                October 2016

   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."

   This Internet-Draft will expire on April 17, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Reducing WebDAV Response Verbosity with
       "return=minimal"  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Minimal PROPFIND Response . . . . . . . . . . . . . . . .   4
     2.2.  Minimal REPORT Response . . . . . . . . . . . . . . . . .   4
     2.3.  Minimal PROPPATCH Response  . . . . . . . . . . . . . . .   4
     2.4.  Minimal MKCALENDAR / MKCOL Response . . . . . . . . . . .   5
   3.  Reducing WebDAV Round-Trips with
       "return=representation" . . . . . . . . . . . . . . . . . . .   5
   4.  The "depth-noroot" Processing Preference  . . . . . . . . . .   6
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
     9.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   Appendix A.  The Brief and Extended Depth Request Header Fields .  11
   Appendix B.  Examples . . . . . . . . . . . . . . . . . . . . . .  12
     B.1.  PROPFIND  . . . . . . . . . . . . . . . . . . . . . . . .  12
     B.2.  REPORT  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     B.3.  PROPPATCH . . . . . . . . . . . . . . . . . . . . . . . .  20

Murchison                Expires April 17, 2017                 [Page 2]
Internet-Draft              Prefer in WebDAV                October 2016

     B.4.  MKCOL . . . . . . . . . . . . . . . . . . . . . . . . . .  22
Show full document text